Package: redshift-gtk
Version: 1.11-1
Severity: wishlist
If the systemd service is enabled (and works, see #827098) then a user
wanting GUI visbility on whatever redshift is doing might naturally
start the graphical application he/she sees in the menus.
In this case, both applications get into a heated power struggle over
the color of the monitor, obviously neither winning.
It would be nice if gtk-redshift:
1. would notice his own partner running
2. abort with a friendly error message
3. eventually, instead of aborting, communicate with the running
process and report information, allow toggling the status and so
on
Thanks!
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing'), (1, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf
Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages redshift-gtk depends on:
ii gir1.2-appindicator3-0.1 0.4.92-4
ii python3-gi 3.22.0-2
ii python3-xdg 0.25-4
pn python3:any <none>
ii redshift 1.11-1
Versions of packages redshift-gtk recommends:
ii at-spi2-core 2.22.0-5+b1
redshift-gtk suggests no packages.
-- no debconf information
