Comment 1 for bug 1610434

I'm not sure what to think so far but I wanted to make some notes of things I've tried (and looked at) so far so I don't forget.

I performed the same identical test on Ubuntu amd64 Trusty w/Utopic HWE on the same hardware this AM and it boots fine. The Ubuntu GNOME install I performed this failed test on yesterday is i386 so I thought it might be either GNOME or arch specific.

To see if it was related to gdm I tried lightdm with lightdm-gtk-greeter but it also won't boot. The one difference is that I actually see the login screen but trying to login just bounces me back to the login screen. (gdm is set to auto-login)

I've tried renaming .Xauthority and .ICEauthority but that didn't change much, if anything. The one difference I notice since renaming those two files and changing back to gdm is that I no longer see "Restoring resolver state" but rather just a blank black screen.

I can always log into a TTY from the "frozen" state. Not sure if this is helpful but .xsession-errors shows:

Script for ibus started at run_im.
Script for auto started at run_im.
Script for default started at run_im.
init: gnome-session (GNOME) main process (1565) terminated with status 1
init: logrotate main process (1491) killed by TERM signal
init: upstart-dbus-session-bridge main process (1533) terminated with status 1
init: Disconnected from notified D-Bus bus

Next I plan on performing another test using Ubuntu GNOME amd64 Trusty w/Wily HWE to see if this might be arch specific. Of course that may not be 100% definitive because the first (failed) test started with a Utopic HWE, but the passing Ubuntu test this AM was on an install using the Utopic HWE.

Have I confused anyone besides myself so far?

I'm subscribing Jeremy Bicha in case he may have some ideas.