Ubuntu
gtk+2.0 package

nautilus crashed with SIGSEGV in app_chooser_online_get_default_ready_cb()

Bug #795332 reported by Eliah Kagan
188
This bug affects 23 people
Affects Status Importance Assigned to Milestone
GTK+
Invalid
Critical
gtk+2.0 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: nautilus

On an Oneiric i386 system in a unity-2d session, I tried to open a file with an unknown extension (.old) in a nautilus 1:3.0.2-0ubuntu2 window. I selected to "Open With Other Application" and indicated the application (leafpad). The file opened successfully but nautilus crashed with SIGSEGV in app_chooser_online_get_default_ready_cb().

This appears to be the same as bug 788739, but with a better trace. If a closer examination supports that, I'll go ahead and mark bug 788739 a duplicate of this bug.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.0.2-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
Uname: Linux 2.6.39-3-generic i686
Architecture: i386
Date: Thu Jun 9 20:28:53 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110604)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.utf8
 LC_MESSAGES=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x1000e8e <app_chooser_online_get_default_ready_cb+62>: mov %eax,0x24(%edi)
 PC (0x01000e8e) ok
 source "%eax" ok
 destination "0x24(%edi)" (0xaaaaaace) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 app_chooser_online_get_default_ready_cb (source=0x92986f0, res=0x939b878, user_data=0x9398000) at /build/buildd/gtk+3.0-3.0.11/./gtk/gtkappchooserdialog.c:164
 g_simple_async_result_complete (simple=0x939b878) at /build/buildd/glib2.0-2.29.4/./gio/gsimpleasyncresult.c:749
 pk_proxy_created_cb (source=0x93b6ae8, result=0x9373190, user_data=0x92986f0) at /build/buildd/gtk+3.0-3.0.11/./gtk/gtkappchooseronlinepk.c:187
 g_simple_async_result_complete (simple=0x9373190) at /build/buildd/glib2.0-2.29.4/./gio/gsimpleasyncresult.c:749
 complete_in_idle_cb (data=0x9373190) at /build/buildd/glib2.0-2.29.4/./gio/gsimpleasyncresult.c:761
Title: nautilus crashed with SIGSEGV in app_chooser_online_get_default_ready_cb()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

this is a gtk+ crash , reassigning also the crash looks unique so i'll send this upstream.

affects: nautilus (Ubuntu) → gtk+2.0 (Ubuntu)
Changed in gtk+2.0 (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

this bug has been sent upstream at: https://bugzilla.gnome.org/show_bug.cgi?id=652322

Changed in gtk+2.0 (Ubuntu):
status: New → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in gtk:
importance: Unknown → Critical
status: Unknown → New
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_app_chooser_button_remove_non_custom (object=0x939b878) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtkappchooserbutton.c:376
 gtk_app_chooser_button_refresh (object=0x939b878) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtkappchooserbutton.c:428
 gtk_tree_view_column_get_sort_column_id (tree_column=0x93b6ae8) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtktreeviewcolumn.c:2742
 _g_resolver_addresses_from_addrinfo (hostname=0x9373190 "\220.\355\b\001", res=0x0, gai_retval=1444, error=0x983ff4) at /build/buildd/glib2.0-2.29.8/./gio/gresolver.c:789
 g_source_unref_internal (source=<value optimized out>, context=0x983ff4, have_lock=149762852) at /build/buildd/glib2.0-2.29.8/./glib/gmain.c:1754

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: removed: need-i386-retrace
Bug Watch Updater (bug-watch-updater)
Changed in gtk:
status: New → Confirmed
Apport retracing service (apport)
tags: added: bugpattern-needed
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

I've found that this still occurs with nautilus 1:3.1.92-0ubuntu3 (see duplicate bug 859622).

Sebastien Bacher (seb128)
affects: gtk+2.0 (Ubuntu) → ubuntu
Pedro Villavicencio (pedro)
affects: ubuntu → gtk+2.0 (Ubuntu)
Revision history for this message
Cristian Aravena Romero (caravena) wrote :

This occurs in file-roller 3.2.1-0ubuntu1

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

@Cristian Aravena
This crash is in nautilus, rather than file-roller. Are you sure you are experiencing the same bug?

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

@Cristian Aravena
Sorry, please disregard my previous post. I was confusing this with another, different bug. Again, my apologies.

Bug Watch Updater (bug-watch-updater)
Changed in gtk:
status: Confirmed → Invalid
Revision history for this message
Nick Jenkins (nickpj) wrote :

If the upstream bug is correct, then that upstream bug is a dupe of: https://bugzilla.gnome.org/show_bug.cgi?id=649121 , which was marked as RESOLVED FIXED 2 months ago. Perhaps this should be marked as RESOLVED FIXED upstream? Also bug 864249 is marked as a dupe of that upstream bug, so alternatively perhaps this bug is a dupe of that one?

Sebastien Bacher (seb128)
Changed in gtk+2.0 (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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