gvfsd-sftp crashed with SIGSEGV in g_utf8_validate()

[tr33m4n]

Attempted to connect to a remote server using SSH through Nautilus 3.4.2

Description: Ubuntu quantal (development branch)
Release: 12.10
gvfs:
  Installed: 1.13.7-0ubuntu1
  Candidate: 1.13.7-0ubuntu1
  Version table:
 *** 1.13.7-0ubuntu1 0
        500 http://gb.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gvfs-backends 1.13.7-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic x86_64
ApportVersion: 2.5.1-0ubuntu2
Architecture: amd64
Date: Fri Aug 24 20:31:04 2012
ExecutablePath: /usr/lib/gvfs/gvfsd-sftp
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
ProcCmdline: /usr/lib/gvfs/gvfsd-sftp --spawner :1.12 /org/gtk/gvfs/exec_spaw/4
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f6ea9325278 <g_utf8_validate+456>: movzbl (%rdi),%r8d
 PC (0x7f6ea9325278) ok
 source "(%rdi)" (0x6874756120656854) not located in a known VMA region (needed readable region)!
 destination "%r8d" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 g_utf8_validate () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new_string () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_new_strv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gvfsd-sftp crashed with SIGSEGV in g_utf8_validate()
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 #1033275, 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.