Bug 17224

Please don't change the status from NEW to ASSIGNED, that's the assignee's job.

This sounds like this problem, which is a bug in Totem or gstreamer somewhere and not a bug in the driver:

http://nvnews.net/vbulletin/showthread.php?t=107009&highlight=totem

Please try the xvattr command listed in that thread.  If that fixes it, then this is NOTOURBUG.

I still think it is problem in driver "nv".
 
the reason are:
1.use vesa driver ,totem or other video player will show right color.
2.use nvidia driver from nvidia company (NVIDIA-Linux-x86-96.43.01-pkg1.run) . totem or other video player will show right color.
 
 
video player -> driver ->show color right?
video player -> driver "vesa" -> show color right
video player -> driver "nvidia" -> show color right
video player -> driver "nv" -> show color wrong
 
is it the video player wrong?
I did not agree it.
 
(In reply to comment #1)
> Please don't change the status from NEW to ASSIGNED, that's the assignee's job.
> 
> This sounds like this problem, which is a bug in Totem or gstreamer somewhere
> and not a bug in the driver:
> 
> http://nvnews.net/vbulletin/showthread.php?t=107009&highlight=totem
> 
> Please try the xvattr command listed in that thread.  If that fixes it, then
> this is NOTOURBUG.
> 

I still think it is problem in driver "nv".

the reason are:
1.use vesa driver ,totem or other video player will show right color.
2.use nvidia driver from nvidia company (NVIDIA-Linux-x86-96.43.01-pkg1.run) . totem or other video player will show right color.


video player -> driver ->show color right?
video player -> driver "vesa" -> show color right
video player -> driver "nvidia" -> show color right
video player -> driver "nv" -> show color wrong

you think it is the video player wrong?
I did not agree it.

----------------------------------------
> From: bugzilla-daemon@freedesktop.org
> To: p00r0@hotmail.com
> Subject: [Bug 17224] Debian Unstable xorg-server 2:1.4.  2-4 nv drive video-color not right
> Date: Wed, 20 Aug 2008 09:00:18 -0700
> 
> http://bugs.freedesktop.org/show_bug.cgi?id=17224
> 
> 
> Aaron Plattner  changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |aplattner@nvidia.com
>          AssignedTo|aplattner@nvidia.com        |p00r0@hotmail.com
>              Status|ASSIGNED                    |NEW
> 
> 
> 
> 
> --- Comment #1 from Aaron Plattner   2008-08-20 09:00:15 PST ---
> Please don't change the status from NEW to ASSIGNED, that's the assignee's job.
> 
> This sounds like this problem, which is a bug in Totem or gstreamer somewhere
> and not a bug in the driver:
> 
> http://nvnews.net/vbulletin/showthread.php?t=107009&highlight=totem
> 
> Please try the xvattr command listed in that thread.  If that fixes it, then
> this is NOTOURBUG.
> 
> 
> -- 
> Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
> You are the assignee for the bug.
> You reported the bug.

_________________________________________________________________
看MSN史诗巨片，票选人气角色，赢取PSP等诸多好礼！
http://im.msn.cn/

Please look for the XV_HUE attribute.  If the driver doesn't support it, the video player can't mess it up.  For the nvidia driver, make sure you're using the Xv overlay adaptor and not the blit adaptor.

Thanks for you answer.

I find solution.
In totem 
menu
Preferences -> Display, the Hue slider is moved to left position

I guess the reason.my Adapter is Older?

(In reply to comment #4)
> Please look for the XV_HUE attribute.  If the driver doesn't support it, the
> video player can't mess it up.  For the nvidia driver, make sure you're using
> the Xv overlay adaptor and not the blit adaptor.
> 

Yes, only certain drivers and hardware support XV_HUE.  If running

   xvattr -a XV_HUE -v 0

fixes it after it's messed up, then it's not a driver bug but rather the video player intentionally changing the hue adjustment.  I'm going to go ahead and mark this NOTOURBUG.  Please reopen if you find evidence that this really is a driver bug.