-   Linux - Desktop (
-   -   No sound in KDE4 (

vincix 12-06-2011 04:28 AM

No sound in KDE4
I know this topic is as old as the hills and I've searched for quite a few posts, but I haven't found an answer yet.
Audio doesn't work anymore, I had sound before, although it was inconsistent - sometimes it worked (in a session that is), sometimes it didn't (youtube, quakelive etc). Now, since I installed a software called tv-maxe (related to which there was this sound problem that's been reported when you turned the volume down), it doesn't work at all. From time to time, KDE would tell me that linux couldn't find anymore neither the hda intel hdmi 0,1 (hdmi audio output, nor hda intel (hdmi 0 and 1) and asked me if I wanted to ignore it - I don't know why it did that, as there's no connection whatsoever to my audio card (i don't use hdmi). It it asks me if I want to permanently forget about these devices. Now, I use a Sound Blaster Audigy, but I also have an integrated audio card (intel hda) When I go to the to the system settings - multimedia to test my sb audio card it works, but it doesn't work in any other programs (neither in tv-maxe in which it did work in the beginning). If I enter audacious, then an error shows up: ALSA error, No suitable mixer element found. So probably linux is shifting between the audio cards? Otherwise, all my kde4 sounds/notifications seem to work.
I use Slackare on a 32-bit arch. with KDE4.

serafean 12-06-2011 11:33 AM


First some definitions :
  • Device : Is the hardware your computer uses to output sound. In your case you have 2 devices : the intel HDA and the Audigy. (If you have a separate graphic card with HDMI output, you might have a third.
  • Alsa : is the layer through which applications talk to the hardware (devices). but its a bit more then that : with proper (read complex) configuration you can do wonders with it (upmixing, bridging ouptputs...). Big downside : any device can be used by only one application at a time.
  • Pulseaudio : is a sound server. its a layer (completely optional) that sits between applications and ALSA. It can do everything ALSA can and a bit more. And since it sits between ALSA and the applications it can mix streams : many apps can play at the same time.

I suspect that the non-kde applications are trying to use the sound devices for themselves, thus not allowing anyone else access. Maybe even trying to use the wrong device : if you set the sound preferences using KDE, it will unfortunately only apply to KDE applications).

If you want easy configuration I suggest you install pulseaudio and work up from there.
if you want to configure ALSA, start with a ~/.asoundrc. Once you chew through the beginnings, it's quite simple. I had to do it, and documented my progress here.
Personnally I don't like PulseAudio, and I'd go with asoundrc;

Unfortunately this Information is all I can give you, since your description doesn't give me enough hints as to figure out what is really going on. I hope you can use all this to figure out what is going on, and maybe even fix it :)
Don't hesitate to post back.

Also the software has absolutely no idea whether something is connected to an audio output or not.
Theory : If a device is taken by another application, kde can't access it and decides it can't be used => asks if you want to forget about it.


All times are GMT -5. The time now is 03:33 AM.