Xorg crashed with SIGSEGV in XIChangeDeviceProperty()

[mperry]

AFter suspending the laptop, xorg.core crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-core 2:1.9.0-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1024x768 1024x768 800x600 800x600 848x480 720x480 640x480 640x480
 edid-base64: AP///////wAwriBAAAAAADIPAQOAHBV46jSFklVTkiYgUFQhCAABAQEBAQEBAQEBAQEBAQEBZBkAQEEAJjAYiDYAHdYQAAAYKBUAQEEAJjAYiDYAHdYQAAAYAAAADwBhQzJhQygPAQANrwcUAAAA/gBOMTQxWEMtTDAxCiAgAEU=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
Date: Sun Sep 19 16:14:09 2010
DkmsStatus:
 virtualbox-ose, 3.2.8, 2.6.35-21-generic, i686: installed
 virtualbox-ose, 3.2.8, 2.6.35-22-generic, i686: installed
ExecutablePath: /usr/bin/Xorg
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100911)
MachineType: LENOVO 200743U
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=c33a0411-cc89-40a3-aa75-edebeb237a74 ro quiet splash
ProcCmdline: /usr/bin/X :0 -nr -verbose -auth /var/run/gdm/auth-for-gdm-TldUcd/database -nolisten tcp vt7
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x8e9dcc: mov 0x1b0(%edx),%eax
 PC (0x008e9dcc) ok
 source "0x1b0(%edx)" (0x000001b0) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
 ?? () from /usr/lib/xorg/modules/input/synaptics_drv.so
 XIChangeDeviceProperty ()
 ?? ()
 ?? ()
 ?? ()
Title: Xorg crashed with SIGSEGV in XIChangeDeviceProperty()
UserGroups:

dmi.bios.date: 04/01/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ETE6WW (2.26 )
dmi.board.name: 200743U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr79ETE6WW(2.26):bd04/01/2010:svnLENOVO:pn200743U:pvrThinkPadT60:rvnLENOVO:rn200743U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 200743U
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-22-generic

[Apport retracing service (apport)]

StacktraceTop:
 SetProperty (dev=0x8fee6f0, property=131, prop=0xbfd9fa90,
 XIChangeDeviceProperty (dev=0x8fee6f0, property=131,
 ProcXChangeDeviceProperty (client=0x8c7fff8)
 ProcIDispatch (client=0xbfd9fa90) at ../../Xi/extinit.c:416
 Dispatch () at ../../dix/dispatch.c:432

[bugbot (bugbot)]

Hey mperry,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.