[Flatpak] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

TeamSpeak 6 Client
1

Hi,

I’m packaging the TeamSpeak 5 on flathub.org and currently running TeamSpeak 6 beta branch.

When trying to fix one bug reported by user about access to D-BUS I found out that even when allowing all D-Bus permissions required by TeamSpeak 6 the application still throws following error:

[2:20:0213/170121.626578: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

As flatpak disallows access to full system D-Bus (it breaches the sandbox) and I don’t see any reason for TeamSpeak 6 to want that access, could you look at what is wrong here.

To test this out just install the latest flatpak version following the instructions on beta branch README and run it with flatpak run com.teamspeak.TeamSpeak.

2

Unfortunately, as this flatpak is not maintained/published, I cannot help you with this issue. The only official way to use TeamSpeak is from our download page.

We only provide our client as an archive.

2 Likes
3

Thanks for the reply. I maintain the flatpak by myself, just wanted to ask if you could help with the issue. If not, that is OK.

Still I would like to know why TeamSpeak 6 needs access to whole system D-Bus?