[kde] copy XAUTHORITY may fail and crashes the upgrader (was: Upgrade tool crashed when upgrading 7.04 -> 7.10)

[Slingshot]

Traceback (most recent call last):
  File "/tmp/kde-kymdio/adept_updaterTk3aVa.tmp-extract/dist-upgrade.py", line 60, in <module>
    app.run()
  File "/tmp/kde-kymdio/adept_updaterTk3aVa.tmp-extract/DistUpgradeController.py", line 1550, in run
    self.fullUpgrade()
  File "/tmp/kde-kymdio/adept_updaterTk3aVa.tmp-extract/DistUpgradeController.py", line 1425, in fullUpgrade
    if not self.prepare():
  File "/tmp/kde-kymdio/adept_updaterTk3aVa.tmp-extract/DistUpgradeController.py", line 346, in prepare
    self.openCache()
  File "/tmp/kde-kymdio/adept_updaterTk3aVa.tmp-extract/DistUpgradeController.py", line 209, in openCache
    self._view.getOpCacheProgress())
  File "/tmp/kde-kymdio/adept_updaterTk3aVa.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.

[Slingshot (slingshot)]

and when I tried AGAIN I got this

Failed to fetch http://ftp.de.debian.org/debian/dists/feisty/main/binary-i386/Packages.gz 404 Not Found

[Jonathan Riddell (jr)]

What does "Filen eller katalogen finns inte" mean?

Also how did you start adept?

[Slingshot (slingshot)]

"Filen eller katalogen finns inte" means "File or catalog does not exist". I can't really remember how I started adept but probably it was from the kde menu.

[Steve Langasek (vorlon)]

While update-manager shouldn't fail in this manner, the extraordinary thing here is that $XAUTHORITY is set and points at a non-existent file. update-manager will be unable to establish any further X connections under those circumstances, so aside from the ugliness of the error, the real bug is in whatever has set up $XAUTHORITY to point to a nonexistent file (or has removed the file that $XAUTHORITY was pointing to).

Hence it's necessary to know how update-manager was invoked in order to trace down that bug there.

[julio_1957 (julio-1957)]

Traceback (most recent call last):
  File "/tmp/kde-elcan/adept_updatersBPEjc.tmp-extract/dist-upgrade.py", line 60, in <module>
    app.run()
  File "/tmp/kde-elcan/adept_updatersBPEjc.tmp-extract/DistUpgradeController.py", line 1580, in run
    self.fullUpgrade()
  File "/tmp/kde-elcan/adept_updatersBPEjc.tmp-extract/DistUpgradeController.py", line 1458, in fullUpgrade
    if not self.prepare():
  File "/tmp/kde-elcan/adept_updatersBPEjc.tmp-extract/DistUpgradeController.py", line 352, in prepare
    self.openCache()
  File "/tmp/kde-elcan/adept_updatersBPEjc.tmp-extract/DistUpgradeController.py", line 215, in openCache
    self._view.getOpCacheProgress())
  File "/tmp/kde-elcan/adept_updatersBPEjc.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.

[Jeremiah C. Foster (jeremiah-foster)]

This same problem occurs when you run update-manager -d on the command line trying to go from 9.10 to 10.4.