Live data from Hacker News

Preparing for KDE Plasma's Last X11-Supported Release

blog.davidedmundson.co.uk

281–290 of 392 posts

Re: Preparing for KDE Plasma's Last X11-Supported Release

#281

> Our internal metrics within KDE show that over 95% of users of Plasma 6.6 are on Wayland Wonder how representative of the real end user population this is?

I think most people who even know the difference between x11 and Wayland are much more privacy conscious then those who don’t. 0% of people going out of their way to jump through all the hoops to get plasma working on x11 would ever opt in to such metrics.

Re: Preparing for KDE Plasma's Last X11-Supported Release

#282

Plasma/Wayland Known Significant Issues[1] No ability to save and restore positions of native Wayland windows Real-fake-session-restored apps don't remember which virtual desktop their windows were on No full-screen aspect ratio correction "Spare Layouts" feature not implemented "Per-application Keyboard Layout" does not work No way to change the gamma or manually adjust the colors without generating or finding an ap…

Also, I still haven't found a clipboard manager that works normally on Wayland. And I rarely get it to recognize all my monitors first try. And it crashes semi-regularly. Not sure how much is inherent to Wayland vs Gnome, but life is way better since I upgraded to Xlibre & Cinnamon.

[flagged]

Re: Preparing for KDE Plasma's Last X11-Supported Release

#284

I installed Arch on my old Mac few months ago, alongside Xorg and i3, they were what I was used to before I switched to Mac about 6 years ago. Back then Wayland was a mess, so I never even bothered to check it out this time. However, few days ago my non-technical girlfriend wanted to use my laptop, I couldn't see her using i3 so I decided to install Plasma, a proper desktop environment. Lo and behold I couldn't launc…

I recently had opposite experience - I been using NixOS with X11+i3 for about 2 years and never had any significant issues beside some troubles with one Nvidia driver version, even most Steam games worked for me without any issues. But out of curiosity decided to give try Wayland+Sway. First Sway remind me that Nvidia GPU completely unsupported and probably wont work at all, but in really fix for that just to use some 'unsupported' flag to launch it. After that I found that displays fractional scaling only can multiply original resolution to bigger size so is no way I will able to set up my 3 different displays in way I would like. Then I found that Zoom app can't share display even if everything for that is provided and it thinks that sharing actually happen (it can share if used thought web-browser and it also some workaround with virtual camera thought kernel module and OBS). After that I found that Barrier app (that I been used to share cursor/keyboard between desktop&laptop) while has support for wayland it can't work with Sway yet and is no any real alternative.

For now I can deal with that stuff but it looks like more I use wayland more issues I see so not sure that I will able stick with it long term.

oh now I also has flickers with discord app

Re: Preparing for KDE Plasma's Last X11-Supported Release

#285
post #85

Earlier quoted context omitted.

>> Chrome's PIP is a stupid workaround for Windows and Mac because they do not have robust window management. What are you talking about? It's very convenient when I watch video while I do some work or entertaining thing on other web page or app. It's fine if you don't want to use it but many people do.

Yes, it's fine, but it shouldn't be necessary. If Windows and Mac OS just had native support for always-on-top windows, you wouldn't need it.

Windows has had native support for always on top windows for over 25 years

Re: Preparing for KDE Plasma's Last X11-Supported Release

#286

Earlier quoted context omitted.

my experience us sadly the opposite. when I'm recording gameplay with OBS with x11 and xfce I have roughly a 7-9ms frame render time and with Wayland and any desktop env it creeps up above 16ms, which means I can't get a solid 60fps. in all other cases other than gaming and recording, Wayland has been a delight.

Do you have "allow tearing" enabled?

yep and I've also tried disabling the compositior in KDE, which marginally helps but not enough.

Re: Preparing for KDE Plasma's Last X11-Supported Release

#287

Earlier quoted context omitted.

Also, I still haven't found a clipboard manager that works normally on Wayland. And I rarely get it to recognize all my monitors first try. And it crashes semi-regularly. Not sure how much is inherent to Wayland vs Gnome, but life is way better since I upgraded to Xlibre & Cinnamon.

[flagged]

Why do people only do this to the x11 guy?

I bet if you interrogated the wayland side to the same degree you would find similar, or worse. Afterall, who is more likely to be the bad guy? The corporations hurting linux by killing accessibility and interoperability, or the guy giving his spare time to save them?

Re: Preparing for KDE Plasma's Last X11-Supported Release

#288
post #122

Earlier quoted context omitted.

my experience us sadly the opposite. when I'm recording gameplay with OBS with x11 and xfce I have roughly a 7-9ms frame render time and with Wayland and any desktop env it creeps up above 16ms, which means I can't get a solid 60fps. in all other cases other than gaming and recording, Wayland has been a delight.

If your aim is to only record gameplay (and not stream), then there are far better Wayland-native tools like wl-screenrec[1] for wlroots-based compositors and gpu-screen-recorder[2] for others. The latter even supports live streaming, so could be used as a lightweight alternative to OBS. [1] https://github.com/russelltg/wl-screenrec [2] https://git.dec05eba.com/gpu-screen-recorder/about/

The 940mx on this laptop doesn't support hardware video encoding, so I'm basically forced to run everything on CPU. I do also stream so it's definitely a nice to have.

I could run the game on the GPU and leave more CPU for the desktop and encoder, maybe I'd be able to record and play on Wayland that way, but there's some additional drawing latency if I run the game on the GPU, the frame buffer gets sent back to the CPU before it's drawn on the display anyways.

As it's rhythm games I mainly play (ITGmania, Stepmania fork), the additional latency for getting the picture out on the display it's not really working out great for me.

Re: Preparing for KDE Plasma's Last X11-Supported Release

#289
post #182

Slight tangent but has anyone moved from AwesomeWM to a Wayland-based tiling WM? Interested to hear what people chose. I tried Sway for a bit and while it's not bad by any means it's a bit too unlike what I'm used to. SomeWM is an attempt at "porting" AwesomeWM to Wayland and looks very promising but not quite there yet (I couldn't get Vicious widgets working and not sure if supporting them is even a goal). I'm still…

(one of AwesomeWM core dev here) Vicious is getting quite old. We put tons of effort in AwesomeWM to be perfectly backward compatible all the way back to the 3.5.0 API (ok, 4.0 had documented breaking changes, but still had compat code to minimize the porting work), like bug-compatible level using a **ton of `if` in the code. I really can't blame any effort to implement wayland to nuke that compat code mess when it b…

Yes, when looking into it I realised how dated Vicious is these days. It goes to show how long I've been using AwesomeWM I guess because I think it was the shiny new(ish) thing when I first started using it. It doesn't seem like the functionality I want would be that difficult to replicate without it (famous last words) so I may just do that.

Thanks for all your work on AwesomeWM - whether I keep using it or not it has been a great experience!

Re: Preparing for KDE Plasma's Last X11-Supported Release

#290

Earlier quoted context omitted.

> doesn't allow windows to stay on top. Are you sure that windows that, without your consent, are allowed to stay on top and grab your input are a good idea? And spawned by Chrome? As if we hadn't already enough ad-ware, click-harvesters, and spoofed dialogs popping up everywhere! I know there is a couple of legitimate uses for this, but the ways it can be abused are vastly more. I think the sensitive default should…

Are you aware that if software misuses the capabilities its given by the system you can choose to stop using that software?

You can't do anything about a compromised app or JS from a random website. I always find it weird when people attack Wayland's security model, more isolation is obviously a great idea, as demonstrated by supply chain attacks in the recent decade.

It's that Wayland's design, implementation, their attitude, and everything else about it is terrible. It could have been implemented without compromising on features or convenience by explicitly specifying minimalistic controlled side channels in their security model from the start, instead of shifting it onto ad-hoc implementations. And of course the windowing system is already too large of an attack surface. Many people are thinking about going full Qubes due to the current realities, while the others live in denial and call even window isolation "paranoia". Fascinating.

Post reply on HN