On 26.02.2012 19:02, Teodor MICU wrote: > 2012/2/26 Michael Biebl <bi...@debian.org>: >> Could you send the output of >> systemctl status dbus.socket dbus.service >> directly after (re)boot. > > Here it is. > | dbus.socket - D-Bus System Message Bus Socket > | Loaded: loaded (/lib/systemd/system/dbus.socket; static) > | Active: inactive (dead) > | CGroup: name=systemd:/system/dbus.socket > | > dbus.service - D-Bus System Message Bus > | Loaded: loaded (/lib/systemd/system/dbus.service; static) > | Active: inactive (dead) > | CGroup: name=systemd:/system/dbus.service
Most likely a duplicate of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634472 Could you run systemd in debug mode [1] and attach the output of dmesg. I suspect there is a dependency cycle in one of the sysv init scripts. > Obviously, there is no dbus* process. Also, halt/reboot/shutdown doesn't work: > | shutdown: /run/initctl: No such file or directory > | init: /run/initctl: No such file or directory Different issue: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657979 [1] http://wiki.debian.org/systemd#Debugging_systemd [2] http://wiki.debian.org/systemd#Issue_.233:_Dependency_cycle_in_portmap.2BAC8-nfs-common.2BAC8-rpcbind -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
