Man the Phoronix forums, always some deluded guy arguing against Wayland. But only time will tell, no manner how many developers jump ship from X.org to maintain (X)Wayland…
Discord PTT I can at least confirm works fine on Wayland + KDE. There’s a legacy app hotkeys option that lets it work in every game I play so far, native or WINE.
Also no problems dragging and dropping from Ark to Dolphin.
Tearing can be enabled in the display settings menus now too.
As I understand it, in X, all programs are allowed to see all keyboard inputs all the time. Wayland doesn’t allow that, and only the DE itself and the current application gets the input, or something like that. I think this is an intentional thing for added security but I’m not entirely sure. Anyway, KDE has a setting to allow “legacy” programs to see all keyboard inputs again, and this lets Discord work as expected when playing games and such.
You are right with Wayland having issues, but that’s not the point (I am making). I am pointing out the direction the developing for Linux Windowing system is going towards (cannot get things without the developers).
Wayland is not perfect and no one will dispute that (only extreme people and idiots), because nothing is absolute. Wayland is old (news) at this point and still has active development (which the only thing matters for the wheel to move forward).
thing is, forcing adoption before the time is right is going to reduce linux adoption. We finally have some momentum going, forcing wayland onto desktop users and having it be a terrible experience is just going to kill it
Sometimes that’s the only way to get the software around it to work. Many folks won’t fix things until they stop working, rather than when they know things are going to stop working. I know that it sucks, but that’s just the way it goes sometimes. Linux (as an ecosystem) where you can just mandate someting from on high and force you employees to do it. That’s why everything is so disjointed.
I am also on AMD using Gnome with a Wayland session and push to talk works for me if I have Discord not minimized and on the same virtual desktop as the game I am playing. Might work for you as well. It’s still dumb that it doesn’t work when minimized of course, but a possible workaround is better than nothing.
Man the Phoronix forums, always some deluded guy arguing against Wayland. But only time will tell, no manner how many developers jump ship from X.org to maintain (X)Wayland…
I mean there are a lot of issues. I’m on amd. Most issues I have are all Gnome related.
No Discord push to talk
Remmina multi monitor doesn’t work
Vmware key tunneling doesn’t work
Can’t drag and drop from the archive tool
Lots of annoyances. The push to talk for me is a deal breaker, I hate open micers.
Discord PTT I can at least confirm works fine on Wayland + KDE. There’s a legacy app hotkeys option that lets it work in every game I play so far, native or WINE.
Also no problems dragging and dropping from Ark to Dolphin.
Tearing can be enabled in the display settings menus now too.
Can you explain by what you mean with legacy app hotkeys option?
As I understand it, in X, all programs are allowed to see all keyboard inputs all the time. Wayland doesn’t allow that, and only the DE itself and the current application gets the input, or something like that. I think this is an intentional thing for added security but I’m not entirely sure. Anyway, KDE has a setting to allow “legacy” programs to see all keyboard inputs again, and this lets Discord work as expected when playing games and such.
I think tearing still needs a few extra pieces in the graphics stack to land before that setting actually works.
On Nvidia maybe, it should work on AMD though.
Being frank that’s a big deal to A LOT of gamers and would prohibit adoption big time.
You are right with Wayland having issues, but that’s not the point (I am making). I am pointing out the direction the developing for Linux Windowing system is going towards (cannot get things without the developers).
Wayland is not perfect and no one will dispute that (only extreme people and idiots), because nothing is absolute. Wayland is old (news) at this point and still has active development (which the only thing matters for the wheel to move forward).
thing is, forcing adoption before the time is right is going to reduce linux adoption. We finally have some momentum going, forcing wayland onto desktop users and having it be a terrible experience is just going to kill it
Sometimes that’s the only way to get the software around it to work. Many folks won’t fix things until they stop working, rather than when they know things are going to stop working. I know that it sucks, but that’s just the way it goes sometimes. Linux (as an ecosystem) where you can just mandate someting from on high and force you employees to do it. That’s why everything is so disjointed.
On the other hand, forcing adoption too late is going to delay Wayland, and it’s not like Xorg is ever getting HDR.
Pushing it for 2025 seems about right to me; that’s still two years of dev left, and two years can go fast if there’s real impetus to improve things.
honestly question, do people use application-level push-to-talk often on Linux as opposed to binding a
pactlcommand or similar?I am also on AMD using Gnome with a Wayland session and push to talk works for me if I have Discord not minimized and on the same virtual desktop as the game I am playing. Might work for you as well. It’s still dumb that it doesn’t work when minimized of course, but a possible workaround is better than nothing.