If I launch a window and specify the window size and position, the window is of the correct size, but the position that I specify is ignored. Here is a command that should put a window on my second (right hand) screen, specifically at coordinates X=3754, Y=870. But instead, the window pops up in the upper left of the first (left hand) screen: /usr/bin/konsole --qwindowgeometry 675x678+3754+870 & Reproducible: Always Steps to Reproduce: 1.Run the above command on a system with multiple screens. 2. 3. Actual Results: Wayland ignores the requested placement. Expected Results: Wayland honors the requested placement.
I'm afraid this is simply how things work on Wayland: traditional draggable windows aren't allowed to determine their own position; the compositor is exclusively in charge of that. There are some exceptions and workarounds for non-traditional windows like DE Panels, drop-downs like for KRunner or Yakuake, full-screen overlays, etc. Using the xdg-shell and layer-shell protocols which go through the compositor, they can be positioned manually, relative to known parts of the screen. However those protocols are not intended for traditional app windows you can drag around.
To expand on "this is simply how things work on Wayland": it means it is an active design choice to not allow clients to position themselves, not a missing feature or a bug. However, KWin allows the user to set the initial position of a specific window every time it is launched: look for "Window Rules" in the system settings.
There is also upstream Wayland protocol discussion about supporting some way to do this: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/264
(In reply to Steven A. Falco from comment #0) > If I launch a window and specify the window size and position, the window is > of the correct size, but the position that I specify is ignored. Here is a > command that should put a window on my second (right hand) screen, > specifically at coordinates X=3754, Y=870. But instead, the window pops up > in the upper left of the first (left hand) screen: > > /usr/bin/konsole --qwindowgeometry 675x678+3754+870 & > Out of curiosity, why do you do it this way verses using KWin's window rules mechanism? Is there a specific use-case you're missing here?
My understanding is that that mechanism will work fine for a single konsole window. I don't see how to use those rules for multiple copies of konsole. Here is more of the script that I use to launch konsole windows today: /usr/bin/konsole --qwindowgeometry 675x678+2356+870 & /usr/bin/konsole --qwindowgeometry 675x678+3054+870 & /usr/bin/konsole --qwindowgeometry 675x678+3754+870 & /usr/bin/konsole --qwindowgeometry 675x678+1920+0 & /usr/bin/konsole --qwindowgeometry 1757x1468+2614+0 & Is there a way to do that with the rules you mentioned?
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.