Bug 487880 - Windows lose their sizes and positions after the monitors go to sleep
Summary: Windows lose their sizes and positions after the monitors go to sleep
Status: RESOLVED DUPLICATE of bug 461886
Alias: None
Product: kwin
Classification: Plasma
Component: core (show other bugs)
Version: 6.0.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-01 11:24 UTC by Pavel Urusov
Modified: 2024-06-03 17:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Urusov 2024-06-01 11:24:49 UTC 
SUMMARY
Windows lose their sizes and positions after the monitors go to sleep.

STEPS TO REPRODUCE
1. Arrange windows on a desktop
2. Allow the monitors go to sleep due to inactivity
3. Wake the system up and unlock the user session

OBSERVED RESULT

Windows randomly change their sizes and positions.

EXPECTED RESULT

Windows keep the sizes and positions they had before the system went to sleep.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240524
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.9.1-1-default (64-bit)
Graphics Platform: Wayland
Graphics Processor: AMD Radeon RX 560 Series

ADDITIONAL INFORMATION
I have a suspicion that this bug is related to my multi-monitor setup. It seems that windows keep their positions if I unplug the second monitor. I can only speculate that the monitors wake up / become available to the system in a random order, which causes KWin to rearrange the windows.
Comment 1 Zamundaaa 2024-06-01 22:33:51 UTC 
Were the windows tiled before they were rearranged?
Comment 2 Pavel Urusov 2024-06-02 08:05:06 UTC 
(In reply to Zamundaaa from comment #1)
> Were the windows tiled before they were rearranged?

Hi, some of them were, yes.
Comment 3 Zamundaaa 2024-06-03 17:47:07 UTC 
great, then that should be fixed in 6.0.5

*** This bug has been marked as a duplicate of bug 461886 ***