explicitly picked

We only want to set DISPLAY if the user session is sharing the display
with the login screen.

This will need to get hooked up to a config option.

GDM uses a worker to manage PAM for user sessions and
greeter sessions. For the latter case we shouldn't run
the various Pre/Post scripts, but commit
Sb48a305e71637181975fc7ec479a71079b6fbc broke that.

This commit changes the code to prevent those scripts
from getting run again.

https://bugzilla.gnome.org/show_bug.cgi?id=727703

These functions are unused, so there's no reason to
keep them around.

This commit removes those functions and corresponding test code.

https://bugzilla.gnome.org/show_bug.cgi?id=727183

Lars Uebernickel authored Apr 03, 2014 and Bastien Nocera committed Apr 03, 2014

Set XDG_CURRENT_DESKTOP when DesktopNames is set in the session file.

https://bugzilla.gnome.org/show_bug.cgi?id=727546

vnc sessions, for instance, aren't on a seat.

This commit properly hooks in gnome-keyring into the password
stack, so password changes are caught at login time, and the keyring
is appropriately rekeyed.

It looks like there were a couple of breaks when porting away from
ck-connector.

The first issue is that consolekit uses some hard-coded rules to decide
if a given session is associated with the hard-coded 'Seat1' or not.
One of these rules is the "x11-display-device" property being set.  We
were setting the "display-device" property instead, which is not for
graphical sessions.  This was causing a new seat to be dynamically
created each time gdm started which was causing us to send
ActivateSession requests to the wrong seat.

The second issue is that ActivateSession will "fail" with "Session
already active" errors.  Ignore those.

https://bugzilla.gnome.org/show_bug.cgi?id=727072

There was some confusion over multiple competing enabled variables.

This commit eliminates the confusion.

https://bugzilla.gnome.org/show_bug.cgi?id=680348

Rename this function to be more descriptive after some discussion
with Matthias.

https://bugzilla.gnome.org/show_bug.cgi?id=726813

When the slave was merged to the main daemon process, the code for
doing autologin accounting was accidentally moved earlier in the
autologin process.  This caused the greeter to create a login
screen and do autologin at the same time.

This commit defers the accounting until after the operation is
fully initiated.

https://bugzilla.gnome.org/show_bug.cgi?id=726813

The previous patch missed one case of GDM_SESSION_DISPLAY_MODE_NEW_VT,
resulting in an undefined reference to jump_to_vt().

https://bugzilla.gnome.org/show_bug.cgi?id=726380

fixes distcheck

FreeBSD build broke, so this commit makes wayland a configure time
argument

https://bugzilla.gnome.org/show_bug.cgi?id=726380

The previous commit uses weak references on weak references to manage
transient session lifecycles without doing proper accounting.

That was a bad idea.  This commit uses a hash table to track things
more explicitly.

https://bugzilla.gnome.org/show_bug.cgi?id=726283

Right now, gnome-shell can't unlock screens running on an X server that
isn't managed by GDM (say Xvnc or startx).  This is because GDM handles
the backend processing for unlocking, and it handles that backend
processing from the worker associated with the session.  If there is no
worker associated with the session (as is the case with Xvnc and startx),
then there's no process to handle reauthentication.

This commit notices that case, and creates a transient worker on the fly
just to perform one off authentication for unlock of non-GDM managed
sessions.

https://bugzilla.gnome.org/show_bug.cgi?id=726283

In the future we're going to need to know more details about the
sender to know how to move forward (such as seat id, session id,
if it's remote, etc) in order to create a transient session soley
for reauthentication.

To prepare for that future, this commit adds the necessary
functionality to get_display_and_details_for_bus_sender.

https://bugzilla.gnome.org/show_bug.cgi?id=726283

At the moment we unconditionally set PAM_XDISPLAY
and PAM_XAUTHDATA based on values passed to the worker.

In a future commit, those values are going to become
stubs, so as a first step, this commit makes PAM_XDISPLAY
and PAM_XAUTHDATA optional.

https://bugzilla.gnome.org/show_bug.cgi?id=726283

It doesn't make sense for it to do, and right now the shell does it
up front, waits for the failure, and then does the "right" thing
(opens a new auth session) after.

This commit makes the failure explicit, so we can subsequently make
other cases where a reauth channel is requested work even if there is
no session to channel to by implicitly creating a transient one just
in time.  That will come later.

https://bugzilla.gnome.org/show_bug.cgi?id=726283

... at least for now, until we land logind integration in mutter
and turn on the Xorg logind-aware codepath in gdm.

https://bugzilla.gnome.org/show_bug.cgi?id=726380

https://bugzilla.gnome.org/show_bug.cgi?id=726380

Simply look for "wayland-sessions" as a path element.

https://bugzilla.gnome.org/show_bug.cgi?id=726380

Add the wayland-sessions directory, as shipped by gdm.

https://bugzilla.gnome.org/show_bug.cgi?id=726380

https://bugzilla.gnome.org/show_bug.cgi?id=726380

GNOME is going to need a mode of operation in GDM where the session
manages its own display server. In this mode of operation, we won't
morph the login screen into a user session by reusing the same X server.

Instead, we reset the login screen to prepare it for a future login,
and then let GNOME or the session worker activate its own session.

This commit adds the prerequisite work needed to gdm-manager.c, but
only as dead code, since the way to "turn it on" is stubbed out to
always reuse the existing server.

https://bugzilla.gnome.org/show_bug.cgi?id=726380

The session display mode describes exactly how the worker
environment will set up VTs, and whether the greeter X server
will be reused for the user session.

https://bugzilla.gnome.org/show_bug.cgi?id=726380

This reverts commit 72ccb273.

We're going to take a different approach for this.