> There's already a similar bug report > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=410818
I don't experience the problem described there. s2ram seems to return a sensible exit code (0 on success, 127 on failure), and this is passed back by HAL to kpowersave, which fails to understand it. > The cleanest fix imo would be to remove the direct call to s2ram and > have hal depend on one of the above package instead. > This way we get defined behaviour. No, kpowersave would still be broken, since it misinterprets exit codes from the suspend script. This is independent of the underlying suspend method. You can easily test this, just make the HAL script return any non-zero status code. Having used uswsusp for a while with very good results I don't see the need for another wrapper like hibernate (which doesn't support uswsusp anyway). I already have acpi-support, but it doesn't use uswsusp either. (Whew, this this suspend stuff is a mess...) Marcus
pgpPWzlYlcTjV.pgp
Description: PGP signature
