Ubuntu no longer boot after March 12th updates.

Bug #201688 reported by Nicolas Picard
12
Affects Status Importance Assigned to Milestone
Ubuntu
Confirmed
Undecided
Unassigned

Bug Description

After to have retrieved some updates on March 12th, specially after a python's upgrade that return error code 250..... System crashed after that and after reboot I got:

Gnome wont start and ask for user#pwd
Immediatly after logged in:

malloc : //bash/subst.c : 3472 : assertion botched
free : appel avec un bloc non alloué // ==== call with an unallocated block
Annulation // Abort

malloc : //bash/subst.c : 3472 : assertion botched
free : appel avec un bloc non alloué // ==== call with an unallocated block
Annulation .... init: tty1 main process ended , respawing

And it's asked for user#pwd and again....again.....

Revision history for this message
turox (tuxturox) wrote :

I can confirm this bug similar to Nicolas describes..
By trying to boot with different kernel it stops one time with initramfs
and another messages I get is /lib/ubev/vol_id abnormal exit.

Revision history for this message
Parthan SR (parth-technofreak) wrote :

Thank you for filing the bug and helping to make Ubuntu better. Can you check with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/201684 and confirm whether you also get the same error? If so, and as turox confirms, this bug can be marked as a duplicate of bug #201684. Thanks in advance.

Revision history for this message
turox (tuxturox) wrote :

The bug #201684 describes the same messages I get - and I can confirm this also. So this bug can be marked as duplicate.

Revision history for this message
K.C. Wang (k.c.wang) wrote :

Confirm this. I got:

malloc : //bash/subst.c : 3472 : assertion botched.
free: called with unallocated block argument.
Aborting.
.......

And I can't login.

Revision history for this message
jarteq (j.p.s.) wrote :

Same happend here xD

What to do next, I can't login anymore

Revision history for this message
K.C. Wang (k.c.wang) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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