-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Streaming doesn't work on Wayland #89
Comments
that's an wayland issue that should work on the newer gnome provided they fix remote desktop on the newer gnome |
Thanks for your response! So I will patiently wait for the next release with Gnome 3.36. |
Discord has to support it, new GNOME releases won't help. |
@TingPing you mean discord has to support wayland? |
Well, no they don't really need to care about wayland, they need to support pipewire as a video source. |
@TingPing was/is pipewire already a thing in fedora 31? |
F31 has an older version. I don't know offhand if thats a problem. |
i suspect it does but that's based on my experience with ubuntu 18.04 :p |
That was before Pipewire even existed. |
fair enough hahaha when did pipewire come out |
I guess it existed in late 2017 but it didn't become very useful until into 2018. |
hmmm i see |
To anyone still trying to get this to work, just use the Browser version in Chromium. Enable the |
Discord's Electron version does support Chrome's Pipewire support if you pass |
Kind of related: Does anybody know how to stream audio on xwayland? |
Streaming audio in Discord doesn't work anywhere afaik, you can workaround that by feeding your audio into your microphone. |
I had the same issue after updating some packages the issue was resolved for me |
Alright, Linux nerds, I need help: And this is what you do:
|
...would be useful. |
Okay, a little TL:DR of the comment above since in some discord servers people seemed to misunderstand it Discord ranks issues according to https://support.discord.com - Please upvote those two tickets mentioned above to catch their attention. |
doesn't work in my machine. I also see black screen in the windows that were working before using --enable-features=WebRTCPipeWireCapturer |
@All3xJ What distro are you on? All Ubuntu releases before 21.04 are not able to use PipeWire. If on another distro can you test the discord web app in chromium/chrome (with that flag) or firefox (no flag needed). |
ArchLinux. |
@All3xJ Firefox bug. Chromium bug. So in Chromium/Chrome there should be a cursor fix arriving in 93 probably. |
Helvum |
Discord has said they won't support it and that it's on Wayland. |
Source? |
https://www.reddit.com/r/linux_gaming/comments/vuh1d3/discord_xwayland_is_not_currently_officially/ |
@Doomsdayrs That's just a support person saying Xwayland is not currently officially supported. |
They have no members dedicated to Linux whatsoever. Xwayland etc. I suggest considering a migration of Matrix and using that instead of Discord if possible. |
I'm not suggesting otherwise, but that's not to say it's in any way terminal.
That is not a solution to Discord's screensharing on the official build being broken on Wayland. |
It is terminal, it has been like this for years. I find your attitude in this matter ignorantly optimistic. Thus I shall take no further point in this conversation with you. Good day to you. |
Instead of this nonsense murmur I think it's worth mentioning that some unofficial scripts that make it possible to stream on Discord with PipeWire by illegally modifying the code exist. A workaround for streaming audio as well is not (yet) found. That said I feel like this issue can be locked. No work can be done from the flathub maintainers and the past few months revealed that nothing worth noting came out from here. What do you think, @lionirdeadman |
Locking, was mostly hoping for this issue to be used if people found things. |
Can someone on Wayland please retest this with the current version of Discord (0.0.70)? Thank you. |
Using Fedora 41 Workstation Beta (GNOME 47, pipewire 1.2.5) and the discord flatpak 0.0.70, I can select share targets sort of reasonably (entire screen, app windows) thanks to the portal, but Discord's own picker doesn't integrate too well. Sharing doesn't work though, it ends up in just a blank screen. The only relevant log message I got from running the app from the cli is:
|
That's unfortunate, but thank you very much for testing. It'd be great to also test this with the non-Flatpak package on Wayland, just to make sure the problem isn't specific to Flatpak. If it's specific to Flatpak, we can keep this issue open until we figure out the reason, and a fix. However, if this also affects non-Flatpak Discord, my suggestion for the people affected by this bug would be to report it using the appropriate channel instead, because this bug tracker only deals with Flatpak-specific issues. |
Trying to share the screen on Fedora 31 using Gnome on Wayland leads to a black screen showing only mouse cursor. Is this a bug/missing feature or due to a too strict safety/sandbox regulation?
The text was updated successfully, but these errors were encountered: