gnome-session crashed with SIGSEGV

[xteejx]

Binary package hint: gnome-session

Not too sure what happened here.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-session-bin 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.37-2.10-generic 2.6.37-rc1
Uname: Linux 2.6.37-2-generic i686
Architecture: i386
Date: Fri Nov 12 23:02:48 2010
ExecutablePath: /usr/bin/gnome-session
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20101109)
ProcCmdline: /usr/bin/gnome-session --autostart=/usr/share/gdm/autostart/LoginWindow/
ProcEnviron:
 LANG=en_GB.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0xb6e314bb: cmp %cl,(%edx)
 PC (0xb6e314bb) ok
 source "%cl" ok
 destination "(%edx)" (0x2589836b) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-session
StacktraceTop:
 ?? () from /lib/libc.so.6
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: gnome-session crashed with SIGSEGV
UserGroups:

[Apport retracing service (apport)]

Unsetting the need retracing tag, there is no retracer left running on that version of Ubuntu, the crash will need to be manually retraced

[Sebastien Bacher (seb128)]

sorry natty bugs got cleaned wrongly

[Apport retracing service (apport)]

StacktraceTop:
 __bcopy_ssse3_rep () from /lib/libc.so.6
 ?? ()
 insert_theme (icon_theme=0x92b3c20,
 ?? ()

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?

 This will help us to find and resolve the problem.

[xteejx (xteejx)]

Hi Sebastien. I have no idea why or how this happened, it was a random crash/apport catch. Feel free to close it if needed, there are no duplicates anyway :) Thank you.

[Sebastien Bacher (seb128)]

thanks for the update, closing the bug now since it was a one time issue without enough details to be worked and didn't get duplicates since