From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 44944-done@debbugs.gnu.org
Subject: bug#44944: Unable to log into X session via gdm
Date: Fri, 16 Sep 2022 17:03:50 -0400 [thread overview]
Message-ID: <87k063jakp.fsf@gmail.com> (raw)
In-Reply-To: <8735crdu0p.fsf@gmail.com> (Maxim Cournoyer's message of "Fri, 16 Sep 2022 15:00:22 -0400")
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
[...]
> /var/lib/gdm/.local/share/xorg:
> total 132
> drwxr-xr-x 1 nixbld04 opendht 96 Dec 8 2021 .
> drwxr-xr-x 1 nixbld04 opendht 72 Dec 7 2021 ..
> -rw-r--r-- 1 nixbld04 opendht 52932 Dec 8 2021 Xorg.0.log
> -rw-r--r-- 1 nixbld04 opendht 53878 Dec 8 2021 Xorg.0.log.old
> -rw-r--r-- 1 nixbld04 opendht 10481 Dec 8 2021 Xorg.1.log
> -rw-r--r-- 1 nixbld04 opendht 10481 Dec 8 2021 Xorg.1.log.old
>
> We have some logic in %gdm-activation that was supposed to fix that, but
> it doesn't kick in, because it has some optimization to not recurse if
> the top dir has the correct permissions, and since d429878daf3 the top
> directory permissions are always controlled at system activation time
> (and this must happen before the gdm activation script runs).
>
> I'll follow-up with a patch that puts /var/lib/gdm on a tmpfs. This
> should avoid many pitfalls people have had.
Pushed as d7e56aebec.
This should fix the issue for good!
Closing.
Maxim
next prev parent reply other threads:[~2022-09-16 21:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 13:02 bug#44944: Unable to log into X session via gdm Danny Milosavljevic
2020-11-29 17:00 ` Marius Bakke
2020-11-29 21:20 ` Danny Milosavljevic
2022-09-16 19:00 ` Maxim Cournoyer
2022-09-16 21:03 ` Maxim Cournoyer [this message]
2022-09-20 14:49 ` bokr
2022-09-22 4:11 ` Maxim Cournoyer
2022-09-25 11:47 ` Maxime Devos
2022-09-27 0:12 ` Maxim Cournoyer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k063jakp.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=44944-done@debbugs.gnu.org \
--cc=dannym@scratchpost.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.