Hi,
I updated to KDE 6 and decided to use Wayland. Everything runs great except video conferencing flatpak ‘Jitsi Meet’ doesn’t launch. It does launch on X11, though.
I have another machine running Arch with KDE 6 on Wayland and Jitsi Meet launches just fine on there. This seems to be only happening on Tumbleweed. Anyone know how I can fix this?
Terminal ouput?
flatpak run org.jitsi.jitsi-meet
LaunchProcess: failed to execvp:
xdg-settings
[2:0317/125557.015589:ERROR:ozone_platform_x11.cc(244)] Missing X server or $DISPLAY
[2:0317/125557.015614:ERROR:env.cc(257)] The platform failed to initialize. Exiting.
So after doing some research on your issue it seems that jitsi-meet use --socket=fallback-x11 as permission which mean that it will try to use wayland first and fallback to X11 if wayland is not detected.
I can be wrong but I think that in your case flatpak is not aware that you are using wayland, one thing you could try is to check what value is associated with $DISPLAY and see if it it show nothing, something like “:0” or “wayland-0” … apparently there are other variables worth checking GDK_BACKEND and WAYLAND_DISPLAY
( see : gtk - Flatpak on wayland error "cannot open display: " - Stack Overflow )
You could try to force your app to run with wayland with this command, it is worth a try…
flatpak run --socket=wayland --nosocket=fallback-x11 org.jitsi.jitsi-meet
It is also worth noting that apparently and based on this bug report [Bug]: Flatpak not mounting /tmp/.X11-unix or /run/flatpak/Xauthority · Issue #5487 · flatpak/flatpak · GitHub it appear that in some situation depending on where you start your flatpak application from, the $DISPLAY variable is not accessible resulting in the application unable to start …
@Aboutduck use the built in flatseal component to adjust for a flatpak application.
I tried the command you recommended and this is the terminal output:
flatpak run --socket=wayland --nosocket=fallback-x11 org.jitsi.jitsi-meet
[2:0317/160553.922828: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:0317/160554.062701:ERROR:ozone_platform_x11.cc(244)] Missing X server or $DISPLAY
[2:0317/160554.062709:ERROR:env.cc(257)] The platform failed to initialize. Exiting.
After starting my session on wayland on my side and installed jitsi-meet I was able to reproduce your issue so your are not the only one affected …
I’ve tried to launch another electron app Signal which doesn’t have the --socket=fallback-x11 permission enabled with wayland only and the result is the same …
flatpak run --socket=wayland --nosocket=x11 org.signal.Signal
Debug: Will run signal with the following arguments:
Debug: Additionally, user gave:
Set Windows Application User Model ID (AUMID) { AUMID: 'org.whispersystems.signal-desktop' }
NODE_ENV production
NODE_CONFIG_DIR /app/Signal/resources/app.asar/config
NODE_CONFIG {}
ALLOW_CONFIG_MUTATIONS undefined
HOSTNAME noname-opensuse
NODE_APP_INSTANCE undefined
SUPPRESS_NO_CONFIG_WARNING undefined
SIGNAL_ENABLE_HTTP undefined
userData: /home/noname/.var/app/org.signal.Signal/config/Signal
config/get: Successfully read user config file
config/get: Successfully read ephemeral config file
making app single instance
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
[2:0318/132059.395497:ERROR:ozone_platform_x11.cc(244)] Missing X server or $DISPLAY
[2:0318/132059.395544:ERROR:env.cc(257)] The platform failed to initialize. Exiting.
The good news is that I’ve managed to launch jitsi-meet by disabling the wayland socket
flatpak run --nosocket=wayland org.jitsi.jitsi-meet
Alternatively like @malcolmlewis suggested to make the change permanent
Wayland Windowning SystemPerfect, thank you for this!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.