Package: redshift-gtk Version: 1.12-4 Followup-For: Bug #892275 Dear Maintainer,
It seems that I have the same bug since today’s reboot. See the attached screenshot. Moreover, I can’t stop redshift. I close the window and it comes back. I can’t stop it, even killing it makes the fatal window come back again. redshift uses 100% of a processor. Yours, n. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 5.7.0-1-686-pae (SMP w/3 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR:fr:en_GB:en 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.1-1 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