Xorg crashed with SIGSEGV in dixLookupPrivate()

Bug #328937 reported by Jan David Mol
24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Triaged
High
Unassigned

Bug Description

Running Jaunty 9.04. I did not actually notice the crash until the bug report dialog popped up.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/Xorg
Package: xserver-xorg-core 2:1.5.99.902-0ubuntu6
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcVersion: Linux version 2.6.28-7-generic (buildd@yellow) (gcc version 4.3.3 (Ubuntu 4.3.3-3ubuntu2) ) #20-Ubuntu SMP Mon Feb 9 15:42:34 UTC 2009

Signal: 11
SourcePackage: xorg-server
Stacktrace: #0 0x00000000004346ca in dixLookupPrivate ()
StacktraceTop: dixLookupPrivate ()
ThreadStacktrace:

Title: Xorg crashed with SIGSEGV in dixLookupPrivate()
Uname: Linux 2.6.28-7-generic x86_64
UserGroups:

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07)
     Subsystem: Dell Device [1028:024d]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
     Subsystem: Dell Device [1028:024d]

Revision history for this message
Jan David Mol (jjdmol) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:dixLookupPrivate (privates=0x198, key=0x7d96e0)

Changed in xorg-server:
importance: Undecided → Medium
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi jjdmol,

Could you please collect a full backtrace from when this crash occurs? Directions on collecting full backtraces are at https://wiki.ubuntu.com/X/Backtracing

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Changed in xorg-server:
status: New → Incomplete
Bryce Harrington (bryce)
description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

The trace shows it's failing in privates.c

#0 0x00000000004346ca in dixLookupPrivate (privates=0x198, key=0x7d96e0)
    at ../../dix/privates.c:79
 ptr = <value optimized out>

However the code in question doesn't make it clear where the failure is:

static _X_INLINE int
privateExists(PrivateRec **privates, const DevPrivateKey key)
{
    return *key && *privates &&
        (*privates)[0].state > *key &&
        (*privates)[*key].state;
}

Guess the next step for this one is to go upstream. Still would be wonderful to get a more detailed backtrace though.

Changed in xorg-server (Ubuntu):
importance: Medium → High
status: Incomplete → Triaged
Revision history for this message
Tom Jaeger (thjaeger) wrote :
Revision history for this message
frenet (renet-f) wrote : Re: [Bug 328937] Re: Xorg crashed with SIGSEGV in dixLookupPrivate()

I do not think so. I did not remember seeing a second mouse pointer.

F.

On Mon, Mar 30, 2009 at 5:45 AM, Tom Jaeger <email address hidden> wrote:
> Could be this one:
>
> http://bugs.freedesktop.org/show_bug.cgi?id=19034
>
> --
> Xorg crashed with SIGSEGV in dixLookupPrivate()
> https://bugs.launchpad.net/bugs/328937
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “xorg-server” source package in Ubuntu: Triaged
>
> Bug description:
> Running Jaunty 9.04. I did not actually notice the crash until the bug report dialog popped up.
>
> ProblemType: Crash
> Architecture: amd64
> DistroRelease: Ubuntu 9.04
> ExecutablePath: /usr/bin/Xorg
> Package: xserver-xorg-core 2:1.5.99.902-0ubuntu6
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
> ProcEnviron:
>  PATH=(custom, no user)
>  LANG=en_US.UTF-8
> ProcVersion: Linux version 2.6.28-7-generic (buildd@yellow) (gcc version 4.3.3 (Ubuntu 4.3.3-3ubuntu2) ) #20-Ubuntu SMP Mon Feb 9 15:42:34 UTC 2009
>
> Signal: 11
> SourcePackage: xorg-server
> Stacktrace: #0  0x00000000004346ca in dixLookupPrivate ()
> StacktraceTop: dixLookupPrivate ()
> ThreadStacktrace:
>
> Title: Xorg crashed with SIGSEGV in dixLookupPrivate()
> Uname: Linux 2.6.28-7-generic x86_64
> UserGroups:
>
> [lspci]
> 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07)
>        Subsystem: Dell Device [1028:024d]
> 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
>        Subsystem: Dell Device [1028:024d]
>
>

Revision history for this message
Tom Jaeger (thjaeger) wrote :

The second cursor doesn't show up anymore since
http://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.6-branch&id=0d12c44d832b98da10dccc3b8bac7676d8ea2c96,
 but the underlying issue is still there, it's restricted to animated
cursers, though. Were you using any program that uses XInput (gimp,
inkscape, xournal, easystroke...) at the time?

frenet wrote:
> I do not think so. I did not remember seeing a second mouse pointer.
>
> F.
>

Revision history for this message
frenet (renet-f) wrote :

KDE was starting. No memory of what was running. But certainly not
gimp, inkscape nor xournal.

F.

On Mon, Mar 30, 2009 at 5:21 PM, Tom Jaeger <email address hidden> wrote:
> The second cursor doesn't show up anymore since
> http://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.6-branch&id=0d12c44d832b98da10dccc3b8bac7676d8ea2c96,
>  but the underlying issue is still there, it's restricted to animated
> cursers, though.  Were you using any program that uses XInput (gimp,
> inkscape, xournal, easystroke...) at the time?
>
> frenet wrote:
>> I do not think so. I did not remember seeing a second mouse pointer.
>>
>> F.
>>
>
> --
> Xorg crashed with SIGSEGV in dixLookupPrivate()
> https://bugs.launchpad.net/bugs/328937
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “xorg-server” source package in Ubuntu: Triaged
>
> Bug description:
> Running Jaunty 9.04. I did not actually notice the crash until the bug report dialog popped up.
>
> ProblemType: Crash
> Architecture: amd64
> DistroRelease: Ubuntu 9.04
> ExecutablePath: /usr/bin/Xorg
> Package: xserver-xorg-core 2:1.5.99.902-0ubuntu6
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7
> ProcEnviron:
>  PATH=(custom, no user)
>  LANG=en_US.UTF-8
> ProcVersion: Linux version 2.6.28-7-generic (buildd@yellow) (gcc version 4.3.3 (Ubuntu 4.3.3-3ubuntu2) ) #20-Ubuntu SMP Mon Feb 9 15:42:34 UTC 2009
>
> Signal: 11
> SourcePackage: xorg-server
> Stacktrace: #0  0x00000000004346ca in dixLookupPrivate ()
> StacktraceTop: dixLookupPrivate ()
> ThreadStacktrace:
>
> Title: Xorg crashed with SIGSEGV in dixLookupPrivate()
> Uname: Linux 2.6.28-7-generic x86_64
> UserGroups:
>
> [lspci]
> 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07)
>        Subsystem: Dell Device [1028:024d]
> 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
>        Subsystem: Dell Device [1028:024d]
>
>

Revision history for this message
kseise (kevin-seise) wrote :

I was running a full screen program in Cedega. It crashed and brought me back to the GDM login. Once I logged in, I got the apport crash message. This is a fully up to date Jaunty beta on AMD64

Revision history for this message
Jan David Mol (jjdmol) wrote :

Xorg crashed again for me today with a similar but longer traceback. I reported this as bug #357536, since I was unsure of how to extract the proper information without reporting it as a new bug.

Revision history for this message
Bryce Harrington (bryce) wrote :

Sure that's fine. We'll just dupe this one to that, since this one's backtrace isn't analyzable.

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.