Indeed a broken unit shouldn't fail the boot or shutdown unless it marks
itself as being required for booting. Can you please attach the said
unit, so that I can reproduce this?
It seems your system has some worse problems too:
Apr 26 13:02:29 hostname systemd[1]: Failed to activate swap
/dev/mapper/root-swap.
Apr 26 13:02:36 hostname kernel: usb 1-13: device descriptor read/64, error -110
Apr 26 13:02:39 hostname systemd[1]: Failed to start Light Display Manager.
Apr 26 13:02:56 hostname libvirtd[2008]: Interner Fehler: Untergeordneter
Prozess (/usr/sbin/dmidecode -q -t 0,1,4,17) unerwartet Ende Status 1:
/dev/mem: No such file or directory
All of these are strange and seem to indicate kernel/hardware problems
(message 2 and 4), perhaps a broken fstab (message 1), etc.
Also, there's not only Ctrl+Alt+Del, you can also use "poweroff" or shut
down from the menus. Please don't just pull the plug; if nothing else
helps, "sudo poweroff -f" is still a lot better than that..
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448656
Title:
systemd doesn't allow proper shutdown after it encountered errornous
.service
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448656/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
