Xorg crashed with SIGSEGV in FreeClientResources()

[quezacote]

Xorg crashed with SIGSEGV in FreeClientResources()

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-core 2:1.8.99.905-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-14.20-generic 2.6.35
Uname: Linux 2.6.35-14-generic i686
Architecture: i386
DRM.card0.VGA.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 800x600 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 640x480 720x400 720x400
 edid-base64: AP///////wBMLbYSNTFURB4KAQJoHBVw6vuJoVVLlyQRSEz/+AAxWUVZYUABAQEBAQEBAQEB+RUg+DBYHyAgQBMAC8gQAAAeAAAA/QAyeB43/wAKICAgICAgAAAA/ABTL00gNTUwdgogICAgAAAA/wBIWEFONzEyOTYyCiAgAFw=
Date: Wed Aug 11 18:29:49 2010
DkmsStatus:

ExecutablePath: /usr/bin/Xorg
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-14-generic root=UUID=c54a99ed-12fc-4919-9a8d-c9b411b58721 ro vga=792 splash quiet splash
ProcCmdline: /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-1NGVZv/database -nolisten tcp
ProcEnviron:
 LANG=pt_BR.UTF-8
 PATH=(custom, no user)
 LANGUAGE=pt_BR:pt:pt_PT
SegvAnalysis:
 Segfault happened at: 0x93ab63: mov %edi,0x8(%eax)
 PC (0x0093ab63) ok
 source "%edi" ok
 destination "0x8(%eax)" (0xf2c00a46) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
 ?? () from /lib/libc.so.6
 FreeClientResources ()
 FreeAllResources ()
 _start ()
Title: Xorg crashed with SIGSEGV in FreeClientResources()
UserGroups:

dmi.bios.date: 03/20/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0211
dmi.board.name: K8V-MX
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 6
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0211:bd03/20/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerInc.:rnK8V-MX:rvr:cvnChassisManufacture:ct6:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-14-generic

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()
 ProcXUngrabDeviceButton (client=0xa27502)
 DisableDevice (dev=0xa252f50, sendevent=1 '\001')
 RemoveDevice (dev=0xa252f50, sendevent=1 '\001')

[bugbot (bugbot)]

Hey quezacote,

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.