Hello,

Simen Endsjø <contact@simendsjo.me> skribis:

>> Then please check precisely what hangs and what doesn’t.  You say “herd
>> status” hangs; what about “herd status X”, where X is a service defined
>> for your user shepherd?
>
> Not sure how I can find out precicely what hangs. Operations on
> individual services seems to work fine:
>
> $ herd status emacs-daemon
> ● Status of emacs-daemon:
>   It is running since Sat 11 Jan 2025 07:35:36 PM CET (13 hours ago).
>   # (... snip ...)

Can you try something like:

--8<---------------cut here---------------start------------->8---
for s in xss-lock volctl unclutter redshift picom \
  network-manager-applet dunst cbatticon blueman-applet \
  emacs-daemon ssh-agent dbus x11-display
do
  echo "trying $s"; herd status "$s"
done
--8<---------------cut here---------------end--------------->8---

to try and determine whether one of these is hanging?

If you don’t mind, could you share ~/.local/state/shepherd/shepherd.log,
privately if you prefer?  (Preferably remove everything that comes
before its last boot.)

>> Last, could you share the config file of your user shepherd, or maybe
>> the Guix Home config if that’s what you’re using?
>
> https://git.sr.ht/~simendsjo/dotfiles/tree/main/item/sijo/home/simendsjo/home-environment.scm

[...]

>          (xss-lock volctl unclutter redshift picom network-manager-applet dunst cbatticon blueman-applet emacs-daemon ssh-agent dbus x11-display))))

I checked these and the only one that looks fishy is ‘unclutter’, which
I would change like this: