pcmanfm crashed with SIGSEGV in gtk_widget_get_toplevel()

[Ktux]

OS :Lubuntu 11.10 64 bits
Package: pcmanfm 0.9.9-0ubuntu1

Expected : copy/paste files

Happens : it crashes !

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: pcmanfm 0.9.9-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 27 00:37:45 2011
ExecutablePath: /usr/bin/pcmanfm
InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.1)
Pref_Config_System_lubuntu:
 [Preferred Applications]
 WebBrowser=firefox.desktop
 MailClient=
ProcCmdline: pcmanfm --desktop --profile lubuntu
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd7a945f263 <gtk_widget_get_toplevel+83>: mov 0x58(%rbx),%rax
 PC (0x7fd7a945f263) ok
 source "0x58(%rbx)" (0xaaaaaaaaaaaaab02) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: pcmanfm
StacktraceTop:
 gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 gtk_widget_create_pango_context () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 gtk_widget_get_pango_context () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 gtk_widget_create_pango_layout () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
Title: pcmanfm crashed with SIGSEGV in gtk_widget_get_toplevel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #838489, 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.