nautilus crashed with SIGSEGV in g_str_hash()

[Marc DENTY]

I tried to connect a ssh server :
Home Folder > Connect to Server > Server Address
entered sftp://myserver.com
enter user and password.

In Network section the remote "drive" shows up, and nautilus crashes.

It seems that this only happens on some servers that are configured for sftp only:

$ ssh <email address hidden>
<email address hidden>'s password:
PTY allocation request failed on channel 0
shell request failed on channel 0

$ sftp <email address hidden> .
<email address hidden>'s password:
Connected to myserver.com.
File "/toto" not found.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu5
ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4
Uname: Linux 3.8.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu3
Architecture: amd64
Date: Thu Jan 31 09:23:21 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1187x799+283+90'"
InstallationDate: Installed on 2012-12-19 (42 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f12a80aed90 <g_str_hash>: movsbl (%rdi),%edx
 PC (0x7f12a80aed90) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_hash_table_lookup_extended () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in g_str_hash()
UpgradeStatus: Upgraded to raring on 2013-01-30 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark

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