Comment 9 for bug 267141

The problem appears when uswsusp is installed because of an incorrect test for the use of uswsusp for suspend for SLEEP_MODE=auto.

This is what ships in /usr/lib/pm-utils/pm-functions

        # Try userspace software suspend
        if [ -c /dev/snapshot ] && command_exists s2disk ; then
                SLEEP_MODULE="uswsusp"
        fi

This is what should ship

        # Try userspace software suspend
        if [ -c /dev/snapshot ] && command_exists s2ram ; then
                SLEEP_MODULE="uswsusp"
        fi

The following patch to 10-sleep-mdule-auto-detection.patch appears to resolve the problem

--- pm-utils-1.1.2.4/debian/patches/10-sleep-module-auto-detection.patch.orig 2008-09-18 13:58:46.000000000 -0400
+++ pm-utils-1.1.2.4/debian/patches/10-sleep-module-auto-detection.patch 2008-09-18 11:43:16.000000000 -0400
@@ -20,7 +20,7 @@
 + SLEEP_MODULE="kernel"
 +
 + # Try userspace software suspend
-+ if [ -c /dev/snapshot ] && command_exists s2disk ; then
++ if [ -c /dev/snapshot ] && command_exists s2ram ; then
 + SLEEP_MODULE="uswsusp"
 + fi
 +

However... My thinkpad T61 appears to now get upset with kernel suspend.
So I built debian sid's uswsup-0.8-1 which provides s2ram. And everything appears to be happy now.

Now off to find out why we're still on a 15 month old version of uswsusp, and why splashy.h has gboolean instead of int.