nautilus-sendto crashed with SIGSEGV in g_type_get_qdata()

[Sean Watson]

Ubuntu 13.10, uninstalled empathy, tried send to on a file.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus-sendto 3.6.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Thu Oct 10 12:53:37 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus-sendto
InstallationDate: Installed on 2013-07-19 (82 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: nautilus-sendto file:///home/username/Documents/Einstein's%20Special%20Relativity%20Original%20Paper.pdf
SegvAnalysis:
 Segfault happened at: 0x7f160086a81a <_IO_vfprintf_internal+154>: callq 0x7f16008b4b20 <strchrnul>
 PC (0x7f160086a81a) ok
 source "0x7f16008b4b20" (0x7f16008b4b20) ok
 destination "(%rsp)" (0x7fffb1c39f80) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus-sendto
StacktraceTop:
 g_type_get_qdata () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/python2.7/dist-packages/gobject/_gobject.so
 ?? () from /usr/lib/python2.7/dist-packages/gobject/_gobject.so
 ?? () from /usr/lib/python2.7/dist-packages/gobject/_gobject.so
 ?? () from /usr/lib/python2.7/dist-packages/gobject/_gobject.so
Title: nautilus-sendto crashed with SIGSEGV in g_type_get_qdata()
UpgradeStatus: Upgraded to saucy on 2013-10-10 (0 days ago)
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 #1213878, 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.