Bug 495357 - When system is suspended to RAM manually and after that the lid of the laptop is closed and then opened, Plasma wakes up from suspend, but there are no panels and one have to use KRunnner to search for "Log out" option
Summary: When system is suspended to RAM manually and after that the lid of the laptop...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 6.2.2
Platform: Arch Linux Linux
: NOR grave
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: multiscreen
Depends on:
Blocks:
 
Reported: 2024-10-25 19:05 UTC by Łukasz Konieczny
Modified: 2024-11-09 14:52 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Screenshot of System Settings, which shows phantom display and lack of panel (261.14 KB, image/png)
2024-10-28 08:24 UTC, Łukasz Konieczny 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Łukasz Konieczny 2024-10-25 19:05:57 UTC 
SUMMARY
As in the title of the bug, manually triggering suspend before closing the lid makes panels disappear when waking computer up from suspend by opening the lid.

STEPS TO REPRODUCE
1. Either suspend computer from Kickoff or lock the computer and suspend from KScreenLocker.
2. Close the laptop.
3. Open the laptop.
4. Panel disappears, windows from inactive virtual desktop are inaccessible, the only thing you can do is to launch KRunner by Alt+Space and choose to log out.

OBSERVED RESULT
Plasma without panel(s)

EXPECTED RESULT
Plasma waking from suspend properly

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.2.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Manufacturer: System76
Product Name: Darter Pro
System Version: darp7

ADDITIONAL INFORMATION
This is not regression in the 6.2.2! This bug existed back in 6.1, but I thought someone reported it.
Comment 1 Nate Graham 2024-10-28 03:12:31 UTC 
Can you use KRunner to open a terminal window and see if Plasma has stopped running? `ps -e | grep -i plasmashell` should do it.

Does the system have multiple screens?
Comment 2 Łukasz Konieczny 2024-10-28 08:23:18 UTC 
(In reply to Nate Graham from comment #1)
> Can you use KRunner to open a terminal window and see if Plasma has stopped
> running? `ps -e | grep -i plasmashell` should do it.
> 
> Does the system have multiple screens?

Plasma is still running. It didn't stopped, because it has lower PID than Firefox, from which I actually am writing after triggering the bug again.
The system has only one screen, the screen of the laptop. But it has one additional phony screen named "Unknown-1", which is inactive, but activates when I plug external display via HDMI. I have to deactivate it then.
I have attached screenshot of System Settings, which shows this inactive display and by the way shows the lack of panel on the bottom (and lack of wallpaper).
Comment 3 Łukasz Konieczny 2024-10-28 08:24:10 UTC 
Created attachment 175297 [details]
Screenshot of System Settings, which shows phantom display and lack of panel
Comment 4 Łukasz Konieczny 2024-10-28 13:49:39 UTC 
I have noticed, that there actually two phantom screens, the second has no name
Comment 5 Nate Graham 2024-10-28 16:03:12 UTC 
It seems the system is confused about screens, almost certainly due to Bug 493810.

*** This bug has been marked as a duplicate of bug 493810 ***
Comment 6 Łukasz Konieczny 2024-11-09 14:52:47 UTC 
After upgrade to KDE Frameworks 6.8.0 there are no blank entries in NetworkManager and in System Settings screen management page, but the problem still occurs, because there is a phantom display named "Unknown-1".