On 10/26/07, Rex Dieter <rdieter@xxxxxxxxxxxx> wrote:
_I_ didn't ask for pulseaudio... It just appeared (somehow).
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:
> On 10/26/07, Rex Dieter <rdieter@xxxxxxxxxxxx> 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'.
-- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
