Comment 9 for bug 840462

Hello out there, some news about this:

1. __Tried nvidia driver from nvidia download:__
Yesterday I gave the subject another try uninstalled all nvidia-current/settings, downloaded the original nvidia 280.13 driver from the nvidia download page, compiled an installed it. The tool creates automatically an nvidia aware xorg.conf.

__Result:__
Same problems as described above.

2. __ Installed again 280.13/oneiric and Gnome Shell / Unity 2(!) D: __
It turns out after some hours/days of real work, that using these environments work flawlessly with the driver.
Hopefully I don't suffer from a hardware problem. But this point indicates, that this it not the fact.

__Conclusion:__
A. Switching back to Unity 3D there is an interesting issue:
just in the moment twinview turns out going to work - with the method described in #6 - compiz (unity?!) crashes.
You can have a look for the Xorg.0.log.old (with is the crashed unity session) whats going on there.
Xorg.0.log represents the gnome shell session.

SO FINALLY:

1. This seams not a bug with nvidia 280.13, this is __definitely a bug with Unity 3D AND nvidia driver__ (doesn't matter which version 275/280/285)!

2. The problem is device indepentend. I am working in different environments (office, at home, at school, doing courses with beamer). The problems are the same, no matter what type of second device i am using (vga/dvi, beamer/lcd). On the fly switching is not working, at least extremely buggy.

3. It turns out, working with an xorg file (constructed with nvidia-settings when you where happy to get a running twinview setting) boots flawlessly into a working environment (Untiy 3D), after logout/login/boot

4. Overall performance degraded (compared with natty / 270series of nvidia)

-> I will keep an eye on this issue an probably will file a bug against Unity 3D / nvidia.