Skip to main content


Which X11 software keeps you from switching to Wayland?


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.

in reply to arsCynic

Talon voice.

Autokey.

Anydesk. (although rustdesk is probably going to replace that)

Talon voice though. I'll need X11 for the rest of my life.

in reply to arsCynic

AwesomeWM, and xdotool.

That's it. Oh and Xeyes of course

This entry was edited (1 day ago)
in reply to tetris11

You might be interested in river as a awesome replacement:

codeberg.org/river/wiki

in reply to Übercomplicated

Appreciate the link, and I don't mean to sound so ungrateful, but that extensive README contains everything except what exactly river is. 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.

This entry was edited (1 day ago)
in reply to 𝘋𝘪𝘳𝘬

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
in reply to tetris11

Have you tried ydotools, which works on both Wayland and X?
in reply to arsCynic

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.

This entry was edited (1 day ago)
in reply to Gamma

Check out xremap
github.com/xremap/xremap
in reply to arsCynic

GPU screen recorder, the hotkeys dont work in Wayland
in reply to superglue

This one should be getting resolved soon! With the new global shortcut portal
in reply to arsCynic

Balders Gate 3. Cannot get it to work on Wayland. No issues on X11.
in reply to nevm

I run basically all my games in gamescope, plus I get HDR for those games that support it.
in reply to exu

I wasn't able to get gamescope working while I was using an nvidia card, and haven't tried yet with amd
in reply to nevm

Works for me in Wayland on Bazzite. Maybe depends on your distro and GPU drivers.
in reply to arsCynic

Nvidia drivers, prime offload with Wayland is still a no go.

Linux reshared this.

in reply to arsCynic

Absolutely none. On my setup everything runs fine either natively or with Xwayland.
in reply to 𝘋𝘪𝘳𝘬

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.
in reply to superkret

huh? Isn't that the thing that let's me select the DE/Compositor/Server mashup while logging in? It just occured to me that this sounds like circular reasoning, but that's what it looks like it does
This entry was edited (10 hours ago)
in reply to jh29a

Yes. It's the only package on my system that still depends on X. Without it, I could remove X entirely.
in reply to arsCynic

The inability to roll windows up into just the title bar, or to get Firefox to place each of its windows on the same virtual desktop as before, are major annoyances. Otherwise, Wayland runs better than I expected.
in reply to arsCynic

RustDesk (remote desktop control) and Barriers (KVM-like server to control my laptop screen from my desktop just by moving mouse to that screen). Both of these are tightly integrated in my daily workflow and would be a hard loss.

There's a modern fork of Barriers but I haven't been able to get it working cross-platform yet. I know RustDesk is actively working to complete wayland support, but it's not quite there yet.

in reply to DetachablePianist

I use rustdesk with wayland, works for me for everything i need it to. As for barriers, i believe input-leap works with wayland.
in reply to 1smoothcriminal

RustDesk on Wayland can't run headless, which I need (unless they fixed already and I just haven't noticed yet - I know they've been working on it!)

Yeah, Input-leap is the Barriers fork I was referring to. I need it to work on all platforms though, and I wasn't able to get it working on macOS. I keep checking periodically tho (usually in response to posts like these - I wanna move Wayland like everyone else!)

This entry was edited (46 minutes ago)
in reply to arsCynic

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.
This entry was edited (1 day ago)
in reply to Termight

I don't have that variable set on my environment, but perhaps it's due to my running PCSX2 as an AppImage?
in reply to Frosty

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.

in reply to arsCynic

I need to force keepass and some other things to x11 mode so that autotype and window detection works.
in reply to arsCynic

Xfwm. Taskbars are now wayland, but don't autohide without the compositor supporting it.
This entry was edited (22 hours ago)
in reply to arsCynic

Easystroke github.com/thjaeger/easystroke… please, please, please somebody pick the project, I'll gladly pay a license to use it.
in reply to VITecNet

github.com/jersou/mouse-action…

It's recommended by the easystroke dev too: github.com/thjaeger/easystroke…

This entry was edited (21 hours ago)
in reply to ashaman2007

I tried Mouse Actions many times, just a different beast (many Easystroke users have the same opinion).
in reply to arsCynic

keepassxc's autotype

also, nvidia

This entry was edited (17 hours ago)
in reply to beleza pura

There are still some quirks but it's been generally fine for me with Nvidia, almost a year now.
in reply to muhyb

i heard about that. sadly my gpu is so old the latest driver that supports it is the 470 driver
in reply to beleza pura

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.

in reply to beleza pura

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.
in reply to muhyb

the nouveau driver works fine except when it crashes for no clear reason after some hours of usage
This entry was edited (4 hours ago)
in reply to beleza pura

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.
in reply to muhyb

Even on X11?


yup. i think it had something to do with video calls or screen sharing, which are essential at work

in reply to beleza pura

That makes sense. Nouveau isn't mature for some use cases yet, even though they made a huge jump with NVK. Hardware upgrade might be closer than you think then.
in reply to arsCynic

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), amd libreoffice Writer) work fine.
This entry was edited (13 hours ago)
in reply to arsCynic

Ubuntu 24.04s KDE Package. Have I borked something or when will it ask me about upgrading?
in reply to arsCynic

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.

in reply to arsCynic

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.

in reply to Magnus Åhall

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
in reply to Estebiu

Uhhh, I've been dreaming if this and now I've got it!
in reply to arsCynic

I would really like to see xtrlock find its way into the Wayland session!

But at the moment, it's only available for wlroots based compositors...

in reply to arsCynic

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.
in reply to arsCynic

I used to have issues with middle click scroll, but my own solution works fine and it works on Wayland and X11 too
in reply to arsCynic

Mostly Beamng (ik not software but game using windows Vulkan/native Linux and a note that my de doesnt have good wayland support at this time )
in reply to arsCynic

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)