After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 789720 - GDM 3.26.2 freezes system when run
GDM 3.26.2 freezes system when run
Status: RESOLVED DUPLICATE of bug 789722
Product: gdm
Classification: Core
Component: general
3.26.x
Other Linux
: Normal blocker
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2017-10-31 16:41 UTC by Chad Rodrigue
Modified: 2017-11-01 20:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Chad Rodrigue 2017-10-31 16:41:20 UTC 
Supplimentary threads: https://bbs.archlinux.org/viewtopic.php?id=231381, and https://bugs.archlinux.org/task/56172

On a system with wayland disabled and the nVidia binary blob, I ran a system upgrade, which upgraded gdm and libgdm to 3.26.2.  When I rebooted, my system was frozen... could not even ctrl+alt+f2.  I had to boot into systemctl rescue mode and disable GDM.  StartX with Gnome-shell worked fine from there.  Downgrading gdm to 3.26.1 allows me to use GDM again.  

It is speculated that the new version is somehow ignoring waylanddisable in /etc/gdm/custom.conf.  The Arch forum thread above does a more-than-decent job of tracking down the commit that appears to be causing the problem.  The bug report linked above has a journal log from a user experiencing the problem with gdm debug enabled.

Between those two sources, there should be enough information to do something.

I marked this "blocker" because a desktop manager freezing a system seems like quite a high priority thing.
Comment 1 Chad Rodrigue 2017-11-01 20:41:37 UTC 
Looks like it's already been reported and fixed.  Wow.  Marking as a duplicate.

*** This bug has been marked as a duplicate of bug 789722 ***