nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id()

[Benjamin Geese]

Note: This seems to me like its the same bug as #203191 nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id() from 2008. However, Sebastien Bacher recently commented on this bug one should not reopen it bug file a new one instead. Here it is.

It happened while i was doing some unity testing with checkbox. Wanted to use the unity dash to open gedit (typed gedi and hitted enter), but somehow started nautilus in full screen. as this was not what i wanted i very quickly tryed to close it blicking close. Nothing seemed to happen, clicked several time until the crash message appeared.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.90-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
Date: Thu Mar 1 21:39:54 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 org.gnome.nautilus.window-state geometry '800x550+66+53'
 org.gnome.nautilus.window-state maximized true
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.2)
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f6680cd0110 <gtk_ui_manager_new_merge_id>: mov 0x18(%rdi),%rdx
 PC (0x7f6680cd0110) 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 cdrom dip 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.