Bug 459240 - After unlocking screen and showing desktop, panel and windows disappear on non-primary monitors.
Summary: After unlocking screen and showing desktop, panel and windows disappear on no...
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: multi-screen (show other bugs)
Version: 5.25.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-16 21:37 UTC by dans64
Modified: 2023-02-18 05:58 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:
nate: Wayland-
nate: X11+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dans64 2022-09-16 21:37:31 UTC
SUMMARY
***
After unlocking screen when you had previously used show desktop on a multi monitor display, the panels on non-primary displays disappear for a few seconds before becoming visable.
***


STEPS TO REPRODUCE
1. Have multi-monitor setup
2. Use 'show desktop' button/hotkey to hide windows/show desktop.
3. Lock screen
4. Log back in
5. Unhide desktop with button or shortcut

OBSERVED RESULT
Watch all windows on non-primary displays disappear and you can only see your background, cursor can go over windows and panel to interact with them, even drag/move them onto your primary monitor. Eventually after a few seconds the windows and panel will re-appear.

EXPECTED RESULT
After unhiding desktop after unlocking screen panel and windows should all be visable.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98
Qt Version: 5.15.6

ADDITIONAL INFORMATION
Using AMDGPU, mesa and Xorg, haven't tried Wayland yet. Have dual identical 1440p 144hz monitors connected with Displayport.
Comment 1 dans64 2022-09-18 16:15:57 UTC
updating that this does not happen on wayland, only xorg
Comment 2 dans64 2023-02-18 05:58:57 UTC
Forgot to say, but this hasn't happened since 5.26 and is fixed.