From: Jack Hill <jackhill@jackhill.us>
To: Leo Prikler <leo.prikler@student.tugraz.at>,
39281@debbugs.gnu.org,
Raghav Gururajan <raghavgururajan@disroot.org>
Cc: sirgazil@zoho.com
Subject: bug#39281: gdm doesn't start
Date: Sun, 26 Jan 2020 21:26:03 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.20.2001262111550.11123@marsh.hcoop.net> (raw)
In-Reply-To: <d65f5a5c54b87c11f535d6b3080e794c21dbedd6.camel@student.tugraz.at>
According to my git bisect, d36fa50fbf8169018193774782fd21f1b13b9c0e [0]
is the culprit. It makes some sense that the commit is gnome-related, but
I have no idea why adding more packages to the environment should cause
gdm to fail to run properly. Therefore, I am inclined to believe that it is
a weird timing issue as Leo suspects.
[0] http://git.savannah.gnu.org/cgit/guix.git/commit/?id=d36fa50fbf8169018193774782fd21f1b13b9c0e
On Sun, 26 Jan 2020, Leo Prikler wrote:
> I saw the same warnings on one of my systems as well, but it boots
> fine. On another one, the same behaviour occurs, but GDM can be
> started manually by restarting xorg-server from a TTY. Note, that I
> can not do so from an SSH remote, because SSH fails to start in a
> similar manner.
My system does indeed have a really slow disk, so perhaps this makes the
problem more likely to happen. Obviously, it would be nice if gdm started
correctly, but in a bigger picture, it would be nice if shepherd had a
better way of dealing with misbehaving services. For example, if shepherd
know how to check the health of a service and restarted it wasn't
responding correctly.
I don't know where to go from here. Hopefully someone more knowledgeable
about gnome and gdm can help us out.
Best,
Jack
next parent reply other threads:[~2020-01-27 2:27 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 ` Jack Hill [this message]
2020-01-27 3:30 ` bug#39281: gdm doesn't start 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
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.2001262111550.11123@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=39281@debbugs.gnu.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).