Hello all,

In a recent home configuration, I added a service to automatically start the Emacs daemon. Afterwards, the shepherd.conf item in the store throws an exception and the system refuses to continue booting. The error disappears when I roll back to an older generation, and the shepherd socket is created but booting still doesn't continue and name resolution doesn't work, even after deleting resolv.conf and restarting NetworkManager multiple times. What can I do?

Thanks in advance,

Gábor Gerő


Reply via email to