Bug 491230

Summary: applications opening on wrong screens / window rules to force screen not working
Product: [Plasma] kwin Reporter: Ilia Kats <ilia-kats>
Component: rulesAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: atosser, isma.af, nate
Priority: NOR Keywords: multiscreen
Version First Reported In: 6.1.3   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Ilia Kats 2024-08-03 19:29:37 UTC 
I upgraded to Plasma 6 from Plasma 5 and am trying Wayland for the first time. I have a dual-screen setup. Kwin's screen identification is wonky, based on multiple examples:

1. In Yakuake, screens 1 and 2 are switched around: I have to select screen 2 to have it open on screen 1 (I know the screen IDs by right-clicking on another application's title bar -> "Move To Screen")
2. For a long time, I have had a window rule to always open KRunner on screen 1. This doesn't work anymore, KRunner now opens on the screen where my mouse is. I changed the Window matching based on what Detect Window Properties gives me, no success.
3. When an application is requesting screen sharing, and I select Rectangular Region in the pop up window, both dark overlays open on screen 1. I can move one of them to screen 2 by meta+drag.

I don't know if it's the same bug or several related ones, but it all seems connected.
Comment 1 Ilia Kats 2024-08-03 20:34:47 UTC 
The Yakuake issue seems to be gone after a reboot.
Comment 2 aTosser 2024-08-10 19:35:42 UTC 
I experience the same behavior, window rules work at boot, but then over time, as monitors go to sleep and come back something seems to loose track of the monitors and where things are supposed to be.

Operating System: Gentoo Linux 2.15
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.3-gentoo-dist (64-bit)
Graphics Platform: Wayland


see also: 
bug 491302
bug 474246
Comment 3 Ismael Asensio 2025-02-22 21:40:54 UTC 

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