Package: systemd Version: 20-1 Severity: important Since recently my computer doesn't boot correctly with systemd installed. Network and graphical desktop don't start for example. Errors from network- manager indicate that it can't connect the dbus system socket at /var/run/dbus/system_bus_socket. Examination indicates that this file is on a temp filesystem mounted at boot time and so it doesn't get created or something dunring the boot sequence. If I create the directory manually then stop and start dbus through systemctl I can then carry on to start network-manager and gdm normally. However, this is very frustrating because it means my computer just won't boot normally.
One oddity is that if I start it using the grub "rescue" mode, this problem doesn't occur. I am therefore suspicious that during the normal boot sequence this mount overwrites the systemd dbus socket. Perhaps there's a systemd incompatibility with something early on in the boot sequence that causes /var/run to be mounted as a tmpfs? dbus: Installed: 1.4.6-1 network-manager: Installed: 0.8.3.999-1 Interestingly the owner of /var/run is mountkernfs.sh as you probably know. However, $RAMRUN is no in my environment: root@allie:/etc/default# fgrep RAMRUN * rcS:RAMRUN=no Yet it is clearly mounted as a tmpfs: root@allie:/etc/default# mount | fgrep /var/run tmpfs on /var/run type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755) But it's not in fstab: root@allie:/etc/default# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'vol_id --uuid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 # / was on /dev/sdc2 during installation UUID=6ed62e14-2a42-450e-9b1c-8a395564bdf4 / ext4 errors =remount-ro,discard 0 1 # /home was on /dev/sdd2 during installation UUID=7b1c0169-dbb6-4b16-9c20-c7d91268e186 /home ext4 defaults 0 2 # swap was on /dev/sdc1 during installation UUID=ee759df1-f898-4171-b04a-b3e66b38696e none swap sw 0 0 mediacentre:/ /media/mediacentre nfs4 defaults,user,noauto 0 0 (as you can see this was a fairly fresh install from late last year using squeeze almost release then upgraded to sid). I think that the problem may be with /lib/systemd/system/var-run.mount. This appears to be remounting /var/run, and probably stamping on the existing dbus socket listener in the dbus subdir. Thoughts? Christian -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (701, 'unstable'), (601, 'testing'), (501, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii libaudit0 1.7.13-1+b2 Dynamic library for security audit ii libc6 2.11.2-13 Embedded GNU C Library: Shared lib ii libcap2 1:2.20-1 support for getting/setting POSIX. ii libcryptsetup1 2:1.2.0-2 libcryptsetup shared library ii libdbus-1-3 1.4.6-1 simple interprocess messaging syst ii libpam0g 1.1.2-2 Pluggable Authentication Modules l ii libselinux1 2.0.96-1 SELinux runtime shared libraries ii libudev0 167-2 libudev shared library ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra ii util-linux 2.17.2-9.1 Miscellaneous system utilities Versions of packages systemd recommends: ii libpam-systemd 20-1 system and service manager - PAM m Versions of packages systemd suggests: ii systemd-gui 20-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
