This is intermittent, occurs very seldom. 0: /usr/X11/bin/amd64/Xorg'xorg_backtrace+0x33 [0x4b7363] 1: /usr/X11/bin/amd64/Xorg'xf86SigHandler+0x86 [0x4e2a86] 2: /lib/amd64/libc.so.1'__sighndlr+0x6 [0xfffffd7fff2be066] 3: /lib/amd64/libc.so.1'call_user_handler+0x2a7 [0xfffffd7fff2b0f0f] 4: /usr/X11/bin/amd64/Xorg'TryClientEvents+0xad [0x49192d] 5: /usr/X11/bin/amd64/Xorg'DeliverEventsToWindow+0x1a2 [0x491bc2] 6: /usr/X11/bin/amd64/Xorg'DeliverDeviceEvents+0x24a [0x49265a] 7: /usr/X11/bin/amd64/Xorg'ProcessOtherEvent+0x408 [0x59fa28] 8: /usr/X11/bin/amd64/Xorg'ProcessKeyboardEvent+0xc4 [0x5cb224] 9: /usr/X11/bin/amd64/Xorg'mieqProcessInputEvents+0x3c3 [0x53ace3] 10: /usr/X11/bin/amd64/Xorg'ProcessInputEvents+0xd [0x4e24ed] 11: /usr/X11/bin/amd64/Xorg'Dispatch+0x108 [0x4819c8] 12: /usr/X11/bin/amd64/Xorg'main+0x6dc [0x49f87c] 13: /usr/X11/bin/amd64/Xorg'0x71fcc [0x471fcc]
This patch was added to catch the segv. pEvents is the first pointer reference in TryClientEvents and the offset is small. --- events.c.orig Mon Oct 5 12:02:59 2009 +++ events.c Mon Oct 5 12:02:30 2009 @@ -1889,6 +1889,9 @@ { if (grab && !SameClient(grab, client)) return -1; /* don't send, but notify caller */ + + if(!pEvents) /* guard for segv */ + return -1; type = pEvents->u.u.type; if (type == MotionNotify) {
please try to find a testcase where this occurs. Just fixing up and "ignoring" the crash isn't enough, we need to know if this has wider repercussions. From the backtrace I can see that it's caused by a key event, that's about as much info as I can tell. Does it happen with the same application each time?
any updates on this? Do you still see this issue Jay?
Claiming this is fixed since I haven't seen this in a while. Please reopen if it's still here
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.