Summary: | Application windows restore to wrong monitor (Neon 5.24) | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Jeff Sheffel <jscodefix> |
Component: | multi-screen | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | david.landrith, nate, rqkeating, xaver.hugl |
Priority: | NOR | Keywords: | regression |
Version: | 5.24.3 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.26 | |
Sentry Crash Report: |
Description
Jeff Sheffel
2022-02-26 20:54:32 UTC
I observe that if I manually Sleep my computer, upon waking (and restoring the session?), that the windows are correctly positioned on the dual monitors, as I left them before sleeping. This behavior differs compared to when the monitors switch off or the system sleeps upon timeout (which is when the bug occurs). I am also waiting for Neon to upgrade Plasma to 5.24.2, to see if this bug has been fixed. Sadly, I upgraded to the latest Plasma version (5.24.3) and the bug still occurs. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.24 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 How do I get some attention on this bug? I imagine that many others are suffering from this bug, too. I have seen a couple of other Kwin bugs that could be related. Perhaps the bug is caused by my specific hardware setup (though I doubt that). To reiterate, (most of the time?) if I manually Sleep my computer, the windows do restore properly to each monitor. But, if the Screen Energy Saving timer is triggered, then when I reactivate the monitors (with a mouse move), then the bug occurs. I have set (checked): Window Behavior -> Advanced -> Allow apps to remember the positions of their own window I have selected: Startup/Shutdown -> Desktop Session -> Restore previous saved session Please advise. Please help. > Please advise. Please help. I understand you're frustrated and in need of assistance, but please keep in mind that this is a volunteer project. See https://community.kde.org/Get_Involved/Issue_Reporting#Have_realistic_expectations Of the three major KWin developers, one is a volunteer, one is busy with employer-directed projects, and the third is living in a country that is being invaded by Russia. I'm afraid some patience will be required here. Look into Rapid Hot Plug Detect (Rapid HPD). There is a lot of talk about this with regards to Windows but the description of the problem is the same. (In reply to Nate Graham from comment #4) > > Please advise. Please help. > I understand you're frustrated and in need of assistance, but please keep in > mind that this is a volunteer project. See > https://community.kde.org/Get_Involved/ > Issue_Reporting#Have_realistic_expectations > > Of the three major KWin developers, one is a volunteer, one is busy with > employer-directed projects, and the third is living in a country that is > being invaded by Russia. I'm afraid some patience will be required here. Then maybe your project lead shouldn't be making blog posts denigrating efforts like kwinft that are actually trying to move this effort forward. And maybe, just maybe, if you've got less than 2 1/2 developers working on kwin, you might consider that this makes it pretty dishonest to tout KDE as a viable alternative to Windows or macOS. This was recently fixed for Plasma 5.26. |