Today I noticed, that when I boot kubuntu with KDE4 on my laptop, I get nice "suspend to ram" and "suspend to disk" options in the kickoff menu - but I don't get them on my gentoo box. Why? Are they 'kubuntu only'? Or does KDE think my machine doesn't support suspending? (it does very well, but I have to do it manually via /sys/power/state)

The suspend/hibernate should be available to any KDE install from the logout dialog. (Not Kickoff though) To access them, click and hold on the Power off button in the logout dialog. A popup menu with suspend and hibernate options should appear.

We did add a patch to Kubuntu that makes the suspend/hibernate options also appear in Kickoff, however.

Indeed, the pop-up menu does appear, but neither button work - nothing happens when I click on them.

yabolus wrote:Indeed, the pop-up menu does appear, but neither button work - nothing happens when I click on them.

It works but very strange way. You must press the button and wait wile submenu apears and then choose where you want to suspend: disk or RAM. Sure if you're speedy enough. But if you missed you'll go to poweroff mode. For me it happens very often and I feel very grateful to the author of this genius trick. It is quite remarkable feature of KDE4.

For KDE 4.2, I am running plain trunk and have those options ( Suspend to RAM + Suspend to Disk ) in my Kickoff menu.

alukin wrote:It works but very strange way. You must press the button and wait wile submenu apears and then choose where you want to suspend: disk or RAM. Sure if you're speedy enough. But if you missed you'll go to poweroff mode. For me it happens very often and I feel very grateful to the author of this genius trick. It is quite remarkable feature of KDE4.

It is meant to be that way. One click should shut down. A click and hold on the small arrow should *never* shut down but show the menu.

LinuxIsInnovation wrote:It is meant to be that way. One click should shut down. A click and hold on the small arrow should *never* shut down but show the menu.

1) I do not like vista-style menu as many of us and there's no item for suspend in old-styled menu.
2) It is bad if it is meant to be that way. Notebook users need suspend far more often then shutdown. Gnome has separate items in that dialog and I never miss item I really need. With that "intentional" design I thank developers every time when my notebook goes to poweroff instead of suspend.

I must say that KDE4 has a lot "novelties" that users hate, do you know?

bcooksley wrote:For KDE 4.2, I am running plain trunk and have those options ( Suspend to RAM + Suspend to Disk ) in my Kickoff menu.

Same in Fedora 10 here.

(f) Kickoff->Leave-> Suspend to RAM (or to Disk)

What gives. Are the Linux distributions taking different tacks to presenting KDE?

And I have a bug to report:
Only the first Suspend to RAM works (including the Resume). The 2nd fails. Where to report? KDE guys, Fedora guys, Linux kernel guys?

You will need to discuss that on the Fedora forums. I have no idea what solution Fedora offers. It may be uswsusp, which you likely need to configure. I know how to do that in Debian, but not in Fedora...

sayakb wrote:

alukin wrote:It works but very strange way. You must press the button and wait wile submenu apears and then choose where you want to suspend: disk or RAM. Sure if you're speedy enough. But if you missed you'll go to poweroff mode. For me it happens very often and I feel very grateful to the author of this genius trick. It is quite remarkable feature of KDE4.

It is meant to be that way. One click should shut down. A click and hold on the small arrow should *never* shut down but show the menu.

In Fedora 10: Suspend to RAM is effective only the 1st time

I'm trying "Suspend to RAM" on
KDE4.2, Fedora 10, Thinkpad T500.

I'm activating it from the
KDE Kickoff->Leave->Suspend to RAM

The first time, the system leaves X, gives some messages in the console and goes to sleep. On my Thinkpad, I can wake up from sleep by Fn + F4 keys, or by Fn + moving over the TouchPad (funny, yeah).

If I'm trying the "Suspend to RAM" the 2nd time in the same session, the system remains in active mode, in X, and I'm popped up with kernel error messages (to be sent to the kernel guys).

Are you guys getting the same? Where to report? I've posted it in the Fedora forum too.

JerryS wrote:In Fedora 10: Suspend to RAM is effective only the 1st time

I'm trying "Suspend to RAM" on
KDE4.2, Fedora 10, Thinkpad T500.

I'm activating it from the
KDE Kickoff->Leave->Suspend to RAM

The first time, the system leaves X, gives some messages in the console and goes to sleep. On my Thinkpad, I can wake up from sleep by Fn + F4 keys, or by Fn + moving over the TouchPad (funny, yeah).

If I'm trying the "Suspend to RAM" the 2nd time in the same session, the system remains in active mode, in X, and I'm popped up with kernel error messages (to be sent to the kernel guys).

Are you guys getting the same? Where to report? I've posted it in the Fedora forum too.

BTW, I seems Suspend to Disk works well.

It works twice in sequence, no problem. Great. The only thing lost is Bluetooth connection for the mouse, which may be natural.

BTW, any line command for Suspend to RAM/Disk?

JerryS wrote:BTW, any line command for Suspend to RAM/Disk?

No answer to this one ?

Looking for qdbus command line for suspend/hibernate.

Thanks

You can suspend/hibernate by echoing disk or mem to /sys/power/state, like this:

Code: Select all

echo disk > /sys/power/state

for suspend-to-disk.

Strange. This thread has been closed, moved and reopen.

The "echo disk > /sys/power/state" has already been investigated here: suspend to disk shortcut

If you know exactly which default "suspend to disk" command is used by KDE4, you are welcome to give the answer, may be in this thread where the question was raised.
Thanks.

This thread was caught up in the closure of the Installation & Configuration forum which is still in progress. Topics are being moved out over time.