nautilus crashed with SIGSEGV in g_atomic_int_get()

[James Dearing]

Binary package hint: nautilus

ProblemType: Crash
Architecture: i386
Date: Sun Feb 7 21:45:03 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
Package: nautilus 1:2.29.2-0ubuntu4
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-12.17-generic
SegvAnalysis:
 Segfault happened at: 0xa9bdec <g_atomic_int_get+12>: mov (%eax),%eax
 PC (0x00a9bdec) ok
 source "(%eax)" (0xaaaaaabe) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
Stacktrace:
 #0 0x00a9bdec in g_atomic_int_get () from /lib/libglib-2.0.so.0
 No symbol table info available.
 #1 0xaaaaaabe in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 g_atomic_int_get () from /lib/libglib-2.0.so.0
 ?? ()
Title: nautilus crashed with SIGSEGV in g_atomic_int_get()
Uname: Linux 2.6.32-12-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Stacktrace:
 #0 0x00a9bdec in g_atomic_int_get () from /lib/libglib-2.0.so.0
 No symbol table info available.
 #1 0xaaaaaabe in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 g_atomic_int_get () from /lib/libglib-2.0.so.0
 ?? ()

[Pedro Villavicencio (pedro)]

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[James Dearing (dearingj)]

Sorry about not responding to this sooner. I have been unable to reproduce this bug, so I can't get a backtrace.

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

However, processing it in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!