Trying to adjust the volume and the volume slider become unresponsive.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-services 4.14.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell]
CrashCounter: 1
Date: Sun Sep 11 00:27:54 2011
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f096982ce13 <_int_malloc+387>: mov %rax,0x28(%rsp)
PC (0x7f096982ce13) ok
source "%rax" ok
destination "0x28(%rsp)" (0x7fff701d3ff8) 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:
_int_malloc (av=0x7f0969b4d1c0, bytes=1056) at malloc.c:4411
_int_memalign (av=0x7f0969b4d1c0, alignment=512, bytes=<optimized out>) at malloc.c:5492
__GI___libc_memalign (alignment=512, bytes=496) at malloc.c:3880
__posix_memalign (memptr=0x7fff701d40e8, alignment=<optimized out>, size=<optimized out>) at malloc.c:6315
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in _int_malloc()
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (9 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #837877, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.