Package: gtk-redshift Version: 1.9.1-4 Followup-For: Bug #813553 Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate *** This bug has been around for months and I can confirm that in Jessie Stable, gtk-redshift still simply exits with a return value of 255 if I do not use the -l option to manually specify my location. I have tried with Gnome3 and Cinnamon, so the problem is not restricted to Awesome. Is upstream aware of this? Should we just fix it ourselves? *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gtk-redshift depends on: ii gir1.2-appindicator3-0.1 0.4.92-3.1 ii python-gtk2 2.24.0-4 ii python3 3.4.2-2 ii python3-gi 3.14.0-1 ii python3-xdg 0.25-4 pn python3:any <none> ii redshift 1.9.1-4 Versions of packages gtk-redshift recommends: ii at-spi2-core 2.14.0-1 gtk-redshift suggests no packages. -- no debconf information
