Bug 32950 - KDE magnetic screen after screens off/on
Summary: KDE magnetic screen after screens off/on
Status: UPSTREAM
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: FOR_ERRATA10
Keywords: UPSTREAM
Depends on:
Blocks:
 
Reported: 2024-03-08 15:16 CET by Pierre Fortin
Modified: 2024-03-14 20:29 CET (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Pierre Fortin 2024-03-08 15:16:59 CET
Minor: "easy workarond"; be irritating when it happens (often)

Description of problem: I have 3 identical monitors and 10 desktops:
DP-1    DP-0    DP-2
      primary

I used to have my screens set to never turn off; but a few weeks ago, I  changed systemsettings->Energy Saving to turn them off after 20 minutes. After a period of time, usually the next morning, most of my open windows have migrated to DP-1 which is quite aggravating moving them all back to where I like them.Some windows which were spanning DP-0 & DP-2 end up with the portion which was on DP-0 now off-screen to the left of DP-1

Before screens go off:
[    DP-1    ][    DP-0    ][    DP-2    ]
  W1,w2         W3,W4,W5   W6, W7       <-- W6 spanning DP-0 & DP-2

After screens come on:
[    DP-1    ][    DP-0    ][    DP-2    ]
  W1,w2
   W3,W4,W5
6, W7                 <-- W6 off screen


Version-Release number of selected component (if applicable):
Operating System: Mageia 10
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.6.18-server-1.mga10 (64-bit)
Graphics Platform: X11
Processors: 20 × 12th Gen Intel® Core™ i7-12700K
Memory: 125.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT
Manufacturer: Dell Inc.
Product Name: XPS 8950

How reproducible: not always; but too often


Steps to Reproduce:
1. enable energy saving
2. resume system use after monitors have been off for a while.
3.
Comment 1 David GEIGER 2024-03-08 15:21:26 CET
This type of bug should be reported upstream at https://bugs.kde.org/

Plasma 6 is new and need probably lot of work to make it more stable and with few bugs.

CC: (none) => geiger.david68210

Comment 2 Pierre Fortin 2024-03-08 15:53:07 CET
I'm an end user of Mageia. Going to bugs.kde.org, I'm presented with:
  Next, you must pick a product on which to enter a bug:
    and a list of approximately 50 products.
That looks more like a place for distro people, not end users to report to...
Any suggestion for what product to report this against?
Comment 3 David GEIGER 2024-03-08 16:09:17 CET
And we are not kde developer so it make it impossible for us to fix such as bug, sorry.

I guess plasma-workspace product should be correct.
Comment 4 Pierre Fortin 2024-03-08 17:41:06 CET
https://bugs.kde.org/show_bug.cgi?id=482895
Comment 5 Lewis Smith 2024-03-09 21:25:12 CET
Thanks for that.
Try Wayland rather than X11 for Cauldron Plasma; it is what the KDE people are going for.

CC: (none) => lewyssmith

Comment 6 Pierre Fortin 2024-03-13 15:12:34 CET
Switched to Wayland and haven't seen this since.
Comment 7 Lewis Smith 2024-03-14 20:21:19 CET
@DavidG
This is another of several bugs about new Plasma 6 faults which only happen for X11, not with Wayland. How do we close them?
We certainly need a general ERRATA entry about this: for Plasma 6, use Wayland. Unless upstream fix them.

Status: NEW => UPSTREAM
CC: (none) => fri
Keywords: (none) => UPSTREAM
Whiteboard: (none) => FOR_ERRATA10

Comment 8 David GEIGER 2024-03-14 20:29:09 CET
These are not really bugs but simply upstream which decide to switch to Wayland by default and probably stop to support X11, same for future lxqt 2.0.0.
And we "Mageia" will definitely do the same for mga10.

Note You need to log in before you can comment on or make changes to this bug.