Hi KiBi! Am 21.09.2013 14:02, schrieb Cyril Brulebois: > dist-upgrading sid yesterday led to: > | Setting up pcscd (1.8.8-4+b1) ... > | Failed to issue method call: Unit var-run.mount failed to load: No such > file or directory. See system logs and 'systemctl status var-run.mount' for > details. > | invoke-rc.d: initscript pcscd, action "start" failed. > | dpkg: error processing pcscd (--configure): > | subprocess installed post-installation script returned error exit status 6 > […] > | Setting up bluez (4.101-2+b1) ... > | update-rc.d: warning: start and stop actions are no longer supported; > falling back to defaults > | Failed to issue method call: Unit var-run.mount failed to load: No such > file or directory. See system logs and 'systemctl status var-run.mount' for > details. > | invoke-rc.d: initscript bluetooth, action "start" failed. > | dpkg: error processing bluez (--configure): > | subprocess installed post-installation script returned error exit status 6
I've tried to reproduce the issue within a VM (what I did is install a jessie system, install systemd v44 and enable it, reboot with systemd as PID=1, then dist-upgrade to sid, including the upgrade to v204). I did that for a standard desktop installation (GNOME). I couldn't reproduce the failure. We did drop the var-run.mount and var-lock.mount units in v204, but that doesn't lead to aforementioned error message here and I couldn't fine another service, which would trigger/request its start. Searching around a bit, I found a few references to users who had a similar problem when using NFS shares. KiBi, could you attach your fstab / mount output. Not sure if this is a red herring, but tbh I'm a bit out of ideas where this error is coming from. Michael -- 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
