The only variable I changed in testing was switching between the x11 and Wayland versions of plasma while I still could. Discord no longer prompts to provide an audio source, desktop will but the screen share won’t work once I actually start it. Orca crashes the moment I hit slice unless I add an environment variable to make it use x11 compatibility mode.
Global keybinds on Wayland were a long-standing pain point. Wayland (rightly) doesn’t let apps listen to your keyboard in the background. Instead, it provides a GlobalShortcuts API, but the implementation can be a little tricky. The spec says a shortcut looks like “<Control>z”, but KDE expects “CTRL+z”, so Discord figures out which desktop you’re on and speaks its dialect (send the wrong one and the portal session can fall over entirely). And since every bind request can pop up an approval dialog, we only ask again when your keybinds actually change, instead of nagging you every time Discord starts. Now, features like push-to-talk work on Linux, even when Discord isn’t focused.
What’s Next: More Control of Sound Sharing
We’ve covered a lot of Linux improvements, but there’s more to do before we reach parity with the other desktop platforms. That means changing to the Wayland infrastructure itself. We use xdg-desktop-portal for screenshare, but that doesn’t provide a handle to capture app audio. Linux users have to choose between sharing audio for their whole desktop or sharing no audio at all. That’s not an experience we can accept long term, so we’re building per-app audio sharing on Wayland and giving it to the Linux community.
We’ve once again teamed up with Igalia to implement per-app audio sharing in xdg-desktop-portal, letting you pick exactly which app’s audio is shared. We’re even implementing it on GNOME and KDE ourselves to get it to users faster. This will take some time to reach critical mass across Linux desktops, but it’s a long-term investment to make a great Linux screenshare experience for both Discord and all screensharing apps. Stay tuned!
I’m not saying audio doesn’t work, I’m saying it doesn’t narrow down to just the application I’m sharing, this is a known regression with the discord client to the best of my knowledge, and as far as I know the orcaslicer crash is a mesa issue affecting just Wayland for whatever reason
The only variable I changed in testing was switching between the x11 and Wayland versions of plasma while I still could. Discord no longer prompts to provide an audio source, desktop will but the screen share won’t work once I actually start it. Orca crashes the moment I hit slice unless I add an environment variable to make it use x11 compatibility mode.
That’s very strange, they both work OOTB for me on Fedora with Plasma
They’re actually talking about this in the blog post they released this week. https://discord.com/blog/discord-linux-a-year-of-upgrades
Push-to-Talk etc. on Wayland
Global keybinds on Wayland were a long-standing pain point. Wayland (rightly) doesn’t let apps listen to your keyboard in the background. Instead, it provides a GlobalShortcuts API, but the implementation can be a little tricky. The spec says a shortcut looks like “<Control>z”, but KDE expects “CTRL+z”, so Discord figures out which desktop you’re on and speaks its dialect (send the wrong one and the portal session can fall over entirely). And since every bind request can pop up an approval dialog, we only ask again when your keybinds actually change, instead of nagging you every time Discord starts. Now, features like push-to-talk work on Linux, even when Discord isn’t focused. What’s Next: More Control of Sound Sharing
We’ve covered a lot of Linux improvements, but there’s more to do before we reach parity with the other desktop platforms. That means changing to the Wayland infrastructure itself. We use xdg-desktop-portal for screenshare, but that doesn’t provide a handle to capture app audio. Linux users have to choose between sharing audio for their whole desktop or sharing no audio at all. That’s not an experience we can accept long term, so we’re building per-app audio sharing on Wayland and giving it to the Linux community.
We’ve once again teamed up with Igalia to implement per-app audio sharing in xdg-desktop-portal, letting you pick exactly which app’s audio is shared. We’re even implementing it on GNOME and KDE ourselves to get it to users faster. This will take some time to reach critical mass across Linux desktops, but it’s a long-term investment to make a great Linux screenshare experience for both Discord and all screensharing apps. Stay tuned!
I’m not saying audio doesn’t work, I’m saying it doesn’t narrow down to just the application I’m sharing, this is a known regression with the discord client to the best of my knowledge, and as far as I know the orcaslicer crash is a mesa issue affecting just Wayland for whatever reason