jonls / redshift

Redshift adjusts the color temperature of your screen according to your surroundings. This may help your eyes hurt less if you are working in front of the screen at night.
http://jonls.dk/redshift
GNU General Public License v3.0
5.87k stars 424 forks source link

redshift causing flickering screen? #221

Open rw1018 opened 9 years ago

rw1018 commented 9 years ago

I just installed redshift (ubuntu 14.04) but its causing my screen to flicker between the red color temperature and regular temperature. Anybody know what might be causing this?

Thanks!

micaelbergeron commented 9 years ago

Same problem here, on 4.0.4-2-ARCH, using nvidia binary drivers (352.09). Either randr or vidmode method makes the flickering happen.

I'm on awesome wm and I am running compton.

ghost commented 9 years ago

This is an old issue I guess: https://bbs.archlinux.org/viewtopic.php?id=153873 I had the same experience, there was 2 redshifts running. I ended one of them and everything is fine. I guess this is some sort of autostart bug or it is because I set the location from console, so the first instance started then, and the other one when I installed the gtk. (I use Mint 17.2.)

auxsvr commented 9 years ago

In my case (nvidia) it is not exactly flickering, but an abrupt change of colours for some seconds.

winny- commented 8 years ago

I too had the same issue as @inf3rno, perhaps somebody should close this issue?

ThornedRose commented 8 years ago

I am having this same issue but only on some full screen apps (I've posted here #334 ). I definitely only have one instance of redshift starting (from selecting autostart / if I deselect that it doesn't start) however when I look at my task manager, I have two instances of redshift and one of redshift-gtk. If I kill one instance of redshift, it remains running (ditto if I kill redshift-gtk) but the flickering in certain full screen apps remains.

ThornedRose commented 8 years ago

Forgot to say I didn't have this problem at all on Openbox, LXDE or LXQT but have it in Deepin (on Arch Linux)

jmayday commented 8 years ago

Similar problem here. Currently I'm on Fedora 24 and sometimes screen flickers (for example when I enter youtube or gmail). Effect looks like I you would stop & start redshift (color changes to blue, then slowly to red again).

Those are redshift processes (it's not a problem of two instances being opened in parallel, right?):

[12:12:09] kuba:~ $ ps -A | grep -i redshift
 4705 tty2     00:00:00 redshift-gtk
 4707 tty2     00:00:00 redshift

Those are packages I have installed:

redshift.x86_64                      1.11-2.fc24                @fedora         
redshift-gtk.x86_64                  1.11-2.fc24                @fedora 

I'm running on machine with i7 6700K and use integrated graphics.

kfiresmith commented 8 years ago

Big thanks @inf3rno - I forgot I had the KDE applet running redshift when I finally got around to setting up the ~/.config/redshift.conf and --user systemD unit file, which of course left me with two instances of redshift running and the dreaded flicker. This thread came up on google page 1 for the problem and problem solved!

ghost commented 8 years ago

@kfiresmith You're welcome! :+1: Can you write a short tutorial for the others?

kfiresmith commented 8 years ago

@inf3rno - not really sure where to document, but it's pretty well covered by the first couple of posters in this thread - the problem was not with Redshift but with me foolishly running both the SystemD service and the KDE applet - they were both in contention with eachother.

o7-machinehum commented 7 years ago

If these fixes are not fixing your problem it's possible you have the same problem as me - Typically on my Windows machine I use flux, not knowing about redshift I downloaded some binaries for flux and used some install script. So Flux was actually conflicting with Redshift. Removed flux binaries from /usr/local/bin folder and my problem went away!

PhilipDeegan commented 6 years ago

I'm seeing this with on process on Debian 9 with an AMD Vega

Any thoughts?

chinf commented 6 years ago

I am seeing a problem with intermittent "flicker" - and I definitely have only one instance of redshift running and no other conflicting utilities. My problem appears as an infrequent and intermittent quick flash of default (daytime) colours before the redshifted colours are immediately reapplied. With the colour temp range set to 6500:3500 this is only really visible at night. I can provoke the flicker by repeatedly triggering colour transitions in gtk-redshift.

I have seen this problem for several months now with various versions of AMDGPU-PRO (hybrid) drivers on two different machines (both Ubuntu 16.04), one with RX 460 and the other with RX Vega. I can use either the default "randr" or "vidmode" methods to set colours, but the problem still exists.

For now my workaround is to fire off "redshift -ro" every so often via a crontab to minimise LUT changes.

bestouff commented 6 years ago

Wow ... a nearly 6-years old bug ! Is there any hope seeing this fixed ?

spacekookie commented 6 years ago

I've started having this issue on the Linux 4.15-rc7 kernel, with an AMD graphics card (RX Vega 64). The flickers aren't caused by two instances being open. And only occur once every few minutes, sometimes not at all for ~20 minutes.

Any idea what this could be?

Gotolei commented 6 years ago

Also having random flickers every few minutes or so, started immediately after rebooting from kernel 4.14 to kernel 4.15 (also AMD graphics, RX 560, Padoka PPA drivers in Xubuntu 17.10 on X). 4.15 just officially came out, so if that is the source of the problem then there'll likely be many more people running into this sometime soon.

freed00m commented 6 years ago

Also having this problem with R9 380 AMD card on Kernel 4.15 with single instance of redshift running

System:    Host: DS9 Kernel: 4.15.0-1-MANJARO x86_64 bits: 64 gcc: 7.2.1 Desktop: i3 4.14.1

Graphics:  Card: Advanced Micro Devices [AMD/ATI] Tonga PRO [Radeon R9 285/380] bus-ID: 01:00.0
           Display Server: x11 (X.Org 1.19.6 ) driver: amdgpu Resolution: 1920x1080@60.00hz
           OpenGL: renderer: AMD Radeon R9 380 Series (TONGA / DRM 3.23.0 / 4.15.0-1-MANJARO, LLVM 5.0.1)
zxvfxwing commented 6 years ago

Same issue here after kernel update.

inxi -Fx command output :

System:    Host: zxvfxtie Kernel: 4.15.0-1-ARCH x86_64 bits: 64 gcc: 7.3.0 Desktop: i3 4.14.1
           Distro: Arch Linux

Graphics:  Card-1: Intel HD Graphics 530 bus-ID: 00:02.0
           Card-2: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580]
           bus-ID: 01:00.0
           Display Server: x11 (X.Org 1.19.6 ) drivers: intel,amdgpu (unloaded: modesetting,vesa)
           Resolution: 1920x1080@144.00hz
           OpenGL: renderer: AMD Radeon RX 480 Graphics (POLARIS10 / DRM 3.23.0 / 4.15.0-1-ARCH, LLVM 5.0.1)
bestouff commented 6 years ago

🌞 Aha I have found the cause of the problem, at least on my Ubuntu 17.10 !

Since a recent version, gnome-shell has its own native redshift integration. And I still had gnome-shell-extension-redshift installed, which means both implementations were walking on each other's toes, resulting in some flickering now and then. I just uninstalled the extension and no more flickering, for now.

Hope this help

spacekookie commented 6 years ago

@bestouff That issue also occurs when running Redshift twice. Which isn't the case for me (or it seems OP either) though

bestouff commented 6 years ago

The thing is, gnome-shell has integrated its code, i.e. you can't find a process called redshift but the functionality is there. So if you see a process called redshift it means it's competing with gnome-shell. Try a killall redshift, it should work way better afterwards.

Gotolei commented 6 years ago

Thing is, not everyone is using gnome-shell.

I wonder if this should just be split into a different issue at this point, seems the original problem (two instances) was basically human error while the new problem of kernel 4.15 causing it to glitch isn't.

spacekookie commented 6 years ago

@bestouff You clearly didn't understand what I said. Thank you for explaining me how to kill a program 🙄

freed00m commented 6 years ago

@Gotolei Exactly, but I think the new issue could be dealt with right here as the title of the bug fits the profile.

EDIT: logging verbose output did not produce output.

bestouff commented 6 years ago

My comment was there just to help, don't take offense. Anyway I've created a separate issue for this: tommie-lie/gnome-shell-extension-redshift#30

supagu commented 6 years ago

yes i have this issue on 4.15 kernel single instance of redshift under manjaro kde edition

unixfox commented 6 years ago

I've the same issue after upgrading to the kernel 4.15. I'm using Plasma 5 and I've only one instance running. My GPU is AMD radeon RX480 and the driver is AMDGPU. I tried to use another blue filter software called Iris (without redshift opened) and the same issue appeared so I think that's not specific to redshift.

MageSlayer commented 6 years ago

Same story when upgrading from 4.13 to 4.15+amdgpu dc under RX580.

HadrienG2 commented 6 years ago

Same issue with kernel 4.15.2, amdgpu, and an RX 560. Screen flickers to the native color temperature shortly (I'd say a frame or two) from time to time. I'm running cinnamon 3.6.7, which AFAIK has no built-in blue-light killer. No suspicious output in dmesg or journalctl that could hint at the cause of the issue. No duplicate redshift instance either.

EDIT: Checked that there is no log from redshift -v either, and that the problem happens with either randr or vidmode methods. The drm method has no observable effect on this hardware.

MageSlayer commented 6 years ago

I've created a bug for amdgpu here - https://bugs.freedesktop.org/show_bug.cgi?id=105083 You might be interested in putting some more details.

Vavooon commented 6 years ago

For those who are using pre-Vega Radeon cards: You may try to enable AMDGPU DC (it is enabled by default only for Vega cards) by adding kernel parameter amdgpu.dc=1 in GRUB. After I enabled it I don't see flickering anymore.

ngdio commented 6 years ago

@Vavooon I have been using this kernel parameter since 4.15 was released but still have flickers nonetheless.

HadrienG2 commented 6 years ago

I still get occasional flickers with DC enabled, but it does feel like I get a lot less of them. I think I have not seen one in like, 15 minutes, they were a much more frequent occurence before.

irgendwie commented 6 years ago

@HadrienG2 the same for me, with DC enabled they are less frequent but still occurring. Additionally I enabled the dc log option but in the moment of the flickering (presumably reset of the gamma value?) no event is logged.

I'm using RX580.

ashleybone commented 6 years ago

Interestingly, in my case I only see these flashes with AMDGPU DC enabled. It does seem like the frequency of flashes has dropped with each successive 4.15 release (currently at 4.15.3). I also see nothing in the logs even with amdgpu.dc_log=1 drm.debug=6.

Vavooon commented 6 years ago

I still see flickering, but they are much rare.

Mel34 commented 6 years ago

Question for those affected (@Vavooon , @irgendwie , @HadrienG2 , @MageSlayer et al): are you using KDE Plasma? Is it possible this is related to kwin gaining wayland code for "night mode"?

If I enter Display and monitor->Gamma in KDE systemsettings5, redshift is disabled temporarily and resumes after ~8 seconds. Does this happen for you as well?

MageSlayer commented 6 years ago

@Mel34 Nope. Xfce4 is installed.

Mel34 commented 6 years ago

@MageSlayer thank you.

FWIW, I'm experiencing flicker when rapidly alt-tabbing with amdgpu.dc=1 but not with amdgpu.dc=0 on Linux 4.15.3 rx560

rnhmjoj commented 6 years ago

I'm not using any DE, have kernel 4.15.2 and amdgpu.dc=1. I see a flickering when scrolling in the browser, randomly during video playback and in video games. It's very likely related to hardware acceleration.

ashleybone commented 6 years ago

@Mel34 I'm using plasma 5.12.1, but not wayland. I don't see the behavior you're describing with the Gamma settings. Entering that page doesn't change the state of redshift, whether it's on or off.

HadrienG2 commented 6 years ago

@Mel34: I am using Cinnamon 3.6.7 on top of X11, so most likely the problem does not come from the display server/desktop environment layer of the stack. Could be above, could be below, but the fact that it only happens for AMD users and that kernel config seems to affect it would suggest that something is happening down below.

Vavooon commented 6 years ago

I'm using latest KDE on X11. Entering Gamma doesn't disable Redshift (maybe it is day and there is no gamma changes applied).

irgendwie commented 6 years ago

@Mel34 not using a DE - only dwm as WM

Lillian-Violet commented 6 years ago

Weirdly enough, running latest kde on arch, fidgeting with the gamma settings disables redshift only for my second monitor (1080p iiyama HDMI port) and not my first monitor (Acer 1440p Displayport) on my RX 470 8GB. The flicker also seems random between the two of them, maybe it has to do with refresh rates? My first monitor is 144 hz, my second 60.

Also interesting to note that my second screen flickers a lot more than my first, but perhaps that's because there's less happening on it, or certain applications I keep there cause it. Though all that's open on my second monitor at the time of typing is discord.

edit: changing applications on screen seems to have no effect on the bug, probably has something to do with a deeper layer in the OS.

irgendwie commented 6 years ago

It seems there is no flickering for me and color stays correct, when using the -o (one shot) mode - can anyone reproduce?

ngdio commented 6 years ago

@irgendwie that's because it doesn't actually dynamically adjust the color temperature, but keeps the same color temperature all the time. Of course there's no flickering because that only appears when redshift changes the color temperature.

irgendwie commented 6 years ago

@flak3 I'm aware of that, but I was expecting a different behavior. Why is redshift continuously adjusting the color temperature although it isn't necessary? I mean I'd expect at nighttime redshift sets the color and "sleeps" until dawn, or occasionally checks if the color changed (from an external application) and only if it changed adapts it back to the desired value?

Edit:

C-Higgins commented 6 years ago

Can confirm this happening on 4.15.3 using Cinnamon 3.6.7, only with amdgpu.dc=1. Does not happen if run with -o flag.

HadrienG2 commented 6 years ago

Pinging from the freedesktop thread: some patches to the gamma handling are being proposed for 4.17, can someone try amd-staging-drm-next or drm-next-4.17-wip from https://cgit.freedesktop.org/~agd5f/linux/?h=drm-next-4.17-wip ?