Control: tag -1 confirmed Hello Vincent,
Vincent Lefevre [2015-10-09 3:13 +0200]: > After the upgrade to systemd packages 227-1, I get various timeouts > with lightdm: > > [...] > Oct 09 02:57:45 zira systemd[1581]: run-rpc_pipefs.mount: Mount process > exited, code=exited status=1 > Oct 09 02:57:45 zira systemd[1581]: Failed unmounting /run/rpc_pipefs. > Oct 09 02:57:45 zira umount[1587]: umount: /boot: umount failed: Operation > not permitted [...] Note that these "failed to unmount" messages are from an *user* systemd instance, not from pid 1. This explains the permission errors. I confirm this behaviour, but it should be harmless -- my VMs boot just fine with these, it's mostly cosmetical. Bug #801361 was just filed for something which I suspect to be the same issue, BTW (but not confirmed yet). If it's the same, we can track the confusing "failed to unmount" issue there. > Oct 09 02:58:10 zira lightdm[1578]: pam_systemd(lightdm-greeter:session): > Failed to create session: Connection timed out > [...] That might be a followup of the above (user systemd instance failed due to the bad unmounting, and thus session creation failed), or something entirely unrelated. I don't see this kind of failure in a Debian sid VM (LXDE with lightdm), and the "boot-smoke" autopkgtest ran fine as well. However: I do see the bug in an Ubuntu VM (with https://launchpad.net/~pitti/+archive/ubuntu/systemd, i. e. 227 plus latest changes from trunk) when running the boot-smoke test, so I can reproduce this. I'll bisect / report upstream, etc. Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
