package dbconfig-common 1.8.44ubuntu1 failed to install/upgrade:

Bug #637694 reported by Jg-freedesktop
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dbconfig-common (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: dbconfig-common

May have been caused by my wife logging out during upgrade to 10.04.1LTS.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: dbconfig-common 1.8.44ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Mon Sep 13 20:01:13 2010
ErrorMessage:
 ErrorMessage: subprocess installed post-installation script returned error exit status 1
PackageArchitecture: all
SourcePackage: dbconfig-common
Title: package dbconfig-common 1.8.44ubuntu1 failed to install/upgrade:

Revision history for this message
Jg-freedesktop (jg-freedesktop) wrote :
Revision history for this message
Mathias Gug (mathiaz) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better

As outlined in the log:
Setting up dbconfig-common (1.8.44ubuntu1) ...
1
frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

dpkg: error processing dbconfig-common (--configure):

 subprocess installed post-installation script returned error exit status 1

That would match the fact the session was terminated during the upgrade. Could you try to upgrade the system again?

Changed in dbconfig-common (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
Jim Gettys (jg-laptop) wrote :

I've already completed the upgrade, so I have no good way to reproduce this. As what you see is consistent with what happened, (since I know my wife accidentally logged out during the upgrade) I suggest we close this.

However, preventing accidental logout during upgrades might prevent other such problems. Perhaps that should go in as an enhancement for future releases?

Revision history for this message
Mathias Gug (mathiaz) wrote :

Marking this bug invalid as suggested by the reporter.

Your suggestion seems useful - I'd recommend to open a new bug against update-manager.

Changed in dbconfig-common (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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