Hi,
I installed openSUSE 11.0 with KDE 3.5 on a Thinkpad R50e and on a Thinkpad R61i. Suspend generally works on both machines when I use the keyboard shortcuts or kpowersave. Suspend also works from the login screen. But there’s no option to suspend from out of the Kmenu (or startmenu). Any suggestions?
Same Here…
Google isn’t helping out either
is your power-manager plugin for yast also missing
as root run
#yast2 -l | grep power
to find out…
supertimorplusfort wrote:
>
> Hi,
> I installed openSUSE 11.0 with KDE 3.5 on a Thinkpad R50e and on a
> Thinkpad R61i. Suspend generally works on both machines when I use the
> keyboard shortcuts or kpowersave. Suspend also works from the login
> screen. But there’s no option to suspend from out of the Kmenu (or
> startmenu). Any suggestions?
>
>
There’s an option to select whether the shutdown/sleep/restart menu options
are present in the Kmenu.
KDE Control Center (Personal Settings)
→ System Administration
→ Login Manager
— Click on ‘Administrator Mode’, give root password
→ Shutdown Tab
The “Allow Shutdown” section, Local dropdown selects whether anyone can shut
the machine down, or only root, or no one at all.
I set mine to ‘Only Root’, since they’re used as servers and I don’t want the
kids turning things off or rebooting them (they DO that y’know!). The Kmenu
entries don’t appear, and attempting to reboot or shutdown (or sleep) the
machine cause a root prompt to appear for confirmation.
If it’s set to ‘Everybody’, then the menu entries are present, and you can
perform the actions you’re talking about, sleep/standby/reboot/shutdown.
–
L R Nix
lornix@lornix.com
@ dspoelke: There’s no power-manager plugin for yast installed, nor can I find one. there’s only gnome-power-manager, but I use KDE 3…
@lornix: Shutdown is already permitted to everybody as I see in kcontrol. And in fact I can shutdown and reboot from the Kmenu but suspend only shows up in Kpowersave.
Thanks
supertimorplusfort wrote:
>
> @ dspoelke: There’s no power-manager plugin for yast installed, nor can
> I find one. there’s only gnome-power-manager, but I use KDE 3…
>
> @lornix: Shutdown is already permitted to everybody as I see in
> kcontrol. And in fact I can shutdown and reboot from the Kmenu but
> suspend only shows up in Kpowersave.
> Thanks
>
>
Y’know what… I just looked, and neither of my systems have the suspend/sleep
options in the Kmenu.
Gosh!
I’ll keep an eye out for anything to do with this.
Loni
L R Nix
lornix@lornix.com
bouncing against the wall with this also. It may be something related to KDE 3.5 on openSUSE 11.0, as I’ve installed it before with KDE4 and all the options were available.
I am having this same issue. In the past I was able to resolve it somehow, but can’t remember. As stated, it only happens with KDE 3.xx, not with 4.XX.
Anyone have a fix for this problem? I’m in the same boat.
Dexter1979 wrote:
>
> Anyone have a fix for this problem? I’m in the same boat.
>
>
Try this from a konsole:
kwriteconfig --file ksmserverrc --group General --key offerShutdown --type
bool true
(that’s all one line)
You may need to logout then back in to see the changes.
Loni
–
L R Nix
lornix@lornix.com
What exactly does that command do? offer shutdown?
LinuxIST wrote:
>
> lornix;1846206 Wrote:
>> Dexter1979 wrote:
>>
>> >
>> > Anyone have a fix for this problem? I’m in the same boat.
>> >
>> >
>>
>> Try this from a konsole:
>>
>> kwriteconfig --file ksmserverrc --group General --key offerShutdown
>> --type
>> bool true
>>
>> (that’s all one line)
>>
>> You may need to logout then back in to see the changes.
>>
>> Loni
>>
>>
>> –
>> L R Nix
>> lornix@lornix.com
>
> What exactly does that command do? offer shutdown?
>
>
Sets an option in the kde configuration files so kmenu shows the shutdown
options, which include s2ram, s2disk, reboot and shutdown.
you can also edit the file by hand, the file you need is ‘ksmserverrc’
(found in .kde/share/config), look for the [General] section, and add or
edit a line containing ‘offerShutdown=’ to read ‘offerShutdown=true’.
If you look at the command line given, you can identify all those parts
within.
–
L R Nix
lornix@lornix.com
Sets an option in the kde configuration files so kmenu shows the shutdown
options, which include s2ram, s2disk, reboot and shutdown.
I still only see reboot and shutdown options after executing it.
deano ferrari wrote:
>
>> Sets an option in the kde configuration files so kmenu shows the
>> shutdown
>> options, which include s2ram, s2disk, reboot and shutdown.
>
> I still only see reboot and shutdown options after executing it.
>
>
Did you log out and then back in to reload the settings?
There is also a configuration option in the ‘Configure Desktop / Personal
Settings’ application, under “System Administration”, “Login Manager”.
You’ll have to select “Administrator Mode” to change it. It decides who
receives the shutdown options, local users, only root, no-one, all users,
etc.
–
L R Nix
lornix@lornix.com
I tried this and it doesn’t actually include the suspend to disk/RAM. My motherboard is not on the whitelist. Suspend to disk works fine (it’s the one I want to use anyways) when I use it by either going into a konsole or rightclicking on kpowersave and select suspend to disk.
you can also edit the file by hand, the file you need is ‘ksmserverrc’
(found in .kde/share/config), look for the [General] section, and add or
edit a line containing ‘offerShutdown=’ to read ‘offerShutdown=true’.
When I do this my options under the kpowersave disappear.
Puzzled now.
Dexter1979 wrote:
>
> lornix;1846457 Wrote:
>> Did you log out and then back in to reload the settings?
>> There is also a configuration option in the ‘Configure Desktop /
>> Personal
>> Settings’ application, under “System Administration”, “Login Manager”.
>> You’ll have to select “Administrator Mode” to change it. It decides
>> who
>> receives the shutdown options, local users, only root, no-one, all
>> users,
>> etc.
> I tried this and it doesn’t actually include the suspend to disk/RAM.
> My motherboard is not on the whitelist. Suspend to disk works fine
> (it’s the one I want to use anyways) when I use it by either going into
> a konsole or rightclicking on kpowersave and select suspend to disk.
>
>> you can also edit the file by hand, the file you need is ‘ksmserverrc’
>> (found in .kde/share/config), look for the [General] section, and add
>> or
>> edit a line containing ‘offerShutdown=’ to read ‘offerShutdown=true’.
>> When I do this my options under the kpowersave disappear.
>
> Puzzled now.
>
>
Well, I’m probably not the best to answer the suspend stuff anyways, none of
my machines actually ever shut down. They step the cpu clock down, spin
down the drives, turn off lcd’s, printer and speakers are on a custom built
parallel driven switch to turn them on and off as needed… but never
completely off, unless the UPS’s give up. (Thunderstorms are bad in
Oklahoma this time of year). I’ve tried the suspend2ram and s2d features,
they work here, but I usually end up removing them from the kmenu. Hmmm,
maybe I’ll look into s2d as a end result of ups signalling out-of-power.
that would be cool.
I’m not at all sure what magic is needed to make the menu entries appear.
You could peruse the source code… I have for other questions, and have
learned some interesting things besides. If the kpowersave or konsole
options work, make an icon to do the same. No, not saying to “just accept
it” either. Keep digging I guess. Good Luck?
–
L R Nix
lornix@lornix.com
I believe it is a permission issue because the s2disk/s2ram (standby) is available on Log Out if you’re root.
I believe it is a permission issue because the s2disk/s2ram (standby) is available on Log Out if you’re root.
This possibility occurred to me as likely as well.
This is not the case since I got both Suspend to disk and Suspend to RAM working via kpowersave. Just right click the ‘plug’ icon and it’s there. All works flawlessly. It even works via my sleep button and powerbutton if I assign it either function in Kpowersave.
In short, I’m not bothered about it anymore since it works but still very curious why it is not there in Kicker.
It somehow resolved itself for me today after an update.