Open aleasto opened 6 months ago
Same problem here
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?
same problem
same here. Also wayland native doesn't allow me to share my screen.
still cannot share wit 0.0.46
workaround: Got screen sharing working with https://github.com/flathub/io.github.spacingbat3.webcord
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
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?
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.
Yeah, I also have that. but no screens show up, not on the xwayland bridge share though
Still doesn't work as of 0.0.49
Have you ever stopped to think that this is getting tiring.
still broken. Now the xwaylandvideobridge portal also crashes in Webcord and Vesktop.
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?
still broken:
Vesktop has been working for me on openSUSE TW / KDE Wayland with xwaylandvideobridge.
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).
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.
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.
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.
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.
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
.