GNU bug report logs - #68415
User's shepherd services defined in guix home config can not start after guix pull.

Previous Next

Full log

Message #14 received at 68415 <at> debbugs.gnu.org (full text, mbox):

From: Sergey Trofimov <sarg <at> sarg.org.ru>
To: Feng Shu <tumashu <at> 163.com>
Cc: 68415 <at> debbugs.gnu.org
Subject: Re: bug#68415: User's shepherd services defined in guix home config
 can not start after guix pull.
Date: Wed, 17 Jan 2024 08:04:58 +0100

Feng Shu <tumashu <at> 163.com> writes:

>>
>> Have you tried debugging it? Is your home shepherd running? Do 
>> you see
>
> I tried, but I do not know why: unbound-variable service
>
That is not normal. You need to fix that.

>
> The below code run have problem, and I think shepherd is not 
> run, for
> 'ps aux |grep shepherd' can not found info.

home's shepherd is started by ~/.guix-home/on-first-login, which 
gets invoked in ~/.profile
You can try running the script manually and see what happens.

Please compare your home configuration before and after the pull. 
You can find the configs in 
/var/guix/profiles/per-user/<name>/guix-home-<version>-link/configuration.scm

The subject is "can not start after guix pull", but it seems to me 
your home is misconfigured and the pull might be unrelated.

>
>      (service
>       home-shepherd-service-type
>       (home-shepherd-configuration
>        (shepherd shepherd)

that's the default, no need to specify shepherd

>        (services
>         (list xautolock-service))))
>

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.