nautilus segfaults in gtk_ui_manager_new_merge_id()

Bug #925503 reported by Chris Johnston on 2012-02-02
406
This bug affects 68 people
Affects Status Importance Assigned to Milestone
Nautilus
Invalid
Critical
nautilus (Ubuntu)
High
Unassigned
Precise
High
Unassigned

Bug Description

happened right after an update

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-10.18-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 2 09:42:02 2012
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f0e8be058d0 <gtk_ui_manager_new_merge_id>: mov 0x18(%rdi),%rdx
 PC (0x7f0e8be058d0) 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-02 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Chris Johnston (cjohnston) wrote :

StacktraceTop:
 gtk_ui_manager_new_merge_id (manager=0x0) at /build/buildd/gtk+3.0-3.3.10/./gtk/gtkuimanager.c:1421
 nautilus_ui_prepare_merge_ui (ui_manager=0x0, name=0x50bfb5 "OpenWithGroup", merge_id=0x20364d8, action_group=0x20364d0) at nautilus-ui-utilities.c:56
 reset_open_with_menu (selection=0x0, view=0x2036280) at nautilus-view.c:4391
 real_update_menus (view=0x2036280) at nautilus-view.c:8328
 nautilus_icon_view_update_menus (view=0x2036280) at nautilus-icon-view.c:1448

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nautilus (Ubuntu):
status: New → Confirmed
visibility: private → public
Changed in nautilus (Ubuntu):
importance: Medium → Low
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, did it happen in the middle of the update? did you get only once? what you trigger the bug in some way?

Changed in nautilus (Ubuntu):
status: Confirmed → Incomplete

The crash happened on the initial boot after upgrading to 12.04. It happened only once.

Sent from my iPod

On Feb 8, 2012, at 5:29 PM, Sebastien Bacher <email address hidden> wrote:

> Thank you for your bug report, did it happen in the middle of the
> update? did you get only once? what you trigger the bug in some way?
>
> ** Changed in: nautilus (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (926005).
> https://bugs.launchpad.net/bugs/925503
>
> Title:
> nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id()
>
> Status in “nautilus” package in Ubuntu:
> Incomplete
>
> Bug description:
> happened right after an update
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: nautilus 1:3.3.4-0ubuntu1
> ProcVersionSignature: Ubuntu 3.2.0-10.18-generic 3.2.1
> Uname: Linux 3.2.0-10-generic x86_64
> NonfreeKernelModules: nvidia
> ApportVersion: 1.91-0ubuntu1
> Architecture: amd64
> CrashCounter: 1
> Date: Thu Feb 2 09:42:02 2012
> ExecutablePath: /usr/bin/nautilus
> InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
> ProcCmdline: nautilus
> ProcEnviron:
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0x7f0e8be058d0 <gtk_ui_manager_new_merge_id>: mov 0x18(%rdi),%rdx
> PC (0x7f0e8be058d0) 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-02 (0 days ago)
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/925503/+subscriptions

Happened to me when trying to close a nautilus window, maybe the content of the folder was changing at that time (firefox nightly folder while updating firefox nightly)

Steve Magoun (smagoun) wrote :

I reproduced this in 12.04 by:
1) Plug in an iPhone
2) Navigate around the iPhone's filesystem for a bit
3) Unmount the iPhone from within nautilus by clicking the 'unmount' icons in the left-hand side column
4) Click the close button on the nautilus window. Notice that nothing happens. Click it again...and again

Changed in nautilus (Ubuntu):
status: Incomplete → Confirmed
Timo Witte (spacefish) wrote :

this bug happend to me after dropbox tried to restart nautilus. So it may be something in the "shutdown" routine of nautilus?

Changed in nautilus (Ubuntu):
importance: Low → High
summary: - nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id()
+ nautilus segfaults in gtk_ui_manager_new_merge_id()
Changed in nautilus (Ubuntu):
status: Confirmed → Triaged
Changed in nautilus:
importance: Unknown → Medium
status: Unknown → New
Changed in nautilus:
importance: Medium → Critical
tags: added: bugpattern-needed
Gvozdik Artem (gvozdik) wrote :

Happened on precise with no reason.

It happenned to me when I opened the update-manager. I have no idea what's the reason.

Benjamin Geese (ben-8409) wrote :

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.

I was able to reproduce it once, by opening trying to close it again very fast. Sadly with gdb attached an debug symbols installed, i am no longer able to repduce it. I might be doing something wrong...

tags: added: rls-mgr-p-tracking
tags: added: quantal
Doug McMahon (mc3man) wrote :

In regards to 12.10 dev
Possibly it's just my hardware though don't think it's that uncommon (Dell 13300m, nvidia 8400m, 3.5 yrs. old

If so then then I guess that's just the way it goes..

Tried on both fresh 32 & 64 bit A2 installs - as soon as gtk/gail/naitilus are upgraded to current then it becomes impossible to go more than a min. or so without this crash.
In addition to what's in the various reports show attached in xsession-errors.

Reverting gtk/gail to 3.5.4 & nautilus to 3.5.2 & all works fine
Will give one more try once the current packages are on the daily image to see if upgrading them is involved in issue (here

Karma Dorje (taaroa) wrote :

the same thing happens to 12.10 dev

Sebastien Bacher (seb128) wrote :

the recent quantal issues are likely different from that one and tracked by bug #1018896

Changed in nautilus:
status: New → Invalid
Sebastien Bacher (seb128) wrote :

The bug didn't get activity/new duplicates for some years and the nautilus code saw quite some changes since which probably deprecated the issue so closing it. If it's still a problem in recent Ubuntu/nautilus version please submit a new report

Changed in nautilus (Ubuntu):
status: Triaged → Invalid
Changed in nautilus (Ubuntu Precise):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.