nautilus crashed with SIGSEGV

[Tobiasz Jarczyk]

 $ lsb_release -rd
Description: Ubuntu quantal (development branch)
Release: 12.10

$ apt-cache policy nautilus
nautilus:
  Zainstalowana: 1:3.5.90.really.3.4.2-0ubuntu2
  Kandydująca: 1:3.5.90.really.3.4.2-0ubuntu2
  Tabela wersji:
 *** 1:3.5.90.really.3.4.2-0ubuntu2 0
        500 http://pl.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
ApportVersion: 2.5.3-0ubuntu1
Architecture: amd64
CheckboxSubmission: ed6b163724c03445b4dd8678117c4efa
CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
Date: Sat Sep 29 17:15:37 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'799x580+124+24'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7f7717fba923: mov 0x30(%rbx),%rdi
 PC (0x7f7717fba923) ok
 source "0x30(%rbx)" (0x00002299) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2012-06-28 (92 days ago)
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev nopasswdlogin plugdev sambashare scanner
usr_lib_nautilus:
 evince 3.6.0-0ubuntu1
 file-roller 3.6.0-0ubuntu2
 nautilus-share 0.7.3-1ubuntu2
 totem 3.4.3-0ubuntu4
 ubuntuone-client-gnome 3.99.92-0ubuntu1

[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.