http://bugzilla.suse.com/show_bug.cgi?id=995924
http://bugzilla.suse.com/show_bug.cgi?id=995924#c22
--- Comment #22 from Robert Munteanu
Just compared X logfiles. For the RPMs you still used 367.44, whereas for the .run installation you already used 367.57. So this is no longer a fair comparison I believe. ;-)
Ah, right. This was probably an old bug report, I updated a new one with the 367.57 RPM - 367.44 does not work with the current TW kernel.
Anyway, for me this looks more like a GNOME issue or it has just been fixed in 367.57. We don't and never supported building RPMs yourself. For TW it's recommended to use the .run install method. uut honestly TW and NVIDIA proprietary driver is not a good combination anyway, since any TW update may result in a mess, if Mesa or other components overwrite NVIDIA components ... And after a kernel update you need to rebuild the kernel module ...
For me personally the RPM method has the benefit of not requiring intervention when the kernel minor version is updated - or Mesa IIRC, which is a great benefit. Using the .run driver is instead a great pain in the neck, and I'd rather avoid that. I also uploaded the output of snapper status showing the changes between a broken RPM setup and a working .run setup. Hopefully that sheds some light.
So if you really want to do this uninstall the nVIDIA driver *before* any TW update and reinstall it afterwards.
Reassigning to GNOME guys ...
-- You are receiving this mail because: You are on the CC list for the bug.