Per various discussion I've come across (1, 2, 3) indicating that the
reason Wayland doesn't allow apps to position windows in absolute
coordinates isn't about security; it's about flexibility for more
complex display setups, such as scrollable tiling compositors, non-
rectangular screens, whatnot. I can see that, but but in practice it
leads to problems such as we're seeing here, where people doing
perfectly sensible things in X11 either can't do them at all in Wayland,
or they need to set up complex compositor (kwin, in this case) rules.
So for me the problems are that Chrom{e,ium} will not have all of its
windows restored, and sometimes when I try to open an app it will land
on a different virtual desktop than the one I'm on or even on a
different screen. None of this was ever a problem on X11.
[1]
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/247
[2]
https://hackaday.com/2025/11/11/waylands-never-ending-opposition-to-multi-window-positioning/
[3]
https://www.reddit.com/r/linux/comments/16vciex/lets_make_wayland_have_support_for_window/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/335761
Title:
Placement policy 'Remember' by default for all windows
To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-default-settings/+bug/335761/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs