nautilus crashed with SIGABRT in raise()

[marcobra (Marco Braida)]

Description: Ubuntu quantal (development branch)
Release: 12.10

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

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90-0ubuntu1 [modified: usr/bin/nautilus usr/bin/nautilus-autorun-software usr/bin/nautilus-connect-server usr/lib/nautilus/nautilus-convert-metadata]
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic i686
ApportVersion: 2.5.1-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Thu Aug 23 05:04:01 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+460+100'"
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
ProcCmdline: nautilus -n
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
 __libc_fatal () from /lib/i386-linux-gnu/libc.so.6
 pthread_cancel_init () from /lib/i386-linux-gnu/libpthread.so.0
Title: nautilus crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to quantal on 2012-08-15 (8 days ago)
UserGroups: adm admin audio cdrom debian-tor dialout dip fax floppy fuse icecast lpadmin netdev plugdev powerdev sambashare tape vboxusers video
mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2012-04-28T05:18:08.362891

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