GNOME Bugzilla – Bug 728658
GDM fails to start after upgrade to 3.12.1-2
Last modified: 2018-05-24 11:01:56 UTC
This started happening yesterday, when Arch upgraded gdm from 3.12.1-1 to 3.12.1-2. Several services started taking way longer than normal to start (NetworkManager was over 90 seconds, gdm was about 30, etc.) and then I would fail to get to my login screen and would be forced to switch to a VT and reboot. This didn't happen every boot but would seemingly come in "spurts" where several boots in a row would fail and then several would succeed (well, it techically booted, I just couldn't reach gdm, but you get the point). There were some error messages in the journal I'll paste below that seemed to come from elsewhere, but the problem is seemingly with gdm since it was upgraded the boot before this started happening and downgrading it seemed to fix it. My whole dmesg output from a failed boot is at http://pastebin.com/0EESybyP, but the lines I think are relevant (or at least seemed abnormal) are 859-864, which read [ 36.633579] systemd[1]: Failed to register name: Connection timed out [ 36.646908] systemd[1]: Failed to set up API bus: Connection timed out [ 46.632649] systemd-logind[408]: Failed to enable subscription: Connection timed out [ 56.644949] systemd-logind[408]: Failed to fully start up daemon: Connection timed out [ 56.685097] systemd[1]: Unit systemd-logind.service entered failed state. [ 56.698424] systemd[1]: systemd-logind.service has no holdoff time, scheduling restart. Also, the gdm, avahi, systemd-journald, org.freedesktop.Accounts, and bluez systemd units all failed to start. The only Google results I got for the dmesg errors were from dbus.c in systemd, but unless gdm somehow exposed an earlier bug in systemd, I don't see how that could be the root cause since that wasn't upgraded before this started happening.
(In reply to comment #0) > This started happening yesterday, when Arch upgraded gdm from 3.12.1-1 to > 3.12.1-2 Did you report this to Arch? Where to see the diff between these two versions?
https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/gdm&id=6563c530e2a6092e939aafa5ab535e059ff127f4
(In reply to comment #1) > (In reply to comment #0) > > This started happening yesterday, when Arch upgraded gdm from 3.12.1-1 to > > 3.12.1-2 > > Did you report this to Arch? > Where to see the diff between these two versions? I just did that. Wasn't sure where it would go first; reading Arch's guidelines it seemed like it should be reported upstream. Apologies if I screw anything up; this is my first time actually reporting a bug to any kind of project like this. And it looks like someone else already posted the diff.
Just found out that systemd keeps core dumps in the journal--here's one from the most recent time gdm crashed (too big for an attachment): http://b.armory.com/~smikims/gdm.dump. I've got about a dozen more like it if you want to see another.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/193.