pcmanfm crashed with SIGSEGV in gtk_widget_get_toplevel()

[JJ]

Crash report alert on login. May have been because of the previous session (GNOME/OpenBox?) When I logged in using this option I did not get any panels etc. Used Ctrl+Alt-F1 to "init 6".

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 i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CheckboxSubmission: b75d6f7e8416095436df6fda1142b6d6
CheckboxSystem: c69722ecac764861be52925fa50b4dcc
Config_pcmanfm_System_ubuntu-2d: Error: [Errno 2] No such file or directory: '/etc/xdg/pcmanfm/ubuntu-2d/pcmanfm.conf'
Date: Fri Sep 23 14:30:52 2011
ExecutablePath: /usr/bin/pcmanfm
Pref_Config_System_ubuntu-2d:
 [Preferred Applications]
 WebBrowser=firefox.desktop
 MailClient=
ProcCmdline: /usr/bin/pcmanfm trash://
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x77cf8a <gtk_widget_get_toplevel+106>: mov 0x38(%esi),%eax
 PC (0x0077cf8a) 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 oneiric on 2011-09-23 (0 days ago)
UserGroups: admin pulse sambashare saned www-data

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