Screen sharing broken since 0.0.44

[aleasto]

At least in the XWayland session, screen sharing stopped working since updating to 0.0.44, and reverting back to 0.0.43 works.
The screen share never starts, showing the two spinning dots indefinitely. Both when sharing other X11 apps, and when using xwaylandvideobridge.

[JulianTurner]

Same problem here

[DaGammla]

Same problem here. Using the zypper package, it still works on wayland for me on the newest version, so this is a Flatpak problem. Has anyone tried some whether there are some permissions that might need to be set?

[zqpvr]

same problem

[sebastian-philipp]

same here. Also wayland native doesn't allow me to share my screen.

[sebastian-philipp]

still cannot share wit 0.0.46

[sebastian-philipp]

workaround: Got screen sharing working with https://github.com/flathub/io.github.spacingbat3.webcord

[DaGammla]

Something Changed with the newest update. Maybe Discord is now actively working on full wayland support.
Now, when you try to screenshare, it tries to use pipewire (It opens the selection dialog) but it still fails to actually work

[zqpvr]

Something Changed with the newest update. Maybe Discord is not actively working on full wayland support. Now, when you try to screenshare, it tries to use pipewire (It opens the selection dialog) but it still fails to actually work

Yeah I seen something did change, It doesn't find any other windows or anything. Does Xwayland work?

[DaGammla]

Discord behaves differently depending if you allow it to only use X11 or X11 and Wayland in Flatseal. I tried both, and both do not work. (For me it does not even start, if I only allow Wayland). In both cases the window you pick in the Pipewire dialog shows up in the screen share preview in Discord but it won't screenshare. The Pipewire dialog also keeps reopening after selecting a screen.

[zqpvr]

Yeah, I also have that. but no screens show up, not on the xwayland bridge share though

[rytrix]

Still doesn't work as of 0.0.49

[farribeiro]

Have you ever stopped to think that this is getting tiring.

[sebastian-philipp]

still broken. Now the xwaylandvideobridge portal also crashes in Webcord and Vesktop.

[KarlsonxD]

are there any insights what changed in this udpate?
can't find the commit id to downgrade the flatpak image, does anybody have a tip?

[deddroid]

still broken:

• stable 300377 (dc7e4ba)
• Host 0.0.56 x64
• Build Override: N/A Linux 64-bit (6.9.3-4-cachyos)

[benjamin051000]

Vesktop has been working for me on openSUSE TW / KDE Wayland with xwaylandvideobridge.

[devurandom]

Vesktop has been working for me on openSUSE TW / KDE Wayland with xwaylandvideobridge.

I can confirm: The Vesktop Flatpak works really well for streaming. I streamed a game run with Proton in the Steam Flatpak without any issues (apart from the "select window" dialogue popping up twice instead of just once).

[crimsonfall]

As a workaround, if you have Flatseal, you can scroll down to "Environment" and under "Variables" add a new variable and put XDG_SESSION_TYPE=x11. This has personally worked for me in putting the screen share functionality back into the Discord Flatpak.

This seems to be problem with Discord itself as they're apparently experimenting with Wayland support, but it's pretty botched at the moment. I noticed that this Reddit post started popping up at around the same time this became an issue (https://www.reddit.com/r/linux_gaming/comments/1bp5k66/discord_finally_tries_native_wayland_screen/). Again, this is just my theory.

[asreich]

As a workaround, if you have Flatseal, you can scroll down to "Environment" and under "Variables" add a new variable and put XDG_SESSION_TYPE=x11. This has personally worked for me in putting the screen share functionality back into the Discord Flatpak.

This seems to be problem with Discord itself as they're apparently experimenting with Wayland support, but it's pretty botched at the moment. I noticed that this Reddit post started popping up at around the same time this became an issue (https://www.reddit.com/r/linux_gaming/comments/1bp5k66/discord_finally_tries_native_wayland_screen/). Again, this is just my theory.

You're a legend, this workaround worked for me. Running Clear Linux OS 41880 with Wayland Linux 6.9.3-1439.native, Flatpak Discord 0.0.60.

[Mantissa-23]

As a workaround, if you have Flatseal, you can scroll down to "Environment" and under "Variables" add a new variable and put XDG_SESSION_TYPE=x11. This has personally worked for me in putting the screen share functionality back into the Discord Flatpak.

This seems to be problem with Discord itself as they're apparently experimenting with Wayland support, but it's pretty botched at the moment. I noticed that this Reddit post started popping up at around the same time this became an issue (https://www.reddit.com/r/linux_gaming/comments/1bp5k66/discord_finally_tries_native_wayland_screen/). Again, this is just my theory.

This also worked for my wife and I, latest Bazzite Stable and Fedora 40 Workstation respectively.

[Siiiidox]

Using a fresh Fedora Workstation 40 setup, this works for sharing applications. However, when I try to share my screen, everything is black and only my mouse cursor is visible.

[Yerson-Borda]

Same problem here. It keeps loading or asking which screen to stream in loop.

[guihkx]

Can anyone please check if this still persists with latest Discord (0.0.70)?

That version includes a major version update to Electron, so if we're lucky, this is finally fixed...

I'd test this myself, but I don't/can't use Wayland.

[atirut-w]

Can anyone please check if this still persists with latest Discord (0.0.70)?

Sadly, the problem is still there.

[luisch444]

As a workaround, if you have Flatseal, you can scroll down to "Environment" and under "Variables" add a new variable and put XDG_SESSION_TYPE=x11. This has personally worked for me in putting the screen share functionality back into the Discord Flatpak.

This seems to be problem with Discord itself as they're apparently experimenting with Wayland support, but it's pretty botched at the moment. I noticed that this Reddit post started popping up at around the same time this became an issue (https://www.reddit.com/r/linux_gaming/comments/1bp5k66/discord_finally_tries_native_wayland_screen/). Again, this is just my theory.

For me XDG_SESSION_TYPE=x11 does only allow sharing discord, but I found that if I use an application with env XDG_CURRENT_DESKTOP=sway it allows me to share. I do not know what implications might have but it seems to work rigth.

[DaGammla]

The Canary upstream has finally fixed this issue. Looks like we Wayland users are gonna get a Discord christmas present

[leandromqrs]

The latest stable version 0.0.80 has fixed this issue

[guihkx]

The latest stable version 0.0.80 has fixed this issue

That's great to know!

Unfortunately, we can't update Discord just yet because of another major regression (follow #483 for details & updates).

[DarkArc]

The latest stable version 0.0.80 has fixed this issue

That's great to know!

Unfortunately, we can't update Discord just yet because of another major regression (follow #483 for details & updates).

Is there a branch/way to manually build an updated version?

I would happily trade file picker issues for screen sharing issues.

I've very rarely used discord for sending a file given it's tiny limit and a plethora of other options like Proton Drive, Google Drive, Dropbox, Bitwarden Send and more.

[guihkx]

Is there a branch/way to manually build an updated version?

You can most definitely build/package a newer version of Discord locally, yes.

Providing instructions for it seems out of scope IMO though, but you can look at the flatpak documentation to learn how, or maybe at the logs of our most recent build job on Flathub.

Edit: There's also Discord Canary, which someone has mentioned below and I completely forgot about.

[BuonHobo]

You can just install DiscordCanary from flathub beta.
Here are the instructions I copied from their README:

flatpak remote-add --if-not-exists flathub-beta https://flathub.org/beta-repo/flathub-beta.flatpakrepo
flatpak install flathub-beta com.discordapp.DiscordCanary
flatpak run com.discordapp.DiscordCanary

[DarkArc]

Is there a branch/way to manually build an updated version?

For anyone else that might want to just do this as a one off patch...

git clone https://github.com/flathub/com.discordapp.Discord.git
cd com.discordapp.Discord/
sed -i 's@https://dl.discordapp.net/apps/linux/0.0.74/discord-0.0.74.tar.gz@https://dl.discordapp.net/apps/linux/0.0.80/discord-0.0.80.tar.gz@' com.discordapp.Discord.json
sed -i 's@c9fda02ef0e0cc5d77720a4a1628821c661547ea7b8d9380477ecbd45e8c66f7@a1a9ae1762dc7410b61d4cc1d3c953971beb5e313a605057c0b243ae660a4573@' com.discordapp.Discord.json
sed -i 's@<release version="0.0.74" date="2024-11-12">@<release version="0.0.80" date="2025-01-15">@' com.discordapp.Discord.appdata.xml
flatpak-builder --force-clean --user --install-deps-from=flathub --repo=repo --install builddir com.discordapp.Discord.json

[bcmedeiros]

You can just install DiscordCanary from flathub beta.

Thank you very much for this! I was trying to use the non-canary version for months, I'd have trouble selecting the window to share when streaming and more recently my app would stay open for a couple of seconds and then crash.

The canary version fixes both problems and also works very well on Wayland.