~abcdw/rde#3: 
Shepherd doesn't start without elogind session

As discussed in the thread:

Shepherd doesn't want to start if there is no elogind session. According to source code [fn:1], it ensures that /run/user/$UID/shepherd exists, but for some reason it still fails with:

error: connect: /run/user/1000/shepherd/socket: No such file or directory
  • Reproduce, investigate and fix this behavior.
  • Check if guix home works on non-elogind/non-systemd systems.

#Footnotes

[fn:1] modules/shepherd.scm

-- Best regards, Andrew Tropin

Status
RESOLVED FIXED
Submitter
~abcdw
Assigned to
No-one
Submitted
2 months ago
Updated
a month ago
Labels
No labels applied.

~abcdw REPORTED FIXED a month ago

Problem was different. On first reconfigure, on-first-login script is not evaluated -> shepherd isn't started, the error above appears. Fixed by starting shepherd on reconfigure if it's not started yet.

Register here or Log in to comment, or comment via email.