You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The xdg-settings error is not what's causing your issue, here's a snapshot from how (successfully) launching Jitsi looks like on my laptop running Gentoo;
$ flatpak run org.jitsi.jitsi-meetLaunchProcess: failed to execvp:xdg-settings[3:0604/021713.259257:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory[3:0604/021713.259336:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory02:17:13.275 › APPIMAGE env is not defined, current application is not an AppImage[3:0604/021713.307777:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory[3:0604/021713.307831:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory[3:0604/021713.307869:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory[3:0604/021713.307899:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory[3:0604/021713.311958:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.login1.Manager.Inhibit: object_path= /org/freedesktop/login1: unknown error type: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)[43:0604/021713.351264:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.[43:0604/021717.350677:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
Unfortunately I don't have much experience in debugging electron applications, at least for launch issues or hard crashes.
This happens on fedora 36.
The text was updated successfully, but these errors were encountered: