Bug 22232

> - KP_Enter to Delete
What's formal reason for that change? Is it working like that in MacOS - or just matter of your preference?

> When i press Eject key it appear as Print key in xev application.
Can you show me the output here please?

> My gnome
> keyboard shortcut set to run print screen application. But when i press eject
> key on my workspace, noting happens.
Can that be a gnome bug? Can you try to use that key in some non-gnome (non-gtk) app?

(In reply to comment #1)
> > - KP_Enter to Delete
> What's formal reason for that change? Is it working like that in MacOS - or
> just matter of your preference?
> 

Two enter keys placed close to each other, look not smart. Its my preferences. I like to see it work in this way.

> > When i press Eject key it appear as Print key in xev application.
> Can you show me the output here please?
> 

First i press Space key, then Eject, then Space key again (you can see some garbage as MappingNotify event produced by eject key):

KeyPress event, serial 27, synthetic NO, window 0x5400001,
    root 0x77, subw 0x0, time 9382253, (103,311), root:(109,374),
    state 0x0, keycode 65 (keysym 0x20, space), same_screen YES,
    XLookupString gives 1 bytes: (20) " "
    XmbLookupString gives 1 bytes: (20) " "
    XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x5400001,
    root 0x77, subw 0x0, time 9382349, (103,311), root:(109,374),
    state 0x0, keycode 65 (keysym 0x20, space), same_screen YES,
    XLookupString gives 1 bytes: (20) " "
    XFilterEvent returns: False

MappingNotify event, serial 30, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

MappingNotify event, serial 30, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 247

KeyPress event, serial 30, synthetic NO, window 0x5400001,
    root 0x77, subw 0x0, time 9382693, (103,311), root:(109,374),
    state 0x0, keycode 169 (keysym 0xff61, Print), same_screen YES,
    XKeysymToKeycode returns keycode: 107
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 32, synthetic NO, window 0x5400001,
    root 0x77, subw 0x0, time 9382757, (103,311), root:(109,374),
    state 0x0, keycode 169 (keysym 0xff61, Print), same_screen YES,
    XKeysymToKeycode returns keycode: 107
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

MappingNotify event, serial 32, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

MappingNotify event, serial 32, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 247

KeyPress event, serial 32, synthetic NO, window 0x5400001,
    root 0x77, subw 0x0, time 9382957, (103,311), root:(109,374),
    state 0x0, keycode 65 (keysym 0x20, space), same_screen YES,
    XLookupString gives 1 bytes: (20) " "
    XmbLookupString gives 1 bytes: (20) " "
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x5400001,
    root 0x77, subw 0x0, time 9383037, (103,311), root:(109,374),
    state 0x0, keycode 65 (keysym 0x20, space), same_screen YES,
    XLookupString gives 1 bytes: (20) " "
    XFilterEvent returns: False


> > My gnome
> > keyboard shortcut set to run print screen application. But when i press eject
> > key on my workspace, noting happens.
> Can that be a gnome bug? Can you try to use that key in some non-gnome
> (non-gtk) app?
> 

I do not understand what do you predict. Which application you suggest to run? Some in global key binding, or some independent application? or what?

> Two enter keys placed close to each other, look not smart. Its my preferences.
> I like to see it work in this way.
Well, IMO it is too exotic and personal, I'd live it to xmodmap...

> KeyPress event, serial 30, synthetic NO, window 0x5400001,
>     root 0x77, subw 0x0, time 9382693, (103,311), root:(109,374),
>     state 0x0, keycode 169 (keysym 0xff61, Print), same_screen YES,
>     XKeysymToKeycode returns keycode: 107
>     XLookupString gives 0 bytes: 
>     XmbLookupString gives 0 bytes: 
>     XFilterEvent returns: False
That looks perfectly correct. I guess, it is not XKB.

> I do not understand what do you predict. Which application you suggest to run?
> Some in global key binding, or some independent application? or what?
Well, what I'd do is run X without GNOME, with some simple window manager where all keybindings can be configured directly in the text file (for example, icewm).

Alternatively I would look again into gnome-keybinding-properties, trying to assign the key to the "Take screenshot" function. There, press your Eject key - whether g-k-p sees it and how it displays the key name.

(In reply to comment #3)
> > Two enter keys placed close to each other, look not smart. Its my preferences.
> > I like to see it work in this way.
> Well, IMO it is too exotic and personal, I'd live it to xmodmap...
> 

I made small researching about this problem, xmodmap works buggly. As i suspect you can read russian, here is full article about my research in my blog: http://blog.axet.ru/2009/06/keyboard-mapping-trough-layout-options.html.

In short: xmodmap make wrong mapping for keymodifers, here is only one way to do it: by layout options. Unfortunate, layout options do not solve last problem: mapping eject key to print key.

> > KeyPress event, serial 30, synthetic NO, window 0x5400001,
> >     root 0x77, subw 0x0, time 9382693, (103,311), root:(109,374),
> >     state 0x0, keycode 169 (keysym 0xff61, Print), same_screen YES,
> >     XKeysymToKeycode returns keycode: 107
> >     XLookupString gives 0 bytes: 
> >     XmbLookupString gives 0 bytes: 
> >     XFilterEvent returns: False
> That looks perfectly correct. I guess, it is not XKB.
> 
> > I do not understand what do you predict. Which application you suggest to run?
> > Some in global key binding, or some independent application? or what?
> Well, what I'd do is run X without GNOME, with some simple window manager where
> all keybindings can be configured directly in the text file (for example,
> icewm).

I will try. +

> 
> Alternatively I would look again into gnome-keybinding-properties, trying to
> assign the key to the "Take screenshot" function. There, press your Eject key -
> whether g-k-p sees it and how it displays the key name.
> 

Its detected as "Print" key :)

I'm not found Layout options under Xfce 4 but when i applied xmodmap file with similar mapping algorithm i got no print key working (alt/win/enter keys works)

keycode 64 = Super_L
keycode 133 = Alt_L
keycode 134 = Alt_R
keycode 104 = Delete
keycode 169 = Print Sys_Req


Is it answer to your question or not?

KDE has Layout options and Print key also does not work. (of course it works when i run xev)

May be problem related to some X11 component, not to xkeyboard-config. I dont know.

Enter->Delete map is very useful same useful as Alt/Win behafiour. And i hope it will be included in next release.

> http://blog.axet.ru/2009/06/keyboard-mapping-trough-layout-options.html.
I read that, thanks. I must admit, your patch is good quality;)

> In short: xmodmap make wrong mapping for keymodifers, 
???? Why would you need modifiers for the Delete key?

> do it: by layout options. Unfortunate, layout options do not solve last
> problem: mapping eject key to print key.
Yes, that's really mystery to me. All my life I trusted xev...

Ok, another thing try. If you map it (using XKB) as, say, ... XF86AudioPlay - will it work?

(In reply to comment #7)

> > In short: xmodmap make wrong mapping for keymodifers, 
> ???? Why would you need modifiers for the Delete key?

xmodmap dosn't work correctly with alt/win behavior. enter->del is ok.

> > do it: by layout options. Unfortunate, layout options do not solve last
> > problem: mapping eject key to print key.
> Yes, that's really mystery to me. All my life I trusted xev...
> 
> Ok, another thing try. If you map it (using XKB) as, say, ... XF86AudioPlay -
> will it work?
> 

yes :) i tried with either Enter -> XF86AudioPlay, Eject -> XF86AudioPlay. Booth works fine.

> xmodmap dosn't work correctly with alt/win behavior. enter->del is ok.
Ok, so alt/win you can currently fix using xkb options. I'd leave Enter->del to xmodmap, if you don't mind. The real problem now is eject->print.

> > Ok, another thing try. If you map it (using XKB) as, say, ... XF86AudioPlay -
> > will it work?
> yes :) i tried with either Enter -> XF86AudioPlay, Eject -> XF86AudioPlay.
> Booth works fine.

So, you're saying Eject->Print does not work, while Eject -> XF86AudioPlay works fine, right? Could you please do "xkbcomp :0 -xkb out.xkb" for two situations: when Eject is mapped to Print, when Eject is mapped to AudioPlay.

(In reply to comment #9)
> > xmodmap dosn't work correctly with alt/win behavior. enter->del is ok.
> Ok, so alt/win you can currently fix using xkb options. I'd leave Enter->del to
> xmodmap, if you don't mind. The real problem now is eject->print.
> 

right

> > > Ok, another thing try. If you map it (using XKB) as, say, ... XF86AudioPlay -
> > > will it work?
> > yes :) i tried with either Enter -> XF86AudioPlay, Eject -> XF86AudioPlay.
> > Booth works fine.
> 
> So, you're saying Eject->Print does not work, while Eject -> XF86AudioPlay
> works fine, right?

right

Created attachment 26750 [details]
simple print

Created attachment 26751 [details]
play button

Created attachment 26753 [details]
full print

full print also does not work

[axet@axet-laptop ~]$ xkbcomp :0 -xkb out-print2.xkb
Warning:          Could not load keyboard geometry for :0
                  BadAlloc (insufficient resources for operation)
                  Resulting keymap file will not describe geometry
[axet@axet-laptop ~]$ 

> Warning:          Could not load keyboard geometry for :0
>                   BadAlloc (insufficient resources for operation)
>                   Resulting keymap file will not describe geometry
Oops. That's a bad sign. It seems something inside XKB (in X server) is broken (not fully initialized).

out-print2 and out-play are practically identical (and out.xkb is basically same - it just has the geometry part). My guess would be that it is something inside X server. So, let's ask Xorg input folks...

(In reply to comment #15)
> > Warning:          Could not load keyboard geometry for :0
> >                   BadAlloc (insufficient resources for operation)
> >                   Resulting keymap file will not describe geometry
> Oops. That's a bad sign. It seems something inside XKB (in X server) is broken
> (not fully initialized).

fwiw, that was a bug somewhere in XKB, uninitialized variable. I haven't seen this error for a while, it got fixed a while back. Don't ask me which commit though :)

Problem still here. Now i switched to Fedora 12 (rawhide version) with last X server. Old problem persist, but with other symptoms.

Layout options only affect on xserver, and window manager. I able to switch windows by my new Alt key (old super). But i unable to use new Alt to switch keyboard layout. So, new mapping ignored by keyboard switcher (guy who added through gnome pannel, as "add to panel" command)

xmodmap changes, recognized only by xev utitlity. keymodifiers ( i change my right super to right alt) wont accepted by application. So, i unable to use Right Alt+Left key in firefox to switch backward link.

(In reply to comment #17)

my previous comment indicates some duplicate of keymodifiers in x-server system. xserver use one keymodifers map, application use other. can some one confirm it?

*** Bug 17755 has been marked as a duplicate of this bug. ***

Hi,
Sorry for the delay on answering this one.

So, as far as I can tell, there are three disparate bugs here:
    * Spurious BadAlloc error from xkbcomp about geometry: this is both completely harmless and already fixed upstream, so no problem. :)
    * Map Eject key to Print key but nothing happens: this is almost certainly a GNOME bug - it was buggy for a long time in this respect (although so was the X server, to be fair).  It was finally fixed about a year ago; can you confirm that this still occurs? The MappingNotify from xev indicates that another client does actually have that key grabbed.
    * xmodmap breaks with modifiers: unfortunately, I can't read Russian - can you or Sergey please translate?

Thanks.

(In reply to comment #20)
>     * xmodmap breaks with modifiers: unfortunately, I can't read Russian - can
> you or Sergey please translate?

Actually, your blog doesn't appear to describe the problem with xmodmap at all.

Can you still reproduce this? If so, can you please provide more information (e.g. exact xmodmap recipe, expected result, actual result, output of `xkbcomp -xkb :0 -` from both before and after), as well as the X server version you're using?

Assuming this one is fixed now.