GNOME Bugzilla – Bug 587753
nvidia sets HUE to -1000
Last modified: 2011-04-06 02:08:58 UTC
Please describe the problem: opening movies makes them look blueish due to the fact that nvidia settings have HUE set to -1000 the user can manually fix that, by setting to zero, but the next time a movie is opened it will re-set to -1000 ProblemType: Bug Architecture: amd64 Date: Sat Jul 4 11:44:00 2009 DistroRelease: Ubuntu 9.10 MachineType: To Be Filled By O.E.M. S37S NonfreeKernelModules: nvidia Package: nvidia-glx-180 185.18.14-0ubuntu2 ProcCmdLine: root=UUID=a8aa4adb-b3e6-4e1d-b4ad-e6cd704788b2 ro vga=0x360 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-1.14-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu4 libgl1-mesa-glx 7.5~rc4-1ubuntu2 libdrm2 2.4.11-0ubuntu1 xserver-xorg-video-intel N/A xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu1 SourcePackage: nvidia-graphics-drivers-180 Uname: Linux 2.6.31-1-generic x86_64 dmi.bios.date: 01/22/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: S37S dmi.board.vendor: To Be Filled By O.E.M. dmi.board.version: 1.00 dmi.chassis.asset.tag: 0x00000000 dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd01/22/2008:svnToBeFilledByO.E.M.:pnS37S:pvr1.0:rvnToBeFilledByO.E.M.:rnS37S:rvr1.00:cvnToBeFilledByO.E.M.:ct10:cvr1.0: dmi.product.name: S37S dmi.product.version: 1.0 dmi.sys.vendor: To Be Filled By O.E.M. fglrx: Not loaded system: distro: Ubuntu architecture: x86_64kernel: 2.6.31-1-generic $ apt-cache policy totem totem: Installed: 2.27.1-1ubuntu5 Candidate: 2.27.1-1ubuntu5 Version table: *** 2.27.1-1ubuntu5 0 500 http://darkstar.ist.utl.pt karmic/main Packages 500 http://archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status $ apt-cache policy gstreamer0.10-plugins-base gstreamer0.10-plugins-base: Installed: 0.10.23-3 Candidate: 0.10.23-3 Version table: *** 0.10.23-3 0 500 http://darkstar.ist.utl.pt karmic/main Packages 500 http://archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status Steps to reproduce: 1. open any video on totem 2. image is blue 3. fix it on nvidia settings 4. open another video 5. image is again blue Actual results: image is blueish Expected results: regular colors Does this happen every time? Yes Other information: Philip Muskovac wrote: Mplayer: works fine VLC: works fine Totem: broken Mplayer: now also broken VLC: now also broken Totem bug?
linked downstream https://bugs.launchpad.net/bugs/395476
What's the output of `xvinfo`?
$ xvinfo X-Video Extension version 2.2 screen #0 Adaptor #0: "NV17 Video Texture" number of ports: 32 port base: 280 operations supported: PutImage supported visuals: depth 24, visualID 0x21 depth 24, visualID 0x24 depth 24, visualID 0x25 depth 24, visualID 0x26 depth 24, visualID 0x27 depth 24, visualID 0x28 depth 24, visualID 0x29 depth 24, visualID 0x2a depth 24, visualID 0x2b depth 24, visualID 0x2c depth 24, visualID 0x2d depth 24, visualID 0x2e depth 24, visualID 0x2f depth 24, visualID 0x30 depth 24, visualID 0x31 depth 24, visualID 0x32 depth 24, visualID 0x33 depth 24, visualID 0x34 depth 24, visualID 0x35 depth 24, visualID 0x36 depth 24, visualID 0x37 depth 24, visualID 0x38 depth 24, visualID 0x39 depth 24, visualID 0x3a depth 24, visualID 0x3b depth 24, visualID 0x3c depth 24, visualID 0x3d depth 24, visualID 0x3e depth 24, visualID 0x22 depth 24, visualID 0x3f depth 24, visualID 0x40 depth 24, visualID 0x41 depth 24, visualID 0x42 depth 24, visualID 0x43 depth 24, visualID 0x44 depth 24, visualID 0x45 depth 24, visualID 0x46 depth 24, visualID 0x47 depth 24, visualID 0x48 depth 24, visualID 0x49 depth 24, visualID 0x4a depth 24, visualID 0x4b depth 24, visualID 0x4c depth 24, visualID 0x4d depth 24, visualID 0x4e depth 24, visualID 0x4f depth 24, visualID 0x50 depth 24, visualID 0x51 depth 24, visualID 0x52 depth 24, visualID 0x53 depth 24, visualID 0x54 depth 24, visualID 0x55 depth 24, visualID 0x56 depth 24, visualID 0x57 depth 24, visualID 0x58 depth 24, visualID 0x59 number of attributes: 7 "XV_SET_DEFAULTS" (range 0 to 0) client settable attribute "XV_ITURBT_709" (range 0 to 1) client settable attribute client gettable attribute (current value is 0) "XV_SYNC_TO_VBLANK" (range 0 to 1) client settable attribute client gettable attribute (current value is 1) "XV_BRIGHTNESS" (range -1000 to 1000) client settable attribute client gettable attribute (current value is 0) "XV_CONTRAST" (range -1000 to 1000) client settable attribute client gettable attribute (current value is 0) "XV_SATURATION" (range -1000 to 1000) client settable attribute client gettable attribute (current value is 0) "XV_HUE" (range -1000 to 1000) client settable attribute client gettable attribute (current value is 0) maximum XvImage size: 2046 x 2046 Number of image formats: 4 id: 0x32595559 (YUY2) guid: 59555932-0000-0010-8000-00aa00389b71 bits per pixel: 16 number of planes: 1 type: YUV (packed) id: 0x32315659 (YV12) guid: 59563132-0000-0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar) id: 0x59565955 (UYVY) guid: 55595659-0000-0010-8000-00aa00389b71 bits per pixel: 16 number of planes: 1 type: YUV (packed) id: 0x30323449 (I420) guid: 49343230-0000-0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar)
Totem in GNOME 3.2 doesn't use the Xv port anymore, so we don't need to care about NVidia drivers bug such as this one anymore.