[Conexant CX20561 (Hermosa)] No indicator that input is muted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Sound Menu |
Fix Released
|
Medium
|
Conor Curran | ||
indicator-sound (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned | ||
pulseaudio (Ubuntu) |
Opinion
|
Wishlist
|
Unassigned |
Bug Description
When my computer boots, the audio input is completely muted. When I want to make a Skype or Mumble call, I have to open up the Sound preferences and uncheck the "Mute" checkbox on the input tab. I would argue that this is a bug in itself.
However, the real bug I want to report is that there is no visible indicator that I have to do this. Most commonly, I find out by beginning a conversation, talking and then the other parties in the conversation asking me whether I'm there and whether I'm muted.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: alsa-base 1.0.23+
ProcVersionSign
Uname: Linux 2.6.35-23-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0c: jml 2156 F...m pulseaudio
/dev/snd/pcmC0D0p: jml 2156 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf2620000 irq 46'
Mixer name : 'Conexant CX20561 (Hermosa)'
Components : 'HDA:14f15051,
Controls : 14
Simple ctrls : 7
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'
Mixer name : 'ThinkPad EC 7XHT21WW-1.03'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Wed Dec 1 14:51:15 2010
EcryptfsInUse: Yes
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=en_AU.UTF-8
SHELL=/bin/bash
SelectedCard: 0 Intel HDA-Intel - HDA Intel
SourcePackage: alsa-driver
Symptom: audio
Title: [Conexant CX20561 (Hermosa)] Recording problem
UserAsoundrc:
# ALSA library configuration file
# Include settings that are under the control of asoundconf(1).
# (To disable these settings, comment out this line.)
</home/
dmi.bios.date: 07/30/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 6DET28WW (1.05 )
dmi.board.name: 7454A12
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 7454A12
dmi.product.
dmi.sys.vendor: LENOVO
Related branches
- Ted Gould (community): Approve
-
Diff: 1537 lines (+1044/-44)18 files modifiedsrc/Makefile.am (+5/-1)
src/active-sink.c (+61/-5)
src/active-sink.h (+19/-6)
src/common-defs.h (+5/-1)
src/indicator-sound.c (+62/-4)
src/music-player-bridge.vala (+5/-3)
src/mute-menu-item.c (+1/-0)
src/player-item.vala (+1/-2)
src/pulseaudio-mgr.c (+190/-19)
src/pulseaudio-mgr.h (+2/-0)
src/settings-manager.vala (+2/-0)
src/sound-service-dbus.c (+6/-2)
src/sound-service-dbus.h (+2/-1)
src/sound-service.c (+2/-0)
src/voip-input-menu-item.c (+277/-0)
src/voip-input-menu-item.h (+70/-0)
src/voip-input-widget.c (+279/-0)
src/voip-input-widget.h (+55/-0)
Changed in pulseaudio (Ubuntu): | |
importance: | Undecided → Wishlist |
Changed in indicator-sound (Ubuntu): | |
importance: | Undecided → Wishlist |
Changed in indicator-sound (Ubuntu): | |
status: | New → Opinion |
Changed in indicator-sound: | |
status: | New → Opinion |
assignee: | nobody → Matthew Paul Thomas (mpt) |
tags: | added: design |
Changed in indicator-sound: | |
status: | Invalid → Confirmed |
assignee: | nobody → Conor Curran (cjcurran) |
status: | Confirmed → In Progress |
importance: | Undecided → High |
importance: | High → Medium |
Changed in indicator-sound: | |
status: | In Progress → Fix Released |
So the problem here is that, on a nontrivial portion of hardware, having the input unmuted alongside the output results in pretty disastrous feedback, which is arguably a nastier user experience than an unintuitive capture- enabled- by-default mechanism. This bit of hardware nastiness is not limited to any subset of codecs (or revisions of codecs, even) or controllers either, unfortunately. The question, therefore, becomes, "Should Ubuntu choose brokenness A by default over brokenness B?"
Now, I empathize with your frustration, but at a distro choice level, it's very difficult to judge whether brokenness A is worthwhile over brokenness B.
I think in this case that we should evaluate unmuting the microphone once a pulse client connects a source-output. Any opinions?