Failed to connect to socket /run/dbus/system_bus_socket

Help
1

Trying to run the flatpak for Synology Note Station, but I get the following error:

[2:24:0809/182924.434846:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

The program looks like it starts, but when I login I just get the following error:

Login failed. Please check your network connection and try again later.

I’m confident that the login credentials are correct, since I use the same credentials with the Synology Drive Client (also a flatpak). Any suggestions?

2

Seems like that package assumes /run/dbus/system_bus_socket is an existing socket. Does it exist? I have it on my desktop NixOS.

3

Hi @mightyiam, there is a file at /run/dbus/system_bus_socket and the owner and group are both root. Could it be a permissions issue?

4

I think the app/flatpak package isn’t allowing access to the DBus socket. This is for Signal, but see: Failed to connect to socket /run/dbus/system_bus_socket · Issue #280 · flathub/org.signal.Signal · GitHub

1 Like
5

I submitted an issue on github if the flatpak needs to be updated to access dbus on wayland/hyprland.

6

Interesting discussion on Reddit on the same topic, which also mentions the Signal flatpak DBus socket issue. Still not really sure if this is a configuration issue or a flatpak bug.

7

You can always try to patch the flatpak package yourself and add in support for the dbus socket, then package it and attempt to run it. The Signal GH issue links to a PR for a fix. Maybe try something similar?

1 Like
8

sorry to resuscitate an old thread, but I had the same issue of certain flatpaks not running because of the socket issue along with failure to execute xdg-settings. I am running the niri window manager with xwayland-satellite.

I downloaded the Flatseal flatpak which manages permissions for Flatpaks and found that Flatseal ran perfectly fine, while other flatpaks like Obsidian did not. In the socket area, Flatseal had the following enabled:

  • X11 windowing system (socket=x11)
  • Wayland windowing system (socket=wayland)
  • Fallback to X11 windowing system (socket=fallback-x11)

For the Obsidian flatpak, only the X11 windowing system was enabled by default. I turned on the other two and ran the Obsidian flatpak and it worked.

There are other sockets available in Flatseal for d-bus session or system and more, but these three seem to be the minimum for successful execution of flatpaks.

I also had these same issues running niri on Arch, so it is reproducible in my hands. In addition, running a native package of Obsidian in Arch in niri also created the same issue, so the key to all this seem to be centered around socket=wayland and socket=fallback-x11 not being accessed/invoked. Hope this helps anyone else with similar issues!