I have 2 systems here on this HP6715S laptop(all amd/ati internals)
1. Slamd64-12.2 hibernates just fine.
2. Slackware-13.0 rehibernates on wake up. If I start up again, hibernate works right, so I have to do 2 restarts for one hibernate,

I copied over acpi events and scripts from slamd-12.2, but no go. Nothing noteworthy in the logs. In fact, nothing at all in the logs that gives any hint.

I've seen this sort of thing happen when using the power button on a laptop to make it hibernate. The machine was registering two button presses. The first press sent the machine to hibernate, and then after resuming the machine would react to the second press (even though the physical press was prior to the hibernation), causing it to hibernate again. Is this consistent with what you are seeing?

Evo2.

OK, that gives me a line of inquiry. Thanks.

So you are initiating hibernation by pressing the power button?

What happens if you do it from the command line?

Evo2.

Sorry, I stalled on this due to other priorities.
I'll try the suggestions and get back to you.

Yes. I had a script in the /etc/acpi to hibernate and wake up. Disabling that (chmod -x) stopped the problem. Slackware is sending some other set of signals some other way. 'pgrep acpid' gave me 2 daemons. I am running xfce (no kde loaded), but I finally twigged it with 'ps -e |grep acpid'
110 kacpid
3095 acpid
which, or slocate show me no kacpid. Kernel? Any thoughts? I bet hal is all over acpi and I bet that's responsible. The PITA now becomes that it restore with brightness weak, and I can't tweak that.

I'd love a [SOLVED?] option for this thread.
I have xfce, and slackware-13.0. taking out the default event in /etc/acpi/events also helped with thing. So now I have acpi set up to do nothing at all when told to hibernate, and it works perfectly :-/.

I come up in screensaver mode. I am locked out, and the screensaver always does lock you out. This I regard as a PITA. Yet I can configure the screensaver in XFCE, and 'require authorisation' is not set. Can anyone tell me what's actually running acpi in Slackware-13.0? Because acpid isn't :-o.

This proved to be xfce power manager not quite managing what it said. Because it seems a new kid on the block, it's not included in the settings manager. Hence the confusion. I use runlevel 3 and if I started X, then suddenly I had the extra acpi daemon muscling in on the case. Not a problem in previous versions. So between the bios (which grabs a few things like the power button & lid) and the acpi daemon I knew about and the one I didn't, this left plenty of room for duplication. Thanks to evo2 for pointing me straight on this.