After installing KDE 3.2 I lost the sound, and the usual cures don't seem to help. Reinstalling via Yast2 does nothing, and alsaconf actually hangs while trying to play the sample sound. Removing the alsaconf entries from /etc/modules.conf doesn't help either. What's particularly odd is that although the problem was provoked by installing KDE 3.2, it doesn't seem to be caused by KDE 3.2. I tried booting into runlevel 3, which avoids activating KDE at all, and then ran alsaconf. Again alsaconf hung while trying to play the sample sound. One possibility is that when I ran redcarpet to install KDE 3.2, it also brought in some other package that's causing the problem. If I start at runlevel 5 and log in via kdm as a virgin user (one just created by Yast), I get: Sound server informational message Error while initializing the sound driver device: default can't be opened for playback (Device or resource busy) The sound server will continue using the null output device. Any suggestions on how to go about tracking this one down? Paul Abrahams