-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
[BUG] Screen sharing on Wayland does not work #82
Comments
This does not seem to be a bug directly in GoofCord. There are many reports about the You can also try a native .rpm build |
Hm, strange... All packages have been installed and all services are running smoothly Also I tried .rpm package but with no luck. When I stream, discord doesn't transmit picture and viewers can be heard on the stream, which should not be the case.
P.S.: Obs works fine |
When you click the screen share button, do you first see GoofCord's screen share picker with a black "Entire screen", or your system (pipewire) screen share picker? |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
In screen share picker I can see my desktop on thumbnails, and after I start the stream, but viewers see only a loading screen and hear sound or they see the image with some distortions, like artifacts |
I'm in the same boat of my friends only having a black screen. Also it seems that their audio doubles back on it's self too. |
In the latest beta, the screen sharing doesn't work because it doesn't prompt the desktop environment to select the capture of the application via pipewire |
The 1.8.2-beta.1 did not change how GoofCord requests screen share sources. Can you check the terminal output when attempting to screen share? Also, does screen sharing work in a chromium based browser? You can test it here: https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing If you are talking about artifacts specifically, there is likely not much GoofCord can do, as it uses chromium's capturer with little control over it. |
The screen sharing is working now, but it didn't work before, which is strange, as if the application was running in an X11 environment and made it possible to select specific windows in Discord itself. Logs:
|
Description
Steps to Reproduce
Expected Behavior
Screen shares properly without any artifacts or black screens
Actual Behavior
Screen sharing is broken...
Artifacts, black screen
Screenshots
Environment
Additional Information
Hyprland 46.2
Mesa 24.3.2
Kernel 6.12.8-200_tkg
The text was updated successfully, but these errors were encountered: