Xorg crashed with SIGSEGV in xf86SetCursor()

Bug #450969 reported by datakid
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Expired
Medium
Unassigned

Bug Description

eeepc, 1000H, Karmic

I did ctrl-alt-f2 to get to another virtual terminal while waiting for my desktop to appear. ie I had just entered my password to login, was watching the splash screen and flipped to f2. I flipped back to f7 and boom! had to login again.

When I logged in again, I got the crash report....

ProblemType: Crash
Architecture: i386
Date: Wed Oct 14 15:15:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/Xorg
MachineType: ASUSTeK Computer INC. 1000H
Package: xserver-xorg-core 2:1.6.4-2ubuntu2
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=b83f85b1-e17a-448e-a4d1-7bd7370d51c9 ro priority=low quiet splash
ProcCmdline: /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-emuIxH/database -nolisten tcp vt7
ProcEnviron:
 LANG=en_AU.UTF-8
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.46-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu3
SegvAnalysis:
 Segfault happened at: 0x80fa3c0: mov (%ebx,%eax,4),%edx
 PC (0x080fa3c0) ok
 source "(%ebx,%eax,4)" (0x0073f2e8) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
 ?? ()
 ?? ()
 xf86SetCursor ()
 ?? ()
 ?? ()
Tags: ubuntu-unr
Title: Xorg crashed with SIGSEGV in xf86SetCursor()
Uname: Linux 2.6.31-14-generic i686
UserGroups:

dmi.bios.date: 08/01/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1005
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1000H
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1005:bd08/01/2008:svnASUSTeKComputerINC.:pn1000H:pvrx.x:rvnASUSTeKComputerINC.:rn1000H:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1000H
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-14-generic

Revision history for this message
datakid (datakid) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:RealizeCursorInterleave0 (infoPtr=0x89f11d0, pCurs=0x8c2fb70)
RealizeCursorInterleave64 (infoPtr=0x89f11d0,
xf86SetCursor (pScreen=0x89f0ba8, pCurs=0x8c2fb70, x=532,
xf86CursorSetCursor (pDev=0x8b3f628, pScreen=0x89f0ba8,
xf86CursorEnableDisableFBAccess (index=0, enable=1)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Bryce Harrington (bryce)
tags: added: crash
Changed in xorg-server (Ubuntu):
status: New → Confirmed
Timo Aaltonen (tjaalton)
visibility: private → public
Bryce Harrington (bryce)
tags: added: karmic
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi datakid,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 450969

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 450969 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/450969

Changed in xorg-server (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-retested-on-lucid-by-june
Revision history for this message
Bryce Harrington (bryce) wrote :

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.

Changed in xorg-server (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.