X session crashes with XIO fatal IO error 104
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Xorg Xserver VESA |
New
|
Undecided
|
Unassigned | ||
nvidia-graphics-drivers-180 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xorg
Hello,
since last week or so suddenly mx X/Gnome session crashes randomly after working with it for a few hours. Both screens (laptop and external monitor) go blank for a few seconds, then the GDM login screen reappears. In the .xsession-error file I hve the following messages:
XIO: fatal IO error 104 (Connection reset by peer) on X server ":1.0"
after 26930 requests (26929 known processed) with 0 events remaining.
gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
gnome-volume-
gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
gnubiff: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
ubuntuone-
gnome-settings-
update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) on display ':1.0'.
bluetooth-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
tracker-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
gnome-panel: Fatal IO error 104 (Connection reset by peer) on X server :1.0.
nautilus: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
genesis: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
fusion-icon: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
* Detected Session: gnome
* Searching for installed applications...
* NVIDIA on Xorg detected, exporting: __GL_YIELD=NOTHING
* Using the GTK Interface
nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
gnome-power-
gdu-notificatio
polkit-
padevchooser: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
evolution-
smart-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
NetmonScreenlet.py: Fatal IO error 104 (Connection reset by peer) on X server :1.0.
pidgin: Fatal IO error 104 (Connection reset by peer) on X server :1.0.
(ibus-daemon:2339): IBUS-CRITICAL **: ibus_proxy_call: assertion `priv->connection' failed
<unknown>: Fatal IO error 104 (Connection reset by peer) on X server :1.0.
gnome-terminal: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
prism-bin: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
(gnome-panel:2414): GLib-GObject-
I'm unable to find any other logs regarding this error.
ProblemType: Bug
Architecture: i386
Date: Tue Feb 9 12:56:02 2010
DistroRelease: Ubuntu 9.10
MachineType: LENOVO 64586QG
NonfreeKernelMo
Package: xserver-xorg 1:7.4+3ubuntu10
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: root=/dev/
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu10
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-
xserver-
SourcePackage: xorg
Uname: Linux 2.6.31-19-generic i686
dmi.bios.date: 08/15/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC4WW (2.24 )
dmi.board.name: 64586QG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 64586QG
dmi.product.
dmi.sys.vendor: LENOVO
fglrx: Not loaded
system:
distro: Ubuntu
architecture: i686kernel: 2.6.31-19-generic
xkbcomp:
Error: command ['xkbcomp', ':0', '-w0', '-'] failed with exit code 1: Error: Cannot open display ":0"
affects: | xorg (Ubuntu) → nvidia-graphics-drivers-180 (Ubuntu) |
tags: | added: karmic |
Changed in nvidia-graphics-drivers-180 (Ubuntu): | |
status: | Incomplete → Confirmed |
It seems that this happens after every reboot only once. After it crashes it runs stable for the rest of the day...