Installer Crashed

Bug #104600 reported by phillipblair
This bug report is a duplicate of:  Bug #69470: MASTER: dpkg error on do_remove. Edit Remove
2
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubiquity

Loading 6.10 for first time on Dell Desktop. 2nd try. Burned 6.10 ISO in slower burn rate at 4x.

Got this error
Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 166, in ?
    main()
  File "/usr/bin/ubiquity", line 161, in main
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 57, in install
    ret = wizard.run()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 305, in run
    self.process_step()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 856, in process_step
    self.progress_loop()
  File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 628, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s\n%s" %
RuntimeError: Install failed with exit code 139
Traceback (most recent call last):
  File "/usr/share/ubiquity/install.py", line 1404, in ?
    install.run()
  File "/usr/share/ubiquity/install.py", line 390, in run
    self.remove_extras()
  File "/usr/share/ubiquity/install.py", line 1341, in remove_extras
    self.do_remove(difference)
  File "/usr/share/ubiquity/install.py", line 1258, in do_remove
    if not cache.commit(fetchprogress, installprogress):
  File "/usr/lib/python2.4/site-packages/apt/cache.py", line 204, in commit
    res = self.installArchives(pm, installProgress)
  File "/usr/lib/python2.4/site-packages/apt/cache.py", line 179, in installArchives
    res = installProgress.run(pm)
  File "/usr/share/ubiquity/install.py", line 200, in run
    res = pm.DoInstall(self.writefd)
SystemError: E:Sub-process /usr/bin/dpkg exited unexpectedly

Revision history for this message
phillipblair (pblair-tx) wrote :
Revision history for this message
phillipblair (pblair-tx) wrote :
Revision history for this message
phillipblair (pblair-tx) wrote :

Is it ok to proceed with downloading updates and patches or do i need to fix these bugs first?

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

Judging from all the squashfs errors in your syslog, it looks like the root cause of this was a problem reading from the CD. This is generally due to a faulty CD/DVD disk or drive, rather than being an installer bug as such. It may help to clean the CD/DVD, to burn the CD/DVD at a lower speed, or to clean the CD/DVD drive lens (cleaning kits are often available from electronics suppliers).

However, the particular violence of the crash here is also bug 69470, and will be fixed in the final Feisty release.

Revision history for this message
phillipblair (pblair-tx) wrote :

Thanks Colin:
My first install lent a series of different crash details. So, I burned the iso file at 4x. My second attempt hanged at about 55% on the install. My third attempt lent the above crash details. I'm wondering two things. 1) should i use a iso mount utility and pull it from another network HD. 2) format the HD i'm trying to load 6.10 on. If so, what command would i use to format the HD for a clean install. Thanks.

Revision history for this message
phillipblair (pblair-tx) wrote : Re: Installer Crashed / updates

I read bug 69470. Should I try a reinstall or try to fix the individual error codes with unix commands (i obviously am new at this and have no idea what I am talking about). I just want to get 6.10 up and going so i can add other applications. When I tried to run the update i received a errors. When I tried to fix those errors, I was told i had to be logged in as a superuser.

Revision history for this message
phillipblair (pblair-tx) wrote :

Issue resolved. Here is what I did for the Dell Dimension 3000 Hardware and the Ubuntu 6.10. I went into the BIOS set up F2 and turned off fast swapping. This apparently messes up thing. I burned the ISO file at slower speed and I cleaned the optical drive / CD Rom. Turning off fast swapping seemed to resolve all my issues.

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.