Hi Ludo,
I tried replicating this issue on guix
d67e4f0f9b10c7ddac8fb0ca68cbf1d6ad0a6e5d and was not able to. My guess
is either shepherd 10.2->10.3 resolved the issue or there was a change in
fish.
It seems to work fine now, but I've not tested thoroughly. Hopefully
anyone else who can into the
Hi Richard and all,
Richard Sent skribis:
> However, when fish is in charge of executing on-first-login, stdout and
> stderr for the user shepherd get directed to a pipe instead of
> /dev/null.
>
> fish fds, both stdout and stderr point to a pipe:
>
> $ ls -l /proc//fd)
> lr-x-- 1 richar
Did some more testing and I was able to find a workaround for my version
of this issue, although I don't know if it'll solve it for others. TL;DR
is I changed my login shell from fish back to bash.
The system configuration for the nonworking machine was using fish
`(user-account (shell (file-a
Just throwing out that I'm also experiencing this issue, even with a
home configuration containing a single service, that being
home-gpg-agent-service. I've deployed the same configuration on two
different machines at the same checkout and only experience the issue on
one. The other machine wor
I experience the same thing. I hadn't updated guix since may (last generation
was commit 91bfd30ee3f35dfb7048bf42aea92f939cffbf17), and since I did I'm
encountering issues with shepherd.
Probably unrelated, but for the record: my first issue was caused by the disappearance of the
XDG_LOG_HOME
Hi Guix,
I think this has been happening for quite a long time, but I never paid
attention to it, for everything seemed to be running just fine.
When I run `guix home reconfigure`, it completes with the following message:
```
# […]
Finished updating symlinks.
SSLoading /gnu/store/zbfyaxxigns5lqy
