Red Hat Bugzilla – Bug 1002831
Mic Boost and Internal Mic Boost are both in Playback and Capture in alsamixer
Last modified: 2015-02-18 06:25:39 EST
Description of problem:
When alsamixer is run on my T410 with HDA-Intel - HDA Intel, the Mic Boost and Internal Mic Boost sliders are under Playback, as well as the Capture. I believe microphone settings should be under the Capture only.
Incidently, xfce4-mixer shows the sliders only under Playback and not under Capture.
Version-Release number of selected component (if applicable):
# rpm -qf /bin/alsamixer
Steps to Reproduce:
1. Run alsamixer and try to set the Mic Boost.
The setting is under Playback (and in alsamixer under Capture as well).
The setting is under Capture.
The Mic boost applies to both the playback (the analog loopback) and to the capture. It's not an error.
(In reply to Jaroslav Kysela from comment #1)
> The Mic boost applies to both the playback (the analog loopback) and to the
> capture. It's not an error.
Alright. There's however still the case of xfce4-mixer showing it *only* under Playback. Could you please help me phrase the technical details of a bug report against xfce4-mixer (or reopen this bug and change component)?
For the xfce4-mixer maintainer/developer: Our rule is to expose the shared mixer controls in both directions (playback and capture) in our mixer apps (ALSA).
Jan: would you be willing to file this upstream at bugzilla.xfce.org? Or would you like me to do so?
(In reply to Kevin Fenzi from comment #4)
> Jan: would you be willing to file this upstream at bugzilla.xfce.org? Or
> would you like me to do so?
I'd prefer you did the upstream filing -- you probably already have account there. Thank you.
> The Mic boost applies to both the playback (the analog loopback) and to the capture. It's not an error
for cx20585 headphone , line out and dock line out are driectly connected to audio output and there is no loopback path from Mic jacks to output jacks
so this is a bug of the driver
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
I no longer have access to T410. If this is still a problem on that (and similar) hardware, could someone else chime in about the current state of affairs? Kevin, have we got the XFCE bugzilla that we could link from here?
I don't have a T410 here either.
I cant seem to find the upstream bug... perhaps I failed to file it. ;(
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.