Fedora Account System
Red Hat Associate
Red Hat Customer
Version-Release number of selected component: plasma-workspace-5.92.0-6.fc40 Additional info: reporter: libreport-2.17.11 type: CCpp reason: plasmashell killed by SIGABRT journald_cursor: s=5968396066e146cdb6bb722b2ae5ec9b;i=1efcf;b=8732e1fbb2604876936b81db3fd8f30a;m=2705b8df;t=6104ad851372a;x=6b057cf13f35ea2e executable: /usr/bin/plasmashell cmdline: /usr/bin/plasmashell --no-respawn cgroup: 0::/user.slice/user-1000.slice/user/session.slice/plasma-plasmashell.service rootdir: / uid: 1000 kernel: 6.8.0-0.rc0.20240112git70d201a40823.5.fc40.x86_64 package: plasma-workspace-5.92.0-6.fc40 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.6.1-4.fc40.x86_64/src/corelib/global/qglobal.cpp:161 #5 qt_message_fatal<QString&> at /usr/src/debug/qt6-qtbase-6.6.1-4.fc40.x86_64/src/corelib/global/qlogging.cpp:2003 #6 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) at /usr/src/debug/qt6-qtbase-6.6.1-4.fc40.x86_64/src/corelib/global/qlogging.cpp:378 #7 QMessageLogger::fatal at /usr/src/debug/qt6-qtbase-6.6.1-4.fc40.x86_64/src/corelib/global/qlogging.cpp:901 #8 init_platform at /usr/src/debug/qt6-qtbase-6.6.1-4.fc40.x86_64/src/gui/kernel/qguiapplication.cpp:1284 #9 QGuiApplicationPrivate::createPlatformIntegration at /usr/src/debug/qt6-qtbase-6.6.1-4.fc40.x86_64/src/gui/kernel/qguiapplication.cpp:1532 #10 QGuiApplicationPrivate::createEventDispatcher at /usr/src/debug/qt6-qtbase-6.6.1-4.fc40.x86_64/src/gui/kernel/qguiapplication.cpp:1551 #11 QCoreApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.6.1-4.fc40.x86_64/src/corelib/kernel/qcoreapplication.cpp:900 #12 QGuiApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.6.1-4.fc40.x86_64/src/gui/kernel/qguiapplication.cpp:1579 #13 QApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.6.1-4.fc40.x86_64/src/widgets/kernel/qapplication.cpp:473 #14 QApplication::QApplication at /usr/src/debug/qt6-qtbase-6.6.1-4.fc40.x86_64/src/widgets/kernel/qapplication.cpp:461
Created attachment 2014286 [details] File: proc_pid_status
Created attachment 2014287 [details] File: maps
Created attachment 2014288 [details] File: limits
Created attachment 2014289 [details] File: environ
Created attachment 2014290 [details] File: open_fds
Created attachment 2014291 [details] File: mountinfo
Created attachment 2014292 [details] File: os_info
Created attachment 2014293 [details] File: cpuinfo
the crash happens immediately upon logging into KDE via SDDM Login reporter: libreport-2.17.15 kernel: 6.14.0-0.rc1.15.fc42.x86_64 crash_function: qAbort cmdline: /usr/bin/ksplashqml reason: ksplashqml killed by SIGABRT backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/background.slice/plasma-ksplash.service executable: /usr/bin/ksplashqml type: CCpp runlevel: N 5 package: plasma-workspace-6.2.90-2.fc42 rootdir: / uid: 1000 comment: the crash happens immediately upon logging into KDE via SDDM Login xsession_errors: journald_cursor: s=430a6c72371940eaa4ec325ce8ac98aa;i=c4b8c;b=b6dff8eda85848f9a0f94254267bf6ae;m=25697e84e;t=62d6d6114c6c3;x=684fa454b95e7977
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42.
After an update the system was able to boot. After the login the screen freezes and is black. After some research I could start KDE manually from Terminal (ctrl +alt + f2) via /usr/bin/startplasma-wayland reporter: libreport-2.17.15 type: CCpp reason: plasmashell killed by SIGABRT journald_cursor: s=e04ec49e30e747338b6218a4b6acf4af;i=1e287;b=f56ddb89af374bdbb4bc25d5bc20c434;m=4176bf1a;t=6366b87c865b9;x=91fb1cd4d46c6dd0 executable: /usr/bin/plasmashell cmdline: plasmashell cgroup: 0::/user.slice/user-1000.slice/user/tmux-spawn-5d523e0a-7674-49b5-b8d9-de8eb8b57829.scope rootdir: / uid: 1000 kernel: 6.14.8-300.fc42.x86_64 package: plasma-workspace-6.3.5-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort
I hava connected/disconnected my Dell dock thunderbolt with 3 screen connected. Screen on my laptop has stuck. My computer is only usable on ssh reporter: libreport-2.17.15 type: CCpp reason: xembedsniproxy killed by SIGABRT journald_cursor: s=2f2903e839b04099aebe0e67e67ac2ee;i=57fd58;b=5bcecb1f30574807964c8e43eadbec2a;m=1ff9f7129b;t=6366c61e6e32b;x=60432720cb4adf86 executable: /usr/bin/xembedsniproxy cmdline: /usr/bin/xembedsniproxy cgroup: 0::/user.slice/user-1333.slice/user/background.slice/plasma-xembedsniproxy.service rootdir: / uid: 1333 kernel: 6.14.8-300.fc42.x86_64 package: plasma-workspace-6.3.5-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort
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: gmenudbusmenuproxy killed by SIGABRT journald_cursor: s=cac21689ca51480c92b73ea17c1b8e66;i=246100d;b=d038938070794e289faa077261753f24;m=7d14d41d2d;t=636ea885ceda7;x=7b2ec02c082e0a9f executable: /usr/bin/gmenudbusmenuproxy cmdline: /usr/bin/gmenudbusmenuproxy cgroup: 0::/user.slice/user-1000.slice/user/background.slice/plasma-gmenudbusmenuproxy.service rootdir: / uid: 1000 kernel: 6.14.8-300.fc42.x86_64 package: plasma-workspace-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.
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: ksplashqml killed by SIGABRT journald_cursor: s=cac21689ca51480c92b73ea17c1b8e66;i=246132b;b=d038938070794e289faa077261753f24;m=7d1ac34a0f;t=636ea8e4c1a89;x=211fdff4f0fa36ac executable: /usr/bin/ksplashqml cmdline: /usr/bin/ksplashqml cgroup: 0::/user.slice/user-1000.slice/user/background.slice/plasma-ksplash.service rootdir: / uid: 1000 kernel: 6.14.8-300.fc42.x86_64 package: plasma-workspace-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.
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: plasmashell killed by SIGABRT journald_cursor: s=cac21689ca51480c92b73ea17c1b8e66;i=2460f4c;b=d038938070794e289faa077261753f24;m=7d14d082c6;t=636ea8859533f;x=a777ac0a5e8c0435 executable: /usr/bin/plasmashell cmdline: /usr/bin/plasmashell --no-respawn cgroup: 0::/user.slice/user-1000.slice/user/session.slice/plasma-plasmashell.service rootdir: / uid: 1000 kernel: 6.14.8-300.fc42.x86_64 package: plasma-workspace-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.
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: xembedsniproxy killed by SIGABRT journald_cursor: s=cac21689ca51480c92b73ea17c1b8e66;i=2460d48;b=d038938070794e289faa077261753f24;m=7d14c17063;t=636ea884a40dc;x=c089fcdd146a15b executable: /usr/bin/xembedsniproxy cmdline: /usr/bin/xembedsniproxy cgroup: 0::/user.slice/user-1000.slice/user/background.slice/plasma-xembedsniproxy.service rootdir: / uid: 1000 kernel: 6.14.8-300.fc42.x86_64 package: plasma-workspace-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.
After updating via KDE Discover offline, with it set to automatically reboot, I came back once it had applied, and saw that somehow, the SDDm wallpaper was rendering the "Fedora" logogram with a Qt form slightly off-screen. Upon logging in, I saw that an enormous amount of Plasma software had crashed. reporter: libreport-2.17.15 type: CCpp reason: ksmserver killed by SIGABRT journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=75261a;b=e1bb6ff6b37548a6950c299e12a68ac0;m=4e57190;t=63850e969cd74;x=8fd53474f0bd4cf3 executable: /usr/bin/ksmserver cmdline: /usr/bin/ksmserver cgroup: 0::/user.slice/user-1000.slice/user/session.slice/plasma-ksmserver.service rootdir: / uid: 1000 kernel: 6.15.3-200.fc42.x86_64 package: plasma-workspace-6.4.0-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort comment: After updating via KDE Discover offline, with it set to automatically reboot, I came back once it had applied, and saw that somehow, the SDDm wallpaper was rendering the "Fedora" logogram with a Qt form slightly off-screen. Upon logging in, I saw that an enormous amount of Plasma software had crashed.
Like https://bugzilla.redhat.com/show_bug.cgi?id=2262196#c17 explains, after updating via KDE Discover offline, with it set to automatically reboot, I came back once it had applied, and saw that somehow, the SDDm wallpaper was rendering the "Fedora" logogram with a Qt form slightly off-screen. Upon logging in, I saw that an enormous amount of Plasma software had crashed. reporter: libreport-2.17.15 type: CCpp reason: plasmashell killed by SIGABRT journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=75287d;b=e1bb6ff6b37548a6950c299e12a68ac0;m=4ef68b1;t=63850e973c495;x=e5f04a0c6034c58d executable: /usr/bin/plasmashell cmdline: /usr/bin/plasmashell --no-respawn cgroup: 0::/user.slice/user-1000.slice/user/session.slice/plasma-plasmashell.service rootdir: / uid: 1000 kernel: 6.15.3-200.fc42.x86_64 package: plasma-workspace-6.4.0-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort comment: Like https://bugzilla.redhat.com/show_bug.cgi?id=2262196#c17 explains, after updating via KDE Discover offline, with it set to automatically reboot, I came back once it had applied, and saw that somehow, the SDDm wallpaper was rendering the "Fedora" logogram with a Qt form slightly off-screen. Upon logging in, I saw that an enormous amount of Plasma software had crashed.
Like https://bugzilla.redhat.com/show_bug.cgi?id=2262196#c18 explains, after updating via KDE Discover offline, with it set to automatically reboot, I came back once it had applied, and saw that somehow, the SDDm wallpaper was rendering the "Fedora" logogram with a Qt form slightly off-screen. Upon logging in, I saw that an enormous amount of Plasma software had crashed. reporter: libreport-2.17.15 type: CCpp reason: kcminit killed by SIGABRT journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=7525eb;b=e1bb6ff6b37548a6950c299e12a68ac0;m=4e26fd0;t=63850e966cbb3;x=c6ff438455a16f16 executable: /usr/bin/kcminit cmdline: /usr/bin/kcminit_startup cgroup: 0::/user.slice/user-1000.slice/user/session.slice/plasma-kcminit.service rootdir: / uid: 1000 kernel: 6.15.3-200.fc42.x86_64 package: plasma-workspace-6.4.0-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort comment: Like https://bugzilla.redhat.com/show_bug.cgi?id=2262196#c18 explains, after updating via KDE Discover offline, with it set to automatically reboot, I came back once it had applied, and saw that somehow, the SDDm wallpaper was rendering the "Fedora" logogram with a Qt form slightly off-screen. Upon logging in, I saw that an enormous amount of Plasma software had crashed.
Like https://bugzilla.redhat.com/show_bug.cgi?id=2374575#c0 explains, after updating via KDE Discover offline, with it set to automatically reboot, I came back once it had applied, and saw that somehow, the SDDm wallpaper was rendering the "Fedora" logogram with a Qt form slightly off-screen. Upon logging in, I saw that an enormous amount of Plasma software had crashed. reporter: libreport-2.17.15 type: CCpp reason: gmenudbusmenuproxy killed by SIGABRT journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=7527fe;b=e1bb6ff6b37548a6950c299e12a68ac0;m=4ee6334;t=63850e972bf18;x=d6e42e30243ff49 executable: /usr/bin/gmenudbusmenuproxy cmdline: /usr/bin/gmenudbusmenuproxy cgroup: 0::/user.slice/user-1000.slice/user/background.slice/plasma-gmenudbusmenuproxy.service rootdir: / uid: 1000 kernel: 6.15.3-200.fc42.x86_64 package: plasma-workspace-6.4.0-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort comment: Like https://bugzilla.redhat.com/show_bug.cgi?id=2374575#c0 explains, after updating via KDE Discover offline, with it set to automatically reboot, I came back once it had applied, and saw that somehow, the SDDm wallpaper was rendering the "Fedora" logogram with a Qt form slightly off-screen. Upon logging in, I saw that an enormous amount of Plasma software had crashed.
Like https://bugzilla.redhat.com/show_bug.cgi?id=2374575#c0 explains, after updating via KDE Discover offline, with it set to automatically reboot, I came back once it had applied, and saw that somehow, the SDDm wallpaper was rendering the "Fedora" logogram with a Qt form slightly off-screen. Upon logging in, I saw that an enormous amount of Plasma software had crashed. reporter: libreport-2.17.15 type: CCpp reason: xembedsniproxy killed by SIGABRT journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=7528e3;b=e1bb6ff6b37548a6950c299e12a68ac0;m=4f0c138;t=63850e9751d1c;x=d37d34f5c606169a executable: /usr/bin/xembedsniproxy cmdline: /usr/bin/xembedsniproxy cgroup: 0::/user.slice/user-1000.slice/user/background.slice/plasma-xembedsniproxy.service rootdir: / uid: 1000 kernel: 6.15.3-200.fc42.x86_64 package: plasma-workspace-6.4.0-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort comment: Like https://bugzilla.redhat.com/show_bug.cgi?id=2374575#c0 explains, after updating via KDE Discover offline, with it set to automatically reboot, I came back once it had applied, and saw that somehow, the SDDm wallpaper was rendering the "Fedora" logogram with a Qt form slightly off-screen. Upon logging in, I saw that an enormous amount of Plasma software had crashed.
Like https://bugzilla.redhat.com/show_bug.cgi?id=2374575#c0 explains, after updating via KDE Discover offline, with it set to automatically reboot, I came back once it had applied, and saw that somehow, the SDDm wallpaper was rendering the "Fedora" logogram with a Qt form slightly off-screen. Upon logging in, I saw that an enormous amount of Plasma software had crashed. reporter: libreport-2.17.15 type: CCpp reason: plasma-fallback-session-restore killed by SIGABRT journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=75285d;b=e1bb6ff6b37548a6950c299e12a68ac0;m=4ef3a35;t=63850e9739619;x=ec3473c5c82abe86 executable: /usr/libexec/plasma-fallback-session-restore cmdline: /usr/libexec/plasma-fallback-session-restore cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.plasma\x2dfallback\x2dsession\x2drestore rootdir: / uid: 1000 kernel: 6.15.3-200.fc42.x86_64 package: plasma-workspace-6.4.0-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort comment: Like https://bugzilla.redhat.com/show_bug.cgi?id=2374575#c0 explains, after updating via KDE Discover offline, with it set to automatically reboot, I came back once it had applied, and saw that somehow, the SDDm wallpaper was rendering the "Fedora" logogram with a Qt form slightly off-screen. Upon logging in, I saw that an enormous amount of Plasma software had crashed.
kwin_wayland crashed after connected DELL Dock with no external screen connected. reporter: libreport-2.17.15 type: CCpp reason: gmenudbusmenuproxy killed by SIGABRT journald_cursor: s=2f2903e839b04099aebe0e67e67ac2ee;i=5d9935;b=72e583e1fc1247e2b6263258e8a1d04f;m=10b1109a37;t=6384fca014c92;x=c23b677d3b19857b executable: /usr/bin/gmenudbusmenuproxy cmdline: /usr/bin/gmenudbusmenuproxy cgroup: 0::/user.slice/user-1333.slice/user/background.slice/plasma-gmenudbusmenuproxy.service rootdir: / uid: 1333 kernel: 6.14.11-300.fc42.x86_64 package: plasma-workspace-6.4.0-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort comment: kwin_wayland crashed after connected DELL Dock with no external screen connected.
Occurred on login when https://bugzilla.redhat.com/show_bug.cgi?id=2394108#c0 did. reporter: libreport-2.17.15 type: CCpp reason: ksplashqml killed by SIGABRT journald_cursor: s=46bb43f1faea498db084fdfcb024f166;i=a0b0c2;b=98e3b152a7bf44f68bab22c2540853fa;m=1b4b72a01;t=63e60cf744104;x=a4cbbefc7c03033 executable: /usr/bin/ksplashqml cmdline: /usr/bin/ksplashqml cgroup: 0::/user.slice/user-1000.slice/user/background.slice/plasma-ksplash.service rootdir: / uid: 1000 kernel: 6.16.5-200.fc42.x86_64 package: plasma-workspace-6.4.4-3.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort comment: Occurred on login when https://bugzilla.redhat.com/show_bug.cgi?id=2394108#c0 did.
logged out and logged back in (autologin enabled) reporter: libreport-2.17.15 type: CCpp reason: ksplashqml killed by SIGABRT journald_cursor: s=5a3c09978ddf48d79ba4380dc9e4ee13;i=38c4a44;b=6422f804c68a4c259fbfc6e4d0a4db4f;m=18d05b9d;t=6412a7461aac6;x=7e4e5bc941fe7344 executable: /usr/bin/ksplashqml cmdline: /usr/bin/ksplashqml cgroup: 0::/user.slice/user-1000.slice/user/background.slice/plasma-ksplash.service rootdir: / uid: 1000 kernel: 6.16.11-200.fc42.x86_64 package: plasma-workspace-6.4.5-2.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: qAbort comment: logged out and logged back in (autologin enabled)
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.