Comment # 7 on bug 1020363 from
is any action being taken on this bug?

I encounter this quite often.  Happens when I have an open ssh session and try
to change from multi-user target to graphical target.  I get:
  "Could not sync environment to dbus."

killing session:
USER        PID %CPU %MEM     VSZ   RSS TTY STAT START  TIME COMMAND
message+  14949  0.0  0.0   45876  5862 ?   Ss   09:29  0.00 /bin/dbus-daemon
--system --address=systemd: --nofork --nopidfile --systemd-activation

allows reaching graphical target


ps: the work-a-round removing "the symlink
'/usr/lib/systemd/user/sockets.target.wants/dbus.socket` for the old behavior
(session D-Bus no longer started via systemd)"
works for me.

but is a "work-a-round" a solution?


You are receiving this mail because: