On 10/08/2023 16:53, gene heskett wrote:
On 8/9/23 21:15, Max Nikulin wrote:
On 08/08/2023 09:57, gene heskett wrote:
dbus-update-activation-environment: error: unable to connect to
D-Bus: Failed to connect to socket /run/user/1000/bus: Connection
refused
...
Try to figure out at which moment such messages appear. Try "busctl
--user" and "busctl --user status" as a sanity check.
Both of those get somewhat copious outputs, what should I be looking
for? Should it name the app?
You can compare usual output of the commands and their output just after
the error message appears. You may get some impression of features
exposed through D-Bus.
Looking in /etc/dbus-1, I see two dirs, one of which is empty:
What do you expect to find there? Packages put files into
/usr/share/dbus-1. Systemd units may tell that they may be activated
through D-Bus. Applications may express in .desktop files that they
should handle arguments through D-Bus and Exec=... should be ignored.
dbus has always been a puzzle to me. It has no man pages to explain its
functions.
There are a lot of docs for particular D-Bus APIs, e.g.
https://www.freedesktop.org/software/systemd/man/org.freedesktop.hostname1.html
If you are looking for some overview and introduction then starting
points may be
https://en.wikipedia.org/wiki/D-Bus
and docs linked from
https://www.freedesktop.org/wiki/Software/dbus/
e.g.
https://www.freedesktop.org/wiki/IntroductionToDBus/
The point is that if some application can not connect to D-Bus then
arbitrary features may be broken. However your error is either extremely
severe since session D-Bus is not running at all or it is almost
harmless since it appears due to some race on login or logout.
