Finally! Took a while to find this solution. I had a corrupted
VirtualBox Ubuntu VM, used a clone image and ran into this problem when
running updates via the GUI. Running it in a terminal window solved my
problem. Thank you Paul Brown.
The prompt suggested that I load it on both partitions
I guess this won't help very many people, but if you're encountering
this in VirtualBox like I do you can get passed the update if you have a
backup of your image.
Paul Brown wrote that he thinks that grub setup wants to open a
terminal-like window. Thank you for that comment. Because of that I
Here's a screenshot of mine, and I can provide any extra info needed. I
am using UbuntuMATE 14.04 32-bit version and see this on several
machines. Seems to be due to grub setup wanting to open a
terminal-like window to ask for user input and not being able to??
** Attachment added: Screenshot of
This is a very fatal bug for me, as the end result is eventually a reset
of yhe system, after which my system won't boot up anfd ends up at a
grub rescue prompt. Not sure if this is b/c we're switching the default
order of tje partitions so that swap is first, everything else is after
that. I have
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: update-manager (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1351404
I am a software developer and have this problem on multiple machines.
Update freezes at Setting up grub-pc (2.02~beta2-9ubuntu1.1). The
window goes grey and does not continue even if left overnight. Each
machine is an x86 and has multiple disks with versions of Ubuntu
installed (12.04/14.04 32/64
I am a software developer and have this problem on multiple machines.
Update freezes at Setting up grub-pc (2.02~beta2-9ubuntu1.1). The
window goes grey and does not continue even if left overnight. Each
machine is an x86 and has multiple disks with versions of Ubuntu
installed (12.04/14.04 32/64
I also have this problem, but I let mine run for way longer than 25
minutes. More like 5-6 hours. Is that a normal amount of time for this
particualr installation or has something gone wonky?
-Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
