indicator-sound-service crashed with SIGSEGV in pa_pdispatch_run()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| indicator-sound (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: indicator-sound
1) Added a bluetooth headset to the system.
2) Picked the device for input/output in sound preferences.
What happens: Device gets removed from list in sound preference. I can no longer use the headset, unless I remove and re-add it in the bluetooth preferences.
Expected: Seamless transition, once the audio device is added it should not be removed on its own (unless the device is offline).
ProblemType: Crash
Architecture: i386
Date: Fri Mar 26 22:45:42 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
NonfreeKernelMo
Package: indicator-sound 0.2.1-0ubuntu1
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANG=en_CA.utf8
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x804b815: mov 0x4(%ebx),%edx
PC (0x0804b815) ok
source "0x4(%ebx)" (0x00000004) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-sound
StacktraceTop:
?? ()
?? () from /usr/lib/
?? () from /usr/lib/
pa_pdispatch_run () from /usr/lib/
?? () from /usr/lib/
Title: indicator-
Uname: Linux 2.6.32-17-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| komputes (komputes) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| tags: | removed: need-i386-retrace |
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 #550060, 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.