nautilus crashed with SIGSEGV in g_private_get_impl()

[Fabio Duran Verdugo]

From the command line, put a couple circular symbolic links into a dir:
$ ln -s link2 link1
$ ln -s link1 link2

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.2.1-2ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-5.11-generic 3.2.0-rc5
Uname: Linux 3.2.0-5-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
Date: Mon Dec 19 09:56:00 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0xe1f179: mov %ebx,0x1c(%esp)
 PC (0x00e1f179) ok
 source "%ebx" ok
 destination "0x1c(%esp)" (0xbf211ffc) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_private_get () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_private_get()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

[Apport retracing service (apport)]

StacktraceTop:
 g_private_get_impl (key=0xe9055c) at /build/buildd/glib2.0-2.31.4.tested/./glib/gthread-posix.c:986
 g_private_get (key=0xe9055c) at /build/buildd/glib2.0-2.31.4.tested/./glib/gthread-posix.c:1018
 thread_memory_from_self () at /build/buildd/glib2.0-2.31.4.tested/./glib/gslice.c:500
 g_slice_alloc (mem_size=16) at /build/buildd/glib2.0-2.31.4.tested/./glib/gslice.c:981
 g_slice_alloc0 (mem_size=16) at /build/buildd/glib2.0-2.31.4.tested/./glib/gslice.c:1029

[Pedro Villavicencio (pedro)]

Fabio is this still an issue for you? The developers are requesting more info on the upstream bug tracker, could you please comment there? Thanks.

[Sebastien Bacher (seb128)]

there has been no such issue reported in years, assuming it doesn't exist in the current version of the code and closing