nautilus crashed while executing in live mode from usb-pen drive

[dexMilano]

Binary package hint: nautilus

no problem occurs, but any login i receive this error.
apparently I can continue working whitout problem.

I created the live session with remastersys backup.
The problem could be related to this configuration.

Corrado

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Mar 9 11:42:23 2010
Disassembly: 0x543bad0: Cannot access memory at address 0x543bad0
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
LiveMediaBuild: Custom Live CD - Release i386
Package: nautilus 1:2.28.1-0ubuntu3
ProcCmdline: nautilus
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SegvAnalysis:
 Segfault happened at: 0x543bad0: Cannot access memory at address 0x543bad0
 PC (0x0543bad0) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 exit () from /lib/tls/i686/cmov/libc.so.6
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 _start () at ../sysdeps/i386/elf/start.S:119
Title: nautilus crashed with SIGSEGV in exit()
Uname: Linux 2.6.31-19-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:6426): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:6426): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:6516): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:6550): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (firefox:22746): GLib-WARNING **: g_set_prgname() called multiple times

[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!.