Ubuntu
update-manager package

Update Tool Crashed

Bug #223271 reported by Dave Brougham on 2008-04-27

This bug report is a duplicate of: Bug #222063: [kde] [master] frontend crashes if dpkg was interrupted. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	update-manager (Ubuntu)	Incomplete	Undecided	Unassigned

Bug Description

Binary package hint: update-manager

Traceback (most recent call last):
  File "/tmp/kde-root/adept_updaterFSAc4b.tmp-extract/dist-upgrade.py", line 60, in <module>
    app.run()
  File "/tmp/kde-root/adept_updaterFSAc4b.tmp-extract/DistUpgradeController.py", line 1550, in run
    self.fullUpgrade()
  File "/tmp/kde-root/adept_updaterFSAc4b.tmp-extract/DistUpgradeController.py", line 1425, in fullUpgrade
    if not self.prepare():
  File "/tmp/kde-root/adept_updaterFSAc4b.tmp-extract/DistUpgradeController.py", line 346, in prepare
    self.openCache()
  File "/tmp/kde-root/adept_updaterFSAc4b.tmp-extract/DistUpgradeController.py", line 209, in openCache
    self._view.getOpCacheProgress())
  File "/tmp/kde-root/adept_updaterFSAc4b.tmp-extract/DistUpgradeCache.py", line 51, in __init__
    raise CacheExceptionDpkgInterrupted, e
CacheExceptionDpkgInterrupted: E:dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.

I am trying to upgrade from 7.10 to 8.04

Every time I start the Adept installer, I get a message that says another process is already using it, do I want to try to resolve the conflict or open in read only mode.

Revision history for this message

Dave Brougham (davebrougham) wrote on 2008-04-27:

main.log Edit (1.5 KiB, text/plain)

Revision history for this message

Dave Brougham (davebrougham) wrote on 2008-04-27:

apt.log Edit (390 bytes, text/plain)

Revision history for this message

Michael Vogt (mvo) wrote on 2008-04-28:

Thanks for your bugreport.

This sounds like a earlier run of the dpkg package manager was interrupted (by e.g. power failure). Please open a terminal (e.g. konsole) and
run "sudo dpkg --configure -a" and retry the upgrade after that.

Cheers,
Michael