redshift doesn't work with nvidia 302.17

Bug #1018229 reported by Reed Lipman
66
This bug affects 13 people
Affects Status Importance Assigned to Milestone
Redshift
New
Undecided
Unassigned
Gentoo Linux
New
Undecided
Unassigned

Bug Description

I updated my Arch box today and it pulled down a kernel update and an nvidia update. Since then, redshift isn't changing my colors anymore. I even tried an extreme setting for -t like 5700:1500 and nothing happened.

What information would be helpful here to figure out if it's a redshift or nvidia bug?

Distro: Arch
Kernel: 3.4.4-2
Drivers: Nvidia 302.17

Revision history for this message
Reed Lipman (rmlipman) wrote :

After looking into it more, I was able to get it working by using -m vidmode. Only randr is broken for me.

Revision history for this message
Isaac Aggrey (isaacaggrey) wrote :

Thanks for the tip, Reed. I was wondering why redshift wasn't working anymore...I wonder if this is an Arch-specific issue, but in any case vidmode works perfectly.

Revision history for this message
Jan Vlnas (jnv) wrote :

This is not Arch-specific issue, I have the same problem on Ubuntu with nvidia-current 302.17 from X Updates PPA: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates/

Nvidia drivers v302 added support for RandR 1.2/1.3, so maybe this is related to the issue? http://www.phoronix.com/scan.php?page=news_item&px=MTA5NTY

Revision history for this message
Allan Wang (allanvv) wrote :

I can confirm this on 302.17. I've switched over to RandR for multi monitor support but the randr mode in redshift does not work. Using vidmode works but only affects my main monitor. Trying vidmode:screen=1 fails

bash-4.1$ redshift -m vidmode:screen=1 -v -o -t 6300:4000
Location: 42.000000, -83.000000
Gamma: 1.000, 1.000, 1.000
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 129 (XFree86-VidModeExtension)
  Minor opcode of failed request: 19 (XF86VidModeGetGammaRampSize)
  Value in failed request: 0x17
  Serial number of failed request: 12

Revision history for this message
aurelieng (aurelien-grosdidier) wrote :

Hi all. Exact same symptom and error message than those reported in #4, running Arch w/ nvidia 304.37, redshift 1.7.

Revision history for this message
Jan Vlnas (jnv) wrote :

It seems that randr method works again with the recently released 304.51 which supposedly includes some fixes to RandR.
Can anyone else confirm that?

Revision history for this message
Ray G. (codenomad) wrote :

No go on Arch with nvidia 304.60, redshift 1.7.

codenomad@Mordor:~$ redshift vidmode:screen=1 -v -o -t 6300:4000
Location: 35.180801, 106.519997
Brightness: 1.00
Gamma: 0.800, 0.700, 0.800
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 151 (XFree86-VidModeExtension)
  Minor opcode of failed request: 19 (XF86VidModeGetGammaRampSize)
  Value in failed request: 0x17
  Serial number of failed request: 12
  Current serial number in output stream: 12
codenomad@Mordor:~$ redshift -m vidmode:screen=1 -v -o -t 6300:4000
Location: 35.180801, 106.519997
Brightness: 1.00
Gamma: 0.800, 0.700, 0.800
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 151 (XFree86-VidModeExtension)
  Minor opcode of failed request: 19 (XF86VidModeGetGammaRampSize)
  Value in failed request: 0x17
  Serial number of failed request: 12
  Current serial number in output stream: 12

Revision history for this message
Ole Martin Handeland (j-launchpad-olemartin-org) wrote :

Works fine with 304.60 on Ubuntu x64. Redshift 1.7.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.