<div dir="ltr"><div><br></div><div><br></div><div><div><div> % systemctl --version</div><div>systemd 233<br>+PAM -AUDIT
-SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT
+GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN
default-hierarchy=hybrid</div><div><br></div></div>% machinectl list<br><div>MACHINE CLASS SERVICE OS VERSION ADDRESSES<br>poppy container systemd-nspawn fedora 26 192.168.1.94...</div><div><br></div>% machinectl show poppy <br><div>Name=poppy<br>Id=59b720b533834a4eafe07a62c2482266<br>Timestamp=Wed 2017-07-12 22:07:15 CEST<br>TimestampMonotonic=6928076<br>Service=systemd-nspawn<br>Unit=systemd-nspawn@poppy.service<br>Leader=648<br>Class=container<br>RootDirectory=/var/lib/machines/poppy<br>State=running</div><div><br></div><div>After upgrade from Fedora 25 to 26, there is no more user dbus session for user in container.</div><div><br></div><div>On container:</div>$ ps -ef | grep dbus <br></div><div><div>5:dbus 35 1 0 Jul13 ? 00:00:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only<br>65:root 1195 1163 0 14:18 pts/0 00:00:00 grep -nI --color dbus</div><div><br></div><div>On host:</div><div>$ ps -ef | grep dbus <br>195:dbus 582 1 1 Jul12 ? 00:21:57 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation<br>204:gabx 614 602 0 Jul12 ? 00:00:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation<br>251:gabx 1593 1588 0 Jul12 ? 00:00:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3<br>333:vu-popp+ 16543 16502 0 22:52 ? 00:00:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only</div><div><br></div><div>On container, user can't connect to dbus session, and I have no idea why. <br></div><div>May someone please give me some hints on how to debug this issue? Thank you<br></div></div></div>