nautilus crashed with SIGSEGV in gtk_action_get_name()

[Ernie]

I had just "two finger clicked" the touchpad to bring up the context menu, then clicked "new folder". Nothing happened... waited 5s or so, then Nautilus crashed.

1) Ubuntu Gnome Remix 13.10 dev branch
2) nautilus:
  Installed: 1:3.8.2-0ubuntu1
  Candidate: 1:3.8.2-0ubuntu1
  Version table:
 *** 1:3.8.2-0ubuntu1 0
        500 http://ca.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
        100 /var/lib/dpkg/status

3) A new folder to be created in the current directory and ask me for a folder name
4) 5 second pause, then Nautilus crashed

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Sat Aug 31 11:32:19 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'840x550+0+59'"
InstallationDate: Installed on 2013-08-30 (1 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130830)
MarkForUpload: True
ProcCmdline: nautilus --no-desktop /home/username/Dropbox
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f405c036dd6 <gtk_action_get_name+22>: cmp %rax,(%rdx)
 PC (0x7f405c036dd6) ok
 source "%rax" ok
 destination "(%rdx)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 gtk_action_get_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in gtk_action_get_name()
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 #1193522, 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.