debconf fails with "frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0."

Bug #821630 reported by Bryan O'Brien
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
debconf (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Was performing an upgrade from Meerkat.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: perl-base 5.10.1-17ubuntu4.1
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic i686
Architecture: i386
Date: Fri Aug 5 12:21:41 2011
ErrorMessage: ErrorMessage: package perl-base is already installed and configured
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
SourcePackage: dpkg
Title: package perl-base 5.10.1-17ubuntu4.1 failed to install/upgrade: ErrorMessage: package perl-base is already installed and configured
UpgradeStatus: Upgraded to natty on 2011-08-05 (0 days ago)

Revision history for this message
Bryan O'Brien (bryan-m-obrien) wrote :
affects: ubuntu → dpkg (Ubuntu)
Revision history for this message
Raphaël Hertzog (hertzog) wrote :

The problem is that debconf's graphical interface fails to run due to "Fatal IO error 11". I don't know what can cause this and it would be nice if debconf had some sort of automatic fallback to non-interactive instead of just failing. Thus reassigning to debconf.

Checking for services that may need to be restarted...Checking init scripts...

WARNING: init script for samba not found.

frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

dpkg: error processing libpam0g (--configure):

 subprocess installed post-installation script returned error exit status 1

Errors were encountered while processing:

 libpam0g

summary: - package perl-base 5.10.1-17ubuntu4.1 failed to install/upgrade:
- ErrorMessage: package perl-base is already installed and configured
+ debconf fails with "frontend: Fatal IO error 11 (Resource temporarily
+ unavailable) on X server :0.0."
affects: dpkg (Ubuntu) → debconf (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in debconf (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

That version is no more maintained

Changed in debconf (Ubuntu):
status: Confirmed → Invalid
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.