all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tanguy Le Carrour <tanguy@bioneland.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Problem logging in using GDM
Date: Mon, 21 Oct 2019 09:03:48 +0200	[thread overview]
Message-ID: <20191021070348.73mgi2lqsylb2heq@rafflesia> (raw)
In-Reply-To: <87pnisjvu7.fsf@elephly.net>

Hi Ricardo!


Le 10/19, Ricardo Wurmus a écrit :
> The question here is: is it a failure of GDM or gnome-shell?  The exact
> point where GDM starts gnome-shell is hard to pin-point, of course, but
> the logs (even those on TTY1, Ctrl-Alt-F1) might tell you something
> about whether it is gnome-shell that is crashing or if it doesn’t even
> get that far.

I don't use gnome-shell, but bspwm, so I guess it is a pure gdm problem.
The fact that it works with slim seems to confirm this.

"Funny" thing, I have 2 different problems!

At home, GDM does not even start. I just see the mouse pointer on the
TTY. Nothing really informative in the logs. Just an endless succession
of "New session c1 of user gdm […] closing session […] New session c2 of
user gdm […]".

At work, I can see the GDM screen, but when I provide my
username/password nothing happens.

I'll try to update my laptop at the WE. Hope I won't end up with yet
another variation of the problem! ^_^'

If I have some meaningful logs, I'll post them here.

-- 
Tanguy

      parent reply	other threads:[~2019-10-21  7:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 16:31 Problem logging in using GDM Tanguy Le Carrour
2019-10-19 14:18 ` Joshua Branson
2019-10-21  7:14   ` Tanguy Le Carrour
2019-10-19 20:29 ` pelzflorian (Florian Pelz)
2019-10-19 20:58 ` Ricardo Wurmus
2019-10-19 21:24   ` pelzflorian (Florian Pelz)
2019-10-21  7:03   ` Tanguy Le Carrour [this message]

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=20191021070348.73mgi2lqsylb2heq@rafflesia \
    --to=tanguy@bioneland.org \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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.