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

Can't share screen #46

Open
wjt opened this issue May 18, 2022 · 15 comments
Open

Can't share screen #46

wjt opened this issue May 18, 2022 · 15 comments
Labels
bug Something isn't working

Comments

@wjt
Copy link
Member

wjt commented May 18, 2022

On the development branch of Endless OS, which is a Wayland GNOME 41 session, this Jitsi Meet app cannot share the screen.

Capture d’écran de 2022-05-18 15-33-41
Capture d’écran de 2022-05-18 15-33-40

This is an Electron app. I don't know whether the Electron is new enough to support Chromium's WebRTCPipeWireCapturer flag, but if it is, it might be sufficient to just enable that.

@wjt
Copy link
Member Author

wjt commented May 18, 2022

By way of comparison, meet.jit.si in the Flathub version of Chromium can share my screen.

Capture d’écran de 2022-05-18 15-36-46

@modzilla99
Copy link

Works in the latest version with Gnome 42 on Fedora

@csett86
Copy link
Contributor

csett86 commented Nov 21, 2022

@wjt have another try with yesterdays version 2022.11.0, others report that it now works fine (jitsi/jitsi-meet-electron#785)

Please launch it with wayland enabled, as described in the README: https://github.com/flathub/org.jitsi.jitsi-meet#wayland-support

@wjt
Copy link
Member Author

wjt commented Nov 22, 2022

I ran Jitsi with:

flatpak run --env=JITSI_USE_WAYLAND=1 org.jitsi.jitsi-meet

I joined a meeting. I pressed the Share button. Here is what I see:

Screenshot from 2022-11-22 09-29-37

I then Alt-Tabbed to and from this browser window a couple of times, and Jitsi Meet logged the following to the terminal:

[2:1122/093046.026323:ERROR:wayland_event_watcher.cc(36)] libwayland: wl_surface@60: error 0: gtk_shell::get_gtk_surface already requested

and then died with SIGTRAP.

If I run Jitsi without JITSI_USE_WAYLAND=1, I see the same results, except without the crash. I think telling Chromium to act as a Wayland client is a red herring – X clients can use the portal too.

It actually is possible to trigger the portal dialog, with or without JITSI_USE_WAYLAND=1, as follows:

  1. On the broken popover above, click Share
  2. The broken popover vanishes and the portal dialog appears:

Screenshot from 2022-11-22 09-33-40

  1. Pick a window or screen to share in the portal dialog

So it is no longer true that I can't share the screen; the flow just looks super broken.

@maymage
Copy link

maymage commented Jan 22, 2023

@wjt

The upstream issue is

https://bugs.chromium.org/p/chromium/issues/detail?id=1281200&q=pipewire&can=2&sort=-modified

Not much to be done here in the flathub repo.

@modzilla99
Copy link

Screensharing broke again. Anyone experiencing the same problem? I'm on Fedora 38.

@ananace
Copy link
Collaborator

ananace commented May 23, 2023

Yeah, screensharing seems completely broken - at least on Wayland.
I've also tested with the XWaylandVideoBridge, and it still crashes if I open the sharing dialog.

@ananace ananace added the bug Something isn't working label May 23, 2023
@q-wertz
Copy link

q-wertz commented Nov 3, 2023

Also not working on Manjaro with Gnome 44.5

@csett86
Copy link
Contributor

csett86 commented Feb 13, 2025

Good news: The new release of the electron app 2025.2.0 should improve Wayland screensharing significantly, but it needs a new (yet unreleased version) of jitsi-meet. You can already test it on alpha.jitsi.net, and it will be available with the next jitsi-meet stable release

@q-wertz
Copy link

q-wertz commented Feb 14, 2025

Tried again (having the flatpak version 2025.2.0). When the OS window sharing popup opens and I select a screen it closes for a moment and then reopens...

Console output in this step:

2025-02-14T17:14:36.113Z [AOT] <logInfo>:  [MAIN] hide aot handler
[2:0214/181436.230406:ERROR:shared_x_display.cc(39)] Unable to open display
2025-02-14T17:14:36.498Z [AOT] <logInfo>:  [MAIN] show aot handler
2025-02-14T17:14:36.498Z [AOT] <logInfo>:  [MAIN] sending aot-open state update to renderer process
2025-02-14T17:14:36.502Z [AOT] <logInfo>:  [MAIN] handling new aot window event
2025-02-14T17:14:36.507Z [AOT] <logInfo>:  [MAIN] received window created event
2025-02-14T17:14:36.507Z [AOT] <logInfo>:  [MAIN] setting aot window options
'loop->recurse > 0' failed at ../src/pipewire/thread-loop.c:425 pw_thread_loop_wait()
[2:0214/181446.217010:ERROR:shared_x_display.cc(39)] Unable to open display

Then the app crashes.

Do I need any special flags set?

Full console log:

$ flatpak run org.jitsi.jitsi-meet
Debug: Enabling Wayland backend
Deleting cache directory: /home/clemens/.var/app/org.jitsi.jitsi-meet/config/Jitsi Meet/GPUCache
[2:0214/181341.107040:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
LaunchProcess: failed to execvp:
xdg-settings
[2:0214/181341.456388:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0214/181341.456435:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
18:13:41.481 › APPIMAGE env is not defined, current application is not an AppImage
18:13:41.535 › checkForUpdatesAndNotify called, downloadPromise is null
[2:0214/181341.536915:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0214/181341.536987:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0214/181341.537032:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0214/181341.537072:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0214/181341.641830:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.login1.Manager.Inhibit: object_path= /org/freedesktop/login1: unknown error type: 
^[[A2025-02-14T17:14:16.199Z [AOT] <logInfo>:  [MAIN] received aot event aot-update-state
2025-02-14T17:14:16.199Z [AOT] <logInfo>:  [MAIN] handling aot-conference-joined state update from renderer process
2025-02-14T17:14:16.200Z [AOT] <logInfo>:  [MAIN] adding main window event handlers
2025-02-14T17:14:16.250Z [AOT] <logInfo>:  [MAIN] received aot event aot-update-state
2025-02-14T17:14:16.250Z [AOT] <logInfo>:  [MAIN] handling is-intersecting state update from renderer process
2025-02-14T17:14:16.250Z [AOT] <logInfo>:  [MAIN] hide aot handler
2025-02-14T17:14:20.381Z [AOT] <logInfo>:  [MAIN] show aot handler
2025-02-14T17:14:20.381Z [AOT] <logInfo>:  [MAIN] sending aot-open state update to renderer process
2025-02-14T17:14:20.384Z [AOT] <logInfo>:  [MAIN] handling new aot window event
2025-02-14T17:14:20.392Z [AOT] <logInfo>:  [MAIN] received window created event
2025-02-14T17:14:20.392Z [AOT] <logInfo>:  [MAIN] setting aot window options
2025-02-14T17:14:22.958Z [AOT] <logInfo>:  [MAIN] hide aot handler
2025-02-14T17:14:22.958Z [AOT] <logInfo>:  [MAIN] hiding aot window
2025-02-14T17:14:22.958Z [AOT] <logInfo>:  [MAIN] sending aot-hide state update to renderer process
2025-02-14T17:14:25.881Z [AOT] <logInfo>:  [MAIN] received aot event aot-update-state
2025-02-14T17:14:25.881Z [AOT] <logInfo>:  [MAIN] handling aot-close state update from renderer process
2025-02-14T17:14:25.882Z [AOT] <logInfo>:  [MAIN] removing main window event handlers
2025-02-14T17:14:25.895Z [AOT] <logInfo>:  [MAIN] closing aot window
2025-02-14T17:14:27.068Z [AOT] <logInfo>:  [MAIN] received aot event aot-update-state
2025-02-14T17:14:27.068Z [AOT] <logInfo>:  [MAIN] handling aot-conference-joined state update from renderer process
2025-02-14T17:14:27.068Z [AOT] <logInfo>:  [MAIN] adding main window event handlers
2025-02-14T17:14:27.104Z [AOT] <logInfo>:  [MAIN] received aot event aot-update-state
2025-02-14T17:14:27.104Z [AOT] <logInfo>:  [MAIN] handling is-intersecting state update from renderer process
2025-02-14T17:14:27.104Z [AOT] <logInfo>:  [MAIN] hide aot handler
2025-02-14T17:14:36.113Z [AOT] <logInfo>:  [MAIN] hide aot handler
[2:0214/181436.230406:ERROR:shared_x_display.cc(39)] Unable to open display
2025-02-14T17:14:36.498Z [AOT] <logInfo>:  [MAIN] show aot handler
2025-02-14T17:14:36.498Z [AOT] <logInfo>:  [MAIN] sending aot-open state update to renderer process
2025-02-14T17:14:36.502Z [AOT] <logInfo>:  [MAIN] handling new aot window event
2025-02-14T17:14:36.507Z [AOT] <logInfo>:  [MAIN] received window created event
2025-02-14T17:14:36.507Z [AOT] <logInfo>:  [MAIN] setting aot window options
'loop->recurse > 0' failed at ../src/pipewire/thread-loop.c:425 pw_thread_loop_wait()
[2:0214/181446.217010:ERROR:shared_x_display.cc(39)] Unable to open display
[2:0214/181448.643335:ERROR:screencast_portal.cc(367)] Failed to start the screen cast session.
[2:0214/181448.643356:ERROR:base_capturer_pipewire.cc(81)] ScreenCastPortal failed: 2
Error occurred in handler for 'jitsi-screen-sharing-get-sources': Failed to get sources.
Error occurred in handler for 'jitsi-screen-sharing-get-sources': Failed to get sources.

@csett86
Copy link
Contributor

csett86 commented Feb 14, 2025

No special flags are required, but be sure to test with alpha.jitsi.net (for now), @q-wertz

@q-wertz
Copy link

q-wertz commented Feb 16, 2025

Do you mean as Jisi server URL or install the alpha version of the flatpak?

First thing is not working.
For the second, I would need assistance on how to install the alpha version of a flatpak (didn't find a quick solution).

@csett86
Copy link
Contributor

csett86 commented Feb 17, 2025

I meant the first thing, so using a meeting on alpha.jitsi.net. At least for me that worked well now with Wayland and Gnome (Ubuntu 24.04) and I could reliably share the screen and only the OS screen picker pops up, I select a screen or window, and it shares it without any second popup or crash. What environment are you using (desktop env, Gnome versions, ...)?

@q-wertz
Copy link

q-wertz commented Feb 17, 2025

Tested again the alpha.jitsi.net in the jitsi flatpak.
Still crashing... :(

In the browser (Firefox, non-flatpak) everything works fine (also on the normal server)

Does this information help? If you need more let me know

~ $ lsb_release -a
LSB Version:	n/a
Distributor ID:	ManjaroLinux
Description:	Manjaro Linux
Release:	25.0.0
Codename:	Zetar
~ $ echo $XDG_SESSION_TYPE
wayland
~ $ uname -a
Linux hoth 6.6.75-2-MANJARO #1 SMP PREEMPT_DYNAMIC Mon Feb  3 17:53:46 UTC 2025 x86_64 GNU/Linux
~ $ gnome-shell --version
GNOME Shell 47.4

@csett86
Copy link
Contributor

csett86 commented Feb 17, 2025

Thanks a lot for retesting, and this is enough information!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants