Live data from Hacker News

KDE Plasma 6.0 Is Enabling Wayland by Default

phoronix.com

91–100 of 202 posts

Re: KDE Plasma 6.0 Is Enabling Wayland by Default

#93

I enabled wayland recently and there’s been a lot of annoyances to the point that I wonder why I bother considering X11 works without these issues. For example: * Chrome needs a bunch of extra flags to launch in Wayland mode * Firefox needs extra flags to launch in Wayland mode * Xwayland is just broken on Nvidia with both sides refusing to compromise (implicit vs explicit synchronization - Nvidia refuses to add impl…

Maybe Firefox needing flags is a per-distro thing? I’ll have to check and make sure but I think Firefox works with Waylad sessions out of the box on my Fedora laptop. That’s using an Intel iGPU instead of an Nvidia GPU though so maybe that’s also a factor.

Re: KDE Plasma 6.0 Is Enabling Wayland by Default

#94
post #4

KDE is pretty feature-rich, but it is just ugly. Look at the poor use of spacing/margins, the ugly black & white icons, the ugly font, the square edges, and just the overall look & feel. It needs a major face-lift. I dislike the attempts to dumb down GNOME but KDE being ugly makes it really hard to switch to.

Even as someone who’s using KDE on one machine I tend to agree. Things can be polished up a bit by changing themes and font settings but that only goes so far — it can’t do anything about widget arrangement and the general flow of UI design in KDE apps which I find somewhat awkward.

Re: KDE Plasma 6.0 Is Enabling Wayland by Default

#97
post #62
post #39

Earlier quoted context omitted.

I'm surprised whenever I hear Wayland works flawlessly for someone, since I've tried using it on the NixOS unstable channel for a few releases now, and there are a few major bugs that make it unusable for me. A show stopping one is that the bottom panel is stuck in the middle of the screen, with no way to move it down that I could find, and clicks register in completely different parts of the screen. It's difficult t…

Using an unstable channel and being surprised at bugs is kind of your own making... I also use Wayland + KDE full time and have not experienced any of the issues you described.

NixOS unstable is more of a rolling release than an equivalent unstable version on other distros.

I've also reproduced these issues on Void Linux, and on 3 separate machines. So it's not a hardware or distro specific issue, nor particularly rare.

Re: KDE Plasma 6.0 Is Enabling Wayland by Default

#98
post #10

> - Plasma's start time is up to a few seconds faster. On the one hand, this is impressive. On the other, this is a vague indictment of modern software. Plasma logs you in, draws a background and the taskbar thing across the screen. There shouldn't be seconds involved in that to shave. This must be a recurring feature, every few years someone goes through and fixes up load times.

They mentioned that the culprit for those additional load times was loading all the search backend for their application launcher which they deferred to the moment when there was actually the first search query (still shouldn't take multiple seconds)

Baloo (KDE) and Tracker (Gnome) are typically the first things I disable on any Linux desktop install that requires either of them. Tracker is hot garbage and a pain to disable. Baloo at least is granular and configurable enough to turn off file indexing without breaking search on the entire DE.

Re: KDE Plasma 6.0 Is Enabling Wayland by Default

#99

Wayland has a few glitches, but in general it's good to use. For example, it doesn't have an API to get current cursor position (which breaks keepassxc's browser popup, goldendict's query popup), an API (which most compositor implements) to get current window state, which makes me unable to find an alternative of autokey (kwin script can do this, though, but it lacks the ability to execute arbitary commands..). On th…

Lack of screentearing is the killer app for me. The only GUI programs I run are Firefox, a terminal (foot or wezterm), and video games, so everything works and works better (I dont want screentearing for any of those 3) for me under Wayland.

I just run Compton as compositor and the tearing is gone, which makes hard to move to Wayland and having to solve issues that I currently don't have.

I used it first with XFCE and later with i3.

Post reply on HN