Wayland has still no way to set DPI of multiple monitors. The fonts look terrible on it. I had to move to KDE Plasma on X11 ever since GNOME started forcing Wayland on us.
This is a real shame. I'm using X11 still because Discord doesn't work properly with Wayland, and the alternative (Vesktop) doesn't support keybinds when the window isn't focused. Since my distro (Arch) doesn't support holding back packages, I guess I'll have to switch distros entirely so that my Discord setup stays working. :/
Which distro supports partial upgrades? AFAIK no major distro supports it.
The only difference between Arch and any other regular distro is simply that in Arch there are no major upgrade versions, so any breaking changes you have to perform them manually. Period.
In the rest, they do it for you. But they update key components as well and/or stop getting updated at some point (same as not updating Arch).
For example, I am a happy Fedora user, but I don't get why they don't upgrade the Plasma or Gnome version in the same release but they do upgrade the kernel, when the kernel update may bring more breaking changes...
This is an interesting move, and I wonder what that means for accessibility in Plasma. Wayland simply isn't designed with accessibility in mind, so each compositor ends up having to implement their own non-standard APIs. I know virtual keyboards are lacking for example.
That'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 :(
Wayland is missing one thing still for me. Perhaps someone can tell me there is a way to do this:
1. ssh into a machine with a running session
2. start (something) that lets me remotely connect to it
Right now I have two working solutions for X11 (x11vnc, freerdp-shadow) but zero for Wayland. I think this is intentional because the venn diagram of remote-access-tools and malware has a large intersection, but it's very useful too!
I live in a cave and am not a system programmer -- what's so wrong with X11 so people need to replace it with something else instead of improving it?
Or, what's so wrong with anything so people need to replace it with something else instead of improving it?
Let's say I'm an old man favoring improving existing stuffs instead of starting from scratch. I like debugging and wish to work as a sys programmer specialized in debugging and fixing/improving legacy codebase. But again I'm not really a sys programmer so I'm probably on the wrong side.
Well, 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 to hunt for a new DE.
It looks like the only serious possibilities are:
Cinnamon - my gut says this might have the most users? Often cited as the reason to use Linux Mint by people who don't know the difference between a distro and a desktop environment.
LXQt - apparently has stabilized enough to obsolete LXDE (hopefully it isn't being developed by headless chickens like GNOME and now KDE)
MATE - why must there be so many GNOME forks? (I know why) ... does this one even have anything to distinguish it?
Xfce - the longest stable history as its own thing
(all other DEs are known to lack some combination of widespread support and essential features; there are a handful for which it is possible that support will arrive but it is not the case yet, and they will still lose on the "weight of history" stability criterion)
MATE is specifically a fork of GNOME 2, and works pretty much exactly like it did. there's a similar fork of KDE 3 called trinity that you might want to check out
Half 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.
This is interesting to me, because SteamOS, so Steam Deck uses KDE. I really wonder how they are going to tackle going from X to Wayland on 4 million machines, and what that will bring.
I'm on Kubuntu and use xpra, xdotool and a few other x-specific things fairly regularly. Wondering what this means for me as I'm very reluctant to lose my capabilities. I'd rather freeze my updating indefinitely.
At least XWayland will still be supported. Native Wayland windows don’t support controlling window position or living through transparent windows. This is important for apps that provide overlays.
43 comments
[ 2.5 ms ] story [ 67.6 ms ] threadI guess I have to buy a 4K monitor in future.
The only difference between Arch and any other regular distro is simply that in Arch there are no major upgrade versions, so any breaking changes you have to perform them manually. Period.
In the rest, they do it for you. But they update key components as well and/or stop getting updated at some point (same as not updating Arch).
For example, I am a happy Fedora user, but I don't get why they don't upgrade the Plasma or Gnome version in the same release but they do upgrade the kernel, when the kernel update may bring more breaking changes...
Until it hard crashed my machine after I opened discord in firefox. Konqueror crashed on opening.
https://news.ycombinator.com/item?id=45925950 GNOME 50 completes the migration to Wayland, dropping X11 backend code (linuxiac.com)
12 days ago | 185 comments
1. ssh into a machine with a running session
2. start (something) that lets me remotely connect to it
Right now I have two working solutions for X11 (x11vnc, freerdp-shadow) but zero for Wayland. I think this is intentional because the venn diagram of remote-access-tools and malware has a large intersection, but it's very useful too!
1. KRdp (preferred): a RDP server for KDE Plasma.
2. KRfb: a VNC server for KDE Plasma.
Both should be able to be configured to support your use-case. If they can't, please file bugs!
Or, what's so wrong with anything so people need to replace it with something else instead of improving it?
Let's say I'm an old man favoring improving existing stuffs instead of starting from scratch. I like debugging and wish to work as a sys programmer specialized in debugging and fixing/improving legacy codebase. But again I'm not really a sys programmer so I'm probably on the wrong side.
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 to hunt for a new DE.
It looks like the only serious possibilities are:
(all other DEs are known to lack some combination of widespread support and essential features; there are a handful for which it is possible that support will arrive but it is not the case yet, and they will still lose on the "weight of history" stability criterion)And FreeBSD packages are rolling so I'm normally on the latest and greatest.
In a Qemu VM a testing installation of Plasma+Wayland is dog slow and crashes the whole system. Using the workaround for X it runs faster and stable.