Application: plasmashell (6.3.0) ApplicationNotResponding [ANR]: false Qt Version: 6.8.2 Frameworks Version: 6.10.0 Operating System: Linux 6.12.11-200.fc41.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora Linux 41 (KDE Plasma)" DrKonqi: 6.3.0 [CoredumpBackend] -- Information about the crash: I searched for the "Switch User" menu entry because it isn't listed by default in Kicker's favourites section. When I selected it, a window appeared momentarily, before the shell crashed. Immediately, Dr Konqi appeared. 15s afterward, when it had restarted, I saw a notification that GNOME Abrt had caught it too, and I shall share the URI to its logs when they become available (it's slower to process them than Konqi is). The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #6 0x00007faa44e80183 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78 #7 0x00007faa44e26f9e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x00007faa44e0e942 in __GI_abort () at abort.c:79 #9 0x00007faa4541b91b in qAbort () at /usr/src/debug/qt6-qtbase-6.8.2-2.fc41.x86_64/src/corelib/global/qassert.cpp:49 Reported using DrKonqi
Created attachment 178332 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
(In reply to Roke Julian Lockhart Beedell from comment #0) > I saw a notification that GNOME Abrt had caught it too, and I shall share the URI to its logs when they become available (it's slower to process them than Konqi is). https://bugzilla.redhat.com/show_bug.cgi?id=2325351#c15 is my filing. It appears to have already been reported, which means that although you've got Sentry data, perhaps take a look at their counterpart, too.
(In reply to Roke Julian Lockhart Beedell from comment #0) > The reporter is unsure if this crash is reproducible. I can't report another tonight to demonstrate due to how long debuginfod takes, but I can confirm that it is consistently reproducible. Perhaps relevantly, when switching to the superuser account, I am unable to run `plasmashell`. I see: > QThreadStorage: Thread 0x555a97ea31f0 exited after QThreadStorage {random single-digit integer} destroyed
(In reply to Roke Julian Lockhart Beedell from comment #3) > I can confirm that it is consistently reproducible. After logging out and back in, it no longer reproduces.
I tried to switch the user (even though I'm the only user) just for testing on Debian 13 (unstable repository) with Plasma 6.3.0 and while at first had success as after showing that systemd process log it got me to the login screen preselecting my users and waiting for me to just type my password and enter... After I typed my password and pressed Enter, everything froze and keyboard became unresponsive, including CTRL+ALT+F3, so I had to do a forced reboot from the power button. This problem seems to be the same or very similar with what I've seen with Plasma's beta on KDE Neon as there trying to switch the single user also froze everything. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.10.0 Qt Version: 6.7.2 Kernel Version: 6.12.13-amd64 (64-bit) Graphics Platform: Wayland HARDWARE SPECIFICATIONS Hardware: Laptop Dell Inspiron 5770 (17" 1080p@60Hz screen) CPU: Intel® Core™ i5-8250U CPU @ 1.60GHz GPU 1: Mesa Intel® UHD Graphics 620 (main) GPU 2: AMD Radeon R5 M465 Series RAM: 8 GiB (7.7 GiB usable)
*** Bug 500205 has been marked as a duplicate of this bug. ***
*** Bug 500208 has been marked as a duplicate of this bug. ***
(In reply to Roke Julian Lockhart Beedell from comment #6) Ensure that you don't attempt to switch users if you experience this bug. If the window appears without crashing, you can. If it crashes, don't try to outrun it. (In reply to Roke Julian Lockhart Beedell from comment #7) This doesn't reproduce, so it appears to indicate that the cause is seriously inconsistent. As an example, I have another report that'll be marked as duplicate next which occurs solely in Kicker, but not KRunner!
*** Bug 500209 has been marked as a duplicate of this bug. ***
Should be fixed by https://invent.kde.org/plasma/plasma-workspace/-/commit/1d188e6c285d90c98fdfcbb9b4ab9a1a7334a519, which will be in Plasma 6.4.0.
(In reply to Nate Graham from comment #10) Thank you!
*** Bug 502082 has been marked as a duplicate of this bug. ***
Created attachment 182389 [details] A Demonstration That It Remains In 6.4.0 (In reply to Nate Graham from comment #10) This is marked as a duplicate of https://bugs.kde.org/show_bug.cgi?id=502082#c9, yet it reproduces in 6.4.0: > ~~~ > Operating System: Fedora Linux 42 > KDE Plasma Version: 6.4.0 > KDE Frameworks Version: 6.15.0 > Qt Version: 6.9.1 > Kernel Version: 6.14.11-300.fc42.x86_64 (64-bit) > Graphics Platform: Wayland > Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor > Memory: 32 GiB of RAM (30.4 GiB usable) > Graphics Processor 1: AMD Radeon RX 5700 > Graphics Processor 2: AMD Radeon Graphics > Manufacturer: ASRock > Product Name: X670E Taichi > ~~~ There's nothing of relevance in `journalctl -b -1 -e`: it's mere VS Code log-spam, which is abruptly truncated. I see no events of L1 or 2 with `-p`, and `L3` is filled with irrelevant stack traces for Spectacle due to https://bugs.kde.org/show_bug.cgi?id=505784.
Created attachment 185337 [details] The Output Of `journalctl -b 4265a16e070f49258b97f84afbf6b600` I'll reopen this because https://bugs.kde.org/show_bug.cgi?id=502082#c12 (which is marked as a duplicate of this) still reproduces in 6.4.5. I've attached a log from `journalctl -b 2fc6f8861545419d92b780b7672433e3 > 2fc6f8861545419d92b780b7672433e3.log`, which was a boot which solely reproduced this problem (during which I was forced to utilise SysRq's REI, after which I rebooted via SDDM's GUI). You may want to remove any logs pertaining to https://gitlab.freedesktop.org/drm/amd/-/issues/3248#note_3111855 and https://gitlab.freedesktop.org/drm/amd/-/issues/4266 from it.