Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Preparing for KDE Plasma's Last X11-Supported Release

blog.davidedmundson.co.uk

Post reply on HN
Print view View original

301–310 of 392 posts

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

#301

Post by garciansmith »

timhh wrote: post #230
The_President wrote: post #116

Earlier quoted context omitted.

The Bluetooth integration needs work - missing features such as "never connect automatically." Default lock screen experience still has a needless delay of 5 seconds when entering a wrong (even blank wrong) password, even on the first attempt. +1 on the gamma controls

> Default lock screen experience still has a needless delay of 5 seconds when entering a wrong (even blank wrong) password, even on the first attempt. I suspect that is not KDE's fault (or Wayland's) - it's probably PAM, which by default has a 2 second delay (+/- 50%). That default is extremely difficult to change, but you can configure it. See my instructions here: https://github.com/linux-pam/linux-pam/issues/778#i…

Wow, that has bugged me for years. Frustrating it's not easily configurable.

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

#302

Post by tmtvl »

falsaberN1 wrote: post #299
tmtvl wrote: post #241

Earlier quoted context omitted.

Have you tried LXQt? It made things easy for me when Plasma 6 broke a KWin script I was using to improve the multihead experience.

I use LXQt with virtual machines, is it good for using on bare metal too?

I only used it on bare metal, worked fine.

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

#303

Post by [deleted] »

KptMarchewa wrote: post #282
mminer237 wrote: post #195

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]

[deleted]

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

#304

Post by LtWorf »

bayindirh wrote: post #270
cmxch wrote: post #191

Earlier quoted context omitted.

It’ll be a better place when Wayland (and by extension Gnome/KDE) stops becoming a cargo cult hell bent on destroying X11/Xlibre.

X11 is not dying because of Wayland, it's dying because it became an unmaintainable code mountain over the years since it has been tried to be converted to something which is not designed for in the first place. ...and I'm saying that as a person who likes X11.

There is a maintained fork of Xorg that is banned by several distributions.

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

#305

Post by LtWorf »

toenail wrote: post #220
edumucelli wrote: post #211

Been using Linux as sole OS for 25 years now. I will stick to X11 no problems, I am sure it will be just fine for my usage. When we thought Gnome 2 was gone, MATE fork appeared, X11 will be there for a long time. I am also going through the struggle of porting a software I maintain (github.com/edumucelli/docking) to Wayland and it is awful: "this compositor do this part, that one does that part, no compositor does th…

I have a feeling xorg will still be there, when devs have moved on from wayland to the next new thing.

I'm still thinking wayland will be like pulseaudio. Going from "the future" to "the past" without ever being "the present".

I went from ALSA to pipewire. I tried pulseaudio but it never worked decently.

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

#306

Post by LtWorf »

bluGill wrote: post #40
skeledrew wrote: post #13

I've been using Kubuntu for the past 12 years without any X-related issue, and have and am actively working on stuff that requires it. I guess it's time to switch to another DE.

Most people are not you. A small minority do things that really need X. However there is good reason to say that the things that really need X are things you shouldn't do anyway. Meanwhile there is a slightly larger minority that need things that cannot be done in X. For the vast majority of people they cannot tell the difference, either works just fine. If there are issues they are tiny things they don't notice unti…

> Meanwhile there is a slightly larger minority that need things that cannot be done in X.

List of things that cannot be done in X:

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

#307

Post by TiredOfLife »

brooke2k wrote: post #83

in my mind unfortunately this basically destroys KDE's viability as a gaming platform. SO many older games just do not work properly unless run under X11 (hell, some newer ones too). XWayland is good for everyday applications but for games in my experience it too often falls flat.

SteamOS, and majority of the big gaming Linux distros like CachyOS and Bazzite default to wayland

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

#308

Post by LtWorf »

ceayo wrote: post #281
justinclift wrote: post #168

> 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.

The hoops: "select Xorg in the login manager"

Dude…

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

#310

Post by senfiaj »

kelnos wrote: post #212
MegaDeKay wrote: post #41

Earlier quoted context omitted.

I have a virtual pinball cab with two (and soon) three displays. Wayland really makes life difficult here because the software needs to always put the playfield on one display, the backglass on another, and the "dot matrix display" window on a third. That's a big no-no with Wayland. Fortunately KDE has window rules as a workaround. Sway and Hyprland allow similar rules. Mutter on Gnome has no equivalent. I'm guessing…

That's strange; you should be able to do that with the standard xdg-shell protocol, though I suppose it depends on the app's behavior. The app can tell the compositor which output to fullscreen each window on. Alternately, if it's using layer-shell windows, those can also be pinned to a specific output. If it's not layer-shell, and the windows aren't fullscreen, then yes... it's annoying. The xdg-session-management p…

>> It's all so frustrating watching the Wayland folks reinvent everything, poorly, and after more than 10 years it's still not there yet.

The whole project started in 2008, so almost 18 years.

Post reply on HN