Update from Kubuntu 6.10 to 7.04 crashed

Bug #109014 reported by Vlad Kuusk
30
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
High
Michael Vogt
Feisty
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

The message after the crash asked to create a new bug. I see that this bug is reported but it could be a different reason.

My system is Core2 duo with ATI Radeon X1600Pro

I hope, I can see how to attache the log files on the next page

Revision history for this message
Vlad Kuusk (vkuusk) wrote :
Revision history for this message
Vlad Kuusk (vkuusk) wrote :
Revision history for this message
Vlad Kuusk (vkuusk) wrote : The message in the crash window:

Traceback (most recent call last):
  File "/tmp/kde-root/adept_updaterpBxhwa.tmp-extract/dist-upgrade.py", line 56, in ?
    app.run()
  File "/tmp/kde-root/adept_updaterpBxhwa.tmp-extract/DistUpgradeControler.py", line 1025, in run
    self.fullUpgrade()
  File "/tmp/kde-root/adept_updaterpBxhwa.tmp-extract/DistUpgradeControler.py", line 1014, in fullUpgrade
    self.doPostUpgrade()
  File "/tmp/kde-root/adept_updaterpBxhwa.tmp-extract/DistUpgradeControler.py", line 724, in doPostUpgrade
    if not self.cache._tryMarkObsoleteForRemoval(pkgname, remove_candidates, self.foreign_pkgs):
  File "/tmp/kde-root/adept_updaterpBxhwa.tmp-extract/DistUpgradeCache.py", line 490, in _tryMarkObsoleteForRemoval
    self.restore_snapshot()
  File "/tmp/kde-root/adept_updaterpBxhwa.tmp-extract/DistUpgradeCache.py", line 83, in restore_snapshot
    pkg.markDelete()
  File "/usr/lib/python2.4/site-packages/apt/package.py", line 301, in markDelete
    ver = self._depcache.GetCandidateVer(self._pkg)
SystemError: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

Revision history for this message
Vlad Kuusk (vkuusk) wrote :

Jus one more additional observation:
After the crash of the update the network card lost it's IP

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

Thanks for your bugreport.

I commited a fix that should work around this problem.

Changed in update-manager:
importance: Undecided → High
status: Unconfirmed → Fix Committed
Revision history for this message
Michael Vogt (mvo) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

Accepted into feisty-proposed, please go ahead with QA testing.

Changed in update-manager:
status: Unconfirmed → Fix Committed
assignee: nobody → mvo
Changed in update-manager:
status: Fix Committed → Fix Released
status: Fix Committed → Fix Released
Changed in update-manager:
status: Fix Released → Fix Committed
status: Fix Released → Fix Committed
Revision history for this message
Daniel Hahler (blueyed) wrote :

The fix is in 0.59.25 (which is in feisty-updates).

Changed in update-manager:
status: Fix Committed → Fix Released
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.