nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOOLEAN()

[Mikhail Gavrilov]

Binary package hint: nautilus

-

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.31.92-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Thu Sep 23 21:18:28 2010
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
ProcCmdline: nautilus
ProcEnviron:
 LANG=ru_RU.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x80e6180: mov 0xc(%esi),%edi
 PC (0x080e6180) ok
 source "0xc(%esi)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__BOOLEAN (closure=0x8f51ce8, return_value=0x0, n_param_values=2, param_values=0x91f4850, invocation_hint=0xbf9564a0, marshal_data=0x0) at /build/buildd/glib2.0-2.25.15/gobject/gmarshal.c:113
 g_type_class_meta_marshal (closure=0x8f51ce8, return_value=0x0, n_param_values=2, param_values=0x91f4850, invocation_hint=0xbf9564a0, marshal_data=0x1dc) at /build/buildd/glib2.0-2.25.15/gobject/gclosure.c:877
Title: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOOLEAN()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare wireshark

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__BOOLEAN ()
 ?? () from /usr/lib/libgobject-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.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.