[precise] nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id() upon opening a Home directory

Bug #940834 reported by Oksana Zhuravlova on 2012-02-25
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Undecided
Unassigned

Bug Description

I have installed ubuntu-desktop on a kubuntu installation. Upon my login and opening nautilus the error 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
NonfreeKernelModules: wl fglrx
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
Date: Sat Feb 25 10:53:18 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 org.gnome.nautilus.window-state geometry '800x550+443+181'
 org.gnome.nautilus.window-state maximized true
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
ProcCmdline: nautilus -n
ProcEnviron:
 PATH=(custom, user)
 LANG=uk_UA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f2559c68110 <gtk_ui_manager_new_merge_id>: mov 0x18(%rdi),%rdx
 PC (0x7f2559c68110) 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: Upgraded to precise on 2012-02-25 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Oksana Zhuravlova (oksamyt) wrote :

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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers