https://bugzilla.novell.com/show_bug.cgi?id=723777
https://bugzilla.novell.com/show_bug.cgi?id=723777#c11
--- Comment #11 from Egbert Eich
to keep the chance to catch the race - attach gdb to the running X :0 and set a breakpoint to the evdev stuff to get some more info why it runns into that code...
This will most likely also work. You may try Stefan's idea. This however doesn't bring us much closer to the resolution of this bug. I'm going to build an evdev module with debug symbols for you. So when you get the crash I can use the offset to find where it is crashing. With a bit of luck the Xserver may already dump the function that's crashing. Looks like you are using an x86_64 image, so I will build evdev for this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.