unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jack Hill <jackhill@jackhill.us>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Raghav Gururajan <raghavgururajan@disroot.org>,
	sirgazil <sirgazil@zoho.com>, 39281 <39281@debbugs.gnu.org>,
	Leo Prikler <leo.prikler@student.tugraz.at>
Subject: bug#39281: gdm doesn't start
Date: Mon, 27 Jan 2020 16:06:49 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.20.2001271603130.11123@marsh.hcoop.net> (raw)
In-Reply-To: <20200127212434.1738de43@scratchpost.org>

On Mon, 27 Jan 2020, Danny Milosavljevic wrote:

> Hi,
>
> hmm, if you want to find out whether we could fix it, could you invoke:
>
> useradd gnome-initial-setup

I added gnome-initial-setup to my operating system config and reconfigured 
with 94600c3960d7e2f12a3a9b6d2ed0d98ddacdd055 (the commit before you 
appled the patch).

This did not solve the problem for me.

However, the following messages on the console (presumably from logind):

new session c1 for user gnome-initial-setup

followed a little while later by

removed session c1.

During a successful boot, I see

new session c1 for user gdm

followed by the gdm login screen appearing.

Best,
Jack

  reply	other threads:[~2020-01-27 21:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d65f5a5c54b87c11f535d6b3080e794c21dbedd6.camel@student.tugraz.at>
2020-01-27  2:26 ` bug#39281: gdm doesn't start Jack Hill
2020-01-27  3:30 ` Raghav Gururajan
2020-01-27  4:50   ` Jack Hill
2020-01-27  4:52     ` bug#39281: [PATCH] gnu: gnome: don't propagate gnome-initial-setup Jack Hill
2020-01-27  5:24     ` bug#39281: gdm doesn't start Leo Prikler
2020-01-28  9:37       ` Leo Prikler
2020-01-28 18:03         ` Jack Hill
2020-01-28 18:18           ` sirgazil via Bug reports for GNU Guix
2020-01-28 18:21             ` Jack Hill
2020-01-28 18:26               ` sirgazil via Bug reports for GNU Guix
2020-01-28 20:11         ` Danny Milosavljevic
2020-01-27  8:51   ` Raghav Gururajan
2020-01-27 19:08     ` Jack Hill
2020-01-27 19:54       ` sirgazil via Bug reports for GNU Guix
2020-01-27 20:13         ` Jack Hill
2020-01-27 20:24         ` Danny Milosavljevic
2020-01-27 21:06           ` Jack Hill [this message]
2020-01-27 20:29         ` Danny Milosavljevic
2020-01-27 22:07           ` sirgazil via Bug reports for GNU Guix
2020-01-28  5:21     ` Raghav Gururajan
2020-01-25 20:32 Jack Hill
2020-01-25 22:32 ` sirgazil via Bug reports for GNU Guix
2020-01-26  3:33   ` Jack Hill

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=alpine.DEB.2.20.2001271603130.11123@marsh.hcoop.net \
    --to=jackhill@jackhill.us \
    --cc=39281@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    --cc=leo.prikler@student.tugraz.at \
    --cc=raghavgururajan@disroot.org \
    --cc=sirgazil@zoho.com \
    /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).