Doesn't work in resolution over 1080p

[yuanzhel]

Describe the bug With resolution over 1080p, redshift -O will cause the screen become green.

• [x] I have checked the FAQ and my issue is not mention there.

To Reproduce Steps to reproduce the behavior:

redshift -O 4500 (the number between 1000 to 6500 all will cause this problem) The nouveau driver will limit resolution max 1080p, so redshift works fine in that situation. But i use GT 710 with nvidia driver 418, which can set my 4K display to 2K resolution and redshift does not work.

Expected behavior Change the color temperature as i set.

Error output/logs/screenshots The screen become green. The color temperature set lower, the green stronger.

Software versions (please complete the following information):

• OS: Linux
• Redshift version: 1.10
• Distribution: Ubuntu 16.04 LTS Server with 4.4.0-142-generic kernel/ nvidia driver 418.56
• Redshift installed from: Using apt-get

[yuanzhel]

I already checked with this driver, but set resolution to 1080P, redshift works fine. So please check this bug, i think the problem is in redshift code itself. Thanks for your time, hope you can help out :)

[adm-romanb]

Same thing. Redshift turns my 4k samsung tv, which is connected via HDMI, into green color. It doesnt turn my dell 4k monitor (connecter via DP) into green color but any time I change the brightnest up or down using mouse scroll all my screens become darkner till I see nothing. I may record a video/make a photo if you want. OS: Linux Redshift version: 1.12-2 Distribution: Debian 10.1 Redshift installed from: Using apt-get

[summonholmes]

Same issue as above. 4k Samsung TV connected via HDMI results in a green overlay. I'll also add that I don't have this problem when setting my refresh rate to 30Hz. When set greater than 30Hz, the problem occurs. However, DP is fine.

Redshift Version: 1.12-2 (from the repo) OS: Debian 10.1 Kernel: x86_64 Linux 5.2.0-0.bpo.2-amd64 GPU: NVIDIA 430.50 (NOT from the repo)

[adm-romanb]

Turned out that was Nvidia issue, not redshift. To solve this you need to set Option "UseNvKmsCompositionPipeline" "false" In Device section in xorg.conf file https://www.reddit.com/r/archlinux/comments/acqvmy/high_xorg_cpu_usage_and_lag_while_moving_and/

[AshleyYakeley]

This is still a redshift issue IMO. Redshift should detect and mitigate (or at least warn about) this condition. As a user, I should never have to edit my xorg.conf myself.

[mcmxcdev]

I am running into this issue with a setup of Ubuntu 21.10, X11, nvidia-driver-470 and GNOME Night Light.

Using two 4k monitors, any solutions or workarounds to fix the green tint?

[adm-romanb]

I am running into this issue with a setup of Ubuntu 21.10, X11, nvidia-driver-470 and GNOME Night Light.

Using two 4k monitors, any solutions or workarounds to fix the green tint?

Turned out that was Nvidia issue, not redshift. To solve this you need to set Option "UseNvKmsCompositionPipeline" "false" In Device section in xorg.conf file https://www.reddit.com/r/archlinux/comments/acqvmy/high_xorg_cpu_usage_and_lag_while_moving_and/

[mcmxcdev]

That doesn't do it for me, unfortunately.

Note that one screen uses DisplayPort, which works as expected, but the HDMI one has a green tint.

[adm-romanb]

That doesn't do it for me, unfortunately.

Note that one screen uses DisplayPort, which works as expected, but the HDMI one has a green tint.

I've got same configuration (DP+HDMI) and that xorg option did solve this green problem.

[mcmxcdev]

Strange! What I did was go into /usr/share/X11/xorg.conf.d and edit 10-nvidia.conf, to look like this:

Section "OutputClass"
    Identifier "nvidia"
    MatchDriver "nvidia-drm"
    Driver "nvidia"
    Option "AllowEmptyInitialConfiguration"
    Option "UseNvKmsCompositionPipeline" "false"
    ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"

EndSection

Section "Device"
    Option "UseNvKmsCompositionPipeline" "false"

EndSection

Since there was no device section, I added one, but it feels wrong.

[adm-romanb]

Since there was no device section, I added one, but it feels wrong.

Hm... try to generate a xorg.conf file using Nvidia X Server Settings - Xserver Display Configuration - Save to x Configuration File. Then edit this config and restart xserver/pc/

[mcmxcdev]

Hm... try to generate a xorg.conf file using Nvidia X Server Settings - Xserver Display Configuration - Save to x Configuration File. Then edit this config and restart xserver/pc/

It tries to save the configuration to /etc/x11/xorg.conf by default which doesn't exist yet -> gives me Unable to open X config file for writing. There is a xorg.conf.d folder though but its empty. When I create a new file touch xorg.conf with the intention to have it overwtitten, then I receive the same error tht its unable open the config file.

---

UPDATE: I was not able to save to file directly, but there was a "show preview" button that gave me the generated text content, pasted it in the xorg.conf.d file and now Night Light works properly! Big thanks to @adm-romanb

[GibsDev]

Make sure you add Option "UseNvKmsCompositionPipeline" "false" into the LAST "Device" section of all config files. The files in the /etc/X11/xorg.conf.d/ directory will override settings from the /etc/X11/xorg.conf file. Also keep in mind the files in that directory are executed in alphabetical order.