From: Danny Milosavljevic <dannym@scratchpost.org>
To: Marius Bakke <marius@gnu.org>
Cc: 44944@debbugs.gnu.org
Subject: bug#44944: Unable to log into X session via gdm
Date: Sun, 29 Nov 2020 22:20:20 +0100 [thread overview]
Message-ID: <20201129222020.7a804daa@scratchpost.org> (raw)
In-Reply-To: <87blfg14jn.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
Hi,
On Sun, 29 Nov 2020 18:00:44 +0100
Marius Bakke <marius@gnu.org> wrote:
> Danny Milosavljevic <dannym@scratchpost.org> skriver:
>
> > The latest guix system reconfigure (of yesterday) left me unable to login into
> > my X session. guix system rollback DID NOT fix it.
> >
> > I would enter my password and it would "try" to login and return right back to
> > the gdm login screen.
>
> Can you find any clues in the log files as to why this happened?
I did check, but there were not really good clues in the logs, among other
things because it seemed that ~/.xsession-errors did not get updated. ls
did report that ~/.xsession-errors belongs to me, but it still didn't update
it, which is why I then removed it. But I only did that after removing gdm
as well, so I don't know whether removing gdm or removing ~/.xsession-errors
or both fixed it.
Checking the logs again, I have only this interesting line:
>Nov 29 04:24:26 localhost gdm: GdmDisplay: Session never registered, failing
> Did you reboot after reconfiguring?
I had selected the older system generation in the grub boot menu.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-11-29 21:21 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 [this message]
2022-09-16 19:00 ` Maxim Cournoyer
2022-09-16 21:03 ` Maxim Cournoyer
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=20201129222020.7a804daa@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=44944@debbugs.gnu.org \
--cc=marius@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 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.