Xorg crashed with SIGSEGV in FreeColormap()

Bug #398842 reported by heynnema
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Just enabled apport to troubleshoot an Evolution problem, and now twice, from cold boot, I've seen this xorg crash. I do have a colored desktop picture, and have selected a different icon set. Also, this is running on a 333mhz IBM Thinkpad... so it's possible it's just taking too long at startup?

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/Xorg
Package: xserver-xorg-core 2:1.6.0-0ubuntu14
ProcAttrCurrent: unconfined
ProcCmdline: /usr/X11R6/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-13-generic (buildd@vernadsky) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #45-Ubuntu SMP Tue Jun 30 19:49:51 UTC 2009
Signal: 11
SourcePackage: xorg-server
Stacktrace:
 #0 0x0808088b in FreeColormap ()
 #1 0x080747c6 in FreeClientResources ()
 #2 0x08074896 in FreeAllResources ()
 #3 0x08072322 in main ()
StacktraceTop:
 FreeColormap ()
 FreeClientResources ()
 FreeAllResources ()
 main ()
Title: Xorg crashed with SIGSEGV in FreeColormap()
Uname: Linux 2.6.28-13-generic i686
UserGroups:

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190] (rev 03)
     Subsystem: IBM Device [1014:0138]
01:00.0 VGA compatible controller [0300]: Neomagic Corporation NM2200 [MagicGraph 256AV] [10c8:0005] (rev 12)
     Subsystem: IBM Device [1014:0137]

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

StacktraceTop:FreeColormap (value=0x82eb128, mid=72)
FreeClientResources (client=0x8286860)
FreeAllResources () at ../../dix/resource.c:824
main (argc=10, argv=0xbfb7da44, envp=)

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: jaunty
Bryce Harrington (bryce)
description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi heynnema,

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 398842

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

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

The old ThinkPad is not being used right now, so I can't retest with a newer Ubuntu. Thanks, Al.

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.