gnome-panel crashed with SIGSEGV in magazine_chain_pop_head()

Bug #984357 reported by Benjamin Drung
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Invalid
High
Unassigned

Bug Description

gnome-panel crashed when I changed the theme from Ambiance to Radiance.

Thread 1 (Thread 0x7fd61b0ed980 (LWP 6929)):
#0 magazine_chain_pop_head (magazine_chunks=0x1999660) at /build/buildd/glib2.0-2.32.1/./glib/gslice.c:528
#1 thread_memory_magazine1_alloc (ix=<optimized out>, tmem=<optimized out>) at /build/buildd/glib2.0-2.32.1/./glib/gslice.c:835
        mag = 0x1999660
#2 g_slice_alloc (mem_size=16) at /build/buildd/glib2.0-2.32.1/./glib/gslice.c:994
        tmem = 0x1999650
#3 0x00007fd6185d71a6 in g_slice_alloc0 (mem_size=16) at /build/buildd/glib2.0-2.32.1/./glib/gslice.c:1029
#4 0x00007fd61a2d6a8b in gtk_widget_path_new () at /build/buildd/gtk+3.0-3.4.1/./gtk/gtkwidgetpath.c:119
#5 0x00007fd61a2d6ac5 in gtk_widget_path_copy (path=0x1e56b6f) at /build/buildd/gtk+3.0-3.4.1/./gtk/gtkwidgetpath.c:175
        __PRETTY_FUNCTION__ = "gtk_widget_path_copy"
#6 0x00007fd61a221b5a in create_query_path (context=0x1cfc6e0) at /build/buildd/gtk+3.0-3.4.1/./gtk/gtkstylecontext.c:1039
        priv = 0x1cfc700
#7 style_data_lookup (context=0x1cfc6e0, state=GTK_STATE_FLAG_BACKDROP) at /build/buildd/gtk+3.0-3.4.1/./gtk/gtkstylecontext.c:1104
        path = 0x1ed4080
        priv = 0x1cfc700
        __PRETTY_FUNCTION__ = "style_data_lookup"

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-panel 1:3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
Date: Tue Apr 17 22:41:22 2012
ExecutablePath: /usr/bin/gnome-panel
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111005)
ProcCmdline: gnome-panel --replace
SegvAnalysis:
 Segfault happened at: 0x7fd6185d6ded <g_slice_alloc+477>: mov 0x8(%rax),%rbx
 PC (0x7fd6185d6ded) ok
 source "0x8(%rax)" (0x1e56d0008) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gtk_widget_path_new () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_widget_path_copy () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: gnome-panel crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to precise on 2012-02-25 (52 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Benjamin Drung (bdrung) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=0x1999660) at /build/buildd/glib2.0-2.32.1/./glib/gslice.c:528
 thread_memory_magazine1_alloc (ix=<optimized out>, tmem=<optimized out>) at /build/buildd/glib2.0-2.32.1/./glib/gslice.c:835
 g_slice_alloc (mem_size=16) at /build/buildd/glib2.0-2.32.1/./glib/gslice.c:994
 g_slice_alloc0 (mem_size=16) at /build/buildd/glib2.0-2.32.1/./glib/gslice.c:1029
 gtk_widget_path_new () at /build/buildd/gtk+3.0-3.4.1/./gtk/gtkwidgetpath.c:119

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 gnome-panel (Ubuntu):
importance: Undecided → Medium
summary: - gnome-panel crashed with SIGSEGV in g_slice_alloc()
+ gnome-panel crashed with SIGSEGV in magazine_chain_pop_head()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-panel (Ubuntu):
status: New → Confirmed
Bryce Harrington (bryce)
information type: Private → Public
Changed in gnome-panel (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

Seems to be easily reproducible on 12.04 (tested on several machines).

Found this googling around a bit, found https://mail.gnome.org/archives/gtk-devel-list/2010-December/msg00065.html

Changed in gnome-panel (Ubuntu):
status: Triaged → Invalid
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.