Guix Home: Multiple instances of user Shepherd created

  • Open
  • quality assurance status badge
Details
3 participants
  • Julian Flake
  • Julian Flake
  • xeji
Owner
unassigned
Submitted by
xeji
Severity
important
Merged with
X
X
xeji wrote on 16 Dec 2023 23:42
(name . bug-guix@gnu.org)(address . bug-guix@gnu.org)
835991647.70407.1702766524281@office.mailbox.org
I am trying to use the awesome Guix Home Shepherd service for syncthing (home-syncthing-service-type).
Syncthing works fine but every time I log out of my last user session and log back in again, a new instance of the user shepherd is started (and tries to start syncthing again).
After logging out and in a few times, there are multiple user shepherd processes.
Suspected cause: Apparently the user shepherd process is not killed on last logout before elogind (correctly) removes XDG_RUNTIME_DIR.
So on next login, a new empty XDG_RUNTIME_DIR is created, causing a new user shepherd to be started while the old one is still running happily.
This seems to be a general issue and not particular to the syncthing home service.
System: Guix System on x86_64
Guix commit: ac61e9705fb8c450c6cd0c1731fbb1b909c1f944
--
Uli
Attachment: file
J
J
Julian Flake wrote on 2 Dec 2024 21:48
(address . 67863@debbugs.gnu.org)(address . xeji@cat3.de)
871pypx14c.fsf@flake.de
Hi,

I'm observing exactly the same. Were you able to solve your issue,
meanwhile?

Best Regards,
Julian (nutcase)
J
J
Julian Flake wrote 6 days ago
merge 67863 74912
(name . GNU bug tracker automated control server)(address . control@debbugs.gnu.org)
87bjwdaue5.fsf@uni-koblenz.de
severity 67863 important
merge 67863 74912
thankyou
-----BEGIN PGP SIGNATURE-----

iHMEAREKADMWIQSZos45zYG9CgQjO52pmOo730U57wUCZ4LoohUcZmxha2VAdW5p
LWtvYmxlbnouZGUACgkQqZjqO99FOe9yMwCghxsw9H0nubbMjU6XC2JYELZ4VRAA
niOvwWBqYBCAQhaBbAy2kFqhXuWl
=QKlJ
-----END PGP SIGNATURE-----

?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 67863@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 67863
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch