For me AutoKey is absolutely essential to my workflow. I have tons of text expansions and shortcuts to “remap” keys. E.g., respectively, typing dAt
expands into 2025-05-08, 13:47:40 CEST
, and pressing alt + k
simulates the arrow down key.
Secondly there’s XScreenSaver which has so many wonderful (mathematical) visualizations that it would be a damn shame if these eventually get lost as Wayland gets more adoption.
None of these have Wayland alternatives as far as I know. For text expansion there’s Espanso, but it doesn’t support keyboard shortcuts yet.
urxvt, bspwm, sxhkd, and many small utilities that I built my desktop with. It’s hard to reproduce the same setup.
I’m using Wayland right now, but tentatively.
Right now there’s an issue in WoW where sometimes when I move my mouse and left-click, the camera jumps to a different position, usually trying to look up.
Only happens on Wayland and it’s fixed temporarily by switching between windowed and fullscreen mode. The problem comes back sometimes when alt-tabbing and refocusing the game.
There was a bug in KDE recently where some menus weren’t properly appearing on Wayland, but that seems to have been fixed after my latest update.
Stumpwm. The most ergonomic tiling window manager I know, fantastic configurability like emacs.
Couldn’t use xset to manually set some monitors to standby So I searched how to change it back to X.
Also you couldn’t set display variable to another computer’s ip address (a windows one running xming)
Absolutely none. On my setup everything runs fine either natively or with Xwayland.
Yeah, I think my sway config is around five years old now. The Wayland experience hasn’t been entirely without warts, but as someone who kind of just uses the desktop to drive a browser and a bunch of terminals, there’s not a whole lot of problems to run into either.
keepassxc’s autotype
also, nvidia
There are still some quirks but it’s been generally fine for me with Nvidia, almost a year now.
i heard about that. sadly my gpu is so old the latest driver that supports it is the 470 driver
Well, you can hold onto that GPU for a little longer with X11. But it seems you’ll need an upgrade some time later. Though if you don’t game (aside from FOSS ones), Nouveau driver should do the job for your daily needs. However, it still needs time for Wayland.
Hey, I’m in the same boat. Gigabyte GTX 670. Wayland was a sluggish mess, and same goes for nouveau with X11.
I bit the bullet after eight months of running Arch like this, and experimenting around with newer iGPUs in laptops, and bought a new radeon finally. Time to retire this ancient piece of tech.
670 is still better than nothing.
Hopefully it can find its way to someone else’s home on the cheap and still give them plenty of years of fun.
For me is the lack of virtual displays is Wayland.
I’m using a 49" monitor (with i3) and split it into virtual monitors/displays. For some tasks two displays are good, for others three, and all doesn’t need to be the same size.
The reason for not using i3 splits is that many programs have fullscreen functions that I often use.
Watching a movie is one example, where I have a script that automatically calculate the optimal width without borders and gives me an extra virtual display beside with whatever’s left.
Hyprland can tell a window to be in fullscreen when in fact, it’s not (it’s called… Fakefullscreen). I binded it to shift+f11 and its become part of my workflow, lol
Uhhh, I’ve been dreaming if this and now I’ve got it!
x11
i am not gonna go with any of the idiotchanges. lost me at systemd, flatpaks and so on
moronic people like lennard poettering and everyone at red hat are a desease.
i will start downgrading Iinux PCs to Windows10 just to not have any of the broken linux promises.
do ONE thing but do it right.
Oké grandpa, its time to take your meds
RHEL10 is probably a month away from being the first distro to ship without even the option of using Xorg. It is not even going to be in the repos.
Other distros will follow their lead.
If you are a fan of x11, not liking Red Hat makes sense.
Xfwm. Taskbars are now wayland, but don’t autohide without the compositor supporting it.
AwesomeWM, and xdotool.
That’s it. Oh and x-eyes of course
There’s ydotool.
I find it’s not as reliable in targeting inputs, and you sometimes need to set the XDG_RUNTIME variable yourself.
wtype
is much better at this, but is limited to keystrokes
what do you use x-eyes for?
👀
https://www.x.org/releases/X11R7.5/doc/man/man1/xeyes.1.html
Xeyes watches what you do and reports to the Boss.
Wayland’s been my daily driver for a few years now, mostly without incident. However, occasionally certain applications (Ryujinx and pcsx2, predictably) require the
GDK_BACKEND=x11
environment variable to be set before they’ll function.Glxgears. :P I’m on wayland for a least 4 years
Hilarious. Is vkgears a possible replacement in your workflow?
Easystroke https://github.com/thjaeger/easystroke, please, please, please somebody pick the project, I’ll gladly pay a license to use it.
https://github.com/jersou/mouse-actions
It’s recommended by the easystroke dev too: https://github.com/thjaeger/easystroke/wiki
Network transparency
Gnome. No shell restart on wayland, and not planned.
Pardon?
GNOME defaults to Wayland. GNOME 49 is going to remove X11 support all together.
Only new version default wayland, my version not. And not update. Until shell restart on wayland, not use wayland.