Comment 60 for bug 184440

Just because it only happens with nvidia drivers doesn't mean it's an nvidia problem. In fact, it's not an nvidia problem, it's more of a totem problem.

The problem is that the XV_HUE value has no prescribed default. Totem assumes that it is the middle value, along with Brightness, Contrast, and Saturation (which happen to be correct). In the case of nvidia drivers, this is incorrect for hue because the range is actually 0-360, with 0 being default[1]. The problem is confounded because totem doesn't like the minimum value of 0 for a hue, so it sets whatever default it has on startup[2].

So, there are actually two bugs in totem:
1) "Reset to defaults" makes up values that are usually correct but not always.
2) Totem, upon startup, does not accept the minimum value of 0 for hue and instead sets it to whatever value it has saved in gconf.

So, I'm going to file this against totem.

References:
[1]: <http://nvnews.net/vbulletin/showthread.php?t=107009#post1539184>
[2]: <http://bugzilla.gnome.org/show_bug.cgi?id=306621#c27> (includes patch to totem)