5:17 a.m.
Hi,
I'd like to know where to report problems with key mappings.
On my hardware (Dell Inspiron 6000) there are 'media buttons' (mute,
vol+/-, play, next, prev, stop) which are detected as keypresses with an
unmapped keycode.
I can find the keycodes using xev, then I can map them to something
useful using xmodmap, then compatible applications (eg. rhythmbox) do
the right thing when the buttons are pressed.
The first problem is that the keys are initially unmapped; a secondary
problem is that some controls (eg. volume popup) don't respond to the
volume keys when they probably should.
So, where can I tell someone about this mapping? Which package needs
some extra config? I should be able to provide a patch.
-Cam
--
camilo(a)mesias.co.uk <--
6:44 a.m.
Dnia 27-03-2006, pon o godzinie 12:17 +0100, Cam napisał(a):
The first problem is that the keys are initially unmapped; a
secondary
problem is that some controls (eg. volume popup) don't respond to the
volume keys when they probably should.
1. Write your modmaps to /etc/X11/Xmodmap. I
use
add mod4 = Super_L
add mod4 = Super_R
because Super behavior is broken in Xorg since several years now (it was
long before XFree86 split), pity. I haven't found a way to do it via
GUI. The gnome-keyboard-properties dialog make it work if I go there and
click the option every time I log in. My CLI way is superior and I
recommend it.
2. Maybe offtopic, but I had a problem with volume controls not
responding because of bug in system-config-sound (there's a bug in
bugzilla for it). It breaks the default device in /etc/asound.conf under
some circumstances. If you have two sound cards, maybe that's the
cause :)
Lam
5:45 a.m.
Leszek
> The first problem is that the keys are initially unmapped; a
secondary
> problem is that some controls (eg. volume popup) don't respond to the
> volume keys when they probably should.
1. Write your modmaps to /etc/X11/Xmodmap. I use
Thanks for the reply - yes I can write to xmodmap but should every user
do this?
Couldn't I add a new keyboard type to the system which already includes
the mappings, maybe even have anaconda detect the keyboard?
-Cam
--
camilo(a)mesias.co.uk <--
6:56 a.m.
On Tue, 28 Mar 2006 12:45:28 +0100
Cam <camilo(a)mesias.co.uk> wrote:
>> The first problem is that the keys are initially unmapped; a
secondary
>> problem is that some controls (eg. volume popup) don't respond to the
>> volume keys when they probably should.
> 1. Write your modmaps to /etc/X11/Xmodmap. I use
Thanks for the reply - yes I can write to xmodmap but should every user
do this?
Couldn't I add a new keyboard type to the system which already includes
the mappings, maybe even have anaconda detect the keyboard?
Don't know if this has been mentioned before in the conversation but many
keyboards already have full mappings provided which the user can
select by running gnome-keyboard-properties. Adding additional types
for selection would be helpful.
Sean
3:14 p.m.
sean
Don't know if this has been mentioned before in the conversation
but many
keyboards already have full mappings provided which the user can
select by running gnome-keyboard-properties. Adding additional types
for selection would be helpful.
Now I'm amazed. I stuggled to find the right mappings and put them into
an xmodmap file - only to find that there was a perfectly good 'keyboard
model' hidden in gnome-keyboard-properties. (Thanks Sean!)
I think there are two problems here.
1. the name wasn't intuitive enough: "Laptop/notebook Dell Inspiron
6xxx/8xxx". I might have had a chance if the list was presented as a
hierarchy, or if it was under Dell or Inspiron.
2. it's too easy to choose a working (but incorrect) key model when
installing.
Is this deserving of a bugzilla entry?
-Cam
--
<--
camilo(a)mesias.co.uk
3:30 p.m.
On Wed, 29 Mar 2006 22:14:42 +0100
Cam <camilo(a)mesias.co.uk> wrote:
Now I'm amazed. I stuggled to find the right mappings and put
them into
an xmodmap file - only to find that there was a perfectly good 'keyboard
model' hidden in gnome-keyboard-properties. (Thanks Sean!)
I think there are two problems here.
1. the name wasn't intuitive enough: "Laptop/notebook Dell Inspiron
6xxx/8xxx". I might have had a chance if the list was presented as a
hierarchy, or if it was under Dell or Inspiron.
2. it's too easy to choose a working (but incorrect) key model when
installing.
Is this deserving of a bugzilla entry?
An RFE maybe, although maybe it is more appropriate upstream? I honestly
don't know.
I have run into the problem as well, not knowing which of 10 models actually
matched the keyboard in front of me. Not sure how to make it easier unless
each and every keyboard model can be listed explicitly somehow.
The cat's meow would be to have pictures of each keyboard too; would that
be legal?
Sean
5:31 p.m.
sean
The cat's meow would be to have pictures of each keyboard too;
would that
be legal?
Or... maybe gnome-keyboard-properties would detect that you are running
with a basic keyboard, and ask if you have any media keys... Then asked
you to press 'Play', and as many more keys as it takes to match the
hardware to a map...
-Cam
--
<--
camilo(a)mesias.co.uk
6609
days inactive
6611
days old
6 comments
3 participants
participants (3)
-
Camilo Mesias -
Leszek Matok -
Sean