Le 27/02/2017 à 09:51, Stephan Sokolow (You actually CAN reply) a écrit : > I'm not sure if it's relevant, but I managed to get similar > connection timeouts (specifically, `systemctl` consistently failing > with timeouts on `org.freedesktop.systemd1`) when I ran `apt-get > install systemd-cron` and then changed my mind after I realized my > systemd was too early to support hourly cronjobs and ran > `apt-get install cron`. > > (Luckily for me, I was just experimenting with reducing total memory > usage in a staging VM, so I just reset it to a fresh image and re-ran > ansible-playbook.)
I forgot to update this bug report. On my machine, I did some cleanup (apt-get autoremove + manual removal of package that are not available in stretch any more). This solve the problem: the machine boots correctly without any problematic interaction with dbus. If you wish to dig into this problem, I can provide you the dpkg logs (so that you know the exact list of removed pacakges), else you can close this bug (I wont try the packages one by one to find the culprit and the missing Breaks in systemd or dbus). Regards, Vincent -- Vincent Danjean GPG key ID 0xD17897FA vdanj...@debian.org GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main _______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers