[systemd-devel] [help][227] Enabling a user service breaks a little my system!

[Jorge Araya Navarro]

Well, I'm using dbus version 1.10.2 in a Arch Linux-based GNU/Linux distribution. Checking their
PKGBUILD the `--enable-user-session` option was enabled.

--8<---------------cut here---------------start------------->8---
$ systemctl status -l dbus
● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
   Active: active (running) since jue 2015-11-26 12:26:51 CST; 26min ago
     Docs: man:dbus-daemon(1)
 Main PID: 445 (dbus-daemon)
   CGroup: /system.slice/dbus.service
           └─445 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
--8<---------------cut here---------------end--------------->8---
--8<---------------cut here---------------start------------->8---
$ systemctl --user status -l dbus
● dbus.service - D-Bus User Message Bus
   Loaded: loaded (/usr/lib/systemd/user/dbus.service; indirect; vendor preset: enabled)
   Active: active (running) since jue 2015-11-26 12:28:40 CST; 25min ago
     Docs: man:dbus-daemon(1)
 Main PID: 3652 (dbus-daemon)
   CGroup: /user.slice/user-1000.slice/user at 1000.service/dbus.service
           ├─3652 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation
           ├─3896 /usr/lib/GConf/gconfd-2
           └─3987 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
--8<---------------cut here---------------end--------------->8---

I notice that `gnome-keyring-daemon` is started by dbus.service. However, in my `.xprofile` file at
the `--components` I use more arguments. Actually, I call `gnome-keyring-daemon` like this:

--8<---------------cut here---------------start------------->8---
eval $(gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)
export GPG_AGENT_INFO SSH_AUTH_SOCK
systemctl --user import-environment GPG_AGENT_INFO
systemctl --user import-environment SSH_AUTH_SOCK
--8<---------------cut here---------------end--------------->8---

Not sure if fixing the `Failed to connect to bus: No such file or directory` thing will make
everything else in my system to work back normal or I'll have to change
/usr/lib/systemd/user/dbus.service to suite my needs... 

El jueves 26 de noviembre del 2015 a las 0605 horas, Simon McVittie escribió:

> On 26/11/15 06:33, Jorge Araya Navarro wrote:
>> $ LC_ALL=C systemctl --user
>> Failed to connect to bus: No such file or directory
>
> Do you have a D-Bus session bus as a user service?
>
> If you are using Debian or one of its derivatives like Ubuntu, install
> the dbus-user-session package. This is probably what you want if you
> like user services, but do read its Description first, because it
> changes the interpretation of the D-Bus session bus system-wide.
>
> If you are using Arch Linux, I think recent versions of their dbus
> package make the session bus into a user service unconditionally.
>
> If you are using some other distribution, talk to your distribution's
> dbus and systemd maintainers. I would suggest that distributions that
> are conservative about backwards-compatibility should package the user
> session bits separately so that they are an opt-in (like I did in
> Debian), and bleeding-edge/"legacy-free" distributions should just
> enable them (like in Arch Linux).
>
> If you are compiling your own dbus (>= 1.10), or you *are* your
> distribution's dbus maintainer, the --enable-user-session configure
> option is the one that makes the session bus into a user service. It
> just installs some extra files: on Debian, we always enable that option,
> but we split the files into the dbus-user-session package instead of
> including them in the main dbus package.

-- 
👋 Pax et bonum.
Jorge Araya Navarro
https://es.gravatar.com/shackra