Earlier quoted context omitted.
> what's so wrong with X11 so people need to replace it 1. Security - Any program using X11 can read keystrokes, passwords, or the contents of any other window. Fixing this would break all existing X11 applications. 2. Performance - X11's client-server model doesn't work with hardware accelerated graphics, requiring hacks to get around. X11 is basically stuck with this legacy. The ground-up re-design of X11 to fix th…
> X11's client-server model doesn't work with hardware accelerated graphics I really wish they would figure this out. It just feels like with Threadripper etc the time is perfect for a return of thin-clients/not-so-dummy terminals running X11-like applications over the network on a server. Especially for development where many of us are running under-powered laptops and could use the boost to compilation from a beefy…
KDE Plasma 6.8 Will Go Wayland-Exclusive in Dropping X11 Session Support
111–120 of 248 posts
Re: KDE Plasma 6.8 Will Go Wayland-Exclusive in Dropping X11 Session Support
#112Earlier quoted context omitted.
KDE on Linux is the way. Extremely Stable.
Plasma is KDE. What are you trying to say? Edit: oh, I guess swapping FreeBSD for Linux? Yeah nah, I don't know GP, but I suspect this isn't a reason for them to switch OS just to solve this.
Re: KDE Plasma 6.8 Will Go Wayland-Exclusive in Dropping X11 Session Support
#113That's extremely disappointing. Wayland has gotten a lot better but there are still many, many instances where I have to switch into an X11 session in order to play certain games (especially older ones). I am a huge fan of KDE but this may actually force me to switch to something else :(
Re: KDE Plasma 6.8 Will Go Wayland-Exclusive in Dropping X11 Session Support
#114Earlier quoted context omitted.
I think it might be more of a Discord problem. I've experienced "a few weird crashes" on Windows, Mac, and Wayland GNOME. Windows being the most problematic in general.
idk how we can blame some JavaScript and html inside Firefox causing a Wayland crash as Discord’s fault. They’re like 9000 layers of abstraction away from whatever SIGSEGV caused the crash
I assume others are talking about the standalone client. Which, to be fair, I assume is also an Electron app but that's Chromium, not Firefox.
Re: KDE Plasma 6.8 Will Go Wayland-Exclusive in Dropping X11 Session Support
#115Earlier quoted context omitted.
I could set my screen to 75%, not really 73% but close may be?
How did you do it? It doesn't allow any value below 100%?
I don't know whether GNOME supports anything similar, unlike KDE they really don't like giving users very many configuration options.
Re: KDE Plasma 6.8 Will Go Wayland-Exclusive in Dropping X11 Session Support
#116Earlier quoted context omitted.
I think it might be more of a Discord problem. I've experienced "a few weird crashes" on Windows, Mac, and Wayland GNOME. Windows being the most problematic in general.
idk how we can blame some JavaScript and html inside Firefox causing a Wayland crash as Discord’s fault. They’re like 9000 layers of abstraction away from whatever SIGSEGV caused the crash
I don't see anyone talking about a Wayland crash, it's about Discord crashing.
Re: KDE Plasma 6.8 Will Go Wayland-Exclusive in Dropping X11 Session Support
#117I tried Wayland earlier today on my home lab with Plasma and FreeBSD. It seemed pretty great for a bit and ran my monitor at 120Hz. Until it hard crashed my machine after I opened discord in firefox. Konqueror crashed on opening.
Yes, Wayland is broken by design, since a single crash takes down the whole desktop; unlike other Wayland complaints, this one fundamentally will never be fixed. This is unlike X11, where it was very common to recover from the inevitable single-component crashes.
https://www.phoronix.com/news/Qt-Wayland-Compositor-Restart
As I understand it, in Wayland all the necessary state lives client side, so a client is free to wait around and connect to a new compositor. The compositor might not place the windows exactly where they were before, but there is nothing architecturally that forces clients to crash if the compositor crashes.
Re: KDE Plasma 6.8 Will Go Wayland-Exclusive in Dropping X11 Session Support
#118Well, it's been a nice run. I've loved KDE since 2008 because it provided a lot of useful features (though its advantage over GNOME 2 was minimal at the time; it only became the obvious choice with the self-inflicted fall of GNOME 3). But if KDE is no longer willing to provide the single most important feature of all - actually working in the first place, rather than just denying that bugs exist - I guess I'll have t…
Re: KDE Plasma 6.8 Will Go Wayland-Exclusive in Dropping X11 Session Support
#119Re: KDE Plasma 6.8 Will Go Wayland-Exclusive in Dropping X11 Session Support
#120Half of the software I use on a daily basis (lots of old SunOS-era custom data reduction software) doesn't work under Wayland. Guess I'll finally flip my daily driver over to *BSD.
FreeBSD does have Wayland but it's not ready for prime time