nautilus crashed with SIGSEGV in gtk_action_get_name()

[Vladimir Scherbaev]

Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10
nautilus:
  Установлен: 1:3.8.2-0ubuntu1
  Кандидат: 1:3.8.2-0ubuntu1
  Таблица версий:
 *** 1:3.8.2-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic x86_64
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
CheckboxSubmission: fc038fbbc6dcc038ea950e9a3aece7e1
CheckboxSystem: b8f3ec504801f13fc208edb5c785b099
CrashCounter: 1
Date: Tue Jul 16 20:09:43 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'800x559+83+109'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'163'
InstallationDate: Installed on 2012-08-24 (326 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
MarkForUpload: True
ProcCmdline: nautilus --new-window
SegvAnalysis:
 Segfault happened at: 0x7f085298dd66 <gtk_action_get_name+22>: cmp %rax,(%rdx)
 PC (0x7f085298dd66) ok
 source "%rax" ok
 destination "(%rdx)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 gtk_action_get_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in gtk_action_get_name()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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