Bug#634472: systemd doesn't start dbus.socket
Package: systemd Version: 37-1.1 Followup-For: Bug #634472 Is there any plan on bringing closure to this bug report. I don't know why setserial was installed default on my box but looking at it, it is not really a package required to be installed. If it is something that'll be installed on most boxes, this bug should be brought to closure soon. When trying systemd, because of this bug, it give a false impression that systemd is still broken. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii initscripts 2.88dsf-22 ii libacl1 2.2.51-5 ii libaudit0 1:1.7.18-1.1 ii libc6 2.13-27 ii libcap2 1:2.22-1 ii libcryptsetup4 2:1.4.1-2 ii libdbus-1-3 1.5.10-1 ii libpam0g1.1.3-7 ii libselinux1 2.1.9-2 ii libsystemd-daemon0 37-1.1 ii libsystemd-login0 37-1.1 ii libudev0175-3.1 ii libwrap07.6.q-23 ii udev175-3.1 ii util-linux 2.20.1-4 Versions of packages systemd recommends: ii libpam-systemd 37-1.1 Versions of packages systemd suggests: ii python 2.7.2-10 ii systemd-gui 37-1.1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634472: systemd doesn't start dbus.socket
Hi Tollef, thank you for your reply. I do not have nfs-common installed, but the problem may yet be the same. Here's an excerpt from my /var/log/dmesg: [5.413304] systemd[1]: Found ordering cycle on basic.target/start [5.413312] systemd[1]: Walked on cycle path to sockets.target/start [5.413319] systemd[1]: Walked on cycle path to dbus.socket/start [5.413324] systemd[1]: Walked on cycle path to sysinit.target/start [5.413330] systemd[1]: Walked on cycle path to setserial.service/start [5.413335] systemd[1]: Walked on cycle path to basic.target/start [5.413341] systemd[1]: Breaking ordering cycle by deleting job dbus.socket/start [5.413354] systemd[1]: Found ordering cycle on basic.target/start [5.413360] systemd[1]: Walked on cycle path to sysinit.target/start [5.413365] systemd[1]: Walked on cycle path to setserial.service/start [5.413371] systemd[1]: Walked on cycle path to basic.target/start [5.413376] systemd[1]: Breaking ordering cycle by deleting job setserial.service/start It doesn't make any sense though. The only thing required for setserial.service (which is not a proper systemd service unit but a SysV init script service unit) is $remote_fs (or remote-fs.target), which isn't involved in any of the two cycles above. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634472: systemd doesn't start dbus.socket
]] Matthias Berndt Hi, | thank you for your reply. I do not have nfs-common installed, but the | problem may yet be the same. Here's an excerpt from my /var/log/dmesg: | | [5.413304] systemd[1]: Found ordering cycle on basic.target/start | [5.413312] systemd[1]: Walked on cycle path to sockets.target/start | [5.413319] systemd[1]: Walked on cycle path to dbus.socket/start | [5.413324] systemd[1]: Walked on cycle path to sysinit.target/start | [5.413330] systemd[1]: Walked on cycle path to setserial.service/start | [5.413335] systemd[1]: Walked on cycle path to basic.target/start | [5.413341] systemd[1]: Breaking ordering cycle by deleting job | dbus.socket/start | [5.413354] systemd[1]: Found ordering cycle on basic.target/start | [5.413360] systemd[1]: Walked on cycle path to sysinit.target/start | [5.413365] systemd[1]: Walked on cycle path to setserial.service/start | [5.413371] systemd[1]: Walked on cycle path to basic.target/start | [5.413376] systemd[1]: Breaking ordering cycle by deleting job | setserial.service/start I suspect # chkconfig: 2345 50 75 in the setserial init script might be to blame. Any chance you could remove that line and see if that fixes it? | It doesn't make any sense though. The only thing required for | setserial.service (which is not a proper systemd service unit but a | SysV init script service unit) is $remote_fs (or remote-fs.target), | which isn't involved in any of the two cycles above. Yeah, that should be ok, I think. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634472: systemd doesn't start dbus.socket
Hi, I suspect # chkconfig: 2345 50 75 in the setserial init script might be to blame. Any chance you could remove that line and see if that fixes it? Yes, removing that line does fix the problem. Regards Matthias -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634472: systemd doesn't start dbus.socket
Package: systemd Version: 29-1 Severity: normal Hi, After I installed systemd today, I noticed that NetworkManager had stopped working. There were two reasons, the first was that NetworkManager wasn't enabled; this could easily be fixed with systemctl enable NetworkManager.service. But that alone wasn't enough as NetworkManager.service uses bus activiation and thus requires a running dbus daemon. If I create the dbus socket by calling systemctl start dbus.socket before starting a graphical desktop, everything works fine. But I couldn't get it to create this socket by default. systemctl enable dbus.socket doesn't work (Unit files contain no applicable installation information. Ignoring.). ln -s /lib/systemd/system/dbus.socket /etc/systemd/system/multi-user.target.wants also didn't work, it's just ignored. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.39-2-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to //bin/bash Versions of packages systemd depends on: ii initscripts2.88dsf-13.11 scripts for initializing and shutt ii libaudit0 1.7.13-1.2Dynamic library for security audit ii libc6 2.13-10 Embedded GNU C Library: Shared lib ii libcap21:2.21-2 support for getting/setting POSIX. ii libcryptsetup1 2:1.3.0-3 libcryptsetup shared library ii libdbus-1-31.4.12-5 simple interprocess messaging syst ii libpam0g 1.1.3-2 Pluggable Authentication Modules l ii libselinux12.0.98-1.1SELinux runtime shared libraries ii libudev0 171-3 libudev shared library ii libwrap0 7.6.q-21 Wietse Venema's TCP wrappers libra ii udev 171-3 /dev/ and hotplug management daemo ii util-linux 2.19.1-4 Miscellaneous system utilities Versions of packages systemd recommends: ii libpam-systemd29-1 system and service manager - PAM m Versions of packages systemd suggests: ii python2.6.7-1interactive high-level object-orie ii systemd-gui 29-1 system and service manager - GUI -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634472: systemd doesn't start dbus.socket
]] Matthias Berndt | After I installed systemd today, I noticed that NetworkManager had stopped | working. Do you have nfs-common installed? If so, I suspect this is a duplicate of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622394 -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
