Fedora Account System
Red Hat Associate
Red Hat Customer
Version-Release number of selected component: plasma-drkonqi-6.3.5-1.fc42 Additional info: reporter: libreport-2.17.15 type: CCpp reason: drkonqi killed by SIGABRT journald_cursor: s=86397f013cbe45429ca20265d77a4898;i=39b39e;b=d6585eedeaf044fdba240dff08835c6e;m=2fd72be3;t=635328637ca97;x=8b8d5ad9dbf05350 executable: /usr/libexec/drkonqi cmdline: /usr/libexec/drkonqi --platform xcb --kdeframeworksversion 6.14.0 --qtversion 6.9.0 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/drkonqi-coredump-launcher rootdir: / uid: 1000 kernel: 6.14.6-300.fc42.x86_64 package: plasma-drkonqi-6.3.5-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort Truncated backtrace: Thread no. 1 (11 frames) #4 qAbort at /usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/corelib/global/qassert.cpp:46 #5 qt_message_fatal<QString&> at /usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/corelib/global/qlogging.cpp:2122 #6 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) at /usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/corelib/global/qlogging.cpp:381 #7 QMessageLogger::fatal at /usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/corelib/global/qlogging.cpp:883 #8 init_platform at /usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1345 #9 QGuiApplicationPrivate::createPlatformIntegration at /usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1598 #10 QGuiApplicationPrivate::createEventDispatcher at /usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1617 #11 QCoreApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/corelib/kernel/qcoreapplication.cpp:866 #12 QGuiApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1645 #13 QApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/widgets/kernel/qapplication.cpp:474 #14 QApplication::QApplication at /usr/src/debug/qt6-qtbase-6.9.0-2.fc42.x86_64/src/widgets/kernel/qapplication.cpp:462 Potential duplicate: bug 2260740
Created attachment 2090011 [details] File: proc_pid_status
Created attachment 2090012 [details] File: maps
Created attachment 2090013 [details] File: limits
Created attachment 2090014 [details] File: environ
Created attachment 2090015 [details] File: open_fds
Created attachment 2090016 [details] File: mountinfo
Created attachment 2090017 [details] File: os_info
Created attachment 2090018 [details] File: cpuinfo
Created attachment 2090019 [details] File: core_backtrace
Created attachment 2090020 [details] File: dso_list
Created attachment 2090021 [details] File: var_log_messages
Created attachment 2090022 [details] File: backtrace
System was being used normally with a lot of apps open. I started copying a large file over a NFS share. Then everything froze and my desktop session was killed couple of minutes after. A lot of programs crashed before session ended. reporter: libreport-2.17.15 type: CCpp reason: drkonqi killed by SIGABRT journald_cursor: s=cac21689ca51480c92b73ea17c1b8e66;i=246111e;b=d038938070794e289faa077261753f24;m=7d14ea1c19;t=636ea8872ec93;x=24c9e9dba54ffa3a executable: /usr/libexec/drkonqi cmdline: /usr/libexec/drkonqi --bugaddress submit.org --kdeframeworksversion 6.14.0 --programname KWrite --appname kwrite --signal 11 --apppath /usr/bin --platform wayland --pid 270822 --appversion 25.04.1 --qtversion 6.9.0 --productname kate/kwrite cgroup: 0::/user.slice/user-1000.slice/user/app.slice/drkonqi-coredump-launcher rootdir: / uid: 1000 kernel: 6.14.8-300.fc42.x86_64 package: plasma-drkonqi-6.3.5-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort comment: System was being used normally with a lot of apps open. I started copying a large file over a NFS share. Then everything froze and my desktop session was killed couple of minutes after. A lot of programs crashed before session ended.
Trying to get nvidia to correctly suspend or power down when accessed from a docker container. reporter: libreport-2.17.15 type: CCpp reason: drkonqi killed by SIGABRT journald_cursor: s=a5bd1c8796894f62996dc186bd7f464a;i=34257c;b=ec453d63154e4ffebd9205b94a4fd07d;m=189b94a5d;t=638f9f920017c;x=1519cd830cdf4241 executable: /usr/libexec/drkonqi cmdline: /usr/libexec/drkonqi --appversion 25.04.2 --qtversion 6.9.1 --bugaddress submit.org --appname konsole --apppath /usr/bin --pid 6719 --signal 11 --programname Konsole --kdeframeworksversion 6.15.0 --platform wayland cgroup: 0::/user.slice/user-1000.slice/user/app.slice/drkonqi-coredump-launcher rootdir: / uid: 1000 kernel: 6.15.4-200.fc42.x86_64 package: plasma-drkonqi-6.4.1-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort comment: Trying to get nvidia to correctly suspend or power down when accessed from a docker container.
Very soon after reporting https://bugzilla.redhat.com/show_bug.cgi?id=2376516, `plasmashell` indefinitely hung. I left it for 20s, then invoked `qdbus org.kde.Shutdown /Shutdown org.kde.Shutdown.logout`. reporter: libreport-2.17.15 type: CCpp reason: drkonqi killed by SIGABRT journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=80e14f;b=883863934c534a93ac2e371b83550dbf;m=1cba07b7b;t=63930f069c7b2;x=924ddcd4627818cd executable: /usr/libexec/drkonqi cmdline: /usr/libexec/drkonqi --programname "" --kdeframeworksversion 6.15.0 --apppath /usr/bin --appname plasmashell --qtversion 6.9.1 --appversion 6.4.1 --signal 6 --bugaddress submit.org --pid 46533 --platform wayland cgroup: 0::/user.slice/user-1000.slice/user/app.slice/drkonqi-coredump-launcher rootdir: / uid: 1000 kernel: 6.15.4-200.fc42.x86_64 package: plasma-drkonqi-6.4.1-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort comment: Very soon after reporting https://bugzilla.redhat.com/show_bug.cgi?id=2376516, `plasmashell` indefinitely hung. I left it for 20s, then invoked `qdbus org.kde.Shutdown /Shutdown org.kde.Shutdown.logout`.
Per https://bugzilla.redhat.com/show_bug.cgi?id=2378661#c0, I invoked this application from an SSH client on postmarketOS. The cause of the problem appears to be that $DISPLAY is unset. It solely appears to affect Qt-based applications (not merely KDE Frameworks-based ones). However, it doesn't affect all, for VLC copes fine. (Likewise, the GTK3-based Chromium and Inkscape cope.) reporter: libreport-2.17.15 type: CCpp reason: drkonqi-coredump-gui killed by SIGABRT journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=864c76;b=9a2a7e1fe91e4e5bb9e946b734c27a2b;m=1f0e05f45;t=6396dcafb0dcd;x=8d185a73aa0da793 executable: /usr/bin/drkonqi-coredump-gui cmdline: drkonqi-coredump-gui cgroup: 0::/user.slice/user-1000.slice/session-4.scope rootdir: / uid: 1000 kernel: 6.15.4-200.fc42.x86_64 package: plasma-drkonqi-6.4.2-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort comment: Per https://bugzilla.redhat.com/show_bug.cgi?id=2378661#c0, I invoked this application from an SSH client on postmarketOS. The cause of the problem appears to be that $DISPLAY is unset. It solely appears to affect Qt-based applications (not merely KDE Frameworks-based ones). However, it doesn't affect all, for VLC copes fine. (Likewise, the GTK3-based Chromium and Inkscape cope.)
I presume that Dr. Konqi appeared when, during https://bugzilla.redhat.com/show_bug.cgi?id=2375067#c14, I was informed that the shell had hanged. Unfortunately, the DE killing it, although caused Dr. Konqi to invoke, also removed the last stuck process, so it must have killed Konqi the moment it invoked. reporter: libreport-2.17.15 type: CCpp reason: drkonqi killed by SIGABRT journald_cursor: s=a2d6d580caa24cf3a9483be7f85033e4;i=19c1b6;b=83e7f3b54f684b5497d57f99d2815a01;m=75c08a18c;t=63a772c942d04;x=620fd71888ba3cfe executable: /usr/libexec/drkonqi cmdline: /usr/libexec/drkonqi --appversion 6.4.3 --platform wayland --bugaddress submit.org --apppath /usr/bin --pid 2931 --qtversion 6.9.1 --signal 6 --kdeframeworksversion 6.16.0 --appname plasmashell --programname cgroup: 0::/user.slice/user-1000.slice/user/app.slice/drkonqi-coredump-launcher rootdir: / uid: 1000 kernel: 6.15.6-200.fc42.x86_64 package: plasma-drkonqi-6.4.3-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort comment: I presume that Dr. Konqi appeared when, during https://bugzilla.redhat.com/show_bug.cgi?id=2375067#c14, I was informed that the shell had hanged. Unfortunately, the DE killing it, although caused Dr. Konqi to invoke, also removed the last stuck process, so it must have killed Konqi the moment it invoked.
See https://bugzilla.redhat.com/show_bug.cgi?id=2397085#c0: I was using https://steamdb.info/sub/221245/history/?changeid=23464127 with gamescope -W 2560 -H 1440 --hdr-enabled --adaptive-sync -f --force-grab-cursor -- %command%, which uses `gamescope-3.16.15-1.fc42.x86_64`. Thereafter, I `qdbus-qt6 org.kde.LogoutPrompt /LogoutPrompt org.kde.LogoutPrompt.promptLogout`'d. reporter: libreport-2.17.15 type: CCpp reason: drkonqi killed by SIGABRT journald_cursor: s=46bb43f1faea498db084fdfcb024f166;i=a3d8e5;b=91c985056dfe48e5b3d3b4f14836d53c;m=3ca224685;t=63f3b6f0a4efb;x=1468748a9fd1ad77 executable: /usr/libexec/drkonqi cmdline: /usr/libexec/drkonqi --appname kwin_wayland --apppath /usr/bin --signal 6 --pid 2278 --programname KWin --bugaddress submit.org --appversion 6.4.4 --platform wayland --kdeframeworksversion 6.17.0 --qtversion 6.9.2 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/drkonqi-coredump-launcher rootdir: / uid: 1000 kernel: 6.16.7-200.fc42.x86_64 package: plasma-drkonqi-6.4.4-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort comment: See https://bugzilla.redhat.com/show_bug.cgi?id=2397085#c0: I was using https://steamdb.info/sub/221245/history/?changeid=23464127 with gamescope -W 2560 -H 1440 --hdr-enabled --adaptive-sync -f --force-grab-cursor -- %command%, which uses `gamescope-3.16.15-1.fc42.x86_64`. Thereafter, I `qdbus-qt6 org.kde.LogoutPrompt /LogoutPrompt org.kde.LogoutPrompt.promptLogout`'d.
Did login/logout of desktop reporter: libreport-2.17.15 type: CCpp reason: drkonqi killed by SIGABRT journald_cursor: s=810dbc90bd414d3ab2b64ac1d2703724;i=1fff16;b=5fde58f9cccd40d5b7de114137064559;m=499571c6;t=649d9851ffaee;x=79fcbf8d965e6f44 executable: /usr/libexec/drkonqi cmdline: /usr/libexec/drkonqi --kdeframeworksversion 6.22.0 --qtversion 6.9.3 --platform xcb --programname $'KDE Wallet Service' --pid 3374 --signal 11 --apppath /usr/bin --display :0 --appversion 6.22.0 --bugaddress submit.org --appname ksecretd cgroup: 0::/user.slice/user-1000.slice/user/app.slice/drkonqi-coredump-launcher rootdir: / uid: 1000 kernel: 6.18.8-100.fc42.x86_64 package: plasma-drkonqi-6.5.5-1.fc42 runlevel: N 5 xsession_errors: backtrace_rating: 4 crash_function: qAbort comment: Did login/logout of desktop
This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13. 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 'version' of '42'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 42 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27. Fedora Linux 42 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.