Todd Pytel, le Wed 18 Jan 2012 22:07:10 -0600, a écrit :
> 2) In an untweaked X session, the Num Lock LED works while the Scroll
> Lock one does not. Both keys register in xev output.
>
> 3) After "xmodmap -e 'add mod3 = Scroll_Lock'", the Scroll Lock LED
> works. But it still doesn't trigger the
On 12-01-18 04:21 PM, Semeraro, B David wrote:
> Hello,
>
> I am trying to perform a modular build following the directions from
> this site:
>
> http://www.x.org/wiki/ModularDevelopersGuide#Introduction
Alan is correct, libXau is the first module in the list to require
libtool. You may possibly fi
On Thu, 2012-01-19 at 10:34 +0100, Samuel Thibault wrote:
> These are extremely surprising. I'd have thought that KVM uses the
> keyboard *keypresses*, not the LED changes, to achieve the switch...
Especially since it's not *just* the LED's that matter - otherwise it
would work after xmodmap. So,
Todd Pytel, le Thu 19 Jan 2012 07:41:14 -0600, a écrit :
> > You could try to use strace to check the system call difference between
> > lighting scroll lock through the key and through xset, but in principle
> > there is none, thus the surprise with 3) vs 4) above.
>
> I've straced binaries befor
Hi there Gaetan,
I think there is something whacked with my tools install. I do have libtool
installed but there seems to be some problem with the set up since I am getting
this error. I am going to review my autotools setup and see if I cant find the
problem. I may just have to generate a fres
jumbophut gmail.com> writes:
> A solution would be to set the bits in event.modifierMask to 1 only if
> Xt knows about them. Other bits (13 and 14, used for Xkb) would be
> set to 0 in TMParse.c (that is "don't care" about these bits). The
> modifier "None" then might become slightly misleading
