nautilus crashed with SIGABRT in __GI___open_catalog()

[cacula]

directly after boot

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Jul 25 21:14:29 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'931x1030+785+136'"
InstallationDate: Installed on 2013-07-17 (13 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130716)
MarkForUpload: True
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: nautilus
StacktraceTop: __GI___open_catalog (cat_name=<Fehler beim Lesen der Variable: Cannot access memory at address 0xffffffffffffffbb>, cat_name@entry=<Fehler beim Lesen der Variable: Cannot access memory at address 0x8b>, nlspath=<Fehler beim Lesen der Variable: Cannot access memory at address 0x8b>, env_var=<Fehler beim Lesen der Variable: Cannot access memory at address 0xffffffffffffffb3>, env_var@entry=<Fehler beim Lesen der Variable: Cannot access memory at address 0x8b>, catalog=<Fehler beim Lesen der Variable: Cannot access memory at address 0xffffffffffffffa3>, catalog@entry=<Fehler beim Lesen der Variable: Cannot access memory at address 0x8b>) at open_catalog.c:109
Title: nautilus crashed with SIGABRT in __GI___open_catalog()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2013-07-17T19:37:20.333941

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