To chime in myself and give a differential diagnosis ... I don’t have /var/log/upstart because /var/log is a tmpfs. Do I have to create this subfolder?
Here’s the output from my PC: towolf@ovo:~$ initctl list avahi-daemon start/running, process 845 mountall-net stop/waiting mountnfs-bootclean.sh start/running passwd stop/waiting rc stop/waiting rsyslog start/running, process 841 screen-cleanup stop/waiting udev start/running, process 338 upstart-udev-bridge start/running, process 329 ureadahead-other stop/waiting console-setup stop/waiting hwclock-save stop/waiting idmapd-mounting stop/waiting plymouth-log stop/waiting rpcbind-boot stop/waiting failsafe stop/waiting hybrid-gfx stop/waiting mountall.sh start/running rfkill-store stop/waiting statd stop/waiting atd start/running, process 977 dbus start/running, process 728 mounted-var stop/waiting plymouth stop/waiting portmap stop/waiting resolvconf start/running ssh start/running, process 718 udev-fallback-graphics stop/waiting checkroot.sh start/running control-alt-delete stop/waiting hwclock stop/waiting mounted-proc stop/waiting network-manager start/running, process 838 alsa-store stop/waiting cups-browsed start/running, process 956 setvtrgb stop/waiting shutdown stop/waiting statd-mounting stop/waiting alsa-restore stop/waiting cron start/running, process 5873 gdm start/running, process 962 lightdm stop/waiting mountall stop/waiting mounted-debugfs stop/waiting mountkernfs.sh start/running binfmt-support stop/waiting console stop/waiting mounted-run stop/waiting acpid start/running, process 959 bluetooth stop/waiting checkfs.sh start/running checkroot-bootclean.sh start/running kmod stop/waiting mountnfs.sh start/running plymouth-stop stop/waiting rcS stop/waiting wait-for-state stop/waiting bootmisc.sh start/running flush-early-job-log stop/waiting friendly-recovery stop/waiting gssd-mounting stop/waiting rc-sysinit stop/waiting cups stop/waiting pulseaudio stop/waiting upstart-socket-bridge start/running, process 861 anacron start/running, process 15918 mountdevsubfs.sh start/running tty2 start/running, process 932 udevtrigger stop/waiting container-detect stop/waiting mounted-dev stop/waiting mtab.sh start/running tty3 start/running, process 934 udev-finish stop/waiting hostname stop/waiting mountall-reboot stop/waiting gssd stop/waiting mountall-shell stop/waiting mounted-tmp stop/waiting network-interface (lo) start/running network-interface (wlan0) start/running plymouth-splash stop/waiting plymouth-upstart-bridge stop/waiting portmap-wait stop/waiting tty1 stop/waiting udevmonitor stop/waiting usb-creator-gtk stop/waiting dmesg stop/waiting mountall-bootclean.sh start/running network-interface-security (network-manager) start/running network-interface-security (network-interface/wlan0) start/running network-interface-security (network-interface/lo) start/running network-interface-security (networking) start/running networking start/running procps stop/waiting rfkill-restore stop/waiting console-font stop/waiting idmapd stop/waiting network-interface-container stop/waiting ureadahead stop/waiting towolf@ovo:~$ df -h /var/log/ Filesystem Size Used Avail Use% Mounted on tmpfs 1,9G 896K 1,9G 1% /var/log towolf@ovo:~$ ll -d /var/log/upstart ls: cannot access /var/log/upstart: No such file or directory -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1120660 Title: Kernel Panic when running 'sudo dpkg --configure -a' ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1120660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
