indicator-sound-service crashed with SIGABRT in pa_cvolume_set()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Sound Menu |
Fix Released
|
Critical
|
Conor Curran | ||
indicator-sound (Ubuntu) |
Fix Released
|
Medium
|
Conor Curran |
Bug Description
I did not knowingly have any sounds playing, was using Chrome web browser and had just opened my emai, inbox. When I was presented with the crash notification. I have been installing software using the terminal , but nothing that was using the audio system that I can think of at present. My ubuntu software system is in fail. I was installing apps like gdebi, some gtk themes, gparted, etc. mostly system apps. Sorry not more help. Thank you.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-sound 0.8.0.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-2-generic x86_64
NonfreeKernelMo
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Dec 4 20:03:13 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
Signal: 6
SourcePackage: indicator-sound
StacktraceTop:
raise () from /lib/x86_
abort () from /lib/x86_
pa_cvolume_set () from /usr/lib/
?? ()
dbusmenu_
Title: indicator-
UpgradeStatus: Upgraded to precise on 2011-12-04 (0 days ago)
UserGroups:
Related branches
- Antti Kaijanmäki: Pending requested
- Ted Gould: Pending requested
-
Diff: 173 lines (+36/-25)4 files modifiedsrc/metadata-widget.c (+14/-13)
src/pulseaudio-mgr.c (+0/-1)
src/slider-menu-item.c (+21/-11)
src/transport-widget.c (+1/-0)
visibility: | private → public |
Changed in indicator-sound: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
assignee: | nobody → charles (charlesk) |
Changed in indicator-sound: | |
assignee: | charles (charlesk) → Conor Curran (cjcurran) |
status: | Confirmed → Triaged |
milestone: | none → 0.8.2.0 |
Changed in indicator-sound: | |
status: | Fix Committed → Fix Released |
This crash has the same stack trace characteristics as bug #850662. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.