Your message dated Mon, 30 Aug 2021 14:29:47 +0200
with message-id <[email protected]>
and subject line Re: User systemd units redshift.service and
redshift-gtk.service are both enabled by default which cases both to spawn
redshift
has caused the Debian Bug report #979263,
regarding User systemd units redshift.service and redshift-gtk.service are both
enabled by default which cases both to spawn redshift
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
979263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979263
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: redshift-gtk
Version: 1.12-4
Severity: minor
Hi
I recently noticed that redshift and redshift-gtk now ship user-level
systemd instances, which appear to have been automatically activated,
so that systemd starts them automatically on login.
This causes two actual redshift instances to be started on login, as
seen here:
% ps ax | grep redshift
10027 ? Ssl 0:00 /usr/bin/redshift
10028 ? Ssl 0:00 /usr/bin/python3 /usr/bin/redshift-gtk
10034 ? Sl 0:00 /usr/bin/redshift -v
10045 pts/2 S+ 0:00 grep redshift
This seems to happen because each of redshift.service and
redshift-gtk.service starts their own redshift instance.
These two instances then seem to cause other trouble. For example,
when deactivating redshift throgh the redshift-gtk icon, the display
shifts to the day temperature and then reverts immediately to the
night temperature, because only one of the redshift instances has
actually been deactivated.
I can fix this locally for me, by disabling redshift.service. But I
guess this package is used by users who aren't as experienced with
systemd, so I think a default configuration that works out-of-the-box
(without starting two competing redshift instances) would be
preferable.
Regards
Sven
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-debug
APT policy: (990, 'testing-debug'), (990, 'testing'), (102,
'unstable-debug'), (102, 'unstable'), (101, 'experimental-debug'), (101,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.9.0-5-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
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
--- End Message ---
--- Begin Message ---
Version: 1.12-4.2
Hi,
On Mon, 04 Jan 2021 19:08:26 +0100 Sven Bartscher
<[email protected]> wrote:
I recently noticed that redshift and redshift-gtk now ship user-level
systemd instances, which appear to have been automatically activated,
so that systemd starts them automatically on login.
The systemd services have been removed in 1.12-4.2, so this bug report
is obsolete now.
Regards
Sven
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
