Date: Tue, 3 Aug 2010 22:07:30 +0200 From: Christian Walther <cptsalek@gmail.com> To: stable@freebsd.org Subject: startx/xinit + custom xmodmap messes up session Message-ID: <AANLkTi=-E1rGQD4cQaX1AvmcjrQu4TR=kaxQmPztkips@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi, on my Thinkpad T3I'm using a tiling window manager (stumpwm) and remapped Caps Lock to have an addition modifier key. The systems default modmap is: shift Shift_L (0x32), Shift_R (0x3e) lock Caps_Lock (0x42) control Control_L (0x25), Control_R (0x6d) mod1 Alt_L (0x40), Meta_L (0x9c) mod2 Num_Lock (0x4d) mod3 mod4 Super_L (0x73), Super_R (0x74), Super_L (0x7f), Hyper_L (0x80) mod5 Mode_switch (0x5d), ISO_Level3_Shift (0x71), ISO_Level3_Shift (0x7c) My .xmodmaprc contains the following lines: remove mod4 = Hyper_L remove lock = Caps_Lock keycode 66 = Hyper_L add mod3 = Hyper_L This results in the following xmodmap: shift Shift_L (0x32), Shift_R (0x3e) lock control Control_L (0x25), Control_R (0x6d) mod1 Alt_L (0x40), Meta_L (0x9c) mod2 Num_Lock (0x4d) mod3 Hyper_L (0x42), Hyper_L (0x80) mod4 Super_L (0x73), Super_R (0x74), Super_L (0x7f) mod5 Mode_switch (0x5d), ISO_Level3_Shift (0x71), ISO_Level3_Shift (0x7c) The output of the modified map listed above is what I expected. It works when the session is launched through xdm. However, when I use startx from the command line, for some strange reason xmodmap messes up my session. In this case, the mouse is rendered useless. To make matters worse, when I shutdown X moused is broken too and needs a restart. As I said this doesn't happen with xdm, and it doesn't happen with startx when I don't run xmodmap. My system is running 8.1-RC2, but it happened with 8.0, too. This is not a very important issue for me, because I don't mind running xdm. I just wonder if this bug is known or if this is a case for a bug report. Regards Christian Walther
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=-E1rGQD4cQaX1AvmcjrQu4TR=kaxQmPztkips>