Bug 498762 - Incorrect named screens in window rules
Summary: Incorrect named screens in window rules
Status: RESOLVED DUPLICATE of bug 455703
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kwinrules (show other bugs)
Version: 6.2.5
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-16 19:25 UTC by reszt
Modified: 2025-01-16 20:33 UTC (History)
3 users (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 reszt 2025-01-16 19:25:34 UTC
SUMMARY
In System Settings > Windows Management > Window Rules, the "Size & Position" property when pinning window refers to monitors by numbers (e.g., 0, 1, 3). However, in Display Configuration, screens are identified by model/serial number. This makes it impossible to accurately determine which screen a window rule will apply to before setting up a multi-monitor configuration.
Furthermore, when monitors wake up from sleep, the association between the numbers and physical screens can change. This results in windows with specific screen rules being reordered while the desktop configuration remains unchanged.
After a system restart, the window rules work correctly until next sleep

STEPS TO REPRODUCE
1.  2 or more monitors
2.  Pin window to specific screen in window rules


OBSERVED RESULT
Can't identify the specific monitor

EXPECTED RESULT
Instead of numbers, the values should correspond to the identifiers used when clicking 'Identify' in Display Configuration.

SOFTWARE/OS VERSIONS

Operating System: Arch Linux 
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Kernel Version: 6.12.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2025-01-16 20:33:48 UTC
*** This bug has been marked as a duplicate of bug 455703 ***