| Summary: | Resuming from powersaving/sleep results in display misconfiguration and lost window positions | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Jason Straight <j.straight-kde> |
| Component: | multi-screen | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | edtoml, nate, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | 5.25.90 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Jason Straight
2022-09-26 04:24:27 UTC
Is it any better with the Wayland session? (In reply to Nate Graham from comment #1) > Is it any better with the Wayland session? Afraid not. First try - it lost my screen resolution and refresh rate. That will be because of another bug (monitor information stored in a different way on Wayland vs X11). If you correct those things, reboot, and then try to reproduce the issue, does it happen again? (In reply to Nate Graham from comment #3) > That will be because of another bug (monitor information stored in a > different way on Wayland vs X11). If you correct those things, reboot, and > then try to reproduce the issue, does it happen again? Still happens. After you change the monitor settings back, do the windows move back to their correct places again? (In reply to Zamundaaa from comment #5) > After you change the monitor settings back, do the windows move back to > their correct places again? No. Not in X anyway. The reason I get the idea it has something to do with timing/time is because it takes a while of sitting for this to trigger. For testing, I set my screen sleep to 1 minute. If I wake the monitors right after they go to sleep, they wake up fine. If I wait for the monitor to wake back up and tell me there's no signal on DP, then it goes back to sleep. If I wake it up within several seconds of that, it still wakes up fine. I don't know exactly what the "safe" time is, maybe it's less than a couple minutes. But when it bugs out on me is after I've left it for about 5 or more minutes. When it does come back with the proper screen settings, the windows appear to be in the right spots. Another observation that (so far) seems true, in case it helps: It only seems to have a problem the first time it sleeps the screens after a reboot. After it does the first time, I reconfigure my screen resolution, position, and refresh rate and then every time it sleeps afterwards it successfully wakes the screens with the right settings and window positions. If I use my thunderbolt usb 4 docking station, everything works fine. Still displayport. Update: I switched to OpenSuSE Tumbleweed and no longer have the problems with the resolution being change after waking the screens, but the positions of the windows are not restored. They're shifted to the right, with whatever window was snapped to the right being partially off-screen. A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/3063 sorry, that was the wrong bug number I am on Arch with 5.26.4 using wayland. My Primary monitor (hdmi 1920x1080) is set on the right of my secondary (DP 2560x1440). About one in ten times after waking from display powersaving I get a 'graphic menu' of screen layouts, I need to select the second from the right and then reposition my primary screen. I suspect its a timing issue? The DP monitor wakes much faster than the HDMI monitor. Are there any logs I can collect to see what happens after a good wake vs a bad wake? It seems that what really makes the Windows come up in the wrong spot is when they're snapped to a screen edge. Where I see it is my 2nd monitor, which is an ultra wide, and I often have windows snapped to one side or the other. *** This bug has been marked as a duplicate of bug 461886 *** |