Comment 14 for bug 716167

little progress made here despite tons of debugging.
Here is what I do know:
- unity-2d-launcher and unity-2d-panel correctly registering with gnome-session and correctly providing a response to QueryEndSession() signal sent from org.gnome.SessionManager.ClientPrivate interface with EndSessionResponse() method
- gnome-session is receiving the EndSessionResponse()
- gnome-session then NEVER fires EndSession() signal back to unity-2d-*. This is the problem. Other clients who register with gnome-session (i.e. gnome-power-manager, gnome-keyring, polickit-1-gnome) and get the EndSession() signal and then call the EndSessionResponse() again which causes the disconnect. Without this happening we are running into either
a) the dialog being displayed saying unresponsive program
or
b) a 10 second timeout (as documented in http://people.gnome.org/~mccann/gnome-session/docs/gnome-session.html#org.gnome.SessionManager.ClientPrivate) before the session is killed.

I believe EndSession() signal is not being sent because gnome-session thinks we've inhibited the logout (based on messages I'm seeing when running gnome-session in debug mode). I haven't figured out why this is happening yet.

Attached is a log from running gnome-session in debug mode.