Summary: | Switching users consistently causes black screen with cursor | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Roke Julian Lockhart Beedell <4wy78uwh> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | john.kizer |
Priority: | NOR | Flags: | 4wy78uwh:
Intel-
4wy78uwh: Mesa+ 4wy78uwh: NVIDIA- |
Version First Reported In: | 6.3.3 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
URL: | https://discuss.kde.org/t/switching-users-randomly-causes-black-screen-with-cursor/32103/7?u=rokejulianlockhart | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=439873 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
A Photograph of the Black Display Visible after "Switch User" Has Been Invoked
A Screencast of KRunner in Plasma 6.3.4 A Screencast of Kicker in Plasma 6.3.4 A Screencast of QDBus in Plasma 6.3.4 |
Description
Roke Julian Lockhart Beedell
2025-03-27 17:03:41 UTC
Hi - feel free to reopen if I'm missing something, but this seems like fundamentally the same issue as https://bugs.kde.org/show_bug.cgi?id=500038 - the code path followed by the "Switch User" option found by searching in Kicker doesn't work. *** This bug has been marked as a duplicate of bug 500038 *** (In reply to John Kizer from comment #1) Didn't I demonstrate in the report that this isn't specific to Kicker? It occurs even when I invoke the relevant switch user command via QDBus. Is there another part of the user interface that triggers the problem? The UI issue seems covered by the other bug - if you're wanting to report that there's a D-Bus method that triggers a freeze, that seems like a separate issue? (In reply to John Kizer from comment #3) From what I recall, the issue which you've marked this as a duplicate of didn't cause a freeze. If I verified it does so via KRunner too, would that adequately differentiate them? Then, we'd have Kicker, QDbus, and KRunner all acting the same. Setting aside the D-Bus stuff, the Kicker method is the KRunner method, correct - typing in "Switch User" to find it in search results? Is the issue that sometimes the Kicker/KRunner method causes a regular crash and sometimes a freeze-up, or is it that is used to do one and now does the other? Just trying to clearly delineate if there are distinct steps leading to issues, or the same steps with differing results. Thanks, Created attachment 180147 [details]
A Screencast of KRunner in Plasma 6.3.4
In retrospect, you might be correct. I'll post recordings of every reproduction method, and how the consequence of each differs, when they do.
Created attachment 180148 [details] A Screencast of Kicker in Plasma 6.3.4 (In reply to Roke Julian Lockhart Beedell from comment #6) Created attachment 180149 [details] A Screencast of QDBus in Plasma 6.3.4 (In reply to Roke Julian Lockhart Beedell from comment #6) When Plasma ≥ 3.4 reaches me, I'll try to remember to check whether the issue (at least with QDBus) remains reproducible. *** Bug 486320 has been marked as a duplicate of this bug. *** (In reply to Roke Julian Lockhart Beedell from comment #9) > When Plasma ≥ 3.4 reaches me, I'll try to remember to check whether the issue (at least with QDBus) > remains reproducible. John, this remains consistently reproducible (on the same hardware), despite https://bugs.kde.org/show_bug.cgi?id=500038#c10: > Operating System: Fedora Linux 42 > KDE Plasma Version: 6.3.4 > KDE Frameworks Version: 6.13.0 > Qt Version: 6.9.0 > Kernel Version: 6.14.2-300.fc42.x86_64 (64-bit) > Graphics Platform: Wayland I'm quite confident that this is separate to that bug. That linked comment indicates that the fix for the issue will be released in Plasma 6.4.0 - I may be missing something, but that's not released yet and your device (like mine) is still using Plasma 6.3.4, so it seems logical that the issue wouldn't be fixed yet then? ...I misread my own Plasma version. IDK how. Please forget this ever happened. |