Basically, what is happening is that gnome-screensaver-dialog exits after the
5th failed attempt at unlocking the screen, but before the shake animation
finishes. If the timing is slightly unlucky, this results in gnome-screensaver
accessing X resources that have already been destroyed (I ran it through
xtrace, and that showed this happening)

My patch fixes this by making gnome-screensaver-dialog request to
gnome-screensaver that it be terminated after the 5th failed attempt (rather
than exitting straight away, although there is a fallback timeout too).
gnome-screensaver then terminates the dialog after it is finished with the
shake animation, to avoid the race condition that is currently making it crash.

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

There is no point in passing a GError if we don't act on it.
This fixes RH bug 546656.

This fixes a problem where totem leaves inhibitors behind, see
bug 600488.

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

Make sure to show windows that are added.  And fix an off by one bug.

In order for fading with X.org randr 1.2 drivers to work properly,
the screensaver should use randr to fade the crtcs.

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

Workaround for http://bugzilla.gnome.org/show_bug.cgi?id=584029