Description of problem: Thought I was seeing things... but after paying attention, I see that windows are automatically moved from my primary screen to the non-primary screen. I keep certain apps (claws-mail, certain emacs and firefox windows) on the right screen, others on the left screen. I walk away from the system for a while. When I return, apps are now on the left screen. Not sure how recently this started. I was just assuming I'd forgotten having may be moved them myself; but not that I'm paying attention, it's not me... Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Place windows on both screens 2. Let Power Management kick in 3. move mouse or hit a key 4. app windows on right screen have migrated to left screen Screens: C27F390 HCNR702673 C27F390 HCPR803666 1920x1080 1920x1080 [X] Enabled [X] Enabled [ ] Primary [X] Primary
Thank you for the report. Yet another Plasma quirk (like bug 30315)? (Please always say what desktop is involved in things like this). For both of these bugs, I have to ask whether you have explored the KDE forums to see whether the problem is seen elsewhere. If another Bugsquad person has a system on which the complaint can be verified (with 2 screens + power management), please do. I cannot.
Summary: Power Management moves windows to other screen => Plasma Power Management moves windows to other screenSource RPM: (none) => PlasmaCC: (none) => kde, lewyssmith
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=30315
Just noticed this is for Cauldron, so assigning it directly to the KDE team.
Assignee: bugsquad => kdeCC: kde, lewyssmith => (none)
Slight improvement for konsole windows... instead of moving entire konsole window to left screen, now the konsole is split 25%|75%... still have to move konsole back on every desktop; but now they are not hidden -- easier to move back.
One screen is on UPS. Only saw this when power flickered. I have totally disabled power management (screens stay on 24/7); so not sure if this still exists.
Resolution: (none) => OLDStatus: NEW => RESOLVED