On Sun, Dec 16, 2007 at 07:57:23PM +1030, Ron wrote: > > Andreas, have you seen the discussion that was cc'd to the bts from > linuxwacom-discuss about this? Is what you are seeing the same > issue, or is this something else we should also be discussing there > as well?
It should be the same issue, maybe I should have cc'd it to linuxwacom-discuss, too. This thread isn't visible in the archive for linuxwacom-discuss on sf.net, so I can't see what else was mentioned there. I've got even more for you, maybe you can forward it to the appropriate thread. Further up, Magnus Vigerlöf mentioned: | In XkbIndicatorsToUpdate (./xkb/xkbLEDs.c:56) the call to XkbFindSrvLedInfo | can potentially return NULL, which is not an uncommon cause for a SEGV. My session starts up with numlock enabled. When using my workaround of switching to console during session startup, I noticed that the numlock LED on the keyboard is inverted. Apparantly the unavailability of the keyboard to X when in console circumvents the initialization of the LEDs and thus some bug in that code path. I am using the uim input method, if that matters. -- Andreas Bombe <[EMAIL PROTECTED]> GPG key 0x04880A44
