Mailinglist Archive: opensuse-kde (348 mails)

[Sabine <sjmk@xxxxxxx>]

On Saturday 07 February 2004 10:23, Paul W. Abrahams wrote:

> A useful test of what's going on is to run alsaconf (as root).  As
> the last step in the configuration it tries to play a sound.  
> Before I fixed my sound card settings, alsaconf would hang up when
> trying to play the sample.  My guess is that it's unlikely that
> alsaconf will neither get stuck nor produce a sound.
>
> Another useful test is to use the aplay program from a command line
> to play a wave file directly.  That bypasses any KDE funninesses.

I turned arts off and ran alsaconf and picked my Santa Cruz Turtle 
Beach soundcard. This time it actually did produce sound. But only 
during the alsa setup, not through any application. I ran the alsconf 
on the old soundcard, had sound, then things got sort of mixed up 
(in /etc/modules.conf), so I removed the sound cards via yast, made 
sure this was reflected in modules.conf, disabled and enabled the 
sound in the KDE control center (I have no idea why I did that and it 
might not be necessary at all) and reinstalled the Santa Cruz (yast), 
and all over a sudden I had sound. I rebooted to see if it sticks, 
and it did. Now arts is running, and I have sound. First only the 
apps in kde played sound, but not xmms. Apparently an alsa plugin 
setting got changed, after fixing that I have my sound back.

I really have no idea, why it worked now, since I did remove my sound 
cards before. The only new thing I introduced was that I stopped arts 
before I set up the soundcard. Maybe that was the trick? Anyways, it 
works now. Thanks for the tip with alsaconf, it made me look at this 
from a different angle.

Cheers,
-- 
Sabine