nautilus crashed on login with SIGSEGV in g_slice_alloc()

[Brett Johnson]

Binary package hint: nautilus

Latest Gutsy update as of today. When I log in, Nautilus will either eat up 100% of CPU, or it will segfault. I can subsequently run Nautilus via the "Places" menu, and browse around w/out problem. Possibly relevant out-of-ordinary details: I have the "/apps/nautilus/preferences/show_desktop" gconf key set to false, and I'm running xfdesktop to draw the root window. I'm also running compiz fusion.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Oct 6 22:58:33 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: cdrom
Package: nautilus 1:2.20.0-0ubuntu6
PackageArchitecture: i386
ProcCmdline: nautilus --no-default-window --sm-client-id default2
ProcCwd: /home/brett
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: nautilus
Stacktrace:
 #0 0xb75706fe in g_slice_alloc () from /usr/lib/libglib-2.0.so.0
 #1 0xb7575cb3 in g_string_sized_new () from /usr/lib/libglib-2.0.so.0
 #2 0xb7575d25 in g_string_new () from /usr/lib/libglib-2.0.so.0
 #3 0xb75456a3 in ?? () from /usr/lib/libglib-2.0.so.0
 #4 0x00000000 in ?? ()
StacktraceTop:
 g_slice_alloc () from /usr/lib/libglib-2.0.so.0
 g_string_sized_new () from /usr/lib/libglib-2.0.so.0
 g_string_new () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? ()
Title: nautilus crashed with SIGSEGV in g_slice_alloc()
Uname: Linux river 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner scard video

[Apport retracing service (apport)]

StacktraceTop:IA__g_slice_alloc0 (mem_size=12) at /build/buildd/glib2.0-2.14.1/glib/gslice.c:833
gconf_value_new (type=GCONF_VALUE_STRING) at gconf-value.c:76
gconf_value_copy (src=0x81f61b0) at gconf-value.c:723
gconf_client_get_full (client=0x819e358, key=<value optimized out>, locale=<value optimized out>,
eel_gconf_get_value (key=0x81c64a8 "/apps/nautilus/preferences/show_icon_text")

[Sebastien Bacher (seb128)]

Thanks for your bug report. Could you try to get a valgrind log for the crash (you can follow the instructions on https://wiki.ubuntu.com/Valgrind)?

[Brett Johnson (linuxturtle)]

Hmm. I don't even know how nautilus is being run on login, much less how to start it up under valgrind. AFAICT, I don't see any reason that nautilus should even be trying to start up. It's not in my session script, I'm not using it to manage my desktop, etc...

Anyway, I'd be happy to try running nautilus under valgrind on login, if you can explain how I can do so.

[Sebastien Bacher (seb128)]

does it crash if you stop it using "gnome-session-remove nautilus" and start it again from a command line then? You can also run it under valgrind this way

[Brett Johnson (linuxturtle)]

Unfortunately, no. I've never been able to get it to crash, nor consume 100% CPU when running it from a command line after login. I've only ever seen it happen when logging in (and since it's not in my session, I can't even figure out why it's running).

[Sebastien Bacher (seb128)]

nautilus starts because it's part of the default session, you an run it under valgrind by renaming gnome-session to gnome-session.binary and make a gnome-session wrapper which runs the binary under valgrind for example

[Pedro Villavicencio (pedro)]

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.