Installing Eeebuntu 4 Beta crashes on installing bootloader

Bug #524871 reported by Sietse Brouwer
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

Attempted to install Eeebuntu 4.0 beta 1 from a USB stick made with unetbootin, on an Asus Eee PC 1005HA-M.
The Live OS loaded normally.
Told Ubiquity that I wanted to manually indicate what to do with the partition table.
Subsequently told it not to format anything (except the swap partition).
Told it to install the bootloader on (hd0).
Told it "OK, go ahead, no turning back, let's do this."
It made its way 80+ percent into the install (I don't know the exact number).
Then it crashed, with <first error message>, shown below.

Upon re-running Ubiquity, it auto-loaded the answers I had already given. When I clicked "next" at the end of the 'choose keyboard layout' step, Ubiquity did not crash, but showed the failure message <second error message>, shown below. It let me choose from Continue At Your Own Risk (or something like that), Try Again, and Quit. Repeated clicking on Try Again repeated the failure. I broke off the installation attempt.

<first error message>
Traceback (most recent call last):
  File "/usr/lib/ubiquity/bin/ubiquity", line 457, in <module>
    main(oem_config)
  File "/usr/lib/ubiquity/bin/ubiquity", line 442, in main
    install(args[0], query=options.query)
  File "/usr/lib/ubiquity/bin/ubiquity", line 245, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 465, in run
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtk_ui.py", line 975, in progress_loop
    (ret, realtb))
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 2453, in <module>
    install.run()
  File "/usr/share/ubiquity/install.py", line 459, in run
    self.configure_bootloader()
  File "/usr/share/ubiquity/install.py", line 1810, in configure_bootloader
    "GrubInstaller failed with code %d" % ret)
InstallStepError: GrubInstaller failed with code 1
</first error message>

<second error message>
ubiquity.components.partman failed with exit code 10. Further information may be found in /var/log/syslog. Do you want to try running this step again before continuing? If you do not, your installation may fail entirely or may be broken.
</second error message>

Revision history for this message
Sietse Brouwer (sbbrouwer) wrote :
summary: - Installing Eeebunty 4 crashes on installing bootloader
+ Installing Eeebuntu 4 crashes on installing bootloader
Revision history for this message
Sietse Brouwer (sbbrouwer) wrote : Re: Installing Eeebuntu 4 crashes on installing bootloader

Here's /var/log/partman
(I couldn't see how to attach both at once.)

summary: - Installing Eeebuntu 4 crashes on installing bootloader
+ Installing Eeebuntu 4 Beta crashes on installing bootloader
description: updated
Revision history for this message
Monkey (monkey-libre) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test a current, supported, Ubuntu version. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 524871, and any other logs that are relevant for this particular issue.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Sietse Brouwer (sbbrouwer) wrote :

Hi, Monkey; thanks for getting back to me.

I am, by now, using a current version of Ubuntu, and I've had no problems with it or its bootloader, so as far as I'm concerned we can can consider this bug "either solved or not important any more". I'll wait until Wednesday to give the other subscriber, huco, the chance to object; if nobody has objected by then, I'm marking it invalid.

--Sietse

Revision history for this message
Monkey (monkey-libre) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. Don´t worry, huco can change the current status in the yellow line and then choosing a new status in the revealed drop down box. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in ubiquity (Ubuntu):
status: Incomplete → Invalid
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.