Ubuntu
gtk+3.0 package

gtk-update-icon-cache-3.0 crashed with SIGSEGV

Bug #1298288 reported by Jean-Baptiste Lallement
102
This bug affects 21 people
Affects Status Importance Assigned to Milestone
gtk+3.0 (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Crashed during upgrade from a fresh installation of Precise Desktop + updates to Trusty in graphical mode.

upgrader logs attached.

Problem on errors.u.c:

https://errors.ubuntu.com/problem/51867c7babfc41c749a4ed34ba54148f534a28c1

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: libgtk-3-0 3.10.7-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
Date: Thu Mar 27 09:48:23 2014
ExecutablePath: /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-update-icon-cache-3.0
ExecutableTimestamp: 1394104222
InstallationDate: Installed on 2014-03-26 (0 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140324)
ProcCmdline: gtk-update-icon-cache-3.0 --force --quiet /usr/share/icons/hicolor
ProcCwd: /
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fbefe8bae37: movl $0x0,(%rdx)
 PC (0x7fbefe8bae37) ok
 source "$0x0" ok
 destination "(%rdx)" (0x7fbefe8b8730) in non-writable VMA region: 0x7fbefe8b3000-0x7fbefe8d1000 r-xp /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.2600.1
SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.2600.1
Signal: 11
SourcePackage: gtk+3.0
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0
 ?? ()
 ?? ()
Title: gtk-update-icon-cache-3.0 crashed with SIGSEGV
UpgradeStatus: Upgraded to trusty on 2014-03-27 (0 days ago)
UserGroups:

See original description
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0x00007fbefe8bae37 in collect_save_options (opts=0x5, keys=0x0, vals=0x7fbefe8b8730 <gdk_pixbuf_set_property+24>) at gdk-pixbuf-io.c:1983
   [Error: gdk-pixbuf-io.c was not found in source tree]
 #1 0x00007fbefe8cae23 in ?? () from /tmp/apport_sandbox_O1OXlw/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0
 #2 0x0000000000e16c10 in ?? ()
 #3 0x0000000000000000 in ?? ()
StacktraceTop:
 collect_save_options (opts=0x5, keys=0x0, vals=0x7fbefe8b8730 <gdk_pixbuf_set_property+24>) at gdk-pixbuf-io.c:1983
 ?? () from /tmp/apport_sandbox_O1OXlw/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0
 ?? ()
 ?? ()

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
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1298288

tags: added: iso-testing
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

closing. bad stacktrace

affects: gtk+3.0 (Ubuntu) → ubuntu
Changed in ubuntu:
status: New → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

That's a known issue/ranking high enough on e.u.c, it seems to happen during upgrades and be a mismatch of versions between the running session/what has not been updated yet/what is being unpackged (which is also why the retracing don't work, the running binary doesn't match the installed version used for retracing). Not sure how to workaround it though, upgrades in running session lead to issues like that..

affects: ubuntu → gtk+3.0 (Ubuntu)
Jean-Baptiste Lallement (jibel)
Changed in gtk+3.0 (Ubuntu):
status: Invalid → Confirmed
importance: Undecided → High
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

see bug #1272977 as well (https://bugzilla.gnome.org/show_bug.cgi?id=724685)

Revision history for this message
ealthuis (ealthuis) wrote :

These crashes occurred as the upgrade was rebooting. I will shut down and reboot from scratch

Revision history for this message
Jorge Milian (falco3) wrote :

Add one more to the list. It doesn't seen to be affecting anything (yet)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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