Installer Crashed Xubuntu Edgy 2G USB Flash Memory

Bug #74562 reported by jerrylamos on 2006-12-05
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)

Bug Description

I've been following various forums & Wiki to see how to get mbr and grub on USB flash memory with no success, either for an install or USBLive. Example of failures follows.

We're sorry; the installer crashed. Please file a new bug report at (do not attach your details to any existing bug) and a developer will attend to the problem as soon as possible. To help the developers understand what went wrong, include the following detail in your bug report, and attach the files /var/log/syslog and /var/log/partman:

Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 166, in ?
  File "/usr/bin/ubiquity", line 161, in main
  File "/usr/bin/ubiquity", line 57, in install
    ret =
  File "/usr/lib/ubiquity/ubiquity/frontend/", line 305, in run
  File "/usr/lib/ubiquity/ubiquity/frontend/", line 856, in process_step
  File "/usr/lib/ubiquity/ubiquity/frontend/", line 628, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s\n%s" %
RuntimeError: Install failed with exit code 1
Traceback (most recent call last):
  File "/usr/share/ubiquity/", line 1404, in ?
  File "/usr/share/ubiquity/", line 385, in run
  File "/usr/share/ubiquity/", line 1163, in configure_bootloader
    raise InstallStepError(
InstallStepError: GrubInstaller failed with code 1

I couldn't see how to attach /var/log/syslog and /var/log/partman to this window. I've got the files saved on /target/home/jerry if you can tell me where to send them.

jerrylamos (jerrylamos) wrote :

trying to attach var log partman for above bug

jerrylamos (jerrylamos) wrote :

try again on partman

Mike Dahlgren (dahlgren) wrote :

Thanks for your bug report! However since it has been a long time since it was originally reported, I was wondering if this is still an issue?

       ~ Mike

Charlie Kravetz (charlie-tca) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ubiquity:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers