pcmanfm crashed with SIGSEGV in gtk_window_remove_accel_group()

[Yuv]

Saucy (13.10) developer preview, completely up to date at the time of reporting.

Happens every time I remove a USB key, no matter wheter I umount it first or not.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: pcmanfm 1.1.0-0ubuntu2
Uname: Linux 3.10.0-wl+ x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Config_pcmanfm_System_Lubuntu: Error: [Errno 2] No such file or directory: '/etc/xdg/pcmanfm/lubuntu.conf'
Date: Wed Jul 17 09:13:40 2013
ExecutablePath: /usr/bin/pcmanfm
ExecutableTimestamp: 1357501651
MarkForUpload: True
Pref_Config_System_Lubuntu:
 [Preferred Applications]
 WebBrowser=firefox.desktop
 MailClient=
ProcCmdline: pcmanfm --desktop --profile lubuntu
ProcCwd: /home/yuv
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd58314b2fe <gtk_window_remove_accel_group+30>: cmp %rax,(%rdx)
 PC (0x7fd58314b2fe) ok
 source "%rax" ok
 destination "(%rdx)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: pcmanfm
StacktraceTop:
 gtk_window_remove_accel_group () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libfm-gtk.so.3
 g_datalist_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: pcmanfm crashed with SIGSEGV in gtk_window_remove_accel_group()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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 #1196091, 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.