Wayland is pretty darn great nowadays, hell Iβm running KDE and got HDR on my desktop; havenβt had any odd goings on since 2023 (though nvidia is still meh)
Itβs funny. I used gnome for a long time, and after I fully switched to Debian, I didnβt have any problems with my nvidia card with gnome + wayland. But I switched to plasma recently, and itβs janky. I figured out my vsync issues, but it still runs a post when I wake it from sleep, which just defeats the purpose of sleep mode. I might as well shut it down every time Iβm done using it like itβs 1997.
But I started using X + KDE, and most of my problems went away. Still takes forever to wake from sleep. But thatβs it, really.
I still havenβt been able to get wake from sleep working in distros with Wayland on my PC with an NVIDIA GPU. Tried in EndeavourOS and Garuda. It crashes trying to wake from sleep every time. Iβve tried everything in the arch wiki and search engine results like modifying config files and whatnot, no dice.
LMDE Cinnamon user here. Thereβs a setting in the power options that tells the computer to switch to hibernate if it remains in suspend for a certain amount of time. Hibernated computers suspend to disk rather than RAM and are basically switched off, so need to POST to come back online.
It took me a while to find that setting, and it might be the same case with whatever youβre using.
Whatβs more, it only took effect if I used the GUI to put the computer into suspend mode. I usually use a keyboard combo to suspend the computer at night, but occasionally Iβd use the GUI and come back in the morning to a hibernated computer.
Thought Iβd been taking crazy pills or that there was something wrong.
My main gripes are that inconsistency between suspend methods and also that thereβs no setting for how long to stay in suspend before hibernating. I have no idea if thatβs a UEFI thing or something that could be set elsewhere, but Iβd probably use that feature if I could set it.
As it is Iβm giving the hybrid option a try. Basically it suspends like normal, but also sets up a hibernated restart for if the power goes out. That hasnβt happened yet, so can only assume itβll work when the time comes.
Late edit: The delay between suspend and hibernate is set in /etc/systemd/sleep.conf with the setting HibernateDelaySec=. Manual page reading is required, but even so, this feature is not well documented there or out on the Internet.
There may be syntax available to specify other units of time with a suffix. For example, my computerβs related SuspendEstimationSec= option is given as 60min in the example and not 3600.
Years ago Nvidia employed a developer who fixed incompatibilities with their proprietary driver. He looked at what caused the issue and even had the driver fixed when Plasma exposed a driver bug.
Then Nvidia decided not to continue this and most KDE development now happens on hardware supported by FOSS drivers. Valve investing in KDE because of Steam Deck and its FOSS Radeon drivers underlined this trend.
HDR is pretty much impossible in X11; especially since there are 0 plans for it, and no plans to do anything than bare minimum updates
It really is pretty great nowadays. I always had both my laptops with fractional scaling and currently it all seems to work very well, no more weird renderings anywhere. And a greater thing, I had a external screen I left unused for multiple years because it needed to be used with a different fractional scaling than the laptop it was connected and now it just works and I can finally use it. Itβs nice. I donβt have hdr needs but color management seems to be properly in place now and the bugs I had previously with it are also gone - like it did something weird on some video recording app and some weird stuff with that thing that changes the color of the screen when itβs night - it all just works now.
Works greatβ¦ until you realize your GPU isnβt liked by Wayland when you have more than one monitor lol. Then Wayland is uninstalled and you go back to Xorg or XFCE.
Itβs weird, had this issue with multiple monitors where wayland is either a glitchy refresh rate mess or just doesnβt recognize at all. Nvidia, amd, discrete or dedicated, native driver or oem driver: theyβre all finicky under wayland when multiple monitors are used.
They are called compositors, but they are not as good as X WMs IMO. Iβm keeping an eye on them tho.
It still bothers me how toxic the hyprland devs behaved last year. Keeping an eye on that too π
compositors, but they are not as good as X WMs
Interesting. Iβm curious about what seems to be missing in your use case?
Depends things like shaped window borders for theming, title bars in hyprland, effects, pagers, some automation options, etcβ¦
What I generally miss in Wayland is better mouse automation support, Java support, the ability to have multiple mouse cursors and assign them to different input devices.
Depends things like shaped window borders for theming, title bars
All possible. X had some age-old protocol enabling oval and whatnot windows and noone ever used it, whether you use CSD or SSD you can paint with alpha and say βnope, that mouse click wasnβt for meβ. So even if logically all windows are rectangular because that makes sense because textures are rectangular and you really donβt want to complicate things at that level, UX-wise you can have fractal borders if you really want.
in hyprland,
β¦anything βin hyperlandβ is a hyperland problem, not a wayland problem.
effects, pagers, some automation options, etcβ¦
All Things compositors can do.
What I generally miss in Wayland is better mouse automation support,
Faking input devices is compositor responsibility, for obvious security reasons.
Java support,
As if Java and X work well together.
the ability to have multiple mouse cursors and assign them to different input devices.
Weston does this, protocols support it, I donβt think itβs much of a priority for other compositors. The most common multiple pointing device configuration is to have both devices control one pointer. My tablet works and the tip is properly analogue thatβs plenty of functionality for me (dunno if tilt works by now, blender doesnβt use it anyways).
Not OP, but modularity. An X11 WM is just a WM. You can choose compositor, bar, shortcut daemon, etc. With Wayland, a single implementation holds most of that, and more. If you need a specific feature from your display server, you are stuck on WMs that support it. This has forced me to use KDE for Wayland on my main workstation, and although it works well, itβs not my prefered WM/workflow.
Alongside that, no clones of several X11 WMs exist. bspwm for example. Riverwm exists, but has major limitations, and the workflow isnβt the same.
In practice wayland is way more composable that one would, at first glance, expect, and even accidentally so, because DEs are made up of different components often sharing common interfaces, so the cosmic task bar will run under the sway compositor and suchlike. Not just βrunβ as in βnot crashβ but βactually display tasks based on information from the compositorβ. I expect further standardisation there once the ecosystem matures a bit more. Just because you can include a task bar directly in the compositor process doesnβt mean you have to, and the same goes for window rules, window decorators, whatnot.
Wayland? Does it have colors, window position memory or hotkeys yet? Or are they still in the βwe only sell an idea, you do all the workβ vaporware phase?
Wayland seems to have problems showing colors properly. I was trying to fix this issue myself a couple weeks ago.
Colors in Xorg and Windows(gross) show properly, Wayland always looks dull and muted in comparison. Switching color profiles didnβt change anything.
But hey, maybe thereβs a fix I havenβt tried yet that worksβ¦ I sure would hate to be proven wrong! No seriously, if someone has a fix for the dull colors I would likely start using Wayland again.
org.freedesktop.portal.GlobalShortcuts allows apps to request a global shortcut binding from the compositor. They canβt just log all your keystrokes globally because thatβd be a keylogger. Also thereβd be no way to resolve conflicts between shortcuts.
If your app doesnβt support that then blame the app, the interface has been out for a while, and compositors have supported it for a while.
kinda sad that users canβt (afaik) enable global keyligging for all applications. I totally understand why itβs a bad idea, but itβs just so much simpler to work with.
Wayland has a notable piece of βbut Elon can do no wrong!β cult thing going for it.
Youβre aware you just called the x.org developers Elon, do you?
x.org is just as much a freedesktop project as wayland is or dbus. Or, before they spun off, flatpak. Wayland grew out of the x.org devs deciding that the thing has become literally unmaintainable. The recent pain is caused by downstream devs (including kde, gnome etc) noticing quite late that the x.org people were actually being serious, if they had provided input earlier then the gazillion of protocol extensions that people are whining about now (such as global hotkeys) couldβve been finalised literally ten years ago.
x.org still gets a couple of patches β for xwayland. At some point theyβre going to rip out the whole graphics driver stack and replace it with a wayland compositor, that compositor plus xwayland will be the X server. Youβre free to build a PC with a good ole S3 Trio but donβt expect future x.org releases to support it.
Hyprland bloated? Huh?
Bloat-ware
If you want a lightweight compositor, then boy do i have just the right thing for you
Itβs 3x smaller than dwl! Perfect! (and can only run one program by the ttyβ¦ but no bloat!!!)
