Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#44570 - [gdm] needs restart before showing login

Attached to Project: Arch Linux
Opened by Christian Bürckert (Kriese) - Monday, 13 April 2015, 07:50 GMT
Last edited by Jan de Groot (JGC) - Friday, 08 May 2015, 16:22 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No



After the latest updates I cannot directly login on a systemstart. I first need to switch to tty2 and restart gdm (systemctl restart gdm) before I can login. The tty1 shows just the regular console output and seems to hang. I can see a mouse pointer.

I cannot find any appropriate logs to give you more details but if you tell me where to look I'll do it ;)
I tried reinstalling gdm and nouveau with no effect.

dmesg shows a seg fault but I am not sure if this is associated with this problem.

Additional info:
* package version(s)
extra/gdm (gnome)
extra/xf86-video-nouveau 1.0.11-3 (xorg-drivers xorg)

* config and/or log files etc.

[ 83.337030] gnome-shell[932]: segfault at 18 ip 00007f58a3ed619c sp 00007ffd638f1b10 error 4 in[7f58a3e90000+ed000]

Steps to reproduce:
Restart the System - :)
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 08 May 2015, 16:22 GMT
Reason for closing:  Fixed
Comment by Christian Bürckert (Kriese) - Wednesday, 22 April 2015, 08:23 GMT
Since the upgrades restarting gdm does not help. I need to unplug my laptop from the docking and after login put it back in the dock.
I've googled a bit and found out that there are more issues with multiple monitors in 3.16 so this might be related.

gdm is now on
Comment by Doug Newgard (Scimmia) - Sunday, 26 April 2015, 05:09 GMT
Intel CPU? If so, microcode updated?
Comment by Christian Bürckert (Kriese) - Sunday, 26 April 2015, 11:17 GMT
$ dmesg | grep micro
[ 0.712587] microcode: CPU0 sig=0x106e5, pf=0x10, revision=0x5
[ 0.712604] microcode: CPU1 sig=0x106e5, pf=0x10, revision=0x5
[ 0.712612] microcode: CPU2 sig=0x106e5, pf=0x10, revision=0x5
[ 0.712628] microcode: CPU3 sig=0x106e5, pf=0x10, revision=0x5
[ 0.712650] microcode: CPU4 sig=0x106e5, pf=0x10, revision=0x5
[ 0.712666] microcode: CPU5 sig=0x106e5, pf=0x10, revision=0x5
[ 0.712678] microcode: CPU6 sig=0x106e5, pf=0x10, revision=0x5
[ 0.712696] microcode: CPU7 sig=0x106e5, pf=0x10, revision=0x5
[ 0.712788] microcode: Microcode Update Driver: v2.00 <>, Peter Oruba

I'd say my microcode is on the newest version
Comment by Doug Newgard (Scimmia) - Sunday, 26 April 2015, 14:52 GMT
And I would say it isn't:
% bsdtar -Oxf intel-ucode.img | iucode_tool -tb -ls0x106e5 -
selected microcodes:
001: sig 0x000106e5, pf mask 0x13, 2013-08-20, rev 0x0007, size 7168

The new ucode is still from 2013, so this probably isn't your problem.