nautilus crashed with SIGABRT in raise()

[marcobra (Marco Braida)]

Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04

nautilus:
  Installato: 1:3.6.3-0ubuntu9
  Candidato: 1:3.6.3-0ubuntu9
  Tabella versione:
 *** 1:3.6.3-0ubuntu9 0
        500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu9
ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3
Uname: Linux 3.8.0-13-generic i686
ApportVersion: 2.9.1-0ubuntu1
Architecture: i386
Date: Sat Mar 16 14:22:30 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'1034x376+49+24'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'177'
InstallationDate: Installed on 2012-08-26 (202 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
MarkForUpload: True
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=it_IT:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 __assert_fail () from /lib/i386-linux-gnu/libc.so.6
 _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: nautilus crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to raring on 2013-02-12 (31 days ago)
UserGroups: adm cdrom dip fuse lpadmin netdev plugdev sambashare sudo vboxusers
mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2012-12-19T21:12:46.354871

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