pcmanfm crashed with SIGSEGV in _gtk_marshal_BOOLEAN__OBJECT_INT_INT_UINT()

[yamo]

Crash when launching pcmanfm after starting the computer.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: pcmanfm 0.9.9-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Config_pcmanfm_System_lxde: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/etc/xdg/pcmanfm/lxde/pcmanfm.conf'
CrashCounter: 1
Date: Sat Jan 7 23:01:06 2012
ExecutablePath: /usr/bin/pcmanfm
Pref_Config_Home_lxde:
 [Preferred Applications]
 CustomWebBrowsers=seamonkey.desktop;
ProcCmdline: pcmanfm --desktop --profile LXDE
SegvAnalysis:
 Segfault happened at: 0x7fc31c146863: mov 0x18(%rax),%rax
 PC (0x7fc31c146863) ok
 source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pcmanfm
StacktraceTop:
 ?? () from /usr/lib/libfm-gtk.so.1
 _gtk_marshal_BOOLEAN__OBJECT_INT_INT_UINT (closure=0x19dc530, return_value=0x7fff3c1a37f0, n_param_values=<optimized out>, param_values=0x17bbeb0, invocation_hint=<optimized out>, marshal_data=<optimized out>) at /build/buildd/gtk+2.0-2.24.6/gtk/gtkmarshalers.c:413
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: pcmanfm crashed with SIGSEGV in _gtk_marshal_BOOLEAN__OBJECT_INT_INT_UINT()
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (85 days ago)
UserGroups: adm admin cdrom dialout kqemu kvm lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #908737, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.