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