hello,
i'm currently running debian unstable with the uswsusp package.

at first everything was fine,
i installed debian testing, configured the package according to the http://www.klabs.be/~fpiat/linux/deb...owerManagement HOWTO, and the gnome-power-manager suspend worked.

BUT!!! when i dist-upgraded to unstable, the gnome-power-manager stopped letting me suspend, with the weirdest effect:
it starts to suspend, the screen blanks, the sleep led starts blinking, but then X pops back up!

when i try to suspend with the power manager i get this message in /var/log/messages:
Nov 12 02:06:51 debian gnome-power-manager: (ghostcow) Suspending computer because clicked tray
Nov 12 02:06:56 debian gnome-power-manager: (ghostcow) Resuming computer

i tried `s2ram -f -a3` like the HOWTO stated and it still works fine.

what should i do?

... and discovered that it was unstable?

If it "still works fine", why do you need to "do" anything?

Have you tried looking in /etc/default/acpi-support

i want it to work through the power management applet :P
yes, i got
ACPI_SLEEP=true
ACPI_SLEEP_MODE=mem

im gonna try and set the second variable to standby see what happens
umm anything else i'm missing here?

edit: tried setting the variable like i said, had no concequence
i'm thinking of downgrading my power manager this looks like a bug.

anyone heared of this "suspend and instantly resume" bug?

hah! Now I understand your post... nope, never heard of this.

Your system wakes from suspend - immediately after the suspend, without intervention.
This sounds similar to the old "shutdown is the new reboot" bug. The "resume" message seems to indicate that something is issuing a wake order... try to eliminate HW wake stuff from the equation, like disable any wake-on-lan. Look through the BIOS for anything special to do with hibernate and suspend, disable it.

why would BIOS interrupts be the case if using the "s2ram -f -a 3" command works for me fine?

is the new version of power manager more susceptible to these settings?

edit: disabled wake on lan in the BIOS settings, didn't find any other settings that might be related, and alas, no dice, the problem persists.

I get susped then resume when the system has not enough disk space to copy the ram to disk.
But it's probably not the problem..

Running "s2ram -f -a 3" works on CLI?
Have you checked that your modifications to /etc/hibernate/ususpend-ram.conf have survived the upgrade?

Simon i solved the problem finally
i went through all my config files everything is fine, uninstalled the software completely, and i noticed something strange - the suspend still goes at it when i tried suspending through the gnome power manager applet, even though i removed the 's2ram' bin !
so i dug around a little, and turns out a script package called "pm-utils" is called when using the applet.
here's a good article about those scripts:
http://en.opensuse.org/Pm-utils
so i read about, and created a config file at /etc/pm/config containing simply
S2RAM_OPTNS="-f -a 3" (after re-installing s2ram of course :P) - which worked like a charm!

now i can happily suspend using the gnome applet thanks for all your help!