unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mikhail Tsykalov <tsymsh@gmail.com>
To: 68057@debbugs.gnu.org
Subject: bug#68057: 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	[thread overview]
Message-ID: <3c55270c-0561-4573-875a-5bdbe346c3e8@gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 937 bytes --]

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.

[-- Attachment #1.2: Type: text/html, Size: 1392 bytes --]

[-- Attachment #2: test-config.scm --]
[-- Type: text/x-scheme, Size: 167 bytes --]

(use-modules (gnu home)
             (gnu services)
             (gnu home services shells))

(home-environment
 (services
  (list (service home-bash-service-type))))

             reply	other threads:[~2023-12-27 10:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-27 10:43 Mikhail Tsykalov [this message]
2024-09-30 19:09 ` bug#68057: i see the same when dropbear is the ssh server Attila Lendvai
2024-09-30 19:29 ` bug#68057: scratch that Attila Lendvai

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=3c55270c-0561-4573-875a-5bdbe346c3e8@gmail.com \
    --to=tsymsh@gmail.com \
    --cc=68057@debbugs.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).