FS#56190 - GDM 3.26.2.1-1 - frozen system on boot

Attached to Project: Arch Linux
Opened by wzrd tales (wzrdtales) - Tuesday, 31 October 2017, 23:50 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 01 November 2017, 10:54 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

GDM broke on the latest version and freezes the system on boot. This breaks the whole system unless you switch to tty early enough before gdm gets active.

Additional info:
* 3.26.2.1-1


Logs:

Okt 31 17:35:53 tmdsl systemd[1]: Stopping GNOME Display Manager...
Okt 31 17:35:53 tmdsl gdm[672]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Okt 31 17:35:53 tmdsl gdm[672]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
Okt 31 17:35:53 tmdsl systemd[1]: Stopped GNOME Display Manager.
Okt 31 17:35:53 tmdsl systemd[1]: Starting GNOME Display Manager...
Okt 31 17:35:53 tmdsl systemd[1]: Started GNOME Display Manager.
Okt 31 17:35:54 tmdsl gdm[15295]: GdmDisplay: display lasted 0,767353 seconds
Okt 31 17:35:54 tmdsl gdm[15295]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Okt 31 17:35:54 tmdsl gdm[15295]: Child process -15309 was already dead.
Okt 31 17:35:54 tmdsl gdm[15295]: Child process 15298 was already dead.
Okt 31 17:35:54 tmdsl gdm[15295]: Unable to kill session worker process
Okt 31 17:35:54 tmdsl gdm[15295]: GdmDisplay: display lasted 0,460841 seconds
Okt 31 17:35:54 tmdsl gdm[15295]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Okt 31 17:35:54 tmdsl gdm[15295]: Child process -15338 was already dead.
Okt 31 17:35:54 tmdsl gdm[15295]: Child process 15325 was already dead.
Okt 31 17:35:54 tmdsl gdm[15295]: Unable to kill session worker process
Okt 31 17:35:55 tmdsl gdm[15295]: GdmDisplay: display lasted 0,504183 seconds
Okt 31 17:35:55 tmdsl gdm[15295]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Okt 31 17:35:55 tmdsl gdm[15295]: Child process -15432 was already dead.
Okt 31 17:35:55 tmdsl gdm[15295]: Child process 15421 was already dead.
Okt 31 17:35:55 tmdsl gdm[15295]: Unable to kill session worker process
Okt 31 17:35:55 tmdsl gdm[15295]: GdmDisplay: display lasted 0,626485 seconds
Okt 31 17:35:55 tmdsl gdm[15295]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Okt 31 17:35:55 tmdsl gdm[15295]: Child process -15527 was already dead.
Okt 31 17:35:55 tmdsl gdm[15295]: Child process 15515 was already dead.
Okt 31 17:35:55 tmdsl gdm[15295]: Unable to kill session worker process
Okt 31 17:35:56 tmdsl gdm[15295]: GdmDisplay: display lasted 0,588235 seconds
Okt 31 17:35:56 tmdsl gdm[15295]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Okt 31 17:35:56 tmdsl gdm[15295]: Child process -15618 was already dead.
Okt 31 17:35:56 tmdsl gdm[15295]: Child process 15607 was already dead.
Okt 31 17:35:56 tmdsl gdm[15295]: Unable to kill session worker process
Okt 31 17:35:56 tmdsl gdm[15295]: GdmDisplay: display lasted 0,516076 seconds
Okt 31 17:35:56 tmdsl gdm[15295]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Okt 31 17:35:56 tmdsl gdm[15295]: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors
Okt 31 17:35:56 tmdsl gdm[15295]: Child process -15710 was already dead.
Okt 31 17:35:56 tmdsl gdm[15295]: Child process 15699 was already dead.
Okt 31 17:35:56 tmdsl gdm[15295]: Unable to kill session worker process
Okt 31 17:36:08 tmdsl systemd[1]: Stopping GNOME Display Manager...
Okt 31 17:36:08 tmdsl systemd[1]: Stopped GNOME Display Manager.



Steps to reproduce:

Upgrade gdm to 3.26.2.1-1, reboot.

Steps to fix the issue:

Downgrade to 3.26.1-1.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 01 November 2017, 10:54 GMT
Reason for closing:  Fixed
Comment by wzrd tales (wzrdtales) - Tuesday, 31 October 2017, 23:51 GMT
Some additional infos:

Graphics Drivers:
nvidia-dkms
Comment by Barakah Al Rashedi (barakah) - Wednesday, 01 November 2017, 06:37 GMT
I have same issue yesterday after upgraded GDM ([2017-10-31 12:38] [ALPM] upgraded gdm (3.26.1-1 -> 3.26.2-1)). booting process got stuck on GDM and even can't access tty, I have used archlinux live usb to downgrade GDM and it's working fine now.

it's take me long time to figure it's GDM issue.
[2017-10-31 20:05] [ALPM] downgraded gdm (3.26.2-1 -> 3.26.1-1)

Some additional infos:
Dell laptop with NVIDIA Optimus
01:00.0 VGA compatible controller: NVIDIA Corporation GK106M [GeForce GTX 765M] (rev a1)
Subsystem: Dell GK106M [GeForce GTX 765M]
Kernel driver in use: nvidia



-- Reboot --
Oct 31 14:55:02 alienware systemd[1]: Starting GNOME Display Manager...
Oct 31 14:55:02 alienware systemd[1]: Started GNOME Display Manager.
Oct 31 14:55:02 alienware gdm[507]: GdmDisplay: display lasted 0.336518 seconds
Oct 31 14:55:02 alienware gdm[507]: Child process -581 was already dead.
Oct 31 14:55:02 alienware gdm[507]: Child process 570 was already dead.
Oct 31 14:55:02 alienware gdm[507]: Unable to kill session worker process
Oct 31 14:55:03 alienware gdm[507]: GdmDisplay: display lasted 0.282976 seconds
Oct 31 14:55:03 alienware gdm[507]: Child process 598 was already dead.
Oct 31 14:55:03 alienware gdm[507]: Unable to kill session worker process
Oct 31 14:55:03 alienware gdm[507]: GdmDisplay: display lasted 0.288090 seconds
Oct 31 14:55:03 alienware gdm[507]: Child process 693 was already dead.
Oct 31 14:55:03 alienware gdm[507]: Unable to kill session worker process
Oct 31 14:55:03 alienware gdm[507]: GdmDisplay: display lasted 0.297485 seconds
Oct 31 14:55:03 alienware gdm[507]: Child process 788 was already dead.
Oct 31 14:55:03 alienware gdm[507]: Unable to kill session worker process
Oct 31 14:55:03 alienware gdm[507]: GdmDisplay: display lasted 0.269873 seconds
Oct 31 14:55:03 alienware gdm[507]: Child process 880 was already dead.
Oct 31 14:55:03 alienware gdm[507]: Unable to kill session worker process
Oct 31 14:55:04 alienware gdm[507]: GdmDisplay: display lasted 0.279945 seconds
Oct 31 14:55:04 alienware gdm[507]: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server
Oct 31 16:15:25 alienware systemd[1]: Stopping GNOME Display Manager...
Oct 31 16:15:25 alienware systemd[1]: Stopped GNOME Display Manager.
-- Reboot --
Comment by Marek (mbar) - Wednesday, 01 November 2017, 07:07 GMT
Same here on Asus UX303UB (Nvidia Optimus). Blank screen with GDM error in the log.
Comment by Jan de Groot (JGC) - Wednesday, 01 November 2017, 08:42 GMT
3.26.2-1 is buggy, use 3.26.2.1-1. I think the original reporter also has 3.26.2-1 installed instead.
Comment by wzrd tales (wzrdtales) - Wednesday, 01 November 2017, 10:19 GMT
Seems like it is fixed now, tried the update today again.

Comment by wzrd tales (wzrdtales) - Wednesday, 01 November 2017, 10:20 GMT
[2017-10-31 10:22] [ALPM] upgraded gdm (3.26.1-1 -> 3.26.2-1)
[2017-10-31 17:35] [PACMAN] Running 'pacman -S gdm'
[2017-10-31 17:35] [ALPM] reinstalled gdm (3.26.2-1)
[2017-10-31 17:44] [PACMAN] Running 'pacman -U /var/cache/pacman/pkg/gdm-3.26.1-1-x86_64.pkg.tar.xz'
[2017-10-31 17:44] [ALPM] downgraded gdm (3.26.2-1 -> 3.26.1-1)


And yes had 3.26.2-1, just looked at my logs again.
Comment by PF (greyeye) - Wednesday, 01 November 2017, 10:21 GMT
I have the same issue after updgrading gdm (and libgdm) to 3.26.2-1 yesterday. I tried downgrading gdm and libgdm back to 3.26.1-1 with live usb but for me it didn't help. Still a blank screen and I can't access tty. It's clearly the same problem but I don't understand why downgrading didn't fix it...

Loading...