indicator-sound-service crashed with SIGSEGV kb volume key

Bug #717956 reported by P Cantwall
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-sound (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: indicator-sound

I was in the Live mode of today's Natty DVD because the install failed to set the video correctly. I pressed my Volume Down key on my Microsift keyboard and it crashed the sound.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-sound 0.5.9-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2.6.38-3-generic x86_64
Architecture: amd64
Date: Sun Feb 13 01:05:33 2011
ExecutablePath: /usr/lib/indicator-sound/indicator-sound-service
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110212)
ProcCmdline: /usr/lib/indicator-sound/indicator-sound-service
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xc6f420: adc %bl,(%rdi,%rax,8)
 PC (0x00c6f420) in non-executable VMA region: 0x00c4a000-0x00cb1000 rw-p [heap]
 source "%bl" ok
 destination "(%rdi,%rax,8)" (0x7f45ecf20a90) not located in a known VMA region (needed writable region)!
SegvReason:
 executing writable VMA [heap]
 writing unknown VMA
Signal: 11
SourcePackage: indicator-sound
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libpulse.so.0
 ?? () from /usr/lib/libpulse.so.0
 ?? () from /usr/lib/libpulse.so.0
 ?? () from /usr/lib/libpulsecommon-0.9.22.so
Title: indicator-sound-service crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (nautilus:5025): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (nm-applet:5035): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed
 (nautilus:5025): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (nautilus:5025): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (nautilus:5025): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

Revision history for this message
P Cantwall (p-cantwell) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 context_autospawn (c=0xc7a880)
 try_next_connection (c=0xc7a880)
 ?? ()
 ?? ()

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 indicator-sound (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libjack-jackd2-0: installed version 1.9.6~dfsg.1-3ubuntu1, latest version: 1.9.6~dfsg.1-5ubuntu1
libxft2-dbg: installed version 2.1.14-2ubuntu1, latest version: 2.2.0-2ubuntu1
libplymouth2: installed version 0.8.2-2ubuntu14, latest version: 0.8.2-2ubuntu17
libxft2: installed version 2.1.14-2ubuntu1, latest version: 2.2.0-2ubuntu1
libdbusmenu-gtk3: installed version 0.3.97-0ubuntu1, latest version: 0.3.97-0ubuntu3
libdbusmenu-glib3: installed version 0.3.97-0ubuntu1, latest version: 0.3.97-0ubuntu3
tzdata: installed version 2011a-1ubuntu1, latest version: 2011b-2
plymouth: installed version 0.8.2-2ubuntu14, latest version: 0.8.2-2ubuntu17

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
visibility: private → public
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.