[Assist] systemctl --user status Failed to get D-Bus connection: Connection refused

Wed Apr 9 04:39:02 GMT 2014

I don't know what happen, but I like it!

        <(jorge at abril)---(mar abr 08 22:36:38)>
        [~][1] $ ps axxx | grep user
         7395 ?        Ss     0:00 /usr/lib/systemd/systemd --user
         7533 ?        Sl     0:00 /usr/lib/gvfs//gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
         8363 pts/1    R+     0:00 grep --color=auto user

        <(jorge at abril)---(mar abr 08 22:36:44)>
        [~][2] $ syste
        systemctl                       systemd-coredumpctl             systemd-nspawn
        systemd-analyze                 systemd-delta                   systemd-run
        systemd-ask-password            systemd-detect-virt             systemd-stdio-bridge
        systemd-cat                     systemd-inhibit                 systemd-tmpfiles
        systemd-cgls                    systemd-machine-id-setup        systemd-tty-ask-password-agent
        systemd-cgtop                   systemd-notify                  systemsettings

        <(jorge at abril)---(mar abr 08 22:36:44)>
        [~][2] $ systemctl --user status
        ● abril
            State: running
             Jobs: 0 queued
           Failed: 0 units
            Since: mar 2014-04-08 10:12:01 CST; 12h ago
           CGroup: /user.slice/user-1000.slice/user at 1000.service
                   ├─7395 /usr/lib/systemd/systemd --user
                   └─7407 (sd-pam)  

        <(jorge at abril)---(mar abr 08 22:37:05)>
        [~][3] $ 

        <(jorge at abril)---(mar abr 08 22:38:11)>
        [~][4] $ systemctl --version
        systemd 212
        +PAM -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ +SECCOMP -APPARMOR

        <(jorge at abril)---(mar abr 08 22:38:15)>
        [~][5] $ 

:D
-- 
Pax et bonum.
Jorge Araya Navarro.
Diseñador publicitario, programador Python/C++ y colaborador en Parabola
GNU/Linux-libre. 

El vie, 04-04-2014 a las 09:39 -0400, Luke Shumaker escribió:

> At Fri, 04 Apr 2014 01:26:35 -0600,
> Jorge Araya Navarro wrote:
> > Here:
> >         <(jorge at abril)---(vie abr 04 01:24:02)>
> >         [~][3] $ LC_ALL=C stat /run/user/1000/systemd/
> >         ...
> >         
> >         <(jorge at abril)---(vie abr 04 01:24:09)>
> >         [~][4] $ LC_ALL=C stat /run/user/1000/systemd/private
> >         ...
> > 
> > So far, so good... and so confuse! What could be going wrong here?
> 
> Did you also check that `systemctl --user status` was still giving you
> the D-Bus error message?  Also, if you had run `systemctl --user
> exit`, and haven't logged out since, it is still dissabled.
> 
> To clarify, when I say "log out", I mean log out of all user sessions.
> Verify that this was the case when you log back in by running
> `loginctl list-sessions`, and verifying that there is only one current
> session for your user.  It is possible that a background process is
> keeping an old session alive.  For example, I discovered that if I
> started X, then lxpanel would start menu-cached in the background,
> which would keep running and cause that session to persist even after
> I logged out.
> 
> > El jue, 03-04-2014 a las 23:27 -0400, Luke T.Shumaker escribió:
> > > At Thu, 03 Apr 2014 15:22:48 -0600,
> > > Jorge Araya Navarro wrote:
> > > > I followed the
> > > > instructions from Arch Linux wiki ( as read here
> > > > https://wiki.archlinux.org/index.php/Systemd/User ),
> > > 
> > > I'm not saying not to read that, there's some good stuff there, but on
> > > a scale of "garbage" to "quality documentation", that page is closer
> > > to the former.
> > 
> > Haha, very mean!
> 
> To be fair, it's because it's all changing so quickly.  There's
> "Setup" [for < 206], and "Setup since systemd 206"; BOTH of which
> contain information that is not true in systemd 212.  It's just hard
> to keep up, and update the entire page.
> 
> Basically, everything it says about setting up D-Bus is false.
> dbus.service/dbus.socket are now obsolete; this happens by default
> now.  The DBUS_SESSION_BUS_ADDRESS is now
> $XDG_RUNTIME_DIR/systemd/private instead of $XDG_RUNTIME_DIR/bus or
> $XDG_RUNTIME_DIR/dbus/user_bus_socket (both of which are mentioned in
> the "since 206" section).
> 
> That said, the DBUS_SESSION_BUS_ADDRESS environment variable should
> probably not be set.  With no value, everything should just find the
> correct address.  The systemd people are working to make this all
> simpler and not require these extra things, but sometimes that means
> yesterday's kludges break.
> 
> The variable is is set by /etc/X11/xinit/xinitrc.d/30-dbus, but that
> doesn't seem to mess anything up on my box.  If you are using a
> graphical login, the XDM or DE's session manager may be messing with
> D-Bus and actually mangaging to mess it up.  Try logging into a TTY
> when debugging this.
> 
> Happy hacking,
> ~ Luke Shumaker
> _______________________________________________
> Assist mailing list
> Assist at lists.parabolagnulinux.org
> https://lists.parabolagnulinux.org/mailman/listinfo/assist
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.parabolagnulinux.org/pipermail/assist/attachments/20140408/d74170e5/attachment-0001.html>