commit 7a94b5da594e63038cd32cd52062fb716c828698
Author: Rudolfs Mazurs <rudolfs.mazurs@gmail.com>
Date:   2011-10-08

    Updated Latvian translation.

M	po/lv.po

commit 7b684a1922176509d3399eb5ba315617ecee75bb
Author: Alexandre Rostovtsev <tetromino@gmail.com>
Date:	2011-10-05

    Ignore DPMSSetTimeouts() and DPMSForceLevel() return value

    At least with nvidia binary drivers, DPMSSetTimeouts() and
    DPMSForceLevel()
    always return BadRequest, even if they succeed. On a machine with
    intel
    graphics, DPMSForceLevel() was also observed to return BadRequest
    despite
    successfully changing the DPMS level. So we should just ignore
    the return
    value from these functions, like xset does.

    Also, there's no need to clear the timeouts twice if the mode
    has indeed
    changed.

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

    Signed-off-by: Richard Hughes <richard@hughsie.com>

M	libgnome-desktop/gnome-rr.c

commit 311476792ba7948f0eba5e4d9a1328cf3ff18950
Author: Colin Walters <walters@verbum.org>
Date:	2011-10-03

    GnomeWallClock: Fix non-Linux fallback code

    This fixes the "infinite loop in gnome-screensaver" bug.  Only
    dispatch in cancel on set when the monotonic timeout has expired,
    otherwise we will drop into a tight loop.

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

M	libgnome-desktop/gnome-datetime-source.c

commit 55daaf0972c0021a20624dcd16df5e14cca5d430
Author: Richard Hughes <richard@hughsie.com>
Date:	2011-10-03

    When setting the DPMS mode manually, clear the timeouts

    Based on a patch from Michael Vogt, many thanks.

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

M	libgnome-desktop/gnome-rr.c

commit 9fd6e6a988eaeaccae4545a61bbbd9ae9682b48d
Author: Vincent Untz <vuntz@gnome.org>
Date:	2011-09-26

    release: post-release bump to 3.2.1

M	configure.ac

commit 39ee6b5b9acf176bdc3bf4d4815aa7d9c2273626
Author: Vincent Untz <vuntz@gnome.org>
Date:	2011-09-26

    release: 3.2.0

M	NEWS