[Plasma WAYLAND] Always Open on Primary Screen / Always Open on Active Screen do not work

[GrgMdmn]

Hi ! I have a problem with my most left monitor where the games are automatically launched.
My other monitor is set as primary, but the games I am launching always land on the first (bad) screen.

As a starting, I have tried installing "Always Open on Primary Screen" . When I do this, all the application (opening terminal, folder etc.) go to the bad screen, even if I open them from the second screen... It acts as if the first screen were the primary one, but I have checked in my settings that I have set the second screen as "primary"...

So, in order to bypass this problem, I have installed "Always Open on Active Screen", telling myself this feature would solve my problem. For each application I run from any screen, then the app window opens in the screen where my mouse is... It works for all application... Except the games that are still running on the first screen...! :/

Do you have any idea ? ^^'

I think the problem is on my side and not on the extension's, but maybe someone could help me here.

By the way, I am on linux mint, using kde plasma + wayland.

[nclarius]

Thanks for using my script!

From #11 (comment)

I noticed this happens with XWayland windows which attempt to force remember their positions. This is the case for mGBA and CafeTran Espresso (my main work tool) for instance.

A possible workaround is to create a window rule with the property Ignore requested geometry set to Force: Yes. This can cause issues with dialogs also following the default window placement (e.g. Maximized), but then one can disable the dialog window type.

[DarkShadow44]

I have the same issue, but with Konsole which supports Wayland. Actually, with the script it opens on the wrong screen, without the script it opens on the primary screen.

[ppwwyyxx]

KWin-window-positioning-scripts/always-open-on-primary-screen/contents/code/main.js

Lines 24 to 25 in fe9d164

	// primary screen is 0'th
	var primaryScreen = 0;

The code assumes primary screen is 0th.

I have noticed that on KDE+wayland, this is not necessarily true. Issue should be raised against kwin to provide a way to identify which screen is primary.

[GrgMdmn]

Thank you ! I hope that will be fixed somehow :)

[q5sys]

I asked about this in the kwin matrix channel and was pointed to this:
https://invent.kde.org/plasma/kwin/-/merge_requests/6918/commits?commit_id=418899080e07d6481cb0807f3a066b5c67713126
zzag said: workspace.screenOrder[0] would return the primary output