Skip to content
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

Open
2 tasks done
NotMephisto opened this issue Jan 9, 2025 · 6 comments
Open
2 tasks done

[BUG] Screen sharing on Wayland does not work #82

NotMephisto opened this issue Jan 9, 2025 · 6 comments

Comments

@NotMephisto
Copy link

  • I have searched and found no existing issues on the same topic
  • I have searched the wiki and found no mention of my problem

Description

Steps to Reproduce

  • Open GoofCord
  • Join any voice chat
  • Turn on screen sharing

Expected Behavior

Screen shares properly without any artifacts or black screens

Actual Behavior

Screen sharing is broken...

Artifacts, black screen

[54:0109/094945.533844:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
[54:0109/094945.533944:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
[54:0109/094945.534098:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
[54:0109/094945.534154:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
'loop->recurse > 0' failed at ../src/pipewire/thread-loop.c:425 pw_thread_loop_wait()
[54:0109/094945.537680:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
[54:0109/094945.537773:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
[54:0109/094945.537915:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
[54:0109/094945.537960:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
[3:0109/094947.676313:ERROR:wayland_event_watcher.cc(47)] libwayland: warning: queue 0x79c02204e40 destroyed while proxies still attached:

[3:0109/094947.676387:ERROR:wayland_event_watcher.cc(47)] libwayland:   wl_shm_pool#49 still attached

Screenshots

Environment

  • Operating System (name and version): Fedora 41
  • GoofCord Version: 1.8.1
  • Way of installing: Flatpak

Additional Information

Hyprland 46.2
Mesa 24.3.2
Kernel 6.12.8-200_tkg

@Milkshiift
Copy link
Owner

This does not seem to be a bug directly in GoofCord. There are many reports about the 'loop->recurse > 0' failed at ../src/pipewire/thread-loop.c:425 pw_thread_loop_wait() error online, and it seems to be caused by system misconfiguration.
See:
https://github.com/emersion/xdg-desktop-portal-wlr/wiki/%22It-doesn't-work%22-Troubleshooting-Checklist
https://gist.github.com/saikocat/eec498db43bc71abfee79e2990f4d8b6
SpacingBat3/WebCord#513

You can also try a native .rpm build

@NotMephisto
Copy link
Author

NotMephisto commented Jan 9, 2025

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.

[74561:0109/140615.316930:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
[74561:0109/140615.350281:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
[74561:0109/140615.350355:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
[74561:0109/140615.350471:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
[74561:0109/140615.350509:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
[74561:0109/140615.364854:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
[74561:0109/140615.364987:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
[74561:0109/140615.365158:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
[74561:0109/140615.365233:ERROR:gpu_channel.cc(503)] Buffer Handle is null.
Missing config parameter: windowState:main
(node:74515) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading '1')
    at Fu (file:///opt/GoofCord/resources/app.asar/ts-out/chunk-20jtf6x6.js:15:308)
    at click (file:///opt/GoofCord/resources/app.asar/ts-out/chunk-20jtf6x6.js:20:6307)
    at MenuItem.click (node:electron/js2c/browser_init:2:35295)
    at a._executeCommand (node:electron/js2c/browser_init:2:40710)
(Use `goofcord --trace-warnings ...` to show where the warning was created)
(node:74515) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)
Missing config parameter: windowState:main
(node:74515) UnhandledPromiseRejectionWarning: TypeError: Cannot read properties of undefined (reading '1')
    at Fu (file:///opt/GoofCord/resources/app.asar/ts-out/chunk-20jtf6x6.js:15:308)
    at click (file:///opt/GoofCord/resources/app.asar/ts-out/chunk-20jtf6x6.js:20:6307)
    at MenuItem.click (node:electron/js2c/browser_init:2:35295)
    at a._executeCommand (node:electron/js2c/browser_init:2:40710)
(node:74515) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 8)
[arRPC > bridge] web disconnected
[74515:0109/140631.187548:ERROR:network_service_instance_impl.cc(613)] Network service crashed, restarting service.
[74515:0109/140631.203343:ERROR:gpu_process_host.cc(982)] GPU process exited unexpectedly: exit_code=15

P.S.: Obs works fine

@Milkshiift
Copy link
Owner

Milkshiift commented Jan 12, 2025

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?

@Milkshiift Milkshiift changed the title [BUG] Screen sharing [BUG] Screen sharing on Wayland does not work Jan 12, 2025
@developer-iname

This comment was marked as off-topic.

@developer-iname

This comment was marked as off-topic.

@NotMephisto
Copy link
Author

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?

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants