Ubuntu
ubiquity package

o not attach your details to any existing bug

Bug #102707 reported by Jesus
6
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

Help Me Please ...

We're sorry; the installer crashed. Please file a new bug report at https://launchpad.net/distros/ubuntu/+source/ubiquity/+filebug (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/installer/syslog, /var/log/syslog, and /var/log/partman:

raceback (most recent call last):
  File "/usr/bin/ubiquity", line 130, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 55, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 266, in run
    self.process_step()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 755, in process_step
    self.mountpoints_to_summary()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 1114, in mountpoints_to_summary
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 553, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code -11; see /var/log/installer/syslog and /var/log/syslog

Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better.
Please run the installer again in debug mode by typing `ubiquity -d` in a console. Run the installer until it crashes and then attach /var/log/installer/debug and /var/log/syslog to this bug report. Detailed instructions for doing so can be found here:
https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs

Changed in ubiquity:
assignee: nobody → thotz
status: Unconfirmed → Needs Info
Revision history for this message
Colin Watson (cjwatson) wrote :

There is no need to use debug mode in this situation; /var/log/syslog from after an ordinary installation will do fine. Thomas, please only ask for debug mode if you know why you're asking.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Hi, Just following up on this bug. Will you be able to provide these log files? (you will have to repeat the install attempt with the same Live CD to get them) Without the logs we will not be able to follow up this issue further. This page contains detailed information on uploading log files: https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs

Revision history for this message
Pedro Villavicencio (pedro) 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: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.