I don't have guidance-power-manager installed. Not necessary for a desktop.

To make it clear: in which file can we reassign the KDE4 "suspend to disk" GUI command " ?

However, it now works fine both with Debian and Ubuntu (on the same PC).
The only difference is that Ubuntu requires uswsusp, and not Debian, which means the "suspend to disk" is probably not configured the same way.

"To make it clear: in which file can we reassign the KDE4 "suspend to disk" GUI command " ?"

The answer is finally ..... : /usr/lib/hal/scripts/linux/hal-system-power-hibernate-linux

Different behaviors of KDE4 suspend GUI command is explained by the content of hal-system-power-hibernate-linux.

Now clarified.

KDE 4 uses Solid which instructs its backend to perform the hibernation / suspend. The only available backend for Linux at this time is HAL.

For those having troubles with "suspend to disk" at least with Kubuntu, there is a straight solution:

Install uswsusp

cd /usr/lib/hal/scripts/linux/
sudo mv hal-system-power-hibernate-linux hal-system-power-hibernate-linux.bak
sudo ln -s /usr/sbin/s2disk ./hal-system-power-hibernate-linux

The "suspend to disk" KDE4 GUI command will directly point to /usr/sbin/s2disk

I have a question regarding suspending. I'm using KDE 4.3 with Debian Testing/Sid and want to change the behavior of the "Suspend to ram" button script. What I exacly need is to stop network-manager service before suspend and start it after resume. As I understand the first can be done by modifying the

Code: Select all

hal-system-power-suspend

script (or am I wrong?). What about starting after resume?

Now I am using following combination:

1.

Code: Select all

#service network-manager stop

2. run suspend to ram from KDE menu
...sleeping and after wake:
3.

Code: Select all

#service network-manager start

KDE instructs HAL to perform the system suspension, therefore the correct script to modify is the script your distribution uses to perform the suspend.