Comment 10 for bug 753971

On Wed, Apr 13, 2011 at 09:40:30PM -0000, Daniel Manrique wrote:
> Bryce, I completed the table with the systems we tested, I'm indicating
> whether it's affected by the problem or not, I'm also noting the model
> number, the driver as obtained from Xorg.log, and the VGA card as
> identified by lspci. It's in HTML because it was too unwieldy to be
> handled in text-only format.
>
> http://people.canonical.com/~roadmr/garbled.html
>
> I had some trouble reinstalling some of the systems to verify, so some
> are marked as "could not connect". They are the minority though.
>
> I noticed one thing, all the systems that are marked as "not" affected
> in the sheet, are the ones that couldn't run Unity (they show a dialog
> asking to go into classical mode).
>
> Let me know if you need anything else, thanks for your help!

Thanks, this is a great list!

If it were an X bug, I would expect to see the yes/no to fall along
chipset family lines, and certainly be specific to just one video
driver.

Given that the correlation crosses both chip families as well as
drivers, and as you point out is reproducing only on systems that run
unity, and not on ones that don't, it is suggesting perhaps this is not
an X bug but rather compiz/unity.

Compiz has its own internal logic for handling XRANDR events such as
multi-monitor and rotation, which we've seen bugged previously; this
could be another instance of such a bug. I will forward this to the
unity team. Thanks again for all your excellent testing work!