Package: redshift-gtk Version: 1.12-4 Severity: important X-Debbugs-Cc: deb.b...@gmx.com
Dear Maintainer, With the new version 1.12-4, redshift runs twice in the user session, causing the screen to flicker if a redshift.conf file was previously created. It is also impossible to kill thoses two instances. When trying, they restart (zombie-like), and make the screen darker. This behaviour is due to the fact that redshift and redshift-gtk launch through systemd at startup. When installing redshift and redshift-gtk from terminal, you get to read the following lines: symlink /etc/systemd/user/default.target.wants/redshift.service → /usr/lib/systemd/user/redshift.service symlink /etc/systemd/user/default.target.wants/redshift-gtk.service → /usr/lib/systemd/user/redshift-gtk.service Those links and service files cause a "systemd instance" of redshift to launch parallel to the "user instance" of redshift. Deleting those links and files (as root) solves the problem. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (500, 'groovy') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages redshift-gtk depends on: ii gir1.2-ayatanaappindicator3-0.1 0.5.5-2 ii init-system-helpers 1.60 ii python3 3.9.0-4 ii python3-gi 3.38.0-1+b2 ii python3-xdg 0.26-3 ii redshift 1.12-4 Versions of packages redshift-gtk recommends: ii at-spi2-core 2.38.0-2 redshift-gtk suggests no packages. -- no debconf information
