nautilus crashed with SIGSEGV

[mdmcginn]

Automatically reported. I was moving an MP3 to a different folder.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
CheckboxSubmission: 23f9165fb5269142dfde45beba11cbff
CheckboxSystem: edda5d4f616ca792bf437989cb597002
CrashCounter: 1
Date: Sat Oct 6 07:56:30 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'711x518+169+50'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'198'
 b'org.gnome.nautilus.window-state' b'start-with-sidebar' b'false'
 b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb751e0a0: mov 0x18(%esi),%eax
 PC (0xb751e0a0) ok
 source "0x18(%esi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2012-09-23 (13 days ago)
UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare vboxusers

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