-
Notifications
You must be signed in to change notification settings - Fork 7
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
Version 2023.11.3: Failure to launch (cannot connect to dbus) #91
Labels
bug
Something isn't working
Comments
I think the dbus connection error is a red herring to what's actually failing in the launch. $ flatpak run org.jitsi.jitsi-meet
Debug: Enabling Wayland backend
Deleting cache directory: /home/ace/.var/app/org.jitsi.jitsi-meet/config/Jitsi Meet/GPUCache
[2:0108/192411.216961: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:0108/192411.692990: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:0108/192411.693034: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
19:24:11.711 › APPIMAGE env is not defined, current application is not an AppImage
(jitsi-meet:2): GLib-GIO-WARNING **: 19:24:11.732: Can't find module 'dconf' specified in GSETTINGS_BACKEND
19:24:11.747 › checkForUpdatesAndNotify called, downloadPromise is null
[2:0108/192411.747828: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:0108/192411.747869: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:0108/192411.747892: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:0108/192411.747914: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:0108/192411.784192:ERROR:object_proxy.cc(577)] Failed to call method: org.freedesktop.login1.Manager.Inhibit: object_path= /org/freedesktop/login1: unknown error type:
$ flatpak run --nosocket=wayland org.jitsi.jitsi-meet
Deleting cache directory: /home/ace/.var/app/org.jitsi.jitsi-meet/config/Jitsi Meet/GPUCache
[2:0108/192535.620639: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:0108/192535.907069: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:0108/192535.907111: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
19:25:35.919 › APPIMAGE env is not defined, current application is not an AppImage
(jitsi-meet:2): GLib-GIO-WARNING **: 19:25:35.942: Can't find module 'dconf' specified in GSETTINGS_BACKEND
19:25:35.954 › checkForUpdatesAndNotify called, downloadPromise is null
[2:0108/192535.954975: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:0108/192535.955042: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:0108/192535.955065: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:0108/192535.955091: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:0108/192535.994848:ERROR:object_proxy.cc(577)] Failed to call method: org.freedesktop.login1.Manager.Inhibit: object_path= /org/freedesktop/login1: unknown error type: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On Fedora 39, KDE Spin, Jitsi 2023.11.3 fails to launch. Manually launching from the terminal shows that it is unable to connect to the DBus system bus socket.
Seems that this may be an upstream issue with Jitsi / Electron.
Environment
/etc/os-release
NAME="Fedora Linux"VERSION="39 (KDE Plasma)"
ID=fedora
VERSION_ID=39
VERSION_CODENAME=""
PLATFORM_ID="platform:f39"
PRETTY_NAME="Fedora Linux 39 (KDE Plasma)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:39"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f39/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=39
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=39
SUPPORT_END=2024-11-12
VARIANT="KDE Plasma"
VARIANT_ID=kde
DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1001/bus"
XDG_SESSION_TYPE="wayland"
Error from Terminal
$ flatpak run org.jitsi.jitsi-meet Debug: Enabling Wayland backend [2:0103/131024.338569: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 && $ flatpak run --nosocket=wayland org.jitsi.jitsi-meet [2:0103/140455.170405: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
Flatpak Information
The text was updated successfully, but these errors were encountered: