Closed brittyazel closed 1 year ago
https://docs.flatpak.org/en/latest/sandbox-permissions.html#d-bus-access
Access to the entire bus with --socket=system-bus or --socket=session-bus should be avoided, unless the application is a development tool.
If I'm not mistaken, enabling system bus permission effectively disables the sandbox. It's only meant for briefly testing things.
Is it still an issue with https://github.com/flathub/com.slack.Slack/pull/205 ?
Right now, when launching Slack I am getting a multitude of dbus errors:
[2:0602/111324.324733:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
These errors seem to be resolved when enabling socket=system-bus in Flatseal. Would you consider enabling that in the manifest by default? Is there a reason to not allow access to the dbus system bus?