Xorg crashed with SIGSEGV in xf86nameCompare()

[Nat Taylor]

After the upgrade to 10.10 on a lenovo s10-3t that had the touchscreen working (as described on the forums and at blarneyrabble.wordpress.com) I can only boot into the old kernel and get a black screen when booting into the new kernel. The live usb works fine. The error is from the old lucid kernel

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-core 2:1.9.0-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
NonfreeKernelModules: wl
Architecture: i386
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1024x600
 edid-base64: AP///////wAGr9IjAAAAAAATAQSQFg14Aitpl1dVlikhT1QAAAABAQEBAQEBAQEBAQEBAQEBsBMAQEFYGSAYiDEA330AAAAYAAAADwAAAAAAAAAAAAAAAAAgAAAA/gBBVU8KICAgICAgICAgAAAA/gBCMTAxQVcwMiBWMyAKALg=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
Date: Tue Sep 14 14:27:11 2010
DkmsStatus:
 bcmwl, 5.60.48.36+bdcom, 2.6.35-19-generic, i686: installed
 bcmwl, 5.60.48.36+bdcom, 2.6.32-24-generic, i686: installed
 bcmwl, 5.60.48.36+bdcom, 2.6.35-21-generic, i686: installed
ExecutablePath: /usr/bin/Xorg
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
MachineType: LENOVO 20040M18
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=a9aea226-0fbf-4894-b146-f229751a5e43 ro crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcCmdline: /usr/bin/X :0 -nr -verbose -auth /var/run/gdm/auth-for-gdm-Hp71yx/database -nolisten tcp vt7
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x80c2387 <DeleteInputDeviceRequest+87>: mov 0x10(%edx),%eax
 PC (0x080c2387) ok
 source "0x10(%edx)" (0x00000021) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
 xf86nameCompare ()
 xf86findOption ()
 xf86findOptionValue ()
 ?? ()
 ?? ()
Title: Xorg crashed with SIGSEGV in xf86nameCompare()
UserGroups:

dmi.bios.date: 12/11/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 24CN18WW
dmi.board.name: Caucasus2
dmi.board.vendor: LENOVO
dmi.board.version: Rev 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Lenovo
dmi.chassis.version: Rev 1.0
dmi.modalias: dmi:bvnLENOVO:bvr24CN18WW:bd12/11/2009:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
dmi.product.name: 20040M18
dmi.product.version: Lenovo Ideapad S10-3t
dmi.sys.vendor: LENOVO
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.32-24-generic

[Apport retracing service (apport)]

StacktraceTop:
 xf86nameCompare (
 xf86findOption (list=0x9eb2828, name=0x81df621 "Device")
 xf86findOptionValue (list=0x2ad3f0, name=0x81df621 "Device")
 ParseOptionValue (scrnIndex=<value optimized out>,
 LookupStrOption (optlist=<value optimized out>,

[bugbot (bugbot)]

Hey Nat,

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.