Version: (using KDE 4.2.2) OS: Linux Installed from: Ubuntu Packages anyelon@nirvana:~$ uname -a Linux nirvana 2.6.27-14-generic #1 SMP Wed Apr 15 18:59:16 UTC 2009 i686 GNU/Linux aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Intel [HDA Intel], device 0: ALC880 Analog [ALC880 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 when I start amarok it appears this notification Phonon :KDE's Multimedias Library Audio playback HDA Intel (ALC880 Analog) does not work. Falling back to default. also when I go to the system settings->multimedia->music and test the Audio Output HDA Intel (ALC880 Analog) it appears again.
I have the same problems with my HDA NVIDIA AD198x: **** List of PLAYBACK Hardware Devices **** card 0: NVidia [HDA NVidia], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 1: AD198x Digital [AD198x Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 KNotify tells me, that my HDA NVIDIA AD198x Analog doesn't work and switches to HDA NVIDIA AD198x Digital. It only occures at system-startup, not always but very often (~50%). Sometimes I'm getting the KNotify-message two times (with a delay of about 5) seconds). I noticed that after a restart of Amarok, the device is working again, so maybe something is locking the device ? However, it also occures, if Amarok is not started. I'm using KDE 4.2.4 with Phonon 4.3.1 (Xine) on openSUSE 11.1. Is there something we can do to investigate this ? My knowledge about the sound-system is very limited...
After reading lots of articles/forum-threads during the last weeks, I removed pulseaudio from my system and all problems are gone ! To clarify that: the pure presence of the pulseaudio-server causes the problems. It doesn't make a difference if I install additional modules/plugins or not (with xine-pulseaudio-plugin, an additional device "pulseaudio" appears in the KDE-system settings and it works). Is there anything that could be done to improve the compatibility of Phonon with pulseaudio ?
*** This bug has been marked as a duplicate of bug 188444 ***