Comment 6 for bug 345714

> I've had MANY X related issues today since a recent package update on Jaunty

Can you tell which package update led to the problem? View your /var/log/dpkg.log to see exactly what changed (e.g. grep upgrade /var/log/dpkg.log). I would probably guess it is xserver-xorg-video-intel 2:2.6.3-0ubuntu2, but there's been other X updates recently as well.

See if downgrading the suspected package(s) makes the issue go away. Usually the older debs are still available in your /var/cache/apt/archives/ for some time.

"WARNING: gdm_slave_xioerror_handler: Fatal X error" means X has either crashed or terminated. From your Xorg log I do not see a backtrace, which is typically printed out on crashes. Termination error messages typically get printed to a log file in /var/log/gdm/. Can you see if that is the case, and if so attach an example gdm log with the error?

Alternatively, shut down gdm and run X via `startx` from the console, and after getting it to terminate again, see what gets printed out to stderr.

The errors about vblank counts I believe are innocuous warnings.

This message is curious, one I've not seen before, and appears right before the gdm X termination message:

Mar 19 22:41:51 laptop x-session-manager[10605]: WARNING: Detected that screensaver has left the bus

That makes it sounds like screensaver stuff is somehow associated in the vt switching? Odd.

While I think this is a termination, if it is an X crash, we would next need a backtrace. Directions for getting one are at http://wiki.ubuntu.com/X/Backtracing - this won't help if X is terminating though.

Finally, thanks for including the lspci output. What I actually need is 'lspci -vvnn | grep -A1 "VGA "' as that will provide the PCI ID numbers for the video card.