On Sat, Feb 14, 2015 at 9:37 PM, Alison Chaiken <[email protected]> wrote: > > Mantas: > > It's not broken on stock systemd. As long as your `systemd --user` > instance > > is running, systemctl can contact it directly over the > > "$XDG_RUNTIME_DIR/systemd/private" socket, so there's no hard dependency > on > > on any D-Bus bus either (neither system nor session nor user). > > > > So if you see `systemctl --user` trying to contact systemd over the bus, > it > > only does so after it has given up trying to contact it over the private > > socket. Does that socket exist? > > No, I gather that's the problem: 'ls $XDG_RUNTIME_DIR' shows no > systemd sub-directory at all.
That's weird. Does that directory have correct permissions (owned by you, etc.)? Can you mkdir the "systemd" subdirectory manually? Also try editing [email protected] to launch systemd with --log-level=debug to see if it reveals anything more useful. > > Also check if the system service "user@<your uid>.service" is active, > if it > > has logged any errors. Try starting that .service manually too. > > 'systemctl start [email protected]' shows no errors in the journal; it > just seems to 'exit 0' with no lasting effects. > I suppose that gnome-session is supposed to create > $XDG_RUNTIME_DIR/systemd/private and for some reason, silently fails > to do so. gnome-session shows no associated errors in the journal > either. > It's systemd that would be listening on this socket, so it's systemd that would be creating it. gnome-session has absolutely nothing to do with this... (At most, sometime in the future it might connect to the `systemd --user` instance, or be replaced by it entirely; but it has no hand in actually starting it.) -- Mantas Mikulėnas <[email protected]>
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
