Summary: | Attempting to switch user via Kicker caused Plasma Shell to crash. | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Roke Julian Lockhart Beedell <4wy78uwh> |
Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | ilikefoss, nate |
Priority: | NOR | Keywords: | drkonqi |
Version: | 6.3.0 | ||
Target Milestone: | 1.0 | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
URL: | https://bugzilla.redhat.com/show_bug.cgi?id=2325351#c15 | ||
See Also: | https://bugzilla.redhat.com/show_bug.cgi?id=2325351 | ||
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 |
Description
Roke Julian Lockhart Beedell
2025-02-14 00:13:41 UTC
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. *** |