Bug 510136 - Screens are sometime re-enumerated when displays return from sleep.
Summary: Screens are sometime re-enumerated when displays return from sleep.
Status: RESOLVED DUPLICATE of bug 505945
Alias: None
Product: kwin
Classification: Plasma
Component: multi-screen (other bugs)
Version First Reported In: 6.4.5
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-01 17:52 UTC by aTosser
Modified: 2025-10-02 11:05 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description aTosser 2025-10-01 17:52:47 UTC
I have a dual screen setup, nothing fancy. I started noticing this bug because my workflow involves forcing applications to stay on a specific virtual desktop + screen. As well as, using the option in yakuake to only have it display on my vertical right side monitor.

When my screens sleep (not the system) when they wake up, sometimes a monitor will somehow have been re-enumerated. This throws all of my rules off instantly and I can only recover if I relog into my session. 

STEPS TO REPRODUCE
1. Set system to never sleep, set monitors to turn off and system to lock at the same time. (likely this is not all necessary, this is just my configuration)
2. Allow monitors to go to sleep.
3. Wake monitors.

OBSERVED RESULT

Regularly, screens are re-enumerated when monitors return from sleep

EXPECTED RESULT

The system should be able to recognize these are the same monitors and not number them like new devices.

SOFTWARE/OS VERSIONS

Operating System: Gentoo Linux 2.18
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.3
Kernel Version: 6.16.8-gentoo-dist (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor
Memory: 128 GiB of RAM (125.4 GiB usable)
Graphics Processor: AMD Radeon RX 5700 XT
Comment 1 aTosser 2025-10-01 18:03:29 UTC
Possibly a duplicate of Bug 510077
Comment 2 Zamundaaa 2025-10-02 11:05:17 UTC

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