Re: dbus and swapping systemd targets.
Simon McVittie <smcv-ZGY8ohtN/[email protected]>
| Newsgroups | gmane.comp.freedesktop.dbus |
|---|---|
| Message-ID | <[email protected]> |
On Tue, 09 May 2017 at 16:42:41 +0930, Simon Lees wrote:
> Having done that most desktops won't boot due to not being able to
> connect to dbus and running dbus monitor from the ssh session reports.
>
> Failed to open connection to session bus: Failed to connect to socket
> /run/user/1001/bus: Connection refused
>
> Does anyone have any suggestions for making this work better?
Please look at the Journal log and see whether something has been
stopped that should not have been. If that doesn't guide you to a solution,
please tell us what happened, with excerpts from the log wherever they
seem relevant.
I would guess that `systemctl isolate` might be terminating the
`systemd --user` instance that was started by your ssh login,
which is what listens on the $XDG_RUNTIME_DIR/bus socket? But that's
a wild guess that is not based on any evidence, because I don't have
any evidence.
S
_______________________________________________
dbus mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dbus