[FFE] GDM 3.6.0 won't start without gnome-session 3.6.0

Marking as Critical since this breaks the Ubuntu GNOME Remix and we're trying to release a Beta.

I'm suspicious about this part for the slave log:

gdm-launch-environment][2897]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
gdm-launch-environment][2897]: pam_ck_connector(gdm-launch-environment:session): nox11 mode, ignoring PAM_TTY :0

Another thing to look at is the work that was done on changing autostart stuff.

In fact, maybe we just need the new gnome-session.

Ok, I verified that installing gnome-session 3.6.0 fixes this problem.

 Challenge is that gnome-session has some rdepends, that could introduce risk to the other images, which a day before Beta 2 isn't a good idea.

We're going to need to follow
https://wiki.ubuntu.com/FreezeExceptionProcess#FeatureFreeze_for_new_upstream_versions
on this one.

Can you work with Laney to make sure no side effects to the other images with updating to gnome-session 3.6.0? Timing if there are no red flags would be for Thursday after the beta freeze lifts.

Can you attach the changelog please?

From what Kate told me on IRC it sounds like it should be fine, but I'd prefer to look at it myself.

Stéphane, it looks like they didn't update their NEWS this time.

http://git.gnome.org/browse/gnome-session/log

Besides translation updates, this is the only other change, and it's this change that GDM 3.6 needs
http://git.gnome.org/browse/gnome-session/commit/?id=17b0b11

I tested gnome-session 3.6.0 with lightdm/unity-greeter and gdm. Turning on and off the screen keyboard works; turning on Orca works, but it doesn't turn off in unity-greeter. I verified that the Orca bug also affects the gnome-session we already have in Orca though.

Status changed to 'Confirmed' because the bug affects multiple users.

Downgrading to gdm 3.5.92 is a servicable workaround until this issue is resolved.

For the googlers: `sudo dpkg -i /var/cache/apt/archives/gdm_3.5.92.*.deb`

Ok, sounds reasonable then. Shouldn't that bug be retargeted at gnome-session then?

Status changed to 'Confirmed' because the bug affects multiple users.

Laney has visually inspected the diff, and is reasonably comfortable that it shouldn't introduce regressions. Based on this and the comments in #6 that its been tested under Ubuntu/Edubuntu, as well as its part of the GNOME standing exception, approved.

The following got me back in...

1. At Grub2 Loader, Select Ubuntu (Recovery Mode).
...machine will begin the boot process.

2. From the Options presented select:
Root "Drop to root shell prompt"

3. you must first mount the file system as read/write with the following commands:

# mount --options remount,rw /
# mount --all

4. enter the following at the command prompt:
# sudo dpkg -i /var/cache/apt/archives/gdm_3.5.92.*.deb

This bug was fixed in the package gdm - 3.6.0-0ubuntu2

---------------
gdm (3.6.0-0ubuntu2) quantal; urgency=low

  * debian/control.in:
    - Bump minimum gnome-session to 3.6 (LP: #1056936)
 -- Jeremy Bicha <email address hidden> Wed, 26 Sep 2012 18:08:01 -0400