Karmic - Corrupted Recovery Menu

Bug #458352 reported by emarkay
50
This bug affects 9 people
Affects Status Importance Assigned to Milestone
mountall (Ubuntu)
Incomplete
High
Unassigned
Karmic
Incomplete
High
Unassigned

Bug Description

In Recovery Menu, I have now seen this on 2 machines, when trying to "Make free space".

"Mountall cancelled.
general error mounting filesystems.
A Maintenance shell will now be started.
CONTROL-D will teminate this shell and re-try."

Then it goes to a corrupted CLI, missing the first character, while still in the red and blue Recovery menu. Nothing works except pushing the "Reset" button or powering down.

Also may be related but is NOT the same issue as :
https://bugs.launchpad.net/ubuntu/+bug/452218
and much less, but still related:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/363271

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in friendly-recovery.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntu → friendly-recovery (Ubuntu)
Revision history for this message
emarkay (mrk) wrote :

I did not think to look for "friendly".
I do try to look for appropriate package, but that process is not always straightforward.
(FWIW, see post on this - not related, but applicable to this reply:http://ubuntuforums.org/showthread.php?p=8146872#post8146872)

Revision history for this message
Brian Murray (brian-murray) wrote :

I've confirmed this using friendly-recovery version 0.2.8.1 on Karmic Koala. Attached is a screenshot demonstrating the issue. Additionally, pressing "Ctrl D" does not terminate the shell.

Changed in friendly-recovery (Ubuntu):
status: New → Triaged
importance: Undecided → High
Revision history for this message
Brian Murray (brian-murray) wrote :

Actually, I seem to get this message after pressing the arrow key down 3 times. Navigating the menu view letter keys corresponding to the menu items works fine.

Revision history for this message
Gabriel Forster (gforster) wrote :

I am having the same issue. it is a laptop that is dual-booting XP. Happened after the last update & upgrade just a few hours ago.

Revision history for this message
Pete Savage (petesavage) wrote :

Same issue here on a machine that I did a resize on

Revision history for this message
Pete Savage (petesavage) wrote :

Mine seems to have an issue with swap. mountall: Problem activating swap: I see this if I type exit at the "prompt"

Revision history for this message
Matthew Tompsett (matthewbpt) wrote :

I can confirm this problem after upgrading from Jaunty to Karmic. The problem exists even when booting in recovery mode from the Jaunty kernel after upgrading to Karmic.

Revision history for this message
Matthew Tompsett (matthewbpt) wrote :

This is quite a serious issue as the recovery mode is completely unusable in its current state ...

Revision history for this message
John Yates (andyfranyates) wrote :

Still happening with friendly-recovery version 0.2.8.2.

Revision history for this message
Rasmus Öhrstig Bratt (rasmus-ohrstig) wrote :

I have the same issue on a clean installation apart from WinXP on another drive, not that I think it matters.

The corruption seems to happen when you push down arrow twice. It continues to respond to arrow key presses by redrawing the white on red text.

Revision history for this message
John Yates (andyfranyates) wrote :

I tried removing friendly-recovery to go straight to the password prompt.
Entering anything just repeats the prompt. I think it must be some sort
of keyboard problem.

Revision history for this message
John Yates (andyfranyates) wrote :

This morning's update fixed this for me.
These packages were in the update:

mountall (1.0) ...

libpulse0 (1:0.9.19-0ubuntu4)

libpulse-browse0 (1:0.9.19-0ubuntu4)

pulseaudio-utils (1:0.9.19-0ubuntu4)

libpulse-mainloop-glib0 (1:0.9.19-0ubuntu4)

libusplash0 (0.5.48)

nvidia-173-modaliases (173.14.20-0ubuntu5)

nvidia-185-modaliases (185.18.36-0ubuntu9)

nvidia-96-modaliases (96.43.13-0ubuntu6)

software-center (1.0.2)

usplash (0.5.48)

xserver-xorg-input-evdev (1:2.2.5-1ubuntu6)

xserver-xorg-input-vmmouse (1:12.6.4-1ubuntu3)

pulseaudio-module-udev (1:0.9.19-0ubuntu4)

pulseaudio (1:0.9.19-0ubuntu4)

pulseaudio-esound-compat (1:0.9.19-0ubuntu4)

pulseaudio-module-gconf (1:0.9.19-0ubuntu4)

pulseaudio-module-x11 (1:0.9.19-0ubuntu4)

pulseaudio-module-bluetooth (1:0.9.19-0ubuntu4)

FYI.

Revision history for this message
Steve Langasek (vorlon) wrote :

Yes, it looks like this is a duplicate of bug #458060; closing.

affects: friendly-recovery (Ubuntu Karmic) → mountall (Ubuntu Karmic)
Changed in mountall (Ubuntu Karmic):
status: Triaged → Fix Released
Revision history for this message
emarkay (mrk) wrote :

I beg to differ on the duplication listing as well as the closing. If this is as wide ranging as the tertiary dupe indicates, fine, but, even after this afternoon's updates, it's COMPLETELY corrupted. I hope this does not make it into the final Karmic release!

Revision history for this message
FormerSlacker (sousa-paul) wrote :

I subscribed to a launchpad account simply to add that I'm also affected. Latest mountall did not change a thing. Recovery console is completely unusable after pressing the down arrow a couple of times. Corrupted cli etc...

Exact same situation as emarkay.

I've also noticed that if I switch to tty1 from X (ALT+CTRL+F1), login, load up nano with a file, scroll up/down with PAGE UP/DOWN repeatedly, I'm eventually greeted to the same situation. I seem to be dropped to a maintenance mode with the output that "mountall has failed" and a root prompt, as well as the cli being corrupted and unsuable.

This only happens on tty1, all other tty's are fine. These two issues seem very much related, and there definitely still is an issue IMO.

Changed in mountall (Ubuntu Karmic):
status: Fix Released → Confirmed
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Please attach your /etc/init/mountall.conf file

Changed in mountall (Ubuntu Karmic):
status: Confirmed → Incomplete
Revision history for this message
TMaster (tmaster) wrote :

I am affected by the same problem. It occurs only when booting to recovery mode - regular booting works fine. Still, it's very concerning to realize that once a problem occurs in my main setup, I may not be able to fix it easily.

Some additional details that may help:
- I consciously don' t use swap. Relying on swap space to avoid bugs is not an acceptable solution.
- I have multiple NTFS volumes for my Windows XP setup. Only my XP C: drive is (apparently) set to mount automatically when booting Kubuntu normally. My NTFS data volume needs to be mounted automatically from within Dolphin. Besides this, I think I just use a 10GB ext3 volume for my Kubuntu setup.
- System specs:
Pentium IV Northwood 2.8GHz with HyperThreading
2.5GB RAM
WD Caviar 40GB
Seagate Barracuda 160GB
Kubuntu 9.10 (Reasonably up-to-date, I will now install some recently released patches.)
KDE 4.3.2
Windows XP Home SP3

To obtain more information, please reply to this thread.

Revision history for this message
TMaster (tmaster) wrote :

I'm sorry for the double post, just thought I'd mention two more things.

- I don't think this could be a duplicate of bug #458060, as that fix is supposed to already have been released.
If I broke some rules in replying to a bug marked as a dupe, I apologize. I am not yet familiar with Launchpad etiquette.

- Other than tzdata, no updates were available. I don't think timezones are related to this problem, so I'm still affected. I am now using an up-to-date setup.

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.