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. -- update-manager crashed with SystemError in requiredDownload() https://bugs.launchpad.net/bugs/341503 You received this bug notification because you are a member of Ubuntu Bug Control, which is a direct subscriber. _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-bugcontrol Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-bugcontrol More help : https://help.launchpad.net/ListHelp
