jitsi / jitsi-meet-electron

Jitsi Meet desktop application powered by :electron:
Apache License 2.0
1.48k stars 452 forks source link

Jitsi Meet 2024.5.0 Flatpak won't launch under Wayland #964

Open aer0usa opened 1 month ago

aer0usa commented 1 month ago

What happened?

Jitsi Meet 2024.5.0 Flatpak won't launch under Wayland on Fedora Kinoite 40.20240526.0

Since it wouldn't launch from its app icon, I ran it from the command line to see if I got an error.

eric$ flatpak run org.jitsi.jitsi-meet 
Deleting cache directory: /home/eric/.var/app/org.jitsi.jitsi-meet/config/Jitsi Meet/GPUCache
[2:0526/211344.857721: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:0526/211345.154049:ERROR:ozone_platform_x11.cc(244)] Missing X server or $DISPLAY
[2:0526/211345.154064:ERROR:env.cc(258)] The platform failed to initialize.  Exiting.

I searched for the error and found this forum thread that suggests turning off the app's permission to use Wayland

Turning off the "Wayland Windowing System" checkbox in "Application Permissions" allowed me to run Jitsi Meet under Wayland:

eric$ flatpak run org.jitsi.jitsi-meet 
[2:0526/212254.781165: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:0526/212255.107162: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:0526/212255.107213: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
21:22:55.140 › APPIMAGE env is not defined, current application is not an AppImage
21:22:55.248 › checkForUpdatesAndNotify called, downloadPromise is null
[2:0526/212255.248974: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:0526/212255.249025: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:0526/212255.249100: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:0526/212255.249141: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:0526/212255.463367:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.login1.Manager.Inhibit: object_path= /org/freedesktop/login1: unknown error type: 

So, there is a workaround, but previous versions of the Jitsi Meet Flatpak worked under Wayland, so I assume this workaround isn't how the app is intended to be run.

Please let me know if I can provide more information. Thank you!

Platform

Browser / app / sdk version

Jitsi Meet 2024.5.0 Flatpak

Relevant log output

eric$ flatpak run org.jitsi.jitsi-meet 
[2:0526/212234.798985: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:0526/212235.061090:ERROR:ozone_platform_x11.cc(244)] Missing X server or $DISPLAY
[2:0526/212235.061104:ERROR:env.cc(258)] The platform failed to initialize.  Exiting.

Reproducibility

More details?

I did not check the "Reproducability" checkbox since the app exits before I get to specify a server.

Also, I was able to use Jitsi in Chrome without any issue.