It also appears as "unwanted log-out" as soon as the DPMS screensaver or standby mode blanks the screen. After moving the mouse/ hitting the keyboard, the screen reappears and a previous session is gone, instead I am back at login.

This seems to be a serious problem of a core xorg component or the kernel or whatever, don't really know. An indicator is the line seen above:

(II) AIGLX: Suspending AIGLX clients for VT switch

After this one, X crashes as soon as it is required again. Attempting to disable DRI and/or GLX did NOT HELP anyway...

for me it worked to downgrade all X servers to the latest lucid 10.04 version. This stopped the strange X crashes due to switching to text consoles or blank screen / DPMS (in my case with an S3 savage card).

Hey Chris,
I installed the PPA in December and it seems to be solving the problem
with the bug

On 01/13/2011 05:13 PM, Bryce Harrington wrote:
> Hi Sylvia, Chris has a PPA with a fix for your issue, which you can
> install from here:
>
> https://launchpad.net/~raof/+archive/aubergine
>
> Please try this and report back here if it solves it for you.
>

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.