1

I'm trying to upgrade to 13.10, and the upgrader/installer app has stopped. It doesn't seem to be frozen- it gives me a warning if I try to quit it, but it has been stuck like this for hours now.

the halted installer app

The internet connection is fast and working. Am I going to break things horribly if I quit it and restart?

Matthew Adams
  • 141
  • 9
  • It seems that its completed and and stuck while restarting the system. You should restart your system. If you get any problem I'm sure [this link](http://askubuntu.com/questions/203301/how-to-safely-upgrade-from-an-older-ubuntu-version-to-a-newer-one/360486#360486) will definitely help you. – Saurav Kumar Oct 18 '13 at 19:52
  • @SauravKumar I followed your suggestion and now my system won't boot past the screen where you select which OS to use. – Matthew Adams Oct 19 '13 at 21:27
  • Can you open your system in `Recovery Mode`? If yes then [this link](http://askubuntu.com/questions/340821/ubuntu-12-04-failed-to-reboot-after-unsuccessful-update-done-on-28-8-2013/340834#340834) 2nd option would help you.. If not then I think you've to repair your `Boot-Entry` i,e `grub-menu` through [Boot-Repair](https://help.ubuntu.com/community/Boot-Repair) give it a try.. – Saurav Kumar Oct 19 '13 at 23:05
  • @SauravKumar Yeah that's what I did (like I said in my answer). Thanks for your help! – Matthew Adams Oct 20 '13 at 00:04

1 Answers1

2

Short Answer

At least for my case, it turns out you can force a restart and then repair packages.

Details

I followed @SauravKumar's advice in the comments and forced the system to restart. On reboot, the computer got to the purple screen where it selects which OS to run. If I chose the default Ubuntu, it started loading and then went to a black screen and didn't respond to the keyboard at all.

So I then booted in recovery mode and chose the check packages option. It found out that I was using a different version of etc/default/rcs than the package maintainer. I chose to update it (the default is don't update) and then resumed booting and now it's running fine. Just to make sure, I rebooted again, and it works after a regular reboot too.

Update to 13.10: success!

Matthew Adams
  • 141
  • 9