Up until today I was able to suspend my system and now I can’t. I have reset the actions using the gnome control panel/power management/general tab but to no avail. I am running kernel 2.6.31.12-0.2-desktop and GNOME 2.28.2 in OpenSuse 11.2. Can anyone advise me on this?
Hello pcor and welcome to the community!
Up until today I was able to suspend my system and now I can’t.
Could you give us a bit more information.
You say you can’t suspend your system.
But can’t you select the option?
Or when you click on it nothing happens?
Or does the computer suspend, but doesn’t wake up?
Are there any error messages?
I am running kernel 2.6.31.12-0.2-desktop and GNOME 2.28.2 in OpenSuse 11.2. Can anyone advise me on this?
Try to make a test user and see if he can suspend.
Best of luck!
I can select suspend when the power button is pressed in the General tab of the Gnome Power Manager but when I click on suspend in the shutdown menu or press the power button absolutely nothing happens. I don’t see any error messages in the system logs either. The only change to the system has been the automatic updates. I did downgrade the kernel and gnome-power-manager but to no avail. I also tried suspending as another user but that didn’t work either. This is strange because up until a few days ago it all worked fine.
Hello pcor,
I’m not sure what the problem is.
Could you post the output of this command:
cat /var/log/pm-suspend.log
Up until today I was able to suspend my system and now I can’t.
I’m not sure if GNOME has the same functions.
But in KDE there are two options:
- Suspend to RAM
- Suspend to disk
If GNOME has the same options which one do you use?
Here’s some more information about suspending:
And could you try to suspend in runlevel 3?
For suspend to RAM use “s2ram” (remove the quotes!)
Best of luck!
cat /var/log/pm-suspend.log gives nothing.
The options you mention are not given in gnome.
In run level 3 s2ram only gives me some machine id details but nothing about suspend mode. s2disk reports: “Could not stat the resume device file. Reason: No such file or directory.”
Hello pcor,
In run level 3 s2ram only gives me some machine id details but nothing about suspend mode. s2disk reports: “Could not stat the resume device file. Reason: No such file or directory.”
Sad to hear it doesn’t work.
After some searching I found out which command GnomePowerManager uses to Suspend.
Can you give us the output of this command:
dbus-send --session --dest=org.gnome.PowerManager --type=method_call --print-reply --reply-timeout=2000 /org/gnome/PowerManager org.gnome.PowerManager.Suspend
If this doesn’t work try this command:
powersave -u
This uses the application powersave to suspend.
cat /var/log/pm-suspend.log gives nothing.
This could be right, can you try it again after the command “powersave -u”?
The options you mention are not given in gnome.
I think GNOME calls it Suspend and Hibernate.
Good luck!
I have a similar problem but in KDE…when I try to suspend to ram the only thing that happens is that the screensaver starts…KDE 4.4.1 and kernel 2.6.31.12-0.2-default…
(didnt know if I should start a new topic for my problem)…
Hello tekos,
(didnt know if I should start a new topic for my problem)…
I think you could better do this.
Because the problem could be very different.
And it would be more organized if the two problems are separated.
I have a similar problem but in KDE…when I try to suspend to ram the only thing that happens is that the screensaver starts…KDE 4.4.1 and kernel 2.6.31.12-0.2-default…
Did you try things that are mentioned above?
dbus-send --session --dest=org.gnome.PowerManager --type=method_call --print-reply --reply-timeout=2000 /org/gnome/PowerManager org.gnome.PowerManager.Suspend
This wouldn’t work for KDE.
So you need to run this command:
dbus-send --system --print-reply --dest=org.freedesktop.Hal \
/org/freedesktop/Hal/devices/computer \
org.freedesktop.Hal.Device.SystemPowerManagement.Suspend \
int32:0
Good luck!
Thanks for the answer…I’ll try it and in case it doesnt work I’ll start a new topic…
“dbus-send --session --dest=org.gnome.PowerManager --type=method_call --print-reply --reply-timeout=2000 /org/gnome/PowerManager org.gnome.PowerManager.Suspend” gives:
Failed to open connection to “session” message bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
“powersave -u” gives:
method return sender=:1.0 -> dest=:1.73 reply_serial=2
int32 1
“cat /var/log/pm-suspend.log” still gives nothing.
Hello pcor,
“dbus-send --session --dest=org.gnome.PowerManager --type=method_call --print-reply --reply-timeout=2000 /org/gnome/PowerManager org.gnome.PowerManager.Suspend” gives:
Failed to open connection to “session” message bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Did you ran this command as root?
In run level 3 s2ram only gives me some machine id details but nothing about suspend mode.
I tried s2ram myself and had the same problem.
Looking at the wiki entry I found this.
It means that your machine is not in the whitelist.
A workaround for this is to run the command with the **-f **argument:
s2ram -f
If that didn’t work there are a bunch of others you can try:
s2ram -f -a 3
s2ram -f -a 2
s2ram -f -a 1
s2ram -f -p -m
s2ram -f -p -s
s2ram -f -m
s2ram -f -s
s2ram -f -p
s2ram -f -a 1 -m
s2ram -f -a 1 -s
“powersave -u” gives:
method return sender=:1.0 → dest=:1.73 reply_serial=2
int32 1
I tried it myself as normal user and got the same output, but suspending went fine.
Does nothing happen? Or does your computer freezes?
s2disk reports: “Could not stat the resume device file. Reason: No such file or directory.”
You can’t start s2disk directly.
Try this command as root:
pm-hibernate
Best of luck!
“Did you run this command as root?” Yes; however, s2ram -f works as root (Yay!) but not otherwise. As pcor I get the following message: “Absolute path to ‘s2ram’ is ‘/usr/sbin/s2ram’, so running it may require superuser privileges (eg. root)”.
Hello pcor,
Yes; however, s2ram -f works as root (Yay!) but not otherwise. As pcor I get the following message: “Absolute path to ‘s2ram’ is ‘/usr/sbin/s2ram’, so running it may require superuser privileges (eg. root)”.
You can avoid this by adding this command in the file sudoers.
Open the file /etc/sudoers as root and add this line at the bottom:
%users localhost=/usr/sbin/s2ram -f NOPASSWD
This will allow every user in the users group to run “/usr/sbin/s2ram -f” as root without a password.
If you want that only you can run this command as root change %users into your username.
Good luck!
Thanks for your patience. I edited sudoers as advised but to no effect. Even used visudo as root. Any other suggestions?
Hello pcor,
I edited sudoers as advised but to no effect.
You need to run this command:
sudo /usr/sbin/s2ram -f
Good luck!
Of course! I forgot to use the sudo command. Many thanks for your patience and perseverence. I hope I can be of some help to you some day.
Hi
And I want to thank you a lot Edward.
I faced the same problem in KDE and Gnome.
I switched to gnome, s2ram -f works fine for me.
Also s2disk -r /dev/sda6 works fine to hibernate the system (sda6 is my swap partition).
but My menus i Gnome or KDE don’t work at all, they act like “lock”, I mean they lock the system and turn off the monitor, nothing futher.
BTW thanks again for paitence and excellent solution you gave us.
Hello ehsansadr and welcome to the community!
I’m just glad I can help you!
Are you sure?
Because maybe you are suspending instead of hibernating.
The difference between them is that when suspending an image will placed inside your ram.
From there it can start up in a second or two, leaving you with a locked session.
And with hibernation the image will be saved to swap.
Compared to suspending starting up will take “a bit” longer but you can unplug the computer, saving power.
AFAIK you can choose them separately in KDE.
So make sure you selected the right one!
Good luck!