Xorg crashed with SIGSEGV in dixLookupPrivate()

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

Bug Description

Steps to Reproduce:
1. User 1 logs off the laptop (Dell Latitude D810 w/1GB of RAM).
2. Closes laptop lid.
3. User 2 opens lid of the laptop. A black screen is displayed with large letters on the right side.
4. User 2 selects several keys with no reaction from the user interface (UI).
5. When user 2 selects the "Enter" key, the UI presents Login screen.

Expected Behavior:
When the user selects the any key the UI should display the login screen.

Actual Behavior:
As stated in step 4, the UI did not react to selecting any keys except for the "Enter" key.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Nov 1 15:10:27 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/Xorg
MachineType: Dell Inc. Latitude D810
Package: xserver-xorg-core 2:1.6.4-2ubuntu4
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=2952038e-ec1c-4351-862e-ece7cadd67af ro quiet splash
ProcCmdline: /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-OKkhwZ/database -nolisten tcp
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu7
 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+git20090929.7968e1fb-0ubuntu1
SegvAnalysis:
 Segfault happened at: 0x80730b9 <dixLookupPrivate+41>: cmp (%esi),%edx
 PC (0x080730b9) ok
 source "(%esi)" (0x5f504741) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xorg-server
StacktraceTop:
 dixLookupPrivate ()
 ?? ()
 ?? ()
 ?? ()
 xf86Wakeup ()
Title: Xorg crashed with SIGSEGV in dixLookupPrivate()
Uname: Linux 2.6.31-14-generic i686
UserGroups:

dmi.bios.date: 03/20/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0D8006
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd03/20/2006:svnDellInc.:pnLatitudeD810:pvr:rvnDellInc.:rn0D8006:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D810
dmi.sys.vendor: Dell Inc.
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-14-generic

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

StacktraceTop:dixLookupPrivate (privates=0x8a439c0, key=0x81f70c0)
miDCPutUpCursor (pDev=0x896ea40, pScreen=0x8812690,
miSpriteRestoreCursor (pDev=<value optimized out>,
xf86CursorEnableDisableFBAccess (index=0, enable=1)
xf86Wakeup (blockData=0x0, err=-1, pReadmask=0x81f7440)

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 ZeroC00l,

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 469619

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 469619 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/469619

Changed in xorg-server (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-retested-on-lucid-by-june
Revision history for this message
ZeroC00l (lawrencemcnaughton) wrote : Re: [Bug 469619] Re: Xorg crashed with SIGSEGV in dixLookupPrivate()
Download full text (4.1 KiB)

This defect is no longer reproducible.

On Tue, May 4, 2010 at 3:40 PM, Bryce Harrington
<email address hidden>wrote:

> [This is an automatic notification.]
>
> Hi ZeroC00l,
>
> 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 469619
>
> 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 469619 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/469619
>
>
> ** Changed in: xorg-server (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Tags added: needs-retested-on-lucid-by-june
>
> --
> Xorg crashed with SIGSEGV in dixLookupPrivate()
> https://bugs.launchpad.net/bugs/469619
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “xorg-server” package in Ubuntu: Incomplete
>
> Bug description:
> Steps to Reproduce:
> 1. User 1 logs off the laptop (Dell Latitude D810 w/1GB of RAM).
> 2. Closes laptop lid.
> 3. User 2 opens lid of the laptop. A black screen is displayed with large
> letters on the right side.
> 4. User 2 selects several keys with no reaction from the user interface
> (UI).
> 5. When user 2 selects the "Enter" key, the UI presents Login screen.
>
> Expected Behavior:
> When the user selects the any key the UI should display the login screen.
>
> Actual Behavior:
> As stated in step 4, the UI did not react to selecting any keys except for
> the "Enter" key.
>
> ProblemType: Crash
> Architecture: i386
> CrashCounter: 1
> Date: Sun Nov 1 15:10:27 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/Xorg
> MachineType: Dell Inc. Latitude D810
> Package: xserver-xorg-core 2:1.6.4-2ubuntu4
> PccardctlIdent:
> Socket 0:
> no product info available
> PccardctlStatus:
> Socket 0:
> no card
> ProcCmdLine: root=UUID=2952038e-ec1c-4351-862e-ece7cadd67af ro quiet splash
> ProcCmdline: /usr/bin/X :0 -br -verbose -auth
> /var/run/gdm/auth-for-gdm-OKkhwZ/database -nolisten tcp
> ProcEnviron:
> LANG=en_US.UTF-8
> PATH=(custom, no user)
> ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
> RelatedPackageVersions:
> xserver-xorg 1:7.4+3ubuntu7
> 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+git20090929.7968e1fb-0ubuntu1
> SegvAnalysis:
> Segfault happened at: 0x80730b9 <dixLookupPrivate+41>: cmp (%esi),%edx
> PC (0x080730b9) ok
> source "(%esi)" (0x5f504741) not located in a known VMA regi...

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.]

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.

Other bug subscribers

Remote bug watches

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