| Summary: | Application Windows moving randomly from screen to screen and sometimes to other desktops | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Paul Hands <jphands> |
| Component: | multi-screen | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | nate, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | 5.24.4 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Paul Hands
2022-04-05 03:18:25 UTC
Is it possible that the signal for one or more of your screens is cutting out, causing the monitor to appear off for a moment? When that happens, KWin re-arranges windows, and there is a probably a bug in that behavior that is being triggered. (In reply to Nate Graham from comment #1) > Is it possible that the signal for one or more of your screens is cutting > out, causing the monitor to appear off for a moment? When that happens, KWin > re-arranges windows, and there is a probably a bug in that behavior that is > being triggered. Hi Nate, and thanks for taking the time to reply. That's an interesting idea and question! It's a possibility, as the primary screen sometimes blanks for a moment, but I haven't seen that trigger any rearrangement. Is there any experiment you think I can do? Some debug or log setting? Paul > the primary screen sometimes blanks for a moment
That seems related indeed.
One last question, before I let the KWin developers take over: does this affect *all* windows, or just certain KDE app windows (e.g. Dolphin, Okular, Gwenview, System Settings, and Discover)?
(In reply to Nate Graham from comment #3) > > the primary screen sometimes blanks for a moment > That seems related indeed. > > One last question, before I let the KWin developers take over: does this > affect *all* windows, or just certain KDE app windows (e.g. Dolphin, Okular, > Gwenview, System Settings, and Discover)? Thanks again. Nate. I did an experiment. My initial suspicion about the screen energy saver seems at least partially correct. The timeout was set for 15 minutes, and sure enough, after that time, the screens all went dark....but only for about 15 seconds, when they switched back on without any input events. On coming back on, all the app windows in the rightmost screen had moved to the middle screen, leaving screen 3 empty. During the "off" period, I could see the monitors polling their various inputs for a signal, and I wonder if that is causing some weird interaction with the GPU. I then cut the energy saver period down to 3 minutes, and the situation is totally repeatable. Switching off the energy saver removes the issue. I then let the Screen-locking feature in the Workspace Behavior (I use a bunch of Desktop Effects; not sure if that's relevant) section of System Settings cut in, and after getting back in, no windows had moved. So....I think I can say.... 1. The energy saver cut-in is triggering the app window movement to screen 2. Or the wrongful switching back on is.... 2. The energy saver isn't working correctly, as the monitors come back on after about 15 seconds, even with no mouse or keyboard events. 3. The phenomenon isn't application window type specific - it applies to all windows in screen 3....I tested a few: Signal, Konsole, Firefox, Discover, Opera and System Settings. 4. The issue isn't associated with the Screen Lock functionality, just the energy saver. 5. Turning off energy saving hides the issue, but that's not environmentally great. As before, if I can run any more tests or provide any logs, etc, just let me know. OK, thanks for the information! I think we have enough information to implicate KWin here, rather than than the X11-specific feature to remember (some) KDE app windows' positions. Seems like the behavior to move windows when screens are connected and disconnected may be getting inappropriately activated and/or doing something buggy in response to screens being inappropriately temporarily turned off during screen locking. I'll let the KWin developers take it from here. KWin now has code to move windows back to where they should be, so this should no longer be a problem Thanks, Zamundaaa. What version of kwin should I look out for? 5.27 had some of it, but sort of incomplete and a bit buggy. It should be fully functional and auto-tested in 6.0.5 (In reply to Zamundaaa from comment #8) > 5.27 had some of it, but sort of incomplete and a bit buggy. It should be > fully functional and auto-tested in 6.0.5 Thanks again. I'm on 6.04, so I'll await 6.,05, and let you know if it's fixed for me. |