Andreas Hübner <[EMAIL PROTECTED]> wrote: > Hi Ben, > > On Mon, Mar 26, 2007 at 12:26:39AM +0100, Ben Hutchings wrote: > > I am the new maintainer for ion3. I have seen this sort of problem but > > only occasionally, not consistently. Which key are you using as Mod1? > > xmodmap: up to 3 keys per modifier, (keycodes in parentheses): > > shift Shift_L (0x32), Shift_R (0x3e) > lock Caps_Lock (0x25) > control Control_L (0x42), Control_R (0x6d) > mod1 Alt_L (0x40), Alt_L (0x7d), Meta_L (0x9c) > mod2 Num_Lock (0x4d) > mod3 > mod4 Super_L (0x7f), Hyper_L (0x80) > mod5 Mode_switch (0x5d), ISO_Level3_Shift (0x71), ISO_Level3_Shift > (0x7c)
I didn't notice it before, but there is a FAQ that seems relevant: <http://modeemi.fi/~tuomov/ion/faq/entries/Modifier_releases.html>. You don't use mod4, but you have two Alt_L keys listed for mod1. I have the same misconfiguration, though as I said I don't often see the problem. You should be able to fix this by running: xmodmap -e 'keycode 0x7D =' If you use gnome-settings-daemon, you can add the "keycode 0x7D =" to ~/.xmodmap-$(hostname) and it will be applied in every X session; otherwise you can probably work out how to include it in X session startup. Please let me know whether this works for you. Ben. -- Ben Hutchings Life would be so much easier if we could look at the source code.
signature.asc
Description: This is a digitally signed message part
