Bug 466408

Summary:	Plasma Shell glitches out after waking from sleep when external display is set as primary - on wayland
Product:	[Plasma] plasmashell	Reporter:	Damiano <damianosalan>
Component:	generic-multiscreen	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	aleixpol, nate, notmart
Priority:	NOR
Version:	5.27.1
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Screenshot of both displays when the bug occours and a window is moved

Description Damiano 2023-02-25 15:44:05 UTC

SUMMARY
***
Plasma Shell glitches out after waking from sleep when using wayland- windows leave trails when moved, wallpaper is visible on a quarter of the screen, desktop icons "fall" behind the panel. This happens only when I am using two displays, one external as the primary and the integrated display in my laptop as secondary. More information below
***

STEPS TO REPRODUCE
1. Log into Plasma (Wayland)
2. Open any window
3. Put computer to sleep
4. Wake from sleep and unlock: dekstop looks normal but icons have fallen behind the panel
5. Right click on any point in the right or bottom half of the screen: bottom and right half of the screen glitches out, as visible in attached screenshots
6. Using touchpad gestures "clears out" window trails

OBSERVED RESULT
Desktop icons move behind the panel, bottom and half of the screen become black or white or show a glitched wallpaper, windows leave trails behind when moved (not in the top left quarter of the screen), these trails get cleared when using some touchpad gestures (such as 4 finger swipe up)

EXPECTED RESULT
Dekstop icons stay in their usual position, wallpaper and window not glitched

SOFTWARE/OS VERSIONS
Linux: EndeavourOS, latest stable updates, kernel 6.1.12-zen, Wayland
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Hardware: Asus laptop with dual GPU: integrated Vega 7 (CPU is Ryzen 7 4800HS) + dedicated Nvidia GTX 1660Ti.
Currently running a dual-screen setup, with an external 4K 60Hz display (connected via HDMI) as the primary monitor, and the laptop's integrated 1080p 144Hz display as the secondary. The issue only happens when both are connected and active, and the primary display is the secondary. It works fine if:
- Only the internal display is active
- Only the external display is active
- Both displays are active and the internal display is set as primary

I'm attaching a screenshot of both my displays, where the issue is visible in the form of "window trails" and dekstop icons behind the panel. Dock animations also leave trails.
I can provide more screenshots if necessary

P.S.
It's my first time reporting a bug and English is not my native language. I hope I have done everything correctly, let me know if I can do something better. I can also provide more information if required.
Also, thank you for the amazing work you are doing, apart from a few edge-case bugs like this, Plasma 5.27 has been an amazing release for me

Comment 1 Damiano 2023-02-25 15:47:21 UTC

Created attachment 156711 [details]
Screenshot of both displays when the bug occours and a window is moved

Comment 2 Nate Graham 2023-02-28 20:32:16 UTC


*** This bug has been marked as a duplicate of bug 465712 ***

Comment 3 Damiano 2023-02-28 21:56:46 UTC

(In reply to Nate Graham from comment #2)
> 
> *** This bug has been marked as a duplicate of bug 465712 ***

Hi, could you please explain why my bug has been marked as duplicate of this other one? (I don't want to complain or anything, it's my first time reporting a bug here and I'd like to understand if I've done something wrong so I can avoid doing that next time)

Thank you

Comment 4 Nate Graham 2023-02-28 22:10:12 UTC

Sure! It means that the bug was already reported by someone else. When this happens, we mark any later reports about the same issue as "duplicates" of the original one, so that progress to fix it can be tracked in only one place, not many.

You haven't done anything wrong; accidentally reporting a duplicate bug report is 100% normal because it's rarely possible for anyone to accurately find a pre-existing bug report that accurately describes their exact issue. This is why we have bug triagers whose job it is to know about currently active bugs and consolidate duplicates (among other duties). Hope that helps.

Comment 5 Damiano 2023-02-28 22:23:30 UTC

(In reply to Nate Graham from comment #4)
> Sure! It means that the bug was already reported by someone else. When this
> happens, we mark any later reports about the same issue as "duplicates" of
> the original one, so that progress to fix it can be tracked in only one
> place, not many.
> 
> You haven't done anything wrong; accidentally reporting a duplicate bug
> report is 100% normal because it's rarely possible for anyone to accurately
> find a pre-existing bug report that accurately describes their exact issue.
> This is why we have bug triagers whose job it is to know about currently
> active bugs and consolidate duplicates (among other duties). Hope that helps.

Yes, that's very clear. 
Well, it doesn't sound particularly fun, so thank you for your work. 
I'm not sure that these two bus are exacly the same though, as in my case the issue only appears in Wayland and after waking from sleep, whereas in the other bug it says it happens on both Wayland and X11 and seems unrelated to sleep. Also, looking at the video provided in the other bug, the "symptoms" look different from the ones I am experiencing. Would that still count as a duplicate? Should I provide more informations?

Comment 6 Nate Graham 2023-02-28 22:28:03 UTC

No, to be honest it's not very fun. I appreciate the appreciation!

If the issue goes away when you set both of your screens to have the same refresh rate, it's almost certainly the same issue despite the slightly different symptoms. If not, it's probably something else and not a duplicate.

Can you check?

Comment 7 Damiano 2023-02-28 22:53:59 UTC

(In reply to Nate Graham from comment #6)
> No, to be honest it's not very fun. I appreciate the appreciation!
> 
> If the issue goes away when you set both of your screens to have the same
> refresh rate, it's almost certainly the same issue despite the slightly
> different symptoms. If not, it's probably something else and not a duplicate.
> 
> Can you check?

I checked and I can't reproduce the issue at all, no matter the refresh rate of my displays. Plasma version is still 5.27.1, maybe some updates to some other software have fixed the issue?

Update: before publishing this post, I noticed that Plasma 5.27.2 was available. I installed it and I confirm that somehow the issue has been solved. In the end, I guess that's what matters.

Thank you again for the support