unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Raghav Gururajan <rg@raghavgururajan.name>
Cc: help-guix@gnu.org
Subject: Re: RedShift
Date: Fri, 18 Nov 2022 17:51:10 +0100	[thread overview]
Message-ID: <87h6yw9pfl.fsf@gnu.org> (raw)
In-Reply-To: <6a20b10e-8056-1293-3bc6-e9b58b28c379@raghavgururajan.name> (Raghav Gururajan's message of "Fri, 11 Nov 2022 09:47:08 -0500")

Hi,

Raghav Gururajan <rg@raghavgururajan.name> skribis:

> I'm trying to use the redshift home-service
> [https://git.savannah.gnu.org/cgit/guix.git/commit/?id=39e8025d3b40a0079f75e0ce9a91b6dad6766773],
> but `herd status` always show it as stopped. Unlike the 'manual'
> location-provider example mentioned in the commit, I'm using geoclue.
>
> Do you happen to have an example for redshift with geoclue?

I don’t use Geoclue; instead, I specified my coordinates and I stay
home.  ;-)

If ‘herd start redshift’ fails, there should be more info in
~/.local/var/log/shepherd.log.  Could you check that and share your
findings?

HTH,
Ludo’.


  parent reply	other threads:[~2022-11-18 16:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 14:47 RedShift Raghav Gururajan
2022-11-11 15:05 ` RedShift Felix Lechner via
2022-11-11 16:29   ` RedShift Raghav Gururajan
2022-11-11 16:48     ` RedShift Felix Lechner via
2022-11-12  4:26       ` RedShift Raghav Gururajan
2022-11-12  6:10         ` RedShift Felix Lechner via
2022-11-12 11:23           ` RedShift Raghav Gururajan
2022-11-18 16:51 ` Ludovic Courtès [this message]
2022-11-19  3:31   ` RedShift Raghav Gururajan
2022-12-02  8:43     ` RedShift Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2023-03-11 11:14 redshift Gottfried
2023-03-11 16:47 redshift Gottfried
2023-03-11 17:25 ` redshift Dr. Arne Babenhauserheide
2023-03-12  8:03   ` redshift Gottfried
2023-03-12  8:08     ` redshift Dr. Arne Babenhauserheide
2023-03-12 11:07 ` redshift Sergiu Ivanov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h6yw9pfl.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=rg@raghavgururajan.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).