Bug#517056: X crashes on session exit
Package: xserver-xorg
Version: 1:7.3+18
On my brand new Lenny install, when exiting my X session I get an error like this:
waiting for X server to shut down.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0.0
after 315733 requests (315726 known processed) with 0 events remaining.
Sometimes the second line changes to one of the following:
XIO: fatal IO error 4 (Interrupted system call) on X server :0.0
XIO: fatal IO error 104 (Connection reset by peer) on X server :0.0
The errors persist, I get them every time I log out of X.
My Xorg.conf is the standard blank file the new autoconfiguration seems to prefer, my screen resolution and refresh rate are properly set. The video card seems is correctly detected. That said the following errors persist in my /var/log/Xorg.0.log file (I do not know if these are relevant or not.):
[config/hal]: couldn't initialize context: (null) ((null))
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) Open APM succesful
(II) Configured mouse: ps2EnableDataReporting: succeeded
uname -r: 2.6.26-1-486
dpkg -s libc6 | grep ^Version: 2.7-18
lspci:
00:00.0 Host bridge: Intel Corporation 430TX - 82439TX MTXC (rev 01)
00:01.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01)
00:01.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:01.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 01)
00:09.0 CardBus bridge: Ricoh Co Ltd RL5c475
00:0a.0 Multimedia audio controller: Aureal Semiconductor Vortex 1 (rev 02)
00:0b.0 Multimedia video controller: 3Dfx Interactive, Inc. Voodoo 2 (rev 02)
00:0c.0 VGA compatible controller: Matrox Graphics, Inc. MGA G200 (rev 01)
01:00.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62)
01:00.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62)
01:00.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65)
Seeing as X never crashes during use, this isn't that severe. However the words 'fatal IO error' inspired me to file this anyway, in case it's a sign of a bigger problem.
Reply to: