gvfsd-ftp crashed with SIGABRT in g_assertion_message()

[caspar luc]

This error appeared while trying to save a document from geany to a ftp server.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gvfs-backends 1.15.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4
Uname: Linux 3.5.0-24-generic x86_64
ApportVersion: 2.9-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Mar 6 22:11:08 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-ftp
InstallationDate: Installed on 2012-01-29 (401 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-ftp --spawner :1.4 /org/gtk/gvfs/exec_spaw/10
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
Title: gvfsd-ftp crashed with SIGABRT in g_assertion_message()
UpgradeStatus: Upgraded to raring on 2013-03-02 (3 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x411d0e "name specified", line=line@entry=384, func=func@entry=0x412090 "", message=<optimized out>) at /build/buildd/glib2.0-2.35.8/./glib/gtestutils.c:1912
 g_assertion_message_expr (domain=0x0, file=0x411d0e "name specified", line=384, func=0x412090 "", expr=<optimized out>) at /build/buildd/glib2.0-2.35.8/./glib/gtestutils.c:1923
 g_vfs_backend_ftp_finalize (object=0x202c040) at gvfsbackendftp.c:386
 g_object_unref (_object=0x202c040) at /build/buildd/glib2.0-2.35.8/./gobject/gobject.c:3024
 mount_failed (op_job=<optimized out>, error=<optimized out>) at gvfsjobmount.c:157

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.