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.
You must log in or register to comment.
Every time I build a new box or do an upgrade, I try selecting Plasma on Wayland from the login screen. Every time it doesn’t work, I select X11, and never think of it again for another six months to two years.
I just need steam\proton\wine to support native wayland and then I’ll remove xwayland from my system, can’t wait
i’m on hyprland though
urxvt, bspwm, sxhkd, and many small utilities that I built my desktop with. It’s hard to reproduce the same setup.
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)
AwesomeWM, and xdotool.
That’s it. Oh and x-eyes of course
New hyprland patch can do pretty much all the xdotool stuff since they added a send key to window thing
There’s ydotool.
I find it’s not as reliable in targeting inputs, and you sometimes need to set the XDG_RUNTIME variable yourself.
wtypeis 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.
I don’t think that was entirely serious…
You might be interested in river as a awesome replacement:
Appreciate the link, and I don’t mean to sound so ungrateful, but that extensive README contains everything except what exactly
riveris. Is it a desktop manager? A standalone compositor? What does it fix? What does it replace? etc.Edit: Oh, it’s a tiling window manager, and all WM in wayland have to be compositors.
Have you tried ydotools, which works on both Wayland and X?
deleted by creator
XFCE, mostly.
I’m too dumb to set up Wayland on Nvidia and honestly don’t really care to. My laptop has an intel haswell-ult so it works with Wayland ootb and all the apps I use on it (literally just calibre, falkon, lapce and libreoffice Writer) work fine.
Edit: spelling
To me it’s mostly the lack of feature parity in kwin between x11 and Wayland, specially lack of global menu support for GTK apps in Wayland.
keepassxc’s autotype
also, nvidia
KeepassXC work fine on Wayland with xwayland
only with other x11 applications
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
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.
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.
the nouveau driver works fine except when it crashes for no clear reason after some hours of usage
Even on X11? I tried it on Wayland months ago to see its state and it was generally fine except gaming. Though the results still might depend on the card in use I guess.
Even on X11?
yup. i think it had something to do with video calls or screen sharing, which are essential at work
Xfwm. Taskbars are now wayland, but don’t autohide without the compositor supporting it.
autokey
I accomplish the same thing with compose sequences, and by binding a keyboard shortcut in my desktop to call a script with
wtype. It’s not a cross-compositor solution though, as you’d have to manually setup binds in each of them.I don’t see much hope for this one-to-one unfortunately.
Check out xremap https://github.com/xremap/xremap
ydotool iirc
Same camp as wtype, you have to bind something to exec it.
Gnome. No shell restart on wayland, and not planned.
Pardon?
GNOME defaults to Wayland. GNOME 49 is going to remove X11 support all together.
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=x11environment variable to be set before they’ll function.I don’t have that variable set on my environment, but perhaps it’s due to my running PCSX2 as an AppImage?
I don’t have that variable set on my environment, but perhaps it’s due to my running PCSX2 as an AppImage?
True. AppImages are often convenient because they run w/o requiring any env settings.
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.
