nautilus segfaults in gtk_icon_info_get_attach_points()

Bug #1187709 reported by Angel Guzman Maeso
532
This bug affects 240 people
Affects Status Importance Assigned to Milestone
Nautilus
Fix Released
Medium
gtk+3.0 (Ubuntu)
Fix Released
High
Unassigned

Bug Description

I get this crash when attach files from chrome and a popup for select file appears.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.6.3-0ubuntu17
ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
Uname: Linux 3.8.0-13-generic i686
ApportVersion: 2.10.2-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Mon Jun 3 08:41:20 2013
ExecutablePath: /usr/bin/nautilus
ExecutableTimestamp: 1369745708
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'940x722+65+24'"
InstallationDate: Installed on 2013-02-03 (119 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MarkForUpload: True
ProcCmdline: nautilus --new-window
ProcCwd: /home/shakaran
SegvAnalysis:
 Segfault happened at: 0xb72bcaff <gtk_icon_info_get_attach_points+191>: mov 0x4(%edx),%eax
 PC (0xb72bcaff) ok
 source "0x4(%edx)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 gtk_icon_info_get_attach_points () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in gtk_icon_info_get_attach_points()
UpgradeStatus: Upgraded to saucy on 2013-02-03 (119 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Angel Guzman Maeso (shakaran) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_icon_info_get_attach_points (icon_info=icon_info@entry=0x93e14d8, points=points@entry=0xbf92a1f0, n_points=n_points@entry=0xbf92a1f4) at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkicontheme.c:4619
 nautilus_icon_info_new_for_icon_info (icon_info=0x93e14d8) at nautilus-icon-info.c:150
 nautilus_icon_info_lookup (icon=icon@entry=0x992be18, size=size@entry=48) at nautilus-icon-info.c:413
 nautilus_file_get_icon (file=file@entry=0x98a1348, size=size@entry=48, flags=(NAUTILUS_FILE_ICON_FLAGS_USE_THUMBNAILS | NAUTILUS_FILE_ICON_FLAGS_USE_MOUNT_ICON_AS_EMBLEM)) at nautilus-file.c:4390
 nautilus_canvas_view_container_get_icon_images (container=0x930d0d8, data=0x98a1348, size=48, embedded_text=0xbf92a334, for_drag_accept=0, need_large_embeddded_text=0, embedded_text_needs_loading=0xbf92a338, has_window_open=0xbf92a33c) at nautilus-canvas-view-container.c:95

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-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: nautilus crashed with SIGSEGV in gtk_icon_info_get_attach_points()

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
information type: Private → Public
Revision history for this message
Sebastien Bacher (seb128) wrote :

The issue is not Ubuntu specific and still happening with nautilus 3.8:
https://retrace.fedoraproject.org/faf/reports/134189/

Changed in nautilus (Ubuntu):
importance: Medium → High
summary: - nautilus crashed with SIGSEGV in gtk_icon_info_get_attach_points()
+ nautilus segfaults in gtk_icon_info_get_attach_points()
Changed in nautilus (Ubuntu):
status: Confirmed → Triaged
Changed in nautilus:
importance: Unknown → Medium
status: Unknown → New
Changed in nautilus (Ubuntu):
status: Triaged → Fix Committed
affects: nautilus (Ubuntu) → gtk+3.0 (Ubuntu)
Changed in nautilus:
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gtk+3.0 - 3.8.2-0ubuntu6

---------------
gtk+3.0 (3.8.2-0ubuntu6) saucy; urgency=low

  * debian/rules: don't stop the build on failings tests, on armhf.
    There is a test that started failing recently there, and the issue is
    not easily reproducible. Since the version mismatch between archs is
    breaking builds, let's unblock those while we debug
 -- Sebastien Bacher <email address hidden> Thu, 20 Jun 2013 13:29:00 +0200

Changed in gtk+3.0 (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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