public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: ich bins <imehl_adresse@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE4 suspend to RAM
Date: Mon, 22 Mar 2010 10:26:37 +0100	[thread overview]
Message-ID: <4BA737CD.9020300@gmx.net> (raw)
In-Reply-To: <201003210847.19466.michaelkintzios@gmail.com>

Am 21.03.2010 09:46, schrieb Mick:
> On Saturday 20 March 2010 15:16:57 ich bins wrote:
>   
>> Am 20.03.2010 11:21, schrieb Mick:
>>     
>>> Hi All,
>>>
>>> I want to map a OEM keyboard button to suspend the PC to RAM, but I am
>>> not sure which command KDE4 is using in its menu for suspending to RAM. 
>>> I assume that I will be able to map this button to the command in
>>> question and I wouldn't need to elevate privileges, enter passwds, or the
>>> like, because when I select it from the KDE menu it just runs.
>>>       
>> in the shortcuts section you have to define a new dbus-call
>>
>> org.kde.kded
>> /modules/powerdevil
>> suspend
>> 2
>>     
> Hmm ... this is weird:
>
> I set up Trigger as Sleep and populated the Action fields as you suggested in 
> the Input Actions in SystemSettings.  If I click on the Call button under the 
> Action fields, the machine goes to sleep.  If I use the keyboard Sleep button 
> it does not.  How do I troubleshoot this?
>   
have you populated the Xf86Sleep-button (or which you re using) with the
action? Is the key you re using known by KDE ? which KDE version you re
using?



  reply	other threads:[~2010-03-22  9:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-20 10:21 [gentoo-user] KDE4 suspend to RAM Mick
2010-03-20 15:14 ` ich bins
2010-03-20 15:16 ` ich bins
2010-03-20 17:15   ` Mick
2010-03-21  8:46   ` Mick
2010-03-22  9:26     ` ich bins [this message]
2010-03-22 11:17       ` Mick
2010-03-22 11:24         ` ich bins
2010-03-22 11:44           ` Mick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BA737CD.9020300@gmx.net \
    --to=imehl_adresse@gmx.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox