wayland didn’t remove spacebar heating. Wayland removed the spacebar
So you’ll always get heating, without having to press the spacebar, no?
Betterbut only if you convince yourself you never need to type spaces ever again
Nah it’s fine now. We have rebindings right in the compositor. I can just use the space-key instead.
Took a while, but Wayland is basically at a point now where it generally just works. I’m glad I don’t really need to deal with weird tearing issues or the X server not starting for whatever esoteric reason after a driver update anymore.
Wayland is a protocol, and major desktop versions like gnome and Kde implementation sucks balls…
Desktop crashes, oh there goes all my applikations that I started, gnome can’t keep up with switching workspaces because doesn’t fucking register the release key event. Fuck me dude xorg had no issues with switching windows or crashed barely crashed, gnome crashes 2 times a day. Oh sorry dude you want to use a custom screenshot tool, sorry dude, can’t allow that, have to do some weird workaround.
Oh you want change keybindings, no sorry dude can’t don’t support it.
Oh you wanted to automate window/workspace switching via scripts, you have inject fucking JavaScript into our runtime to query windows ids and state…
Jesus what joke of an implementation, it’s the anti theist of Linux. Everyone got fooled and allowed GUI developers implement the rendering backend…
And the best of all: hey do you want make software for Linux, sorry you app doesn’t work in KDE because the whole implementation of functionality you’re using is different from other Wayland implementation, can you plz fix in kde and gnome?
deleted by creator
Yeah sure, if you don’t anything with it
deleted by creator
I use an Nvidia GPU with GNOME and Wayland and everything works great for me.
Yep, but my laptop I use the igpu
deleted by creator
Tbh I dont enjoy any OS I actually hate computers, they are in the way of what I’m trying to do, it’s just an interface to do something else. But when the interface is effecting your experience to much it’s just sad.
Unreasonably funny
I’m using gnome rn and it doesn’t crash much anymore. When I used xorg, there’d be crashes that brought down the entire desktop (or the computer as a whole) too. Also, generally every time I have a crash now it’s from using xwayland to play a game and having certain extensions enabled at the same time (although those issues seem to have disappeared recently too). All the other issues I either don’t care about or are supported with some extra work. For gnome, some of the issues are just because they have a phobia of exposing settings and you need to use stuff like dconf to deal with it.
Jesus what joke of an implementation, it’s the anti theist of Linux. Everyone got fooled and allowed GUI developers implement the rendering backend…
As you mentioned earlier, it’s a protocol. Implementation issues are due to how gnome/kde/whatever implemented their compositors. I think it’s pretty much standard for Linux given that stuff like systemd and flatpak exist. If you want to use something more traditional unix-y, maybe you should use a bsd or solaris derivative or something.
I still use x11 with suckless dwm, but for work I’m forced to use Ubuntu 25.10 gnome shit. It’s a sad state. Gnome owns all the process you start via gnome, that is why if gnome dies all the child process es dies as well, genius. Because the buggy mess, doesn’t critical errors and never will have…
I don’t know how you use gnome, if it doesn’t crash for you, fine, good. But that’s not my reality, it can crash because I open the laptop screen while being on an external monitor. It can crash because I’m screen sharing, it can crash because some software I used froze, it can crash for random reason (doesn’t happen often, but still annoying).
I still use x11 with suckless dwm
I can tell from the way you write, no need to mention it.
No worries, I would like you to have it in written statement.
I think it’s pretty much standard for Linux given that stuff like systemd and flatpak exist. If you want to use something more traditional unix-y, maybe you should use a bsd or solaris derivative or something.
That’s a pretty toxic take, much in the way like Windows does things.
I mean the person I’m responding to seems to want a traditional Unix experience given how they’re talking (and given they use suckless software). Linux generally isn’t that, and it never really has been (or at least hasn’t for many years). If you want something more traditional, there are a bunch of available options like the BSDs. If you insist on using Linux, you can use distros that don’t use Wayland, systemd, flatpak, etc., but the support for them is lower, and if you need to use something that isn’t packaged for example you’ll need to deal with getting it working with e.g. systemd on your own. A bunch of software makes assumptions that stuff like systemd is now included if you use Linux. I’m currently using a distro without systemd and am seriously considering swapping back to my old one because it’s such a hassle.
Admitedly, i’m currently in a “take a step back” phase and like to see software breaking. It’s healthy for the linux ecosystem if things break.
And in software that is a hassle (usually Gnomes on a not-Gnome environment) either the software itself is really good and somebody made a patch or packaged a old working version already. Or i look for something simpler to do the same.
kde crashes don’t exit your applications, kde crashes everytime my pc goes into sleep mode and it preserves the apps
Desktop crashes, oh there goes all my applikations that I started, gnome can’t keep up with switching workspaces[…]
GNOME, found your problem.
I can take screenshots or rebind keys on KDE, all of that without session losing crashes.
All you are describing simply doesn’t happen in KDE, and GNOME is notoriously bad at handling crashes, so go complain about GNOME rather than wayland as wayland is clearly not the culprit.
Damn that 30 year old protocol for sneaking up on people.
The title of this article is a refreshing take on the Wayland vs X thing. I’ve had Wayland on my lunar lake PC and battery life nearly doubles with Wayland in-use. I can also have multiple monitor and resolution setups without issue at all. I had to use X unfortunately for a presentation I was recording and everything was just scaled terribly wrong.
I’ve had þe opposite experience. I have a laptop I ran X on for years. Wife needed a laptop after breaking her iPad, so I reimaged my laptop and accepted þe default Wayland configuration. Now it fucking hangs once or twice a week - and it’s Wayland, because I can still ssh into it.
I’m going to configure it to use X and uninstall Wayland.
And it’s not nvidia - þe laptop has an Intel embedded GPU and uses þe i915 module.
Worked perfectly fine under X for years; regularly hangs under Wayland.
I’ve discovered this once on my own, I had a complex control remapper and that I had been evolving into a horrific bash hydra of hacks over many years. I briefly tried to get it working when I switched to Wayland. I don’t remember which component broke me, but it went something like this:
“Hey, I wonder why doesn’t this thing work in Wayland. I wonder if I can whip up a pale imitation.”
10 minutes of stack overflow searches later…
“Oh… oh no.”People use windows because it has decades of backwards compatibility sort of.
That should be:
People
useused windows because ithashad decades of backwards compatibility sort of.Nowadays: it has current compatibility sort of.
Microsoft is a mess now, so it’s no surprise that their current Windows version is also a mess.
For the most part they just didn’t update.
See XP usage.
These just-so stories are easy to write, harder to write convincingly. I gladly use Wayland because I’m in a mixed-DPI setup, and didn’t rely on anything that broke. But loads of people are still pissed off due to persistent incompatibility.
The way Wayland made everything the responsibility of non-existent compositors really fucked over anyone not using GNOME or KDE, basically.
It’s fine. There’s still some quirks with Wayland I don’t like. Either having to be in a game or have Discord focused in order for push to talk to work for example. Some mouse constraint issues with certain games that for whatever reason KDE has been able to figure out but every other wayland compositor hasn’t.
it’s absolutely not fine. You as a user, should be able to access the content of any window on your machine.
By that, do you mean that every program running with your user privileges should be able to access the content of every window on your machine?
Sorry I have never looked into the specifics, but I read some way for flatpaks to listen for specific keybinds even in the background, it’s mostly a permissions thing IIRC.
Sorry I’m assuming bazzite Fedora as well.
tried it on arch, nixos, fedora both native pkgs and flatpaks. no dice. push to talk only works when either in a game or when discord is focused. all via various wayland des/wms be it KDE, Niri, Sway, Hyprland, etc
Wayland is pure trash. It’s written like an Android App. Just short-sighted garbage.
Who said it will kill desktops? X11 desktops still work fine. And some specific tools like screen recorders are not workflows. Wayland had issues with some tools, those get solved and some people use it and are happy with it. Other people don’t use it and are equally happy. Why try to invent some apocalypse when there’s none?
