GNU bug report logs -
#68415
User's shepherd services defined in guix home config can not start after guix pull.
Previous Next
Reported by: Feng Shu <tumashu <at> 163.com>
Date: Sat, 13 Jan 2024 05:17:01 UTC
Severity: normal
Done: Ludovic Courtès <ludo <at> gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 68415 in the body.
You can then email your comments to 68415 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#68415
; Package
guix
.
(Sat, 13 Jan 2024 05:17:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Feng Shu <tumashu <at> 163.com>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Sat, 13 Jan 2024 05:17:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
After I guix pull, services defined in guix home config can no start:
-------------------------
服务 root 已启动。
WARNING: Use of `load' in declarative module (#{ g117}#). Add #:declarative? #f to your define-module invocation.
unbound-variable(#f "Unbound variable: ~S" (service) #f)
Some deprecated features have been used. Set the environment
variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
program to get more information. Set it to "no" to suppress
this message.
Creating XDG user directories... done
Comparing /gnu/store/bfkgfz1sm9q75jyn56pav2kmwl48i7w8-home/profile/share/fonts and
/gnu/store/bfkgfz1sm9q75jyn56pav2kmwl48i7w8-home/profile/share/fonts... done (same)
Evaluating on-change gexps.
-----------
When I run command: herd status, show error:
feng <at> Guix ~$ herd status
error: connect: /run/user/1000/shepherd/socket: No such file or directory
--
Information forwarded
to
bug-guix <at> gnu.org
:
bug#68415
; Package
guix
.
(Tue, 16 Jan 2024 06:55:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 68415 <at> debbugs.gnu.org (full text, mbox):
Feng Shu <tumashu <at> 163.com> writes:
> After I guix pull, services defined in guix home config can no
> start:
>
> -------------------------
> 服务 root 已启动。
> WARNING: Use of `load' in declarative module (#{ g117}#). Add
> #:declarative? #f to your define-module invocation.
> unbound-variable(#f "Unbound variable: ~S" (service) #f)
>
> Some deprecated features have been used. Set the environment
> variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
> program to get more information. Set it to "no" to suppress
> this message.
> Creating XDG user directories... done
> Comparing
> /gnu/store/bfkgfz1sm9q75jyn56pav2kmwl48i7w8-home/profile/share/fonts
> and
> /gnu/store/bfkgfz1sm9q75jyn56pav2kmwl48i7w8-home/profile/share/fonts...
> done (same)
> Evaluating on-change gexps.
>
> -----------
>
> When I run command: herd status, show error:
>
> feng <at> Guix ~$ herd status
> error: connect: /run/user/1000/shepherd/socket: No such file or
> directory
Have you tried debugging it? Is your home shepherd running? Do you
see shepherd mentions in ~/.guix-home/on-first-login?
Have you tried restarting your system?
Information forwarded
to
bug-guix <at> gnu.org
:
bug#68415
; Package
guix
.
(Tue, 16 Jan 2024 12:45:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 68415 <at> debbugs.gnu.org (full text, mbox):
Sergey Trofimov <sarg <at> sarg.org.ru> writes:
> Feng Shu <tumashu <at> 163.com> writes:
>
>> After I guix pull, services defined in guix home config can no
>> start:
>>
>> -------------------------
>> 服务 root 已启动。
>> WARNING: Use of `load' in declarative module (#{ g117}#). Add
>> #:declarative? #f to your define-module invocation.
>> unbound-variable(#f "Unbound variable: ~S" (service) #f)
>>
>> Some deprecated features have been used. Set the environment
>> variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
>> program to get more information. Set it to "no" to suppress
>> this message.
>> Creating XDG user directories... done
>> Comparing
>> /gnu/store/bfkgfz1sm9q75jyn56pav2kmwl48i7w8-home/profile/share/fonts
>> and
>> /gnu/store/bfkgfz1sm9q75jyn56pav2kmwl48i7w8-home/profile/share/fonts...
>> done (same)
>> Evaluating on-change gexps.
>>
>> -----------
>>
>> When I run command: herd status, show error:
>>
>> feng <at> Guix ~$ herd status
>> error: connect: /run/user/1000/shepherd/socket: No such file or
>> directory
>
> Have you tried debugging it? Is your home shepherd running? Do you see
I tried, but I do not know why: unbound-variable service
The below code run have problem, and I think shepherd is not run, for
'ps aux |grep shepherd' can not found info.
(define xautolock-service
(shepherd-service
(provision '(xautolock))
(documentation "Run 'xautolock'")
(start #~(make-forkexec-constructor
(list #$(file-append xautolock "/bin/xautolock")
"-detectsleep")))
(stop #~(make-kill-destructor))))
...
(service
home-syncthing-service-type)
(service
home-shepherd-service-type
(home-shepherd-configuration
(shepherd shepherd)
(services
(list xautolock-service))))
> shepherd mentions in ~/.guix-home/on-first-login?
> Have you tried restarting your system?
Restart system no effect.
>
--
Information forwarded
to
bug-guix <at> gnu.org
:
bug#68415
; Package
guix
.
(Wed, 17 Jan 2024 07:15:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 68415 <at> debbugs.gnu.org (full text, mbox):
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))))
>
Information forwarded
to
bug-guix <at> gnu.org
:
bug#68415
; Package
guix
.
(Wed, 17 Jan 2024 12:57:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 68415 <at> debbugs.gnu.org (full text, mbox):
Sergey Trofimov <sarg <at> sarg.org.ru> writes:
Today, after I guix pull again and reconfig guix home, this problem
dispear, I do not know why :-)
> 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))))
>>
>
--
Reply sent
to
Ludovic Courtès <ludo <at> gnu.org>
:
You have taken responsibility.
(Sun, 31 Mar 2024 14:20:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Feng Shu <tumashu <at> 163.com>
:
bug acknowledged by developer.
(Sun, 31 Mar 2024 14:20:02 GMT)
Full text and
rfc822 format available.
Message #22 received at 68415-done <at> debbugs.gnu.org (full text, mbox):
Hi,
Feng Shu <tumashu <at> 163.com> skribis:
> Today, after I guix pull again and reconfig guix home, this problem
> dispear, I do not know why :-)
>
>> Feng Shu <tumashu <at> 163.com> writes:
[...]
>>> I tried, but I do not know why: unbound-variable service
I believe this problem was due to the fact that you were running
shepherd < 0.10.
Shepherd 0.10 introduce (service …) as a replacement for (make <service>
…) and Guix switched to that idiom in
477d4f7d241165b5a5fd315c27efd7803fad4a04, meaning that to complete your
upgrade, you effectively had to start the new shepherd (reboot or
whatever).
Closing!
Thanks,
Ludo’.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 29 Apr 2024 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 5 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.