Bug 445791 - "Apply Initially" rules are re-applied after certain circumstances
Summary: "Apply Initially" rules are re-applied after certain circumstances
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kwin
Classification: Plasma
Component: rules (show other bugs)
Version: 5.23.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-20 08:22 UTC by tgnff242
Modified: 2023-09-06 10:38 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tgnff242 2021-11-20 08:22:35 UTC
SUMMARY
For example, if you create a rule to set the position of certain windows initially (ie. using the "Apply Initially" setting), the window, sometimes, is moved again to that position after the monitor is switched off (as part of the energy saving plan), or dis/reconnected.


STEPS TO REPRODUCE
1. Create a rule:
Description: Firefox to the right hand side
Window Class: firefox
Match whole window class: Yes
Window Types: Normal Window
Position: Apply Initially: 718 x 0
2. Set the shortcut to pack windows to the left in Settings > Shortcuts > KWin.
3. Log out/in. This step is important.
4. Open two firefox windows.
5. Select one of the windows and use the shortcut defined in step 2 to pack it to the left.
6. Dis/reconnect your monitor's cable.

OBSERVED RESULT
At step 6, when the monitor is disconnected, the window is moved to the rule-defined position.

EXPECTED RESULT
Since the "Apply Initially" setting is selected, the window should only move to that position when it's displayed for the first.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2 + KDE patches

ADDITIONAL INFORMATION
This started with Plasma 5.23.0, and it affects both X11 and Wayland.
Comment 1 David Edmundson 2023-09-06 10:38:51 UTC
This bug was reported against an outdated version of KWin. We have made many changes since the. 
If the issue persists in newer versions can you reopen the bug report updating the version number.