indicator-sound-service crashed with SIGSEGV in pa_cvolume_valid()

Bug #705009 reported by leonardo.cs.bsb@hotmail.com
46
This bug affects 7 people
Affects Status Importance Assigned to Milestone
PulseAudio
Invalid
Undecided
Unassigned
The Sound Menu
Fix Released
High
Conor Curran
indicator-sound (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: indicator-sound

Favor, resolva esse problema também.

Obrigado!

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: indicator-sound 0.5.0.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Sat Jan 15 12:07:17 2011
ExecutablePath: /usr/lib/indicator-sound/indicator-sound-service
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: /usr/lib/indicator-sound/indicator-sound-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb06599 <pa_cvolume_valid+25>: movzbl (%edx),%ecx
 PC (0x00b06599) ok
 source "(%edx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-sound
StacktraceTop:
 pa_cvolume_valid () from /usr/lib/libpulse.so.0
 pa_cvolume_avg () from /usr/lib/libpulse.so.0
 ?? ()
 ?? ()
 ?? () from /usr/lib/libpulse.so.0
Title: indicator-sound-service crashed with SIGSEGV in pa_cvolume_valid()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:14031): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:14039): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

Revision history for this message
leonardo.cs.bsb@hotmail.com (leonardo-cs-bsb-hotmail) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 pa_cvolume_valid (v=0x8) at pulse/volume.c:471
 pa_cvolume_avg (a=0x8) at pulse/volume.c:92
 get_default_sink_volume () at pulse-manager.c:213
 context_state_callback (c=0x8918e10, userdata=0x0)
 pa_context_set_state (c=0x8918e10, st=PA_CONTEXT_FAILED)

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):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Conor Curran (cjcurran)
Changed in indicator-sound:
assignee: nobody → Conor Curran (cjcurran)
Revision history for this message
Conor Curran (cjcurran) wrote :

Odd bug, do you experience this frequently ?

Conor

Changed in indicator-sound:
status: New → Triaged
Revision history for this message
Pascal Hartig (passy) wrote :

I experience this as well and it does in fact happen quite frequently, but at least in my case it's cause is pulseaudio, that crashes from time to time. However, the crashing pulseaudio daemon should not tear down the indicator-sound, should it?

Revision history for this message
Conor Curran (cjcurran) wrote :

Well it shouldn't but I guess if Pulse can't handle the service querying the current volume level I have little way around this. Will point this bug upstream. This part of the indicator sound code base has not changed since this time last year and this is the first time I have had a bug like this reported. Will keep it active on indicator-sound, I am currently refactoring my pulse code.

Changed in indicator-sound:
importance: Undecided → High
Revision history for this message
Conor Curran (cjcurran) wrote :

Okay this should be fixed in the last release, so as if the pulse server has gone down then the controls (mute and volume) should be disabled. This will ensure the pulsecontext is not null. At least the indicator will not crash but it does not solve the problem as to why the pulse server is going away. Going to mark this as fix released for now. If you experience the pulse server crashing again please file a new bug against the pulseserver project (one of the projects affected by this bug)

Changed in indicator-sound:
milestone: none → 0.5.9
status: Triaged → Fix Committed
Changed in pulseaudio:
status: New → Invalid
Changed in indicator-sound (Ubuntu):
status: New → Fix Committed
Changed in indicator-sound:
status: Fix Committed → Fix Released
Conor Curran (cjcurran)
Changed in indicator-sound:
status: Fix Released → Fix Committed
Revision history for this message
Conor Curran (cjcurran) wrote :

This should be rock solid from 0.5.9 for Natty. Tracking maverick similar issues in bug #715099

Conor Curran (cjcurran)
Changed in indicator-sound:
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-sound - 0.5.9-0ubuntu1

---------------
indicator-sound (0.5.9-0ubuntu1) natty; urgency=low

  * New upstream release.
    - crashed with SIGSEGV in pa_cvolume_valid () (LP: #705009)
    - The players list should be customizable (LP: #685725)
    - Allow players to set their own title (LP: #709367)
    - refactor pulse manager (LP: #709371)
    - listen for playlist changed signal (LP: #715277)
    - playlist name not updated corrrectly (LP: #715694)
    - Not enough feedback when changing the volume (LP: #669163)
    - indicator-sound volume does not detect sink change (LP: #700361)
  * debian/control
    - Added new build depends libnotify-dev
 -- Ken VanDine <email address hidden> Thu, 10 Feb 2011 11:52:59 -0500

Changed in indicator-sound (Ubuntu):
status: Fix Committed → 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.