Bug 500038 - Attempting to switch user via Kicker caused Plasma Shell to crash.
Summary: Attempting to switch user via Kicker caused Plasma Shell to crash.
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: 6.3.0
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL: https://bugzilla.redhat.com/show_bug....
Keywords: drkonqi
: 500205 500208 500209 502082 (view as bug list)
Depends on:
Blocks:
 
Reported: 2025-02-14 00:13 UTC by Roke Julian Lockhart Beedell
Modified: 2025-06-19 15:11 UTC (History)
2 users (show)

See Also:
Latest Commit: https://invent.kde.org/plasma/plasma-workspace/-/commit/1d188e6c285d90c98fdfcbb9b4ab9a1a7334a519
Version Fixed In: 6.4.0
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/132758/events/202769a1c8d34ba99324bc499d356650/

Attachments
New crash information added by DrKonqi (262.26 KB, text/plain)
2025-02-14 00:13 UTC, Roke Julian Lockhart Beedell 		Details
A Demonstration That It Remains In 6.4.0 (3.68 MB, video/mp4)
2025-06-19 15:11 UTC, Roke Julian Lockhart Beedell 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Roke Julian Lockhart Beedell 2025-02-14 00:13:41 UTC 
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
Comment 1 Roke Julian Lockhart Beedell 2025-02-14 00:13:42 UTC 
Created attachment 178332 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Roke Julian Lockhart Beedell 2025-02-14 00:21:29 UTC 
(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.
Comment 3 Roke Julian Lockhart Beedell 2025-02-14 00:29:10 UTC 
(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
Comment 4 Roke Julian Lockhart Beedell 2025-02-14 00:53:58 UTC 
(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.
Comment 5 John 2025-02-14 06:39:36 UTC 
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)
Comment 6 Roke Julian Lockhart Beedell 2025-02-16 18:00:23 UTC 
*** Bug 500205 has been marked as a duplicate of this bug. ***
Comment 7 Roke Julian Lockhart Beedell 2025-02-16 18:52:22 UTC 
*** Bug 500208 has been marked as a duplicate of this bug. ***
Comment 8 Roke Julian Lockhart Beedell 2025-02-16 19:03:58 UTC 
(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!
Comment 9 Roke Julian Lockhart Beedell 2025-02-16 19:28:13 UTC 
*** Bug 500209 has been marked as a duplicate of this bug. ***
Comment 10 Nate Graham 2025-02-18 22:41:21 UTC 
Should be fixed by https://invent.kde.org/plasma/plasma-workspace/-/commit/1d188e6c285d90c98fdfcbb9b4ab9a1a7334a519, which will be in Plasma 6.4.0.
Comment 11 Roke Julian Lockhart Beedell 2025-02-18 23:13:25 UTC 
(In reply to Nate Graham from comment #10)  
Thank you!
Comment 12 John Kizer 2025-04-09 18:36:29 UTC 
*** Bug 502082 has been marked as a duplicate of this bug. ***
Comment 13 Roke Julian Lockhart Beedell 2025-06-19 15:11:50 UTC 
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.