gdm

~vcs-imports/gdm/+git/gdm:multi-stack-async-stop

Last commit made on 2009-05-07
Get this branch:
git clone -b multi-stack-async-stop https://git.launchpad.net/~vcs-imports/gdm/+git/gdm

Branch merges

Branch information

Name:
multi-stack-async-stop
Repository:
lp:~vcs-imports/gdm/+git/gdm

Recent commits

f544cd0... by Ray Strode <email address hidden>

in progress work to make pam module death async

ec17488... by Ray Strode <email address hidden>

create_new_session not reset_session for autologin

The latter forces a session close and we won't have a session to close.

ffdb443... by Ray Strode <email address hidden>

Store name of worker job after starting it

This makes it easier to print debug messages.

0f9656a... by Ray Strode <email address hidden>

Don't tie unix signals to event loop in worker

One common bit of boilerplate we use in the various parts of GDM is the
gdm_signal_handler* functions. They handle bridging asynchronous unix
signals to the glib main loop so they can be processes safely.

It doesn't make sense to use those functions in the worker, though.
Often the worker will be blocking in a PAM module instead of the glib
main loop, so deferring signal handling until the main loop iterates,
may be deferring signal handling indefinitely.

This is especially bad for the worker, since the slave sends a TERM
signal to the greeter to terminate the PAM conversation. The above code
meant that some conversations were never getting terminated.

80107a0... by Ray Strode <email address hidden>

When one PAM conv. wins, actually stop the others

We weren't properly keeping the winning conversation
around in the previous commit

339ca93... by Ray Strode <email address hidden>

When one PAM conversation wins, stop the others

This doesn't work yet, it's still in progress code.

c98a8ac... by Ray Strode <email address hidden>

reset all conversations if password conversation fails

This is a temporary hack until we store plugin policy in
gconf.

996f22a... by Ray Strode <email address hidden>

Notify plugins if their user choose requests fail

This allows the smart card plugin to cancel pending
conversations when a card gets inserted.

This isn't perfect. We really want to only cancel
the conversations if they're for a user other
than the user the smartcard is for.

adf3297... by Ray Strode <email address hidden>

Drop the different auth modes in favor of calling reset manually

23902b5... by Ray Strode <email address hidden>

Add new function find_task_with_service_name

It hides a bunch of icky foreach calls.