unplugging USB speakerphone resulted in - indicator-sound-service crashed with SIGSEGV in pa_pdispatch_run()

Bug #550060 reported by Ali Asad Lotia
48
This bug affects 8 people
Affects Status Importance Assigned to Milestone
The Sound Menu
Fix Released
High
Conor Curran
indicator-sound (Ubuntu)
Fix Released
Medium
Conor Curran

Bug Description

Binary package hint: indicator-sound

Going through the USB sound checkbox test and had the Sound Preferences window open.
Unplugging the USB device while the window was open caused volume indicator to appear as if the output was muted and a the application crash notification appeared with prompts to report the bug.
Changing output volume had no effect on the "indicator-sound".
Audio is functional, I can change volume, the OSD notification appears, but the volume indicator in the top menu bar does not change, it continues to sugges that the output volume is muted.

ProblemType: Crash
Architecture: amd64
Date: Sun Mar 28 01:56:10 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/indicator-sound/indicator-sound-service
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100327)
Package: indicator-sound 0.2.1-0ubuntu1
ProcCmdline: /usr/lib/indicator-sound/indicator-sound-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SegvAnalysis:
 Segfault happened at: 0x403cec: mov 0x8(%rbx),%esi
 PC (0x00403cec) ok
 source "0x8(%rbx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-sound
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libpulse.so.0
 ?? () from /usr/lib/libpulsecommon-0.9.21.so
 pa_pdispatch_run ()
 ?? () from /usr/lib/libpulse.so.0
Title: indicator-sound-service crashed with SIGSEGV in pa_pdispatch_run()
Uname: Linux 2.6.32-17-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1560): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-terminal:2237): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
 (gnome-terminal:2481): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

Related branches

Revision history for this message
Ali Asad Lotia (ali-asad-lotia) wrote :
Revision history for this message
Ali Asad Lotia (ali-asad-lotia) wrote :

The speakerphone was a ClearOne Chat 50 in case the submitted files don't have the USB device information.

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

StacktraceTop:
 update_sink_info (c=<value optimized out>, info=0x0,
 context_get_sink_info_callback (
 run_action (pd=0x163ef10, r=0x164d260, command=0,
 pa_pdispatch_run (pd=0x163ef10,
 pstream_packet_callback (p=<value optimized out>,

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-amd64-retrace
Revision history for this message
David Barth (dbarth) wrote :

Putting that under the radar

Changed in indicator-sound:
assignee: nobody → Conor Curran (cjcurran)
importance: Undecided → High
milestone: none → ubuntu-10.04-beta-2
status: New → Triaged
David Barth (dbarth)
Changed in indicator-sound (Ubuntu):
milestone: none → ubuntu-10.04-beta-2
David Barth (dbarth)
Changed in indicator-sound (Ubuntu):
assignee: nobody → Conor Curran (cjcurran)
status: New → Triaged
visibility: private → public
Conor Curran (cjcurran)
Changed in indicator-sound:
status: Triaged → In Progress
Revision history for this message
Conor Curran (cjcurran) wrote :

This is a duplicate of 522428 (cannot mark as a duplicate for some reason). Honestly it seems like an odd bug. Its like the info pointer in the update callback has become Null just as the callback has been triggered. The fix is to make the update code safer at this point. Will keep an eye on this.

I have not been able to reproduce from my end (which is annoying).
Please retest with indicator-sound-0.2.2
Conor

Changed in indicator-sound:
status: In Progress → Fix Committed
Conor Curran (cjcurran)
Changed in indicator-sound (Ubuntu):
status: Triaged → In Progress
Conor Curran (cjcurran)
Changed in indicator-sound:
status: Fix Committed → Fix Released
Conor Curran (cjcurran)
Changed in indicator-sound (Ubuntu):
status: In Progress → 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.