Installer crashed on "Configuring Apt"

Bug #47647 reported by Tomas Gold
8
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 120, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 54, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 264, in run
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 538, in progress_loop
    raise RuntimeError, "Install failed with exit code %s" % ret
RuntimeError: Install failed with exit code 1

Restarting the installer solved the problem - besides a couple of blank message boxes during the same time as it crashed for the first time the installer confirmed a complete and successful instalation at the end.

Revision history for this message
Colin Watson (cjwatson) wrote :

Could you attach /var/log/installer/syslog and /var/log/partman to this bug, please? (or /var/log/installer/partman if you've already rebooted into the completed installation)

Changed in ubiquity:
status: Unconfirmed → Needs Info
Revision history for this message
Tomas Gold (tomas-gold) wrote : /var/log/installer/syslog

syslog

(I'm dumb, I didn't keep the log from the first installation so this one is from the second)

Revision history for this message
Tomas Gold (tomas-gold) wrote : /var/log/installer/partman

Yes, I rebooted.

Revision history for this message
Colin Watson (cjwatson) wrote :

As far as I can tell, you tried to start up the installer again while it was already running, it unmounted /target as the first thing it did, and then everything got very confused. We should have better locking to avoid this.

Changed in ubiquity:
status: Needs Info → Confirmed
Revision history for this message
Tomas Gold (tomas-gold) wrote :

As far as I remember I restarted the installer AFTER getting the "Installer crashed" message.

Revision history for this message
Colin Watson (cjwatson) wrote :

The log's pretty clear here. I think this is essentially the same as bug 46569, which is now fixed in Edgy.

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.