This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Remove Suspend options from Kickoff

Tags: None
(comma "," separated)
arizonagroovejet
Registered Member
Posts
12
Karma
0

Remove Suspend options from Kickoff

Tue Feb 03, 2009 3:15 pm
Is there some way to remove the Suspend to Disk and Suspend to Ram options from the Kickoff menu? I don't want them there for users to click on.

I can get rid of the Suspend to Ram option by passing acpi=off to the kernel at boot but that's not an acceptable method in practice because then the machine won't actually turn off after being told to shut down.
I tried removing the resume= option from the boot but to see if that got rid of the Suspend to Disk option, but the option remains and just doesn't do anything.

I'm using KDE 4.2 with openSUSE 11.1. I don't know whether these options are controlled by KDE or whether KDE picks up on something set by the distro or whatever.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
I believe KDE automatically detects if your system is capable or not, and shows them if the system can. The easiest way to control this functionality would be to convince the lower systems ( HAL in particular ) that the system is not suspend capable.

Otherwise you will need to ask the developers whether a configuration file option is available to disable the functionality.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
arizonagroovejet
Registered Member
Posts
12
Karma
0
I have now found a solution. There's a script /usr/bin/pm-is-supported which can be used to determine the suspend capabilities of the machine and KDE 4 evidently uses that to determine whether to show the Suspend options. I say this not because I found it documented anywhere but due to result of experimentation. I replaced pm-is-supported with a script which just does

Code: Select all
exit 1


rebooted the machine and found the Suspend options are no longer listed in Kickoff. This works on openSUSE 11.1 and Kubuntu 8.10. (Though with Kubuntu I've only tested on a virtual machine on which 'Suspend to RAM' was never listed as 'pm-is-supported --hibernate' exits with 1.) It's a hack but it's one I can live either as it's easy to implement. If anyone has any suggestions on a more elegant method it would be interesting to hear.
roooooooooot
Registered Member
Posts
18
Karma
0
OS
I think this solution is very elegant :)


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]