Bug 464157

Summary: One monitor is sometimes left without a panel or background and right clicking the desktop does nothing
Product: [Plasma] plasmashell Reporter: gendillj
Component: generic-multiscreenAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED FIXED    
Severity: crash CC: aleixpol, gendillj, nate, notmart
Priority: NOR    
Version: git-stable-Plasma/5.26   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: The Xorg log from when the bug happened

Description gendillj 2023-01-11 16:16:54 UTC
Created attachment 155213 [details]
The Xorg log from when the bug happened

SUMMARY
When I unlock my computer after a while of it being locked (not sleeping) It sometimes comes up with the primary monitor functioning with KDE the secondary monitor works just fine except with the primary monitor's panel.


STEPS TO REPRODUCE
1. Lock screen
2. WAit an unknown amount of time
3. Unlock and log in

OBSERVED RESULT
The secondary monitor has the main monitors panel and the primary monitor is left with no panel or desktop and right-clicking the primary monitor does nothing

EXPECTED RESULT
Dekstop wakes with the previous configuration

SOFTWARE/OS VERSIONS
Windows: N/A
macOS: N/A
Linux/KDE Plasma: 6.1.4-arch1-1
(available in About System)
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

Using AMD graphics card this never happened on Intel

KDE log spams `"Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/1”"`

`file:///usr/share/plasma/wallpapers/org.kde.slideshow/contents/ui/main.qml:21: TypeError: Cannot read property 'configuration' of null`

and `requesting unexisting screen 1`
Comment 1 Nate Graham 2023-01-11 18:38:45 UTC
This is finally fixed in Plasma 5.27!

*** This bug has been marked as a duplicate of bug 353975 ***
Comment 2 gendillj 2023-01-11 22:57:01 UTC
(In reply to Nate Graham from comment #1)
> This is finally fixed in Plasma 5.27!
> 
> *** This bug has been marked as a duplicate of bug 353975 ***

That's convenient thank you!