dpkg locks up operations upon error frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: php5
automatically-
Upgrading ubuntu from 9.04 -> 9.10 -> 10.04.01
package failed to install. The terminal window was in front of the dialog box asking if I wanted to keep the existing /etc/php5/
There being no way to continue, I rebooted the machine, and then did a partial upgrade. The partial upgrade came to the same choice, where I chose to replace it (after making a copy of the existing file)
1)
# lsb_release -rd
Description: Ubuntu 10.04.1 LTS
Release: 10.04
2)
# apt-cache policy libapache2-mod-php5
libapache2-
Installed: 5.3.2-1ubuntu4.5
Candidate: 5.3.2-1ubuntu4.5
Version table:
*** 5.3.2-1ubuntu4.5 0
500 http://
500 http://
100 /var/lib/
5.3.2-1ubuntu4 0
500 http://
3)
doh
4)
see notes above
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: libapache2-mod-php5 5.3.2-1ubuntu4.5
ProcVersionSign
Uname: Linux 2.6.32-25-generic x86_64
Architecture: amd64
Date: Thu Nov 4 07:00:51 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 1
SourcePackage: php5
Title: package libapache2-mod-php5 5.3.2-1ubuntu4.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Hi derek, thanks for taking the time to file this bug report and help us make Ubuntu better!
I see this in the DpkgTerminalLog .txt:
Installing new version of config file /etc/apache2/ mods-available/ php5.conf ...
frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
That is most likely a transient error, but one that dpkg should probably handle better. I can see other bug reports with the same error message and they appear not to be reproducible. However, this seems like a point where dpkg's X frontend could simple retry (as it should with an error message like that).
Re-assigning to dpkg, and marking as Confirmed based on bug 505277 and bug 406698 which seem to be the same issue (and will be marked as duplicates of this one).