Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40477 - [redshift] cannot start with systemctl, miss Environment=DISPLAY=:0 in service files

Attached to Project: Community Packages
Opened by Bastien Traverse (Neitsab) - Wednesday, 21 May 2014, 02:05 GMT
Last edited by Lukas Fleischer (lfleischer) - Friday, 09 January 2015, 13:32 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
As noted in  FS#40476  (https://bugs.archlinux.org/task/40476), redshift and redshift-gtk fail to start with $ systemctl --user start if the option "Environment=DISPLAY=:0" isn't added to the service files' [Service] section.

See the first part of this post https://bbs.archlinux.org/viewtopic.php?pid=1417568#p1417568 for the complete details.

Additional info:
* package versions: redshift 1.9-3, 1.9.1-1
* original and corrected service files attached.

Steps to reproduce:
# pacman -S redshift
$ systemctl --user start redshift
--> nothing happens, $ journalctl -b --user-unit=redshift indicates a failed state.

* add "Environment=DISPLAY=:0" to the service files (/usr/lib/systemd/user/redshift.service & /usr/lib/systemd/user/redshift-gtk.service) [Service] section and retry to start the services --> it works.
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Friday, 09 January 2015, 13:32 GMT
Reason for closing:  Upstream
Comment by Lukas Fleischer (lfleischer) - Friday, 22 August 2014, 10:22 GMT
Did you report this upstream?
Comment by Bastien Traverse (Neitsab) - Friday, 22 August 2014, 10:33 GMT
Yes I did, and it has seen some recent activity: see https://github.com/jonls/redshift/issues/91 (notably with an Arch fellow proposing what seems to be an acceptable solution for upstream).

Loading...