nautilus crashed with SIGSEGV in thread_memory_from_self()

[Draycen DeCator]

Binary package hint: nautilus

This happens consistantly whenever I attempt to open /usr/bin, have not been able to reproduce the crash when opening any other folders. Let me know if I need to add any extra information.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: nautilus 1:2.30.0-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Tue Apr 27 21:43:50 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f28f93f156e <IA__g_slice_alloc+750>: callq *0x60(%rax)
 PC (0x7f28f93f156e) ok
 source "*0x60(%rax)" ok
 destination "(%rsp)" (0x7fffbac05fc0) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 thread_memory_from_self (mem_size=32)
 IA__g_slice_alloc (mem_size=32)
 IA__g_slice_alloc0 (mem_size=39752224)
 IA__g_type_create_instance (type=40476672)
 g_object_constructor (type=39752224,
Title: nautilus crashed with SIGSEGV in thread_memory_from_self()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:3225): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (Do:3234): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.

[Apport retracing service (apport)]

StacktraceTop:
 IA__g_slice_alloc (mem_size=32)
 IA__g_slice_alloc0 (mem_size=39752224)
 IA__g_type_create_instance (type=40476672)
 g_object_constructor (type=39752224,
 IA__g_object_newv (

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Draycen DeCator (ddecator)]

I ran valgrind, although it launched Nautilus then ended the process, and Nautilus crashed after that. Not sure if it caught what is causing this, but there seem to be a lot of errors in the log, so I'm attaching it all the same. If I need to run it again with any more debug symbols or arguments, please let me know.

[gianluca.pettinello (g-pet)]

I had the same problem and finally succeeded in solving it.
Basically there are some broken links in /usr/bin which make nautilus to crash. Search with another browser like gnome-commander the broken links and restore them or delete them. Afterwards nautilus won't crash any more

[Launchpad Janitor (janitor)]

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

[Azyl (dj-azyl)]

i was able thanks to your advice to delete the broken links using gnome-commander, it would be nice to add to nautilus a way to handle this kind of things, maybe add a option to delete this kind of broken links?

[Pedro Villavicencio (pedro)]

Thanks for the report, is this reproducible on Ubuntu 11.10 ? May you please try the same and comment back? Thanks.

[Launchpad Janitor (janitor)]

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]