update-manager crashed with SystemError in requiredDownload()

Thanks for your bugreport.

Could you please attach the logs in /var/log/dist-upgrade/* to this report of the failed upgrade? Do you get this crash (with the attached traceback) everytime you run update-manager and click on "Install" ? If so, could you please attach your /var/lib/dpkg/status file ?

Please find attached the requested logs.
Le jeudi 12 mars 2009 à 09:29 +0000, Michael Vogt a écrit :
> Thanks for your bugreport
>
> Could you please attach the logs in /var/log/dist-upgrade/* to this
> report of the failed upgrade? Do you get this crash (with the attached
> traceback) everytime you run update-manager and click on "Install" ? If
> so, could you please attach your /var/lib/dpkg/status file ?
>
> ** Changed in: update-manager (Ubuntu)
> Assignee: (unassigned) => Michael Vogt (mvo)
> Status: New => Incomplete
>

status: confirmed

More than two people (15) have the bug and the missing files are provided.

I reported a new bug #521403 from apport, but received email that it was the same ss this one. I do not understand all the files that apport collects, but my crash was not on an upgrade from one version to another (intrepid to jaunty for this bug) but rather a weekly security update of karmic involving screensaver, mysql and the newest released kernel for karmic. I believe I had the same kind of crash on the weekly update last week, but it ran through a second time I tried it I believe. This time I was able to go to synaptic, have it show me the packages available for upgrade (within version 9.10 or 9.04 or whatever ought to be called update rather than upgrade it seems to me). It showed me the ones that I remembered as having available upgrades, so I selected them withing synaptic and ran apply, turned on full verbosity and saw no errors when I rebooted not since, except that it has thrown an apport error (without offering me the apport error reporting) with

nspluginwrapper/i386/linux/npviewer.bin (command line "/usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /opt/Adobe/Reader9/Browser/intellinux/nppdf.so --connection /org/wrapper/NSPlugins/nppdf.so/3245-1")

Which I thought I had removed when I installed the alpha flash library for x86_64 arch.

What do I need to look at to understand how my bug is the same as this one?

I do not have any files in /var/log/dist-upgrade/ .

Hello Stew,

When my update crashed I rebooted and restarted the updates.
The result was that not much functioned and I had all sorts of rubbish to clean out.
In the end, I zapped Ubuntu and did a clean install of the good old 9.04 which worked fine.
I'll just wait for a stable 10 something version before I try again.
For me, having the latest version is unimportant because I just use it at home.
Right now I'm testing Linux Mint 8's KDE version, which, so far, looks nice.

Greetings from France

Arend

> Message du 14/02/10 16:45
> De : "Stew Ellis"
> A : <email address hidden>
> Copie à :
> Objet : [Bug 341503] Re: update-manager crashed with SystemError in requiredDownload()
>
>
> I reported a new bug #521403 from apport, but received email that it
> was the same ss this one. I do not understand all the files that apport
> collects, but my crash was not on an upgrade from one version to another
> (intrepid to jaunty for this bug) but rather a weekly security update of
> karmic involving screensaver, mysql and the newest released kernel for
> karmic. I believe I had the same kind of crash on the weekly update
> last week, but it ran through a second time I tried it I believe. This
> time I was able to go to synaptic, have it show me the packages
> available for upgrade (within version 9.10 or 9.04 or whatever ought to
> be called update rather than upgrade it seems to me). It showed me the
> ones that I remembered as having available upgrades, so I selected them
> withing synaptic and ran apply, turned on full verbosity and saw no
> errors when I rebooted not since, except that it has thrown an apport
> error (without offering me the apport error reporting) with
>
> nspluginwrapper/i386/linux/npviewer.bin (command line
> "/usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin
> /opt/Adobe/Reader9/Browser/intellinux/nppdf.so --connection
> /org/wrapper/NSPlugins/nppdf.so/3245-1")
>
> Which I thought I had removed when I installed the alpha flash library
> for x86_64 arch.
>
> What do I need to look at to understand how my bug is the same as this
> one?
>
> I do not have any files in /var/log/dist-upgrade/ .
>
> --
> update-manager crashed with SystemError in requiredDownload()
> https://bugs.launchpad.net/bugs/341503
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “update-manager” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: update-manager
>
> During the upgrade from intrepid to jaunty, sivp has failed to upgrade (remain in 0.4.3.-4 and in trouble). Since, I can't success to upgrade it or remove it, can't success also to remove scilab. Now, the proper upgrade sivp 0.5.0-1 seems to be available, but clicking on the updating button causes that immediate crash. So my problem : Because this package can not be upgraded, all videos are in a big mess (gstreamer, flashplugin... are in troubles...). Now the upgrade is available in the repositories. But anyhow I can not success to make that upgrade.
>
> How to escape from this uncomfortable situation, and recover ? Could you please help me in this ?
>
> ProblemType: Crash
> Architecture: am...

Bug 375313 (and its duplicates) are likely a duplicate of this bug.

I just got a similar crash whilst doing my daily lucid update. Packages to be upgraded were console-setup and libmjpegtools. Apport fired up and pointed me to this bug report, noting it was the same problem I was trying to report.

However, after closing update-manager and launching it again everything worked out just fine, no crash, all updates applied correctly.

I think this can happen when the archives are in an inconsistent state. The relevant lines from the tracebacks are:

SystemError: E:I wasn't able to locate file for the XXX package. This might mean you need to manually fix this package.

where XXX can be different packages depending on what you're trying to update. python-apt is thrown a low-level SystemError in pm.GetArchives() and update-manager doesn't catch this, or know how to recover from it. I'm not sure what the best way to fix this is, though we can probably do better than UM crashing.

Perhaps the thing to do is to catch SystemErrors in the .requiredDownload call in checkFreeSpace(). If that happens probably the simplest thing to do is to pop up a dialog stating that something went wrong during free space calculation, explain that UM is going to quit now and that you should try again later. Eventually the archives will be consistent and accessible and the update will succeed.

If you wanted to get more sophisticated, you could probably re-check for available updates and try it all over again right then and there.

@Brian: yes I think bug 375313 is a duplicate of this, but the LP api doesn't make it easy to mark that bug as such, because of *its* duplicates. I guess I'll write a launchpadlib script to do that.

I just got another crash of update-manager and was redirected to this bug report by apport. Again this happened on a lucid system during my daily system update.

The attached .crash file contains a traceback showing a SystemError Exception saying that python-apt was unable to locate the ubuntu-minimal package.

#5 Stew Ellis: Behind the scenes, the button "check" actually runs "apt-get update" and the button "install updates" runs "apt-get upgrade". When you upgrade from 9.04 to 9.10 it is called a "distribution upgrade".
So what you are calling a weekly update is in fact also called an upgrade.

After no problems for several months, I got bit again trying to do a weekly update of karmic. I was initially directed to update some obsolete files mostly krb libs. I did so, tried to run update manager again and was directed here.

I recently upgraded from Karmic to Lucid, but this error did not occur during the upgrade. Instead I believe it to be a problem with the screensaver. The screensaver does not come out of sleep mode well, and my laptop was dormant (sleeping) when it tried to do this daily update. When I brought it back to life this error occurred. My guess is that it might have something to do with difficulty re-acquiring a network connection (wireless) after going to sleep.

Update manager "crashed" (window still there and perhaps usable) even before asking me for my password.
Update was for two mysql updates (libmysqlclient16 (5.1.37-1ubuntu5.1 , 5.1.37-1ubuntu5.4) and mysql-common (5.1.37-1ubuntu5.1 , 5.1.37-1ubuntu5.4), and openoffice.org-emailmerge (1:3.1.1-5ubuntu1.1 , 1:3.1.1-5ubuntu1.2) (which was still there from the other day when it failed to install properly, when it erroneously reported openoffice.org was running).
I will close the window and pull up the program again from the System menu, and see what happens.

I now see that there is a /var/crash file for this. Here it is.

I have TWO windows stating that Update Manager crashed, which is odd, as I had already updated and then closed the Update Manager window.(update was for Firefox 3.6.8).

There WAS something odd earlier, though:
  When I booted, there was Update Manager, and I clicked on it and it showed the Firefox update/upgrade.
When I clicked on update/upgrade, nothing happened. The button briefly went darker, and then returned to its unclicked appearance. I did this several times, with the same result. I then closed Update Manager, used the menu to bring it up (System->Administration->Update Manager), and everything worked fine from there.

During the upgrade from intrepid to jaunty, ....

Is this a regression then?

Just did dist-upgrade on Precise install in Virtualbox, and update-manager crashed.

I cant update