Bug 1701481

Summary: [abrt] plasma-drkonqi: qt_message_fatal(): drkonqi killed by SIGABRT
Product: [Fedora] Fedora Reporter: lonelywoolf
Component: plasma-drkonqiAssignee: Martin Kyral <mkyral>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: achinovnikov, a.thiaville, bdm, edwardp, fedora, flydove, heri, juha.heljoranta, julius.schwartzenberg, kde-sig, linuxhippy, maglckbugz+illa, matt.fagnani, mkyral, oliver, ozeszty+rhbz, vindicators
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/dfc886cfb5ca9857aa5448a8dae656251281231a
Whiteboard: abrt_hash:aefffa7e231100f69f5695c51f495e8b082a1b7d;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-25 15:00:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description lonelywoolf 2019-04-19 08:06:49 UTC 
Version-Release number of selected component:
plasma-drkonqi-5.15.4-1.fc30

Additional info:
reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/libexec/drkonqi -platform xcb -display :0 --appname telegram-desktop --apppath /usr/bin --signal 11 --pid 4456 --startupid 0
crash_function: qt_message_fatal
executable:     /usr/libexec/drkonqi
journald_cursor: s=6e0043f3f735439aa59244fb04bf5969;i=14704;b=328e522eda5a4e4c80e8982d68f676cb;m=468de4b6;t=586cf74abaa7a;x=a19b3a0df52454fc
kernel:         5.0.7-300.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (8 frames)
 #2 qt_message_fatal at global/qlogging.cpp:1901
 #3 QMessageLogger::fatal at global/qlogging.cpp:887
 #4 init_platform at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:208
 #5 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1384
 #6 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1401
 #7 QCoreApplicationPrivate::init at kernel/qcoreapplication.cpp:857
 #8 QGuiApplicationPrivate::init at kernel/qguiapplication.cpp:1430
 #9 QApplicationPrivate::init at kernel/qapplication.cpp:566

Potential duplicate: bug 1641701
Comment 1 lonelywoolf 2019-04-19 08:06:54 UTC 
Created attachment 1556361 [details]
File: backtrace
Comment 2 lonelywoolf 2019-04-19 08:06:56 UTC 
Created attachment 1556362 [details]
File: cgroup
Comment 3 lonelywoolf 2019-04-19 08:06:58 UTC 
Created attachment 1556363 [details]
File: core_backtrace
Comment 4 lonelywoolf 2019-04-19 08:07:00 UTC 
Created attachment 1556364 [details]
File: cpuinfo
Comment 5 lonelywoolf 2019-04-19 08:07:03 UTC 
Created attachment 1556365 [details]
File: dso_list
Comment 6 lonelywoolf 2019-04-19 08:07:04 UTC 
Created attachment 1556366 [details]
File: environ
Comment 7 lonelywoolf 2019-04-19 08:07:06 UTC 
Created attachment 1556367 [details]
File: limits
Comment 8 lonelywoolf 2019-04-19 08:07:09 UTC 
Created attachment 1556368 [details]
File: maps
Comment 9 lonelywoolf 2019-04-19 08:07:12 UTC 
Created attachment 1556369 [details]
File: mountinfo
Comment 10 lonelywoolf 2019-04-19 08:07:13 UTC 
Created attachment 1556370 [details]
File: open_fds
Comment 11 lonelywoolf 2019-04-19 08:07:14 UTC 
Created attachment 1556371 [details]
File: proc_pid_status
Comment 12 ozeszty 2019-04-23 13:27:57 UTC 
Similar problem has been detected:

Happned after tryng to switch user (from Application menu) and clicking on 'Start new session'.
After that sddm allows to login to different profile, but previous session (user's I switched from) is no longer available.

reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/libexec/drkonqi -platform xcb -display :0 --appname kwalletd5 --apppath /usr/bin --signal 11 --pid 1010 --startupid 0
crash_function: qt_message_fatal
executable:     /usr/libexec/drkonqi
journald_cursor: s=3b4792021f4a40e5b1758b0cc6bc868d;i=490ad;b=0df91e00963b4ef7b354f6148f997361;m=6060fc7;t=58731fe079df0;x=f1aaf09273d59ed6
kernel:         5.0.7-300.fc30.x86_64
package:        plasma-drkonqi-5.15.4-1.fc30
reason:         drkonqi killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 13 Dennis Schridde 2019-06-04 04:46:49 UTC 
*** Bug 1716752 has been marked as a duplicate of this bug. ***
Comment 14 Matt Fagnani 2019-06-09 01:39:46 UTC 
Similar problem has been detected:

These 2 crashes happened when I logged out of Plasma 5.15.5 in F30 to sddm. The drkonqi crashes seemed to be because drkonqi was running after the Wayland compositor connection had broken based on the following journal messages.

Jun 08 20:34:26 drkonqi[12664]: Failed to create wl_display (No such file or directory)
Jun 08 20:34:26 drkonqi[12664]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Jun 08 20:34:26 audit[12664]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=9 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=12664 comm="drkonqi" exe="/usr/libexec/drkonqi" sig=6 res=1
Jun 08 20:34:26 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@1-12669-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
...
Jun 08 20:34:26 drkonqi[12664]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
                                
                                Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Jun 08 20:34:26 systemd[1]: Started Process Core Dump (PID 12669/UID 0).

Segmentation faults in /usr/libexec/org_kde_kwin_xclipboard_syncer appeared to be the reason for drkonqi being run according to coredumpctl info and gnome-abrt due to the command line
/usr/libexec/drkonqi -platform xcb -display :1 --appname org_kde_kwin_xclipboard_syncer --apppath /usr/libexec --signal 11 --pid 1408 --startupid 0

I'll try to find out more about those crashes.

reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/libexec/drkonqi -platform xcb -display :1 --appname org_kde_kwin_xclipboard_syncer --apppath /usr/libexec --signal 11 --pid 1408 --startupid 0
crash_function: qt_message_fatal
executable:     /usr/libexec/drkonqi
journald_cursor: s=c8604fe939df427387254aded2bb6f94;i=575a;b=ee49ce1b884f4e87bdc098e34171ea72;m=336bbd18;t=58ad0e263530a;x=c7ef47a2a192e999
kernel:         5.1.7-300.fc30.x86_64
package:        plasma-drkonqi-5.15.5-1.fc30
reason:         drkonqi killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 15 edward 2019-07-05 18:24:19 UTC 
Similar problem has been detected:

Logged in via KDE Plasma, crash appeared.

reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/libexec/drkonqi --appname kdeinit5 --kdeinit --apppath /usr/bin --signal 11 --pid 2116 --startupid 0
crash_function: qt_message_fatal
executable:     /usr/libexec/drkonqi
journald_cursor: s=7f5c1c38a7264a889612e4c452a023f1;i=2ce5f;b=7490119f96b84a4aaaf4a8b5cb249402;m=751efc97;t=58c00ca2e6a39;x=704e88ac43c3862
kernel:         5.1.12-300.fc30.x86_64
package:        plasma-drkonqi-5.15.5-1.fc30
reason:         drkonqi killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 16 edward 2020-01-07 02:59:17 UTC 
Similar problem has been detected:

Attempted to login to KDP Plasma desktop, it apparently crashed and brought me back to the desktop manager login screen.

reporter:       libreport-2.11.3
backtrace_rating: 4
cmdline:        /usr/libexec/drkonqi -platform xcb -display :0 --appname ksplashqml --apppath /usr/bin --signal 11 --pid 1229 --startupid 0
crash_function: qt_message_fatal
executable:     /usr/libexec/drkonqi
journald_cursor: s=3bca3ecdd52e49e38799a77a77acc911;i=1d5b;b=0dd12ca3d80b4a66b132f3e2c8ae572c;m=6e1b55f;t=59b454fa16b1a;x=8518f914a8430130
kernel:         5.3.16-200.fc30.x86_64
package:        plasma-drkonqi-5.15.5-1.fc30
reason:         drkonqi killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors:
Comment 17 Ben Cotton 2020-04-30 20:34:42 UTC 
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 18 Christian Stadelmann 2020-05-24 17:03:53 UTC 
*** Bug 1833750 has been marked as a duplicate of this bug. ***
Comment 19 Christian Stadelmann 2020-05-24 17:05:44 UTC 
I see this crash (bug #1833750) when logging out of a GNOME/Wayland session with KDE/Qt applications (KDE Connect, Telegram flatpak, QuiteRSS) running.
Comment 20 Clemens Eisserer 2020-09-26 11:17:48 UTC 
Similar problem has been detected:

crash while logging out & in again

reporter:       libreport-2.13.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-1.scope
cmdline:        /usr/libexec/drkonqi -platform xcb -display :0 --appname plasmashell --apppath /usr/bin --signal 11 --pid 1478 --appversion 5.18.5 --programname Plasma --bugaddress submit.org --startupid 0 --restarted
crash_function: qt_message_fatal
executable:     /usr/libexec/drkonqi
journald_cursor: s=e2705a46cc0b414aadc1f0478aa7e8dd;i=e7e4;b=2ff9f34dd34c4326bb2da8669abedf94;m=16c86f7d;t=5b0353dd8ca49;x=ee8de49d4674fcf7
kernel:         5.8.10-200.fc32.x86_64
package:        plasma-drkonqi-5.18.5-1.fc32
reason:         drkonqi killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors:
Comment 21 Clemens Eisserer 2020-09-30 06:27:12 UTC 
Similar problem has been detected:

crash after logging out and in again

reporter:       libreport-2.13.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-1.scope
cmdline:        /usr/libexec/drkonqi -platform xcb -display :0 --appname plasmashell --apppath /usr/bin --signal 11 --pid 1702 --appversion 5.18.5 --programname Plasma --bugaddress submit.org --startupid 0 --restarted
crash_function: qt_message_fatal
executable:     /usr/libexec/drkonqi
journald_cursor: s=e2705a46cc0b414aadc1f0478aa7e8dd;i=169ea;b=786191e483534d558a3877e49256402c;m=34b1ec3;t=5b06d869d93d4;x=3610f344194e5fa4
kernel:         5.8.11-200.fc32.x86_64
package:        plasma-drkonqi-5.18.5-1.fc32
reason:         drkonqi killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors:
Comment 22 Clemens Eisserer 2020-10-05 06:31:04 UTC 
Similar problem has been detected:

crash after logging out & in again

reporter:       libreport-2.13.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-1.scope
cmdline:        /usr/libexec/drkonqi -platform xcb -display :0 --appname drkonqi --apppath /usr/libexec --signal 11 --pid 6259 --appversion 5.18.5 --programname Die KDE-Absturzbehandlung --bugaddress submit.org --startupid 0
crash_function: qt_message_fatal
executable:     /usr/libexec/drkonqi
journald_cursor: s=d88fa8f9833243a4b371e4ca1af12c40;i=28c2d;b=4a55eb1f229e46dbb75ba620b9fe0345;m=d8eae53;t=5b0e6734dc728;x=74ca070899dcf36a
kernel:         5.8.12-200.fc32.x86_64
package:        plasma-drkonqi-5.18.5-1.fc32
reason:         drkonqi killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors: KCrash: Attempting to start /usr/libexec/drkonqi
Comment 23 Clemens Eisserer 2020-10-14 06:28:37 UTC 
Similar problem has been detected:

crash after logging out and in

reporter:       libreport-2.13.1
backtrace_rating: 4
cmdline:        /usr/libexec/drkonqi -platform xcb -display :0 --appname drkonqi --apppath /usr/libexec --signal 11 --pid 3213 --appversion 5.18.5 --programname Die KDE-Absturzbehandlung --bugaddress submit.org --startupid 0
crash_function: qt_message_fatal
executable:     /usr/libexec/drkonqi
journald_cursor: s=3082743f83264931a888eb75a82e37eb;i=fdc5;b=e96af643f7b64c7a82b4e631d6462b2a;m=555675a;t=5b19b645abba5;x=4d52ea18daa83ad0
kernel:         5.8.13-200.fc32.x86_64
package:        plasma-drkonqi-5.18.5-1.fc32
reason:         drkonqi killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors:
Comment 24 Clemens Eisserer 2020-10-17 19:06:47 UTC 
Similar problem has been detected:

crash after logging out & in again

reporter:       libreport-2.13.1
backtrace_rating: 4
cmdline:        /usr/libexec/drkonqi -platform xcb -display :0 --appname plasmashell --apppath /usr/bin --signal 11 --pid 2535 --appversion 5.18.5 --programname Plasma --bugaddress submit.org --startupid 0 --restarted
crash_function: qt_message_fatal
executable:     /usr/libexec/drkonqi
journald_cursor: s=1b203182fe114599a44daca0023b5035;i=6f2b;b=b0a1f7b84a8f4ba0a13e17ed80b6f974;m=40ff5a9;t=5b1e28c2a1602;x=d3b6d3db43f6852b
kernel:         5.8.15-201.fc32.x86_64
package:        plasma-drkonqi-5.18.5-1.fc32
reason:         drkonqi killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors:
Comment 25 FlyDove 2020-11-23 02:04:03 UTC 
*** Bug 1900440 has been marked as a duplicate of this bug. ***
Comment 26 maglckbugz+illa 2020-12-10 21:16:29 UTC 
Similar problem has been detected:

Fresh install of Fedora 32 KDE, did typical post-install routine, restarted, did more post-install setup, and restarted again, this time to a crash in plasma-drkonqi.

If it could be helpful, I can provide a list of everything that was done before each restart, but I noticed this is detected as a duplicate, so I won't bother for now.

reporter:       libreport-2.13.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/dbus\x2d:1.2\x2dorg.kde.kdeconnect.slice/dbus-:1.2-org.kde.kdeconnect
cmdline:        /usr/libexec/drkonqi -platform xcb -display :0 --appname kdeconnectd --apppath /usr/libexec --signal 11 --pid 8094 --startupid 0
crash_function: qt_message_fatal
executable:     /usr/libexec/drkonqi
journald_cursor: s=82545f1cae7040f0814d680800dbeff1;i=29c3;b=2ddf421c44dc4ef0bddcccc5aaa22c7b;m=6c8bf061;t=5b62262587ab8;x=a9d5a7493682261a
kernel:         5.9.12-100.fc32.x86_64
package:        plasma-drkonqi-5.18.5-1.fc32
reason:         drkonqi killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors:
Comment 27 Fedora Program Management 2021-04-29 15:55:29 UTC 
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 28 Ben Cotton 2021-05-25 15:00:44 UTC 
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.