public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Benno Schulenberg <benno.schulenberg@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: Migration to xorg-x11 7.0 - Great except for one   detail
Date: Sun, 23 Jul 2006 23:14:08 +0200	[thread overview]
Message-ID: <200607232314.08606.benno.schulenberg@gmail.com> (raw)
In-Reply-To: <ea050a$6mj$1@sea.gmane.org>

Remy Blank wrote:
> Benno Schulenberg wrote:
> > There are just no actions like "Play", "Volume Down" or "Mute"
> > that I could assign XF86AudioPlay, XF86AudioLowerVolume or
> > XF86AudioMute to.
>
> Ok, I get it, sorry. I don't want to assign them to "Play" or
> other audio actions. I want XF86AudioPlay to lock the the session
> (Lock session) and XF86AudioStop to logout (Log Out). I assigned
> the key codes, but nothing happens when I press the keys.

See below for some vague suggestions.  Meanwhile I've figured out 
how to create actions such as "Mute" and "Volume Up" and assign 
them shortcuts.  It's done in the Control Center under Regional > 
Input Actions.  First press New Group.  If the group appears where 
you don't want it, drag it to before Examples, it will then appear 
as a top-level group at the end.  Then in that group create a New 
Action, give it a name, like "Mute", and select the Action type as 
Keyboard Shortcut -> Command/URL.  Then go to the Keyboard Shortcut 
tab and assign it a shortcut, like XF86AudioMute. Then go to 
Command/URL Settings and fill in the related command, like "dcop 
kmix Mixer0 toggleMute 0".  Press Apply.  And so on for other 
actions.

> It was just strange that the keys stopped working right 
> after the xorg-x11 update to 7.0.

Then it is most likely related.  Maybe the numbers changed, the 
codes that X assigns to XF86AudioPlay and such?  An extract from 
xev for some of the extra keys on my Logitech keyboard (this is for 
Xorg 6.8, which I'm still using, so you might be able to check 
whether in Xorg 7.0 the keysyms changed):

    keycode 178 (keysym 0x1008ff18, XF86HomePage),
    keycode 160 (keysym 0x1008ff12, XF86AudioMute),
    keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume),
    keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume),

But maybe KDE is looking in the old place /usr/lib/X11 for keyboard 
files, which for Xorg 7.0 moved to /usr/share/X11.  It might be 
trying to read /usr/lib/X11/XKeysymDB but not find it.  You could 
try a symlink: ln -s ../../share/X11/XKeysymDB /usr/lib/X11/
Or maybe link to ../share/X11 the entire /usr/lib/X11

Benno
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-07-23 21:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e9r4n1$95g$1@sea.gmane.org>
2006-07-22 21:34 ` [gentoo-user] Migration to xorg-x11 7.0 - Great except for one detail Benno Schulenberg
2006-07-23  7:00   ` [gentoo-user] " Remy Blank
2006-07-23 10:15     ` Benno Schulenberg
     [not found]       ` <e9vka1$uin$1@sea.gmane.org>
2006-07-23 11:51         ` Benno Schulenberg
     [not found]           ` <ea050a$6mj$1@sea.gmane.org>
2006-07-23 21:14             ` Benno Schulenberg [this message]
2006-07-26 16:47               ` Remy Blank
2006-07-27 10:55                 ` Benno Schulenberg
2006-07-27 12:07                   ` Remy Blank
2006-07-28 22:40                     ` Benno Schulenberg

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=200607232314.08606.benno.schulenberg@gmail.com \
    --to=benno.schulenberg@gmail.com \
    --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