ubuntu-x-swat team mailing list archive

[marco caminati <spam.caminati@xxxxxxxxx>]

Here I have the same bug:

X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.33.3-tinycore i686 
Current Operating System: Linux box 2.6.33.3-tinycore #2012 SMP Wed May 12 17:05:42 EEST 2010 i686
Kernel command line: multivt showapps superuser text norestore
Build Date: 28 May 2010  06:50:29PM

My .xmodmap file:

xmodmap -e "remove lock = Caps_Lock"
xmodmap -e "add Mod3 = Caps_Lock"

However, I found that the problem doesn't necessarily throw the error
message quoted in original report. After a reboot the one-liner:

DISPLAY=:0.0 xmodmap -e "clear lock"

will silently fail from deallocating CapsLock. 
More precisely, if I issue it from a non-X console, it has no effect, while from a xterm it works. I compared the environment variables from within the two consoles. No significant differences (only DISPLAY and TERM variables). I also took care of equaling the environment variables of the console to that of the xterm, no way. Weird.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
https://bugs.launchpad.net/bugs/524774

Title:
  xmodmap failure BadValue error, 118 (X_SetModifierMapping)