unity-panel-service crashed with SIGSEGV in thread_memory_from_self()

Bug #806290 reported by Chris Halse Rogers
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Unity
Fix Released
Undecided
Unassigned
unity (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

This crash consistently happens when trying to move the volume slider of indicator-sound.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-services 4.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
Uname: Linux 3.0-3-generic x86_64
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,imgjpeg,decor,imgsvg,snap,text,grid,imgpng,gnomecompat,unitymtgrabhandles,place,vpswitch,compiztoolbox,notification,resize,regex,animation,move,loginout,mousepoll,expo,workarounds,resizeinfo,session,wall,ezoom,staticswitcher,fade,scale,unityshell,scalefilter,scaleaddon]
Date: Wed Jul 6 12:37:01 2011
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110117)
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 SHELL=/bin/zsh
 LC_MESSAGES=en_AU.utf8
 LANGUAGE=en_AU:en_GB:en
 PATH=(custom, no user)
 LANG=en_AU.utf8
SegvAnalysis:
 Segfault happened at: 0x7f60831bff5a <g_slice_alloc+538>: callq *0x60(%rax)
 PC (0x7f60831bff5a) ok
 source "*0x60(%rax)" ok
 destination "(%rsp)" (0x7fff37fa0000) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 thread_memory_from_self (mem_size=48) at /build/buildd/glib2.0-2.29.8/./glib/gslice.c:441
 g_slice_alloc (mem_size=48) at /build/buildd/glib2.0-2.29.8/./glib/gslice.c:825
 g_slice_alloc0 (mem_size=48) at /build/buildd/glib2.0-2.29.8/./glib/gslice.c:854
 g_signal_emit_valist (instance=0x171e030, signal_id=33, detail=0, var_args=0x7fff37fa01c8) at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:2951
 g_signal_emit (instance=<value optimised out>, signal_id=<value optimised out>, detail=<value optimised out>) at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:3044
Title: unity-panel-service crashed with SIGSEGV in thread_memory_from_self()
UpgradeStatus: Upgraded to oneiric on 2011-06-17 (18 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sbuild

Revision history for this message
Chris Halse Rogers (raof) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 thread_memory_from_self (mem_size=48) at /build/buildd/glib2.0-2.29.8/./glib/gslice.c:441
 g_slice_alloc (mem_size=48) at /build/buildd/glib2.0-2.29.8/./glib/gslice.c:825
 g_slice_alloc0 (mem_size=48) at /build/buildd/glib2.0-2.29.8/./glib/gslice.c:854
 g_signal_emit_valist (instance=0x171e030, signal_id=33, detail=0, var_args=0x7fff37fa01c8) at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:2951
 g_signal_emit (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>) at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:3044

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 unity (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in unity (Ubuntu):
importance: Medium → Critical
Changed in unity (Ubuntu):
status: New → Confirmed
Neil J. Patel (njpatel)
visibility: private → public
Revision history for this message
Neil J. Patel (njpatel) wrote :

Hi, I believe this is now fixed with the latest Oneiric which changes the way the sound slider works. If it still happens on latest Oneiric, please re-open this bug, thanks!

Changed in unity:
status: New → Fix Released
Changed in unity (Ubuntu):
status: Confirmed → 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.