As of (about) Monday's Rawhide update, I now get a dialog box when I log in with a KDE session:
Sound server informational message: Error while initializing the sound driver: device: default can't be opened for playback (Connection refused) The sound server will continue, using the null output device.
Sound still seems to be working, audacity & xine are all I've tried. Assuming the message isn't bogus, where should I look next?
TIA Fulko
Fulko Hew wrote:
As of (about) Monday's Rawhide update, I now get a dialog box when I log in with a KDE session:
Sound server informational message: Error while initializing the sound driver: device: default can't be opened for playback (Connection refused) The sound server will continue, using the null output device.
pulseaudio not working?
Make sure you have 'kde-settings-pulseaudio' installed.
-- Rex
On 10/26/07, Rex Dieter rdieter@math.unl.edu wrote:
Fulko Hew wrote:
As of (about) Monday's Rawhide update, I now get a dialog box when I log in with a KDE session:
Sound server informational message: Error while initializing the sound driver: device: default can't be opened for playback (Connection refused) The sound server will continue, using the null output device.
pulseaudio not working?
Make sure you have 'kde-settings-pulseaudio' installed.
Thanks! That was it, but... that implies there was an uncaught dependency during the daily rawhide upgrade process...
The pulseaudio stuff that was already installed was:
alsa-plugins-pulseaudio-1.0.14-5.fc8 akode-pulseaudio-2.0.1-9.fc8 pulseaudio-0.9.7-0.16.svn20071017.fc8 pulseaudio-libs-0.9.7-0.16.svn20071017.fc8 pulseaudio-esound-compat-0.9.7-0.16.svn20071017.fc8 pulseaudio-core-libs-0.9.7-0.16.svn20071017.fc8
So I assume at some point this 'kde-settings-pulseaudio' was created and added, but, and I'm speculating now... it was not a dependency of anything that was updated since then. I.e. Why wasn't it auto-sucked in?
I guess in the long run, only Rawhide updaters would get caught by this problem (because they update piecemeal). Otherwise, this package would/should have been caught by an update of KDE if you were to do a KDE update today?
Fulko Hew wrote:
On 10/26/07, Rex Dieter rdieter@math.unl.edu wrote:
Fulko Hew wrote:
As of (about) Monday's Rawhide update, I now get a dialog box when I log in with a KDE session:
Sound server informational message: Error while initializing the sound driver: device: default can't be opened for playback (Connection refused) The sound server will continue, using the null output device.
pulseaudio not working?
Make sure you have 'kde-settings-pulseaudio' installed.
Thanks! That was it, but... that implies there was an uncaught dependency during the daily rawhide upgrade process...
...
So I assume at some point this 'kde-settings-pulseaudio' was created and added, but, and I'm speculating now... it was not a dependency of anything that was updated since then. I.e. Why wasn't it auto-sucked in?
It's not a hard dependency (you have the option of running without pulseaudio). but added to comps' kde-desktop group.
You'd get that, plus any new default stuff via: yum groupinstall kde-desktop
-- Rex
On 10/26/07, Rex Dieter rdieter@math.unl.edu wrote:
Fulko Hew wrote:
On 10/26/07, Rex Dieter rdieter@math.unl.edu wrote:
Fulko Hew wrote:
As of (about) Monday's Rawhide update, I now get a dialog box when I log in with a KDE session:
Sound server informational message: Error while initializing the sound driver: device: default can't be opened for playback (Connection refused) The sound server will continue, using the null output device.
pulseaudio not working?
Make sure you have 'kde-settings-pulseaudio' installed.
Thanks! That was it, but... that implies there was an uncaught dependency during the daily rawhide upgrade process...
...
So I assume at some point this 'kde-settings-pulseaudio' was created and added, but, and I'm speculating now... it was not a dependency of anything that was updated since then. I.e. Why wasn't it auto-sucked in?
It's not a hard dependency (you have the option of running without pulseaudio). but added to comps' kde-desktop group.
_I_ didn't ask for pulseaudio... It just appeared (somehow).
You'd get that, plus any new default stuff via:
yum groupinstall kde-desktop
Right, but my point is that... I had an already running, installed system, I did a yum update and now I get error/warning messages. - I didn't do anything wrong. - The system allowed a 'bad' thing to happen. - The system didn't auto-add 'kde-settings-pulseaudio', - I didn't know I (now) needed 'kde-settings-pulseaudio'.
Fulko Hew wrote:
Right, but my point is that... I had an already running, installed system, I did a yum update and now I get error/warning messages.
- I didn't do anything wrong.
- The system allowed a 'bad' thing to happen.
- The system didn't auto-add 'kde-settings-pulseaudio',
- I didn't know I (now) needed 'kde-settings-pulseaudio'.
My point too, is that things *should* continue to "just work". Something else is causing your problem. Is alsa-plugins-pulseaudio installed? if so, bingo.
-- Rex
On 10/26/07, Rex Dieter rdieter@math.unl.edu wrote:
Fulko Hew wrote:
Right, but my point is that... I had an already running, installed
system,
I did a yum update and now I get error/warning messages.
- I didn't do anything wrong.
- The system allowed a 'bad' thing to happen.
- The system didn't auto-add 'kde-settings-pulseaudio',
- I didn't know I (now) needed 'kde-settings-pulseaudio'.
My point too, is that things *should* continue to "just work". Something else is causing your problem. Is alsa-plugins-pulseaudio installed? if so, bingo.
Yes it is (I listed all the pulse rpms I had installed) in a previous email. so... is having alsa-plugins-pulseaudio good, or bad? I didn't explictly include it, but it would have come in based on something else, but I couldn't tell you what.
On 10/26/07, Rex Dieter rdieter@math.unl.edu wrote:
Fulko Hew wrote:
Yes it is (I listed all the pulse rpms I had installed) in a previous email. so... is having alsa-plugins-pulseaudio good, or bad?
Good if you're actually using pulseaudio, bad if not. See my and Stan's followup's in other threads...
Yes, I've started watching that thread too, but it all begs the question/comment:
"I'm a dumb user... how do I know if I'm using pulseaudio or not?... when do I want pulseaudio versus alsa (alsa-plugins-pulseaudio)?
I just want my audio to work, and not get any error messages."
Actually I _am_ smarter than that ;-) but not neccessarily that knowlegable in each audio sub-system each audio app, both desktop infrastructures, and their relationships. :-(
Fulko Hew wrote:
On 10/26/07, Rex Dieter rdieter@math.unl.edu wrote:
Fulko Hew wrote:
Yes it is (I listed all the pulse rpms I had installed) in a previous email. so... is having alsa-plugins-pulseaudio good, or bad?
Good if you're actually using pulseaudio, bad if not. See my and Stan's followup's in other threads...
Yes, I've started watching that thread too, but it all begs the question/comment:
"I'm a dumb user... how do I know if I'm using pulseaudio or not?... when do I want pulseaudio versus alsa (alsa-plugins-pulseaudio)?
I just want my audio to work, and not get any error messages."
It's an area wrt fedora's pulseaudio support that NEEDSWORK. I agree with you, things should "just work".
Right now, the work to enable, and integrate with pulseaudio is left to individual DE's (ie, gnome, kde). Not ideal.
-- Rex
-
Fulko Hew -
Rex Dieter