| Summary: | Black window with only cursor after sleep | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | nilskemail+kde |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.1.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
System log while reproducing the bug
User log while reproducing the bug |
||
|
Description
nilskemail+kde
2024-09-19 17:30:25 UTC
This seems bad. When you do it a second time, it sounds like KWin is crashing. Can you get a backtrace of the kwin_wayland crash? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl. Hopefully that will give us a clue regarding what's happening here. Thanks a lot! (In reply to Nate Graham from comment #1) > This seems bad. When you do it a second time, it sounds like KWin is > crashing. Can you get a backtrace of the kwin_wayland crash? There is nothing related to that crash listed by coredumpctl. Not kwin or anything else Could be that KWin is exiting with a Wayland protocol error, then. Since that's a secondary effect, possibly triggered by the initial issue, let's dig into the initial issue. It seems that plasmashell has also exited rather than crashing. The next time this happens, can you use KRunner (Alt+Space) to open Konsole and then use Konsole to run `journalctl --reverse` and see if there are any suspicious-looking messages from plasmashell? Just copy and paste the last minute's worth of messages here. Thanks! Created attachment 173921 [details]
System log while reproducing the bug
Created attachment 173922 [details]
User log while reproducing the bug
I reproduced the bug while running journalctl --follow (with and without --user) and piping the output into a file. I also just noticed that when I activate the lock screen using Meta+L, move the cursor to unlock it (I have an empty password), and lock the screen again using Meta+L, I can achieve a similar situation. The screen is also black and the cursor is visible but moving it does not unlock the PC. However, unlike the original scenario after a wake-up from sleep, I can put any finger on the fingerprint reader (also unregistered ones) which unlocks the PC and shows my plasma session again. This is not possible with the scenario when waking up from sleep after closing the laptop lid though... Even though these are a bit different, I feel like they might be related or share the same cause. It is weird that one can be resolved by starting a scan with the fingerprint sensor (even a failing one) while the other one is not affected by it but also the fact that this, as well as the reproduction in the video, happens at the second time only seems like a very odd coincidence - and, well: There are no coincidences. I am not sure how I encountered this initially but so far all my reproductions with sleeping/lid closing also happened on the second try only IIRC... Aha, this is Bug 493572. *** This bug has been marked as a duplicate of bug 493572 *** |