On Mon, Nov 3, 2008 at 4:12 PM, Marcelo Boveto Shima <<email address hidden>
> wrote:
>
> On Sat, Nov 1, 2008 at 3:57 PM, Martin Emrich <email address hidden> wrote:
>
>> I tried it with Gnome, KDE, IceWM and even a bare xterm on the server
>> side, all with the same effect. So I don't think it has anything to do
>> with the chosen desktop environment.
>>
>
> Maybe, but, using an intrepid client and a hardy (or older) server:
> 1) Start a xterm session with "new virtual desktop".
> 2) Execute gnome-session on xtem.
> 3) Change the keyboard model.
> 4) Kill the gnome-session.
> 5) Start a new gnome-session on the same xterm.
> 6) The keyboard now works as spected
>
> So I really think it is a gnome bug, maybe gnome-control-center, maybe
> gnome-settings-daemon
> or even gnome-session.
>
On Mon, Nov 3, 2008 at 4:12 PM, Marcelo Boveto Shima <<email address hidden>
> wrote:
> center, maybe daemon
> On Sat, Nov 1, 2008 at 3:57 PM, Martin Emrich <email address hidden> wrote:
>
>> I tried it with Gnome, KDE, IceWM and even a bare xterm on the server
>> side, all with the same effect. So I don't think it has anything to do
>> with the chosen desktop environment.
>>
>
> Maybe, but, using an intrepid client and a hardy (or older) server:
> 1) Start a xterm session with "new virtual desktop".
> 2) Execute gnome-session on xtem.
> 3) Change the keyboard model.
> 4) Kill the gnome-session.
> 5) Start a new gnome-session on the same xterm.
> 6) The keyboard now works as spected
>
> So I really think it is a gnome bug, maybe gnome-control-
> gnome-settings-
> or even gnome-session.
>
I just found the workaround:
$ killall metacity
This should reset the hotkeys table.