nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id()

[Anders Kaseorg]

nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id()

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4
Uname: Linux 3.5.0-2-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.2.5-0ubuntu1
Architecture: amd64
Date: Sun Jul 1 03:43:44 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7fbc66481580 <gtk_ui_manager_new_merge_id>: mov 0x18(%rdi),%rdx
 PC (0x7fbc66481580) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 gtk_ui_manager_new_merge_id () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout fuse 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 #925503, 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.