Just want to give a heads up that manual unpack followed by apt install -f still crashes, however the VM automatically rebooted this time (instead of remaining dead) and I was able to proceed with usual apt update afterwards with no further issues.
root@web1:~# curl -LO https://launchpad.net/ubuntu/+archive/primary/+files/libjson-c2_0.11-4ubuntu2.2_amd64.deb % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 21858 100 21858 0 0 10273 0 0:00:02 0:00:02 --:--:-- 164k root@web1:~# dpkg --unpack libjson-c2_0.11-4ubuntu2.2_amd64.deb (Reading database ... 39096 files and directories currently installed.) Preparing to unpack libjson-c2_0.11-4ubuntu2.2_amd64.deb ... Unpacking libjson-c2:amd64 (0.11-4ubuntu2.2) over (0.11-4ubuntu2.2) ... Processing triggers for libc-bin (2.23-0ubuntu11) ... root@web1:~# reboot root@web1:~# logout [root@redacted ~]# vzctl enter 040199a0-e959-4428-87e6-76dd3b26262e entered into CT root@web1:/# apt install -f Reading package lists... Done Building dependency tree... 50% [1]+ Stopped apt install -f Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up libjson-c2:amd64 (0.11-4ubuntu2.2) ... Processing triggers for libc-bin (2.23-0ubuntu11) ... Got signal 9 [root@redacted ~]# -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update Status in json-c package in Ubuntu: Triaged Bug description: Installing the 0.11-4ubuntu2.1 security update on a Xenial system with upstart installed, the system crashes with a kernel panic. The error message is: [ 99.992278] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 [ 99.992278] [ 99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu [ 99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 99.996057] 0000000000000086 0f10ff6977efbf32 ffff88003d45fe10 ffffffff8140926b [ 99.996057] ffffffff81caddf8 ffff88003d45fea8 ffff88003d45fe98 ffffffff81195a84 [ 99.996057] ffff880000000010 ffff88003d45fea8 ffff88003d45fe40 0f10ff6977efbf32 [ 99.996057] Call Trace: [ 99.996057] [<ffffffff8140926b>] dump_stack+0x6d/0x92 [ 99.996057] [<ffffffff81195a84>] panic+0xd3/0x227 [ 99.996057] [<ffffffff81088ded>] do_exit+0xb9d/0xba0 [ 99.996057] [<ffffffff81088e77>] do_group_exit+0x47/0xb0 [ 99.996057] [<ffffffff81088ef4>] SyS_exit_group+0x14/0x20 [ 99.996057] [<ffffffff818449db>] entry_SYSCALL_64_fastpath+0x22/0xcb [ 99.996057] Kernel Offset: disabled Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue. Steps to reproduce: * Create a system with Xenial installed (I'm using an AWS instance with AMI ami-0f2ed58082cb08a4d) * Install upstart: apt-get install upstart-sysv * Reboot * Update apt and upgrade the packages: apt-get update && apt-get upgrade . This causes the kernel panic. * To repeat the kernel panic, run dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
