From: Timothy Sample <samplet@ngyro.com>
To: Jan <tona_kosmicznego_smiecia@interia.pl>
Cc: 37423@debbugs.gnu.org
Subject: bug#37423: Changing the login service from GDM to SLiM and then back to GDM causes a really bad loop
Date: Tue, 17 Sep 2019 00:45:58 -0400 [thread overview]
Message-ID: <871rwf5y49.fsf@ngyro.com> (raw)
In-Reply-To: <20190916005154.41b74430@interia.pl> (Jan's message of "Mon, 16 Sep 2019 00:51:54 +0200")
Hi Jan,
Jan <tona_kosmicznego_smiecia@interia.pl> writes:
> Hi.
>
> Changing the login service from GDM to SLiM and then back to GDM makes
> GDM to loop like this:
> "New session c1 of user gdm."
> "Removed session c1."
> "New session c2 of user gdm."
> "Removed session c2."
> ...
>
> And it continues like this to relatively high numbers like c167. Didn't
> check how far it could go, but that's not important anyway.
> Reverting to the previous definition of the system by using
> "guix system switch-generation" or using grub menu entries doesn't help,
> changing /etc/config.scm back to the default gdm configuration and
> running
> "guix system reconfigure" doesn't help either.
Could this be the same issue as <https://bugs.gnu.org/36508>? In short,
Guix doesn’t guarantee that the “gdm” user will have the same UID if it
gets deleted and recreated (which happens when you remove the GDM
service and add it again). You can fix this by ensuring the owner of
the files under “/var/lib/gdm” is the current “gdm” user.
-- Tim
next prev parent reply other threads:[~2019-09-17 4:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 22:51 bug#37423: Changing the login service from GDM to SLiM and then back to GDM causes a really bad loop Jan
2019-09-17 4:45 ` Timothy Sample [this message]
2019-09-17 11:16 ` Jan
2019-09-19 21:22 ` Ludovic Courtès
2019-09-19 21:47 ` Gábor Boskovits
2019-09-20 9:40 ` Ludovic Courtès
2019-09-20 11:03 ` Julien Lepiller
2019-09-20 13:25 ` Timothy Sample
2019-09-20 21:10 ` Ludovic Courtès
2019-09-19 22:00 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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=871rwf5y49.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=37423@debbugs.gnu.org \
--cc=tona_kosmicznego_smiecia@interia.pl \
/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).