On tisdag 18 december 2007, Magnus Vigerlöf wrote: [...] > > > 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. > > Try the following patch, it *is* the wrong place to fix this imho, but > it's the smallest part to recompile. If it doesn't crash, look for output > starting with 'Wacom: xf86WcmKbdLedCallback' in the log. If you find it > you had a Null-ptr deref and that should be considered a bug in the > xserver. [...]
Hi, Linuxwacom 0.7.9-6 is now available. Included is a fix for this issue, it is the easiest place to change to avoid the crash it seems. I had a look at the place in the xserver source where the crash happened, but I could not see any recent changes that should cause the crash only in Xserver 1.4. I hope this solves this crash for everybody. Cheers Magnus
