51–60 of 392 posts
> Moving forward with a single code path going through Wayland is going to allow us to bring new performance improvements, memory optimisations [sic], and brand new exciting features throughout Plasma. I wish they would have listed what some of those features might be.
I empathize but every time I try a Wayland based desktop I always end up encountering weird bugs and corner cases with basic usability that drive me back to X11. I'll be sad if that is still the case when 6.8 rolls around as then I'll be hunting for another DE.
When was the last time you tried? What compositor?
What is a compositor - thing that actually draws window content on the screen? Whatever KDE provides?
Edit: To be fair to KDE/Wayland, the Wayland Kubuntu 24.04 experience was vastly improved over Kubuntu 22.04.
What's sad is that after many years Wayland still lacks several things/features that X11 has/allows. Some of them are intentionally not implemented because of security paranoia. For example, Chrome "picture in picture" window doesn't stay on top when I click somewhere else since Wayland doesn't allow windows to stay on top. If I had a lot of time I could list how Wayland breaks many applications. Not saying that X11…
If you use KDE, you can work around this because of the powerful feature set the window manager has for setting custom window behavior. 1. Right click the PIP window and then click "More Actions-> Special Window Settings". 2. On the window that pops up, click "Add Property", and add "Window title". Change the drop-down from "Unimportant" to "Exact match" (this works on Firefox because the window title is always "Pict…
What's sad is that after many years Wayland still lacks several things/features that X11 has/allows. Some of them are intentionally not implemented because of security paranoia. For example, Chrome "picture in picture" window doesn't stay on top when I click somewhere else since Wayland doesn't allow windows to stay on top. If I had a lot of time I could list how Wayland breaks many applications. Not saying that X11…
If the logic is that it's the window manager's job to set window rules for this, fine, but in that case Plasma should probably ship with preconfigured rules matching the Chrome/Firefox PiP window.
I also find the lack of an Xlib-compatible macro API disruptive but I usually run an X11 session inside Xvnc for this purpose anyway.
I empathize but every time I try a Wayland based desktop I always end up encountering weird bugs and corner cases with basic usability that drive me back to X11. I'll be sad if that is still the case when 6.8 rolls around as then I'll be hunting for another DE.
> but every time I try a Wayland based desktop I always end up encountering weird bugs and corner cases with basic usability that drive me back to X11. The risk in that in this age of AI-assisted bughunting, X11 security vulnerabilities are more numerous and as nasty as they've ever been. And that says a lot. https://www.phoronix.com/news/MTU1NzA https://www.phoronix.com/news/X.Org-9-Vulnerabilities-AI
> Moving forward with a single code path going through Wayland is going to allow us to bring new performance improvements, memory optimisations [sic], and brand new exciting features throughout Plasma. I wish they would have listed what some of those features might be.
HDR support would be one I suppose. IIRC it's plain impossible with X11.
KRdp on Plasma/Wayland is still much more fragile. It depends on a logged-in Plasma session, has rough edges around unattended access, session startup, reconnection, display sizing, authentication/cert handling, and general automation. Those are exactly the things cloud desktops and disposable VM images need to be boringly reliable.
I’m not against deprecating X11 long term, but deprecating it before KRdp is a solid replacement leaves server/VM/remote-desktop users in a bad spot, hopefully now the team can focus solely on Wayland, KRdp will receive some much needed love.
Earlier quoted context omitted.
I know nothing about the detailed technical differences between X11 and Wayland but with Hyprland for me the PIP is working as expected so I assume its not just a Wayland issue but specific to the window manager you are using? Maybe somebody else can explain?
Gnome has a "Always on Top" toggle for each window. I imagine there's a protocol for an application to set it by default but the OP's window manager might not implement it or there might be an incompatibility.
What's sad is that after many years Wayland still lacks several things/features that X11 has/allows. Some of them are intentionally not implemented because of security paranoia. For example, Chrome "picture in picture" window doesn't stay on top when I click somewhere else since Wayland doesn't allow windows to stay on top. If I had a lot of time I could list how Wayland breaks many applications. Not saying that X11…
I think the KDE developers in particular have done a great job of pushing Wayland forward and getting features that people want and need added as new protocols. KDE feels a lot smoother and more responsive when using Wayland than when using X11, and by this point most stuff has been updated to work properly on Wayland so I don't notice any breakage or missing features in day-to-day usage. > Moving forward with a sing…
> KDE feels a lot smoother and more responsive when using Wayland than when using X11 Or, the X11 code is more complex and they prefer Wayland because it is simpler. Fewer features. Is it a surprise that wayland would be faster, if it does less? > by this point most stuff has been updated to work properly on Wayland Really? Strange how comments on reddit do not confirm this. Admittedly they did fix various issues. I…
That is because people who don't have a problem don't think about this and so don't comment. Many wayland users don't know. I think I switched this machine I'm using now to wayland a while ago but I don't remember, and maybe it switched back in an update and I didn't notice (which is the point, I know I switched at some point and I couldn't tell the difference - which is how it should be)