pcmanfm crashed with SIGSEGV in gtk_widget_get_toplevel()

[Adolfo Jayme Barrientos]

It happened suddenly after executing a program.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: pcmanfm 0.9.10-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-12.20-generic 3.2.2
Uname: Linux 3.2.0-12-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Config_pcmanfm_System_ubuntu-2d: Error: [Errno 2] No existe el archivo o el directorio: '/etc/xdg/pcmanfm/ubuntu-2d/pcmanfm.conf'
Date: Mon Jan 30 03:00:32 2012
ExecutablePath: /usr/bin/pcmanfm
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
Pref_Config_System_ubuntu-2d:
 [Preferred Applications]
 WebBrowser=firefox.desktop
 MailClient=
ProcCmdline: pcmanfm /home/username/Escritorio/tor-browser_en-US
SegvAnalysis:
 Segfault happened at: 0x83e76a <gtk_widget_get_toplevel+106>: mov 0x38(%esi),%eax
 PC (0x0083e76a) ok
 source "0x38(%esi)" (0xaaaaaae2) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: pcmanfm
StacktraceTop:
 gtk_widget_get_toplevel () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 gtk_widget_create_pango_context () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 gtk_widget_get_pango_context () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 gtk_widget_create_pango_layout () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
Title: pcmanfm crashed with SIGSEGV in gtk_widget_get_toplevel()
UpgradeStatus: Upgraded to precise on 2011-11-16 (75 days ago)
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 this software 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.