Red Hat Bugzilla – Bug 427625
kscd alsa backend should use 'default' device for proper pulseaudio operation
Last modified: 2009-01-09 00:42:34 EST
Description of problem:
When I play an audiocd with kscd (via direct digital playback with the alsa
backend) it plays fine through the front speaker outputs. However, the output
stream does not appear in the pulseaudio volume control (pavucontrol) and so I
cannot switch to my headphones on the rear speaker output of my soundcard(*).
Presumably I would be unable to take advantage of PAs ability to switch to usb
If I set the alsa output device to 'default' in the kscd configuration (and
restart kscd to make it pick up changes), then the output stream is seen by
pulseaudio, as expected.
The arts backend has no problems with pulseaudio.
* Note that the PA default configuration only uses the first device for each
soundcard. I've added a second output sink with "load-module module-alsa-sink
device=rear sink_name=Headphones" in my .pulse.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Play music in kscd with the alsa backend
2. Open pavucontrol
3. Look for output stream from kscd.
FWIW the KDE 4 version of Kscd now defaults to Phonon, so for KDE 4 this should
be fixed by my patch to make Phonon default to the ALSA default device.
The default still needs fixing for Fedora 8 (and arguably 7 too, "default"
should also be used with dmix) though.
Should we set the default in kde-settings or should I patch kdemultimedia to
make it do the right thing by default? There's some code to use "plughw:0,0" as
the device if the device is not set, we can patch that to "default" or we can
just set "default" in kde-settings.
If either works (right?), it sounds to me like patching (and pushing upstream)
would be the preferred option.
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
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 prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
As I said, this is already fixed in F9, still it should be relatively easy to fix in F8, so maybe we should do it?
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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.
Thank you for reporting this bug and we are sorry it could not be fixed.