nautilus crashed with SIGSEGV in g_type_check_instance()

Bug #1182307 reported by Steve Langasek
32
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Nautilus
Fix Released
Critical
nautilus (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Nautilus crashed when I closed the 'Trash' window after emptying the Trash.

TEST CASE:
1. Click on the Trash Icon on the launcher.
2. Close the trash window that just opened.

ACTUAL RESULT:
This crash

EXPECTED RESULT:
Trash closes without crashing.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.6.3-0ubuntu16
ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2
Uname: Linux 3.9.0-2-generic x86_64
ApportVersion: 2.10.1-0ubuntu1
Architecture: amd64
Date: Mon May 20 20:41:11 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1213x746+65+25'"
InstallationDate: Installed on 2010-09-24 (969 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MarkForUpload: True
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7f7980a2b789 <g_type_check_instance+25>: mov (%rax),%rdi
 PC (0x7f7980a2b789) ok
 source "(%rax)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance (type_instance=type_instance@entry=0x2958390) at /build/buildd/glib2.0-2.37.0/./gobject/gtype.c:4082
 g_signal_handler_disconnect (instance=0x2958390, handler_id=3748) at /build/buildd/glib2.0-2.37.0/./gobject/gsignal.c:2580
 ?? ()
 g_object_run_dispose (object=0x26b38c0) at /build/buildd/glib2.0-2.37.0/./gobject/gobject.c:1062
 gtk_box_forall (container=<optimized out>, include_internals=<optimized out>, callback=0x7f79831cb150 <gtk_widget_destroy>, callback_data=0x0) at /build/buildd/gtk+3.0-3.6.4/./gtk/gtkbox.c:1865
Title: nautilus crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: Upgraded to saucy on 2013-05-06 (14 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare src sudo

Revision history for this message
Steve Langasek (vorlon) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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: added: apport-failed-retrace
tags: removed: need-amd64-retrace
tags: added: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance (type_instance=type_instance@entry=0x2958390) at /build/buildd/glib2.0-2.37.0/./gobject/gtype.c:4082
 g_signal_handler_disconnect (instance=0x2958390, handler_id=3748) at /build/buildd/glib2.0-2.37.0/./gobject/gsignal.c:2580
 nautilus_trash_bar_dispose (obj=0x26b38c0) at nautilus-trash-bar.c:109
 g_object_run_dispose (object=0x26b38c0) at /build/buildd/glib2.0-2.37.0/./gobject/gobject.c:1062
 gtk_box_forall (container=<optimized out>, include_internals=<optimized out>, callback=0x7f79831cb150 <gtk_widget_destroy>, callback_data=0x0) at /build/buildd/gtk+3.0-3.6.4/./gtk/gtkbox.c:1865

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote : Updated stack trace from duplicate bug 1189485

Package: nautilus 1:3.6.3-0ubuntu17
ProcCmdline: nautilus -n

Revision history for this message
Apport retracing service (apport) wrote : Dependencies.txt
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

This crash always occurs during autopilot tests of Unity.

To reproduce:
1. Open a guest session
2. autopilot run -v unity
3. Wait until nautilus crashes

information type: Private → Public
description: updated
Changed in nautilus (Ubuntu):
assignee: nobody → Iain Lane (laney)
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nautilus - 1:3.6.3-0ubuntu18

---------------
nautilus (1:3.6.3-0ubuntu18) saucy; urgency=low

  * debian/patches/0001-trash-bar-fix-double-disconnect-handler.patch:
    Backport upstream commit fixing use after free (double disconnect). (LP:
    #1182307)
 -- Iain Lane <email address hidden> Mon, 10 Jun 2013 18:04:35 +0100

Changed in nautilus (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Iain Lane (laney) wrote :

It's not fixed! Somebody should have complained :P

Changed in nautilus (Ubuntu):
status: Fix Released → Triaged
assignee: Iain Lane (laney) → nobody
Changed in nautilus:
importance: Unknown → Critical
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nautilus - 1:3.6.3-0ubuntu20

---------------
nautilus (1:3.6.3-0ubuntu20) saucy; urgency=low

  * Remove previous patch; it wasn't the optimal approach. Add
    debian/patches/disconnect-extra-location-widgets.patch to remove
    references to NautilusTrashBar, causing it to be disposed at the right
    time instead.
 -- Iain Lane <email address hidden> Thu, 20 Jun 2013 09:38:18 +0100

Changed in nautilus (Ubuntu):
status: Triaged → Fix Released
Changed in nautilus:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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