Ubuntu
kdialog package

kdialog crashed with SIGABRT in qt_message_fatal()

Bug #1960949 reported by Erich Eickmeyer on 2022-02-15

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	kdialog (Ubuntu)	New	Medium	Unassigned

Bug Description

This seems to occur if kdialog is run by a script on the GNOME desktop. I understand that it's not meant to run on GNOME, but it seems silly that this bug exists in this way?

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: kdialog 4:21.12.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12
Uname: Linux 5.15.0-18-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Feb 15 10:03:35 2022
ExecutablePath: /usr/bin/kdialog
InstallationDate: Installed on 2021-08-19 (180 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210818)
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
XDG_RUNTIME_DIR=<set>
PATH=(custom, no user)
Signal: 6
SourcePackage: kdialog
StacktraceTop:
QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
QGuiApplicationPrivate::createPlatformIntegration() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
QGuiApplicationPrivate::createEventDispatcher() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
QCoreApplicationPrivate::init() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
QGuiApplicationPrivate::init() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
Title: kdialog crashed with SIGABRT in QMessageLogger::fatal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

Tags:

Revision history for this message

Erich Eickmeyer (eeickmeyer) wrote on 2022-02-15:

#1

Dependencies.txt Edit (9.8 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.1 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (122.0 KiB, text/plain; charset="utf-8")
ProcCmdline.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (77.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Registers.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Stacktrace.txt Edit (3.9 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (4.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2022-02-15:

#2

StacktraceTop:
qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
QMessageLogger::fatal (this=this@entry=0x7ffc10dcd870, msg=msg@entry=0x7ff3b304b505 "%s") at global/qlogging.cpp:893
init_platform (argv=<optimized out>, argc=@0x7ffc10dcdb4c: 3, platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...) at kernel/qguiapplication.cpp:1254
QGuiApplicationPrivate::createPlatformIntegration (this=0x55e118bab7f0) at kernel/qguiapplication.cpp:1481
QGuiApplicationPrivate::createEventDispatcher (this=<optimized out>) at kernel/qguiapplication.cpp:1498

tags:

removed: need-amd64-retrace

Revision history for this message

Apport retracing service (apport) wrote on 2022-02-16: Stacktrace.txt

#4

Stacktrace.txt Edit (11.1 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2022-02-16: StacktraceSource.txt

#5

StacktraceSource.txt Edit (2.8 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2022-02-16: ThreadStacktrace.txt

#6

ThreadStacktrace.txt Edit (11.2 KiB, text/plain)

Changed in kdialog (Ubuntu):
importance:	Undecided → Medium
summary:	- kdialog crashed with SIGABRT in QMessageLogger::fatal() + kdialog crashed with SIGABRT in qt_message_fatal()

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.