I have redshift working on both my desktop and laptop, here's how I have things set up: * If you don't have "normal" desktop environment like GNOME, then you need to start the geoclue agent manually (note that the path to it recently changed, which may be way people have having problems again recently). Make sure you're running the latest geoclue, as there was an issue for systems without wifi. * Ensure redshift and the agent are allowed to access geoclue in /etc/geoclue/geoclue.conf (again, this is for people who aren't running GNOME, which includes me). * I have disabled the user service, mostly because I start things manually. That may help if people find that redshift keeps restarting (check your user journal also). * I don't have a xdg-autostart service running, so I'm not affected by redshift adding itself there automatically. Not sure if others are being affected by this though.
I don't think this is grave, important at best, for redshift (I'd say this is due to geoclue changes, so the bug should be assigned there). It might be worth seeing though if some kind of autopackagetest could be added so regressions due to geoclue changes get flagged though. James -- Don't send me files in proprietary formats (.doc(x), .xls, .ppt etc.). It isn't good enough for Tim Berners-Lee, and it isn't good enough for me either. For more information visit http://www.gnu.org/philosophy/no-word-attachments.html. Truly great madness cannot be achieved without significant intelligence. - Henrik Tikkanen If you're not messing with your sanity, you're not having fun. - James Tocknell In theory, there is no difference between theory and practice; In practice, there is.
