Comment 4 for bug 398026

> To make the analysis easier, could you remove the file
> .config/monitors.xml in your home directory? This is the file where
> custom mode setting for your user is stored. I don't see anything wrong
> with it, but it makes it easier to not have to take that file into
> account. Then I would like the Xorg.0.log produced when you log in next
> time without monitors.xml.
Attached. However, this corruption occurs at GDM time, before my
monitors.xml is read.

>
> You mention that this happens with the latest version of xserver-xorg-
> video-intel (2:2.7.99.901+git20090702.74227141-0ubuntu1). Does that mean
> that it doesn't happen with the previous version?
Correct. This behaviour appeared with the latest intel update.

>
> Did you also upgrade the linux kernel recently? You have
> 2.6.31-2-generic and I seem to remember that the default was
> 2.6.31-1-generic until recently. Could you try to downgrade that as well
> to see if it changes anything (if you have an installed system, you
> probably have the old versions available in your boot menu)? The reason
> I'm asking is that the actual mode setting is now handled in the kernel
> (c.f. https://lists.ubuntu.com/archives/ubuntu-x/2009-June/000578.html)
> and if this problem was just introduced, it could have been through a
> kernel update.
While there have been kernel updates, I didn't think the introduction of
this problem corresponded with an update. Indeed, I've just checked and
this behaviour occurs with 2.6.31-1-generic, too.

>
> A piece of information which may be useful to the developers is whether
> this also happens without kernel mode setting. To disable kernel mode
> setting add the boot parameter i915.modeset=0 to the kernel boot
> options. An Xorg.0.log and `xrandr --verbose` output from this case
> might be useful as well.
This does not appear with KMS disabled. I'll get those logs.