nautilus crashed with SIGSEGV in g_type_class_meta_marshal()

[Salvatore Vassallo]

Binary package hint: nautilus

Description: Ubuntu karmic (development branch)
Release: 9.10

nautilus 2.27.1-0ubuntu1 0

ProblemType: Crash
Architecture: i386
Date: Sun Jun 7 09:51:38 2009
Disassembly: 0x0:
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.27.1-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-8.9-generic
SegvAnalysis: Failure: invalid literal for int() with base 16: '0x0:'
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 g_type_class_meta_marshal (closure=0x952c9a0,
 IA__g_closure_invoke (closure=0x8ee0458,
 signal_emit_unlocked_R (node=<value optimized out>,
 IA__g_signal_emit_valist (instance=0x952c9a0, signal_id=30,
Title: nautilus crashed with SIGSEGV in g_type_class_meta_marshal()
Uname: Linux 2.6.30-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev pulse pulse-access pulse-rt sambashare

[Apport retracing service (apport)]

StacktraceTop:?? ()
g_type_class_meta_marshal (closure=0x952c9a0,
IA__g_closure_invoke (closure=0x8ee0458,
signal_emit_unlocked_R (node=<value optimized out>,
IA__g_signal_emit_valist (instance=0x952c9a0, signal_id=30,

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem. May you also tell us a few easy steps in order to reproduce the crash? Thanks in advance.

[Salvatore Vassallo (vassallosalvatore)]

Hi Pedro,

thank you for your suggestions.
Unfourtunatly I don't have anymore this pc, I'll install soon karmic on the new one and I'll try to reproduce the bug and to update this bug report.

The crash happens when I mount a multimedia hd (lacie Cinema) and a pen drive and when I switch beetwen them (two different nautilus' windows)

Thank You

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.