Ubuntu
glibc package

Kernel panic while configure

Bug #1269669 reported by Alan
This bug report is a duplicate of:  Bug #1269731: init crashed with SIGSEGV. Edit Remove
44
This bug affects 9 people
Affects Status Importance Assigned to Milestone
glibc (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

After a upgrade of some packages the configure process of libc6 version 2.18 generates a kernel panic.
When I try reconfigure again the packages broken (sudo dpkg --configure -a) I get the same kernel panic.

I must poweroff my computer from the button. That means that I not have a full core dump..
But I found a similar kernel panic that says:

Kernel panic - not syncing: Attempted to kill init! exitcode=0x....

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in glibc (Ubuntu):
status: New → Confirmed
Revision history for this message
Quinn Balazs (qbalazs) wrote :

Could anyone affected here attach the contents of "etc/default/grub".

Changed in glibc (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Alan (alanjas) wrote :
Revision history for this message
David Oftedal (rounin) wrote :

This started happening on my system when I tried to upgrade to 14.04.

Installing libc6, either amd64 or i386, it would appear, and either via do-release-upgrade or dpkg directly, will cause the kernel panic.

"not syncing: Attempted to kill init!"

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.