this post was submitted on 26 Jan 2026
140 points (85.7% liked)
Linux
12115 readers
285 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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
Just in case it helps:
My Discord keybinds were having a struggle when I used 3rd party apps like armcord and vesktop. The actual Discord bin program is doing global keybinds correctly for my toggle mute microphone on my keyboard.
I use the Discord Nix pkg, not armcord or vesktop. I've always had this issue be it on arch, nixos, or fedora. I'm starting to lean towards "user error" as I just must not have something set up right. but yeah I've never used armcord, vencord, or vesktop.
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?