[MASTER] Upgrade Tool Crashed

Bug #99380 reported by miika
144
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
High
Michael Vogt
Nominated for Gutsy by bjcurran

Bug Description

Binary package hint: update-manager

Traceback (most recent call last):
  File "/tmp/kde-root/adept_managerituizb.tmp-extract/dist-upgrade.py", line 56, in ?
    app.run()
  File "/tmp/kde-root/adept_managerituizb.tmp-extract/DistUpgradeControler.py", line 977, in run
    self.fullUpgrade()
  File "/tmp/kde-root/adept_managerituizb.tmp-extract/DistUpgradeControler.py", line 966, in fullUpgrade
    self.doPostUpgrade()
  File "/tmp/kde-root/adept_managerituizb.tmp-extract/DistUpgradeControler.py", line 709, in doPostUpgrade
    self._view.getTerminal().call([script], hidden=True)
  File "/tmp/kde-root/adept_managerituizb.tmp-extract/DistUpgradeView.py", line 72, in call
    subprocess.call(cmd)
  File "subprocess.py", line 413, in call
    return Popen(*args, **kwargs).wait()
  File "subprocess.py", line 543, in __init__
    errread, errwrite)
  File "subprocess.py", line 975, in _execute_child
    raise child_exception
OSError: [Errno 13] Permission denied

Revision history for this message
Andrew Cartine (cartine) wrote :

i had the same bug, says to include apt.log and main.log, so i'm adding them here.

Revision history for this message
Andrew Cartine (cartine) wrote :

here is the main.log as well

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

I'm preparing a fix right now and will upload very soon. If you got to this point, that means that the upgrade was successfull and everything should be fine. There is just a cleanup script not run that will check for auto-install information in the apt database. I will attach it here so that you can run it manually to complete this step as well.

Sorry for the trouble,
 Michael

Thanks,
 michael

Changed in update-manager:
assignee: nobody → mvo
importance: Undecided → High
status: Unconfirmed → In Progress
Revision history for this message
Michael Vogt (mvo) wrote :

This is fixed in my latest upload of update-manager.

Changed in update-manager:
status: In Progress → Fix Released
Revision history for this message
Martin Pagh Goodwin (martin-goodwin) wrote :

Not that I want to sound impatient, but how do we run the cleanup script?

Otherwise thanks for the quick fix.
Martin

Revision history for this message
Michael Vogt (mvo) wrote :

This script will remove the automatic-installed information from direct dependencies of meta-packages like "kubuntu-desktop". This ensures that if you remove "kubuntu-desktop" it does not automatically want to remove most of your kde applications (we have the same issue for ubuntu-desktop btw). It can just be run as it is, needs no additional parameters and writes a log to /var/log/dist-upgrade.

Revision history for this message
Laance (cyborghunter) wrote :

When I ran you script I got the following errors:

$ sudo sh ./apt-autoinst-fixup.py
Password:
./apt-autoinst-fixup.py: 3: import: not found
./apt-autoinst-fixup.py: 4: import: not found
./apt-autoinst-fixup.py: 6: import: not found
./apt-autoinst-fixup.py: 7: Syntax error: word unexpected (expecting ")")

And, I do not see a new log in /var/log/dist-upgrade,
only "apt.log main.log"

Furthermore, the Adapt-Updater warning has stayed in the KDE Panel
ever since the Upgrade Tool Crashed. It insists that NEdit is upgradable
from v. 1:5.5-1ubuntu1, to 1:5.5-2ubuntu3, but no matter how many times I
let it upgrade it doesn't take (although it seems to complete successfully).

Lance

Revision history for this message
Laance (cyborghunter) wrote :

Never mind the Adapt-Updater warning issue. I worked that out
and it was unrelated to the "Upgrade Tool Crash" issue.

Revision history for this message
Michael Vogt (mvo) wrote :

Please run it with:
$ sudo python ./apt-autoinst-fixup.py

Revision history for this message
Margot (margot-andree-gmx) wrote :

My error log is different:
Traceback (most recent call last):
  File "/tmp/kde-root/adept_updaterBdSZha.tmp-extract/dist-upgrade.py", line 56, in ?
    app.run()
  File "/tmp/kde-root/adept_updaterBdSZha.tmp-extract/DistUpgradeControler.py", line 1025, in run
    self.fullUpgrade()
  File "/tmp/kde-root/adept_updaterBdSZha.tmp-extract/DistUpgradeControler.py", line 1014, in fullUpgrade
    self.doPostUpgrade()
  File "/tmp/kde-root/adept_updaterBdSZha.tmp-extract/DistUpgradeControler.py", line 740, in doPostUpgrade
    res = self.cache.commit(fprogress,iprogress)
  File "/usr/lib/python2.4/site-packages/apt/cache.py", line 204, in commit
    if res == pm.ResultCompleted:
  File "/usr/lib/python2.4/site-packages/apt/cache.py", line 179, in installArchives
    installProgress.finishUpdate()
  File "/usr/lib/python2.4/site-packages/apt/progress.py", line 206, in run
    select.select([self.statusfd],[],[], self.selectTimeout)
  File "/tmp/kde-root/adept_updaterBdSZha.tmp-extract/DistUpgradeViewKDE.py", line 227, in fork
    self.child_pid = os.fork()
OSError: [Errno 12] Cannot allocate memory

Revision history for this message
Margot (margot-andree-gmx) wrote :

and here is the main.log

Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

Is this the same issue? I'm just going to paste what I experienced from here:
http://digg.com/linux_unix/Upgrading_to_Ubuntu_7_10_NOW_before_the_rush

My upgrade dialog freezes at the point its status is "asking for confirmation". Anyone else experiencing this?

I've tried the upgrade 5 times now, always with this same freeze. Maybe I should wait til the 18th?

btw, I tried the instructions @ https://help.ubuntu.com/community/GutsyUpgrades

They didn't help. The "Distribution Upgrade" dialog still freezes. I don't know if it is just taking a long time, or if some error has occurred behind the scenes without notification at the window level.

Processor activity is low, and there doesn't seem to be any network activity either, so I think it just died while leaving that dialog orphaned.

I've ultimately decided not to try anymore until the 18th. I just hope my tries (this morning) don't corrupt the official-release's ability to upgrade my laptop on the 18th.

If you can't get the upgrade to work, be sure to undo the software sources it added by going to:
System > Administration > Software Sources > Third Party

I removed all 3rd party sources, but you may only need to remove the ones with "gusty" in them.

Also, you'll need to re-check everything in Ubuntu Software tab and under the Updates tab make sure you have "important security updates" checked (I also check recommended updates).

After all these changes, click the close button (not the revert button).

Revision history for this message
Ed Fisher (ed-fisher) wrote :

Scheduled update process offered to fetch and run the upgrade tool. During process, errored as follows...

Failed to fetch http://archive.canonical.com/ubuntu/dists/gutsy/Release Unable to find expected entry commercial/binary-i386/Packages in Meta-index file (malformed Release file?)

Verified network connectivity and name resolution. Manually wg(o)t the http://archive.canonical.com/ubuntu/dists/gutsy/Release file and parsed it...no listing for commercial/binary-i386/Packages

Revision history for this message
Dan Connell (scopenut) wrote :
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.