Summary: | Primary monitor desktop environment breaks after monitor sleep or shutoff (or randomly), black screen and panels move to secondary monitor | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Max Sloan <maxsloan44> |
Component: | Containment | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | nate, notmart, xaver.hugl |
Priority: | NOR | Keywords: | multiscreen |
Version First Reported In: | 6.2.4 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Other | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Max Sloan
2024-12-13 23:07:39 UTC
I am not sure if that gdb output will be useful, so if more information is needed, I would be glad to provide it of course. We unfortunately have a number of bug reports about similar things, all on X11. Am I correct in assuming that it never happens when you use the Wayland session? (In reply to Nate Graham from comment #2) > We unfortunately have a number of bug reports about similar things, all on > X11. Am I correct in assuming that it never happens when you use the Wayland > session? I actually really never use Wayland, so I can't speak to that unfortunately. As of right now I switched over to xfce, but I'm more than willing to keep trying to provide any more information if needed. Even if I lost my patience and moved to a different desktop environment I'd like to be able to help get the bug resolved because it does seem pretty common. Am I understanding that you no longer have an environment capable of reproducing the issue? (In reply to Nate Graham from comment #4) > Am I understanding that you no longer have an environment capable of > reproducing the issue? I do still have plasma on my system. I just meant that as a daily driver, I'm using xfce to avoid this bug. But, I do still prefer the features and design of plasma so I'm keeping it on my system and can continue to work with it and troubleshoot. Ok cool. So would you mind logging into a Plasma Wayland session sometime, to test whether it's only on X11 that it happens? So I just logged into a Wayland session to test it, and it's... strange. On Wayland, what happens is very similar, but also it immediately resolves itself rather than me having to fix it myself by reloading display configuration settings. When I turn off my monitor, nothing changes, and everything stays where it should be. But when I turn my monitor back on... 1. I get the device disconnect sound, immediately followed by a connect sound, which does NOT happen on X11 2. The panels move to my secondary monitor like in X11, but *immediately* disappear from the secondary monitor, presumably moving back to their correct places 3. My primary monitor takes maybe a second or two longer to turn back on from a black screen, but everything is where it should be and the containment and DE aren't broken. Everything is normal. So... it's still weird and not quite right, but as opposed to me having to manually "refresh" it myself to kick it back into gear, it takes maybe a couple extra seconds and immediately fixes itself, so I guess using Wayland instead of X11 is a partial workaround? But again, still not quite right... bug still happens, just a lot faster and fixes itself instead. It seems like they're both struggling with the same process but Wayland can recover from it automatically, while X11 simply can't. Very interesting; thanks for testing. It does sound like maybe the same underlying thing is happening, but on Wayland it ends up in a better codepath that makes it able to self-repair. Of course, no problem. Yeah, it's quite strange. If there's any other testing you'd like me to do to help figure things out let me know. *** This bug has been marked as a duplicate of bug 496926 *** |