GNU bug report logs - #68057
home container: XDG_RUNTIME_DIR doesn't exists, on-first-login script won't execute anything.

Previous Next

To reply to this bug, email your comments to 68057 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Mikhail Tsykalov <tsymsh <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: home container: XDG_RUNTIME_DIR doesn't exists, on-first-login script
 won't execute anything.
Date: Wed, 27 Dec 2023 13:43:19 +0300

[Message part 1 (text/plain, inline)]

When running "guix home container test-config.scm" (attached) the 
following warning appears on screen:

warning: XDG_RUNTIME_DIR doesn't exists, on-first-login script
won't execute anything.  You can check if xdg runtime directory exists,
XDG_RUNTIME_DIR variable is set to appropriate value and manually execute the
script by running '$HOME/.guix-home/on-first-login'

I don't know if on-first-login does anything useful when run in the 
container, but the warning looks scary.

A lot of users don't hit it because they run shepherd which creates 
XDG_RUNTIME_DIR in the process of creating a command socket.

I think that "guix home container" should create XDG_RUNTIME_DIR by 
itself, since there is no logind in the container.

This warning was discussed before in https://issues.guix.gnu.org/56758.

There was also this IRC discussion 
https://logs.guix.gnu.org/guix/2023-12-27.log#083824 that prompted me to 
file this bugreport.

[Message part 2 (text/html, inline)]

[test-config.scm (text/x-scheme, attachment)]

Message #8 received at 68057 <at> debbugs.gnu.org (full text, mbox):

From: Attila Lendvai <attila <at> lendvai.name>
To: "68057 <at> debbugs.gnu.org" <68057 <at> debbugs.gnu.org>
Subject: i see the same when dropbear is the ssh server
Date: Mon, 30 Sep 2024 19:09:44 +0000

my issue and this one may have the same root cause. my suspicion is that in both contexts some kind of integration is not triggering elogind (?) to create that directory.

my issue: i switched from openssh to dropbear (after their latest blunder), and after that i started to see this warning when i log into my servers through ssh (i.e. no local login from their consoles, only through ssh).

my root symptom was that emacs-tramp stopped working right after the switch.

apparently, it was due to a missing newline at the end of this warning that derailed tramp's prompt detection (fixed by https://git.savannah.gnu.org/cgit/guix.git/commit/?id=cbf46d2565112180fe7b316b2530293ed2d3acf3).

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“You will never know if someone is an asshole until he becomes rich.”
	— Nassim Taleb (1960–)

Message #11 received at 68057 <at> debbugs.gnu.org (full text, mbox):

From: Attila Lendvai <attila <at> lendvai.name>
To: "68057 <at> debbugs.gnu.org" <68057 <at> debbugs.gnu.org>
Subject: scratch that
Date: Mon, 30 Sep 2024 19:29:18 +0000

> since there is no logind in the container

err, i should have paid more attention.

maybe my issue is not that closely related to this one.

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
God give me grace to accept with serenity the things that can not be changed,
the Courage to change the things which should be changed,
and the Wisdom to distinguish the one from the other.
	— The Serenity Prayer

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.