SUMMARY A window position "Force" rule targeting Yakuake works on initial display. However, once yakuake is dismissed (default keybinding of F12) and shown again, the position reverts to the default value as configured in Yakuake. STEPS TO REPRODUCE 1. In Plasma 6 Wayland session, specify a window rule for yakuake. E.g., set the "Y" coordinate offset to 120. 2. Start yakuake, the application is shown with the y-coordinate offset as intended. 3. Hide yakuake and then show it again. OBSERVED RESULT The window rule no longer has any effect. I.e., the yakuake application is displayed with the default 0 y-coordinate. EXPECTED RESULT The window rule should continue to have effect. I.e., the yakuake application should continue to be displayed (when visible) with y-coordinate offset of 120. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed / Plasma 6.0.2 (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2
Might be a Yakuake issue?
(In reply to Nate Graham from comment #1) > Might be a Yakuake issue? In Wayland, applications can choose to ignore window rules? Short of fixing the issue, how would one confirm/deny whether or not this is a yakuake issue? And if it is, is there some action I need to take to ensure
This also happens in konsole when launched in background mode. If I launch "konsole --background-mode" then set a force rule targeting the window or application, after the window has been dismissed and shown again via ctrl-shift-F12, konsole doesn't take into consideration the configured rule. This still happens both in yakuake and konsole 24.05.
confirmed on plasma 6.0.4. updated description and changed product to kwin (since it's affecting multiple applications that have something like konsole's background-mode).
(In reply to Nate Graham from comment #1) > Might be a Yakuake issue? This bug is still present in version 6.1.1. And given how both Konsole and Yakuake are affected, this seems much more likely to be a KWin issue. Are there any additional details that I can share that would make it easier to find and resolve the bug?