From: Xinglu Chen <public@yoctocell.xyz>
To: Jan Nieuwenhuizen <janneke@gnu.org>, 50945@debbugs.gnu.org
Cc: Andrew Tropin <andrew@trop.in>
Subject: bug#50945: Guix home: No such file or directory: "/run/user/1003/on-first-login-executed"
Date: Fri, 01 Oct 2021 19:05:40 +0200 [thread overview]
Message-ID: <87ilygllp7.fsf@yoctocell.xyz> (raw)
In-Reply-To: <87y27czr0v.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
On Fri, Oct 01 2021, Jan Nieuwenhuizen wrote:
> Hi,
>
> When using su or sudo to enter an account managed by guix home, I get
> this error
>
> --8<---------------cut here---------------start------------->8---
> Backtrace:
> 2 (primitive-load "/home/guix/.guix-home/on-first-login")
> In ice-9/ports.scm:
> 461:11 1 (call-with-output-file "/run/user/1003/on-first-login-…" …)
> In unknown file:
> 0 (open-file "/run/user/1003/on-first-login-executed" "w" …)
>
> ERROR: In procedure open-file:
> In procedure open-file: No such file or directory: "/run/user/1003/on-first-login-executed"
> --8<---------------cut here---------------end--------------->8---
>
> Upon a console login or ssh login, /var/run/1003 is created and all is fine.
>
> See below for the scenario, home-minimal.scm is attached.
>
> Greetings,
> Janneke
[ Cc Andrew who did most of the work on Guix Home ]
I think this is because Guix Home relies on $XDG_RUNTIME_DIR to be
defined, otherwise it falls-back to /run/user/UID. But it looks like
/run/user/UID isn’t created when using ‘su’ to login. I don’t really
know how these things work under the hood; maybe using $XDG_RUNTIME_DIR
isn’t best idea.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2021-10-01 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 15:46 bug#50945: Guix home: No such file or directory: "/run/user/1003/on-first-login-executed" Jan Nieuwenhuizen
2021-10-01 17:05 ` Xinglu Chen [this message]
2021-10-07 5:21 ` Andrew Tropin
2021-11-05 16:58 ` Xinglu Chen
2021-11-08 9:24 ` Andrew Tropin
2021-11-14 22:11 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilygllp7.fsf@yoctocell.xyz \
--to=public@yoctocell.xyz \
--cc=50945@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=janneke@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).