From: Jack Hill <jackhill@jackhill.us>
To: sirgazil <sirgazil@zoho.com>
Cc: 39281 <39281@debbugs.gnu.org>
Subject: bug#39281: gdm doesn't start
Date: Sat, 25 Jan 2020 22:33:12 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.20.2001252227250.11123@marsh.hcoop.net> (raw)
In-Reply-To: <16fded63c2c.b2fb007833955.7928297236018515505@zoho.com>
I've started bisecting between my known bad and good commits.
Unfortunately, this will be a slow process both because my computer is
only so fast, and because rebooting to check a commit disrupts other work.
That said, why checking one of the bad commits, I noticed that the gdm
process was indeed started by shepherd and hadn't died, but it was not
making any progress for some reason. Running `sudo herd restart
xorg-server` caused it to bring up the gdm greater, and work normally.
I did notice the following in /var/log/gdm/greeter.log There was not
anything interesting in the xorg log. Unfortunately, I didn't think to
strace the gdm process before restarting it.
(EE)gnome-session-binary[837]: WARNING: Lost name on bus: org.gnome.SessionManager
(gsd-screensaver-proxy:927): GLib-GIO-WARNING **: 22:00:51.322: Error releasing name org.freedesktop.ScreenSaver: The connection is closed
(gsd-housekeeping:924): GLib-GIO-WARNING **: 22:00:51.322: Error releasing name org.gnome.SettingsDaemon.Housekeeping: The connection is closed
Fatal server error:
(EE) systemd-logind disappeared (stopped/restarted?)
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/lib/gdm/.local/share/xorg/Xorg.0.log" for additional information.
(EE)
(EE) systemd-logind: ReleaseControl failed: Connection was disconnected before a reply was received
(EE) Server terminated with error (1). Closing log file.
Gdk-Message: 22:00:51.636: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Gdk-Message: 22:00:51.636: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Gdk-Message: 22:00:51.636: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Gdk-Message: 22:00:51.636: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Gdk-Message: 22:00:51.636: .gnome-shell-real: Fatal IO error 4 (Interrupted system call) on X server :0.
Gdk-Message: 22:00:51.636: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Gdk-Message: 22:00:51.638: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
next prev parent reply other threads:[~2020-01-26 3:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 20:32 bug#39281: gdm doesn't start Jack Hill
2020-01-25 22:32 ` sirgazil via Bug reports for GNU Guix
2020-01-26 3:33 ` Jack Hill [this message]
[not found] <d65f5a5c54b87c11f535d6b3080e794c21dbedd6.camel@student.tugraz.at>
2020-01-27 2:26 ` Jack Hill
2020-01-27 3:30 ` Raghav Gururajan
2020-01-27 4:50 ` Jack Hill
2020-01-27 5:24 ` 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
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.2001252227250.11123@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=39281@debbugs.gnu.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).