keycode  65 = space 0x010000a0 0x010000a0 0x0100200b 

also whitespace (unicode x a0) isn't known by gnome. OO brings only a mark. kate does the right thing...

Das geschütze Leerzeichen (unicode x a0) wird von gnome auch nicht erfasst. OO bringt ein Kästchen, kate kann damit umgehen!

Moving to correct product/component

Gnome respect user's xmodmap files. As long as their names are in the gconf list
/desktop/gnome/peripherals/keyboard/general/update_handlers

http://bugzilla.gnome.org/show_bug.cgi?id=398722

I think, gnome should respect xmodmap always! 

Espezially strange is, that it respects some changes but others not!

So it is still a bug for me, because as user i can run xmodmap but as user i have no write-access to /etc/opt/gnome/gconf/gconf.xml.schemas/schemas/desktop/gnome/peripherals/keyboard/general/%gconf.xml

So how the names of my xmodmap-files could come to this gconf list?

Or is it possible to put a gconf in the users home? (How?)

Btw - please give an example, how it should be done (having write access), for files ~/xmodmap.example1 ~/xmodmap.example2 - in my /etc/opt/gnome/gconf/gconf.xml.schemas/schemas/desktop/gnome/peripherals/keyboard/general/%gconf.xml
I find only this part:

        <entry name="update_handlers" mtime="1168114624" type="schema" stype="list" owner="gnome" list_type="string">
                <local_schema locale="pt" short_desc="Manipuladores de Actualização do Teclado">
                        <longdesc>Uma colecção de scripts a executar sempre que o estado do teclado é relido. Útil para reaplicar ajustamentos baseados no xmodmap</longdesc>
                </local_schema>

[...snip...]

        </entry>

Werner, as user you should not modify gconf files directly. Please use gconftool or gconf-editor. And I cannot give you example in terms of xml - please use the tools provided by gconf - and most probably you'll find you do not have to modify anything in /etc.

Will it work for you?

gnome respects xmodmap - it just has no idea which files to use in the user directory.

> Will it work for you?

I'll try as soon as possible. Thanks for the hint.

[
But why doesn't work just 
# xmodmap ~/.Xmodmap.modified
?

(Why gnome doesn't use X's xmodmap?)

Especially I wonder about the fact, that some modifications work and some don't.
]

How GNOME is supposed to find that the name of your file is .Xmodmap.modified? We do not want to hardcode anything like that - so we added the list into gconf where you can mention any of these files. And then gnome will do "xmodmap (whatever your filename is)"

1.
> How GNOME is supposed to find that the name of your file is .Xmodmap.modified?

Why it should - I do the 
xmodmap ~/.Xmodmap.bla 
command.
But gnome ignores it (partly).

2.
And I checked the gconf and my xmodmap-files are listed there. 
But all the problems described above occure. (and didn't occure in suse10.0)
So gnome seems really to ignore (partly) my xmodmap and that is bad and I think it's really a bug and should be solved.
I don't want to open the main-menu with the right window-key and all the other problems.

1. Gnome has its own keyboard management code. It initialized keyboard configuration _from_ the_scratch_ - so whatever you do before the gnome session starts is ignored. The only way for you to ask gnome use your xmodmap file - but it in the gconf key mentioned above.

2. Gnome has no way to ignore _parts_ of your xmodmap file. It just executes xmodmap passing the filename as parameter.

(In reply to comment #9)
> 1. Gnome has its own keyboard management code. It initialized keyboard
> configuration _from_ the_scratch_ - so whatever you do before the gnome session
> starts is ignored. 

I did the command 
xmodmap ~/.Xmodmap.bla 
in the gnome-terminal and I can switch xmodmaps that way. Only all the problems I described above occur.

> The only way for you to ask gnome use your xmodmap file -
> but it in the gconf key mentioned above.

I did this, but the line
keycode 116 = ISO_Level3_Shift
is still ignored - the right windows-key still opens the main menu.

What if not gnome can be responsible for that?

The other problems maybe concern not the gnome-keyboard-section but gedit and other apps.

> 2. Gnome has no way to ignore _parts_ of your xmodmap file. It just executes
> xmodmap passing the filename as parameter.

So gnome does the same thing as I do.

But why can I change the behaviour of key "menu-key" (in the right of the right "window-key") but not of key 116 (right "window-key")?

So how to put *any* function/letter/command on the right window-key (keycode 116) instead of "open 'main-menu'"?

Who can help?

Is that related to this bug?

In any case, the key should only open the main menu if that is configured in the keybindings capplet. If you don't want it, just disable it there.

> I did this, but the line
> keycode 116 = ISO_Level3_Shift
> is still ignored - the right windows-key still opens the main menu.
> 
> What if not gnome can be responsible for that?
I do not know. GNOME really cannot be responsible for that - it does not even check whether the file is there (I do not talk about opening it). GNOME (namely g-s-d) just composes the command line for xmodmap - and launches it. As simple as that. You can check it by replacing xmodmap with your own script and looking at parameters (for example, use command line

echo "$@" > /tmp/xmodmap.params

> But why can I change the behaviour of key "menu-key" (in the right of the right
> "window-key") but not of key 116 (right "window-key")?
Ask xmodmap maintainers, of course. Also, ask people handling gnome keybindings. I think you should open separate bug about it (but first check whether this bug is already reported). Let's not mix several issues together, ok?

*** This bug has been marked as a duplicate of 413017 ***