From: dan <i@dan.games>
To: "(" <paren@disroot.org>, 59132@debbugs.gnu.org
Subject: [bug#59132] [PATCH] system: images: wsl2: Create $XDG_RUNTIME_DIR on first login.
Date: Wed, 9 Nov 2022 12:26:12 +0800 [thread overview]
Message-ID: <031d4167-c217-06f7-2ea2-801781ab41c6@dan.games> (raw)
In-Reply-To: <CO773WJBB1O3.1VGM0YVMCG3OO@guix-framework>
On 11/9/2022 4:27 AM, ( wrote:
> elogind/seatd are tasked with setting up login sessions, which includes creating
> XDG_RUNTIME_DIR. They probably do work on WSL, since I'm pretty sure desktops do?
i tried the following things:
adding `(syslog-service)' and `(service elogind-service-type)' to the
operating-system's service list. and when i login to wsl, it shows the
following error:
> sudo: pam_open_session: Error in service module
> sudo: policy plugin failed session initialization
also tried seatd, by adding `(udev-service)' and `(service
seatd-service-type)' to the service list. and when logging in, it shows:
> 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'
normally, when logging into wsl, users don't need to type their
password. i'm not sure if it related to the issue, but it might perform
differently with a normal linux distro.
--
dan
next prev parent reply other threads:[~2022-11-09 4:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 20:05 [bug#59132] [PATCH] system: images: wsl2: Create $XDG_RUNTIME_DIR on first login dan
2022-11-08 20:11 ` ( via Guix-patches via
2022-11-08 20:23 ` dan
2022-11-08 20:27 ` ( via Guix-patches via
2022-11-09 4:26 ` dan [this message]
2022-11-09 7:24 ` dan
2022-11-08 20:27 ` ( via Guix-patches via
2022-11-09 12:26 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-09 13:48 ` dan
2022-11-18 14:00 ` Ludovic Courtès
2022-12-26 8:36 ` bug#59132: " Mathieu Othacehe
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=031d4167-c217-06f7-2ea2-801781ab41c6@dan.games \
--to=i@dan.games \
--cc=59132@debbugs.gnu.org \
--cc=paren@disroot.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).