Yes, it only seems to happen with KDE. I also found that Pulseaudio installs one extra start-up script for KDE only in /etc/xdg/autostart. The man pages of these scripts both mention they will use an already running Pulseaudio.
I think the proper solution is either:
- run Pulseaudio *once* and never again (when logging in)
- fix Pulseaudio's self-detection so that it works when the first instance is still initializing
As for running Pulseaudio as a specific user, I wonder what would happen when multiple users are logging onto a system at the same time. Would this not create a similar conflict with each user's Pulseaudio trying to use the ALSA devices at the same time?
Yes, it only seems to happen with KDE. I also found that Pulseaudio installs one extra start-up script for KDE only in /etc/xdg/autostart. The man pages of these scripts both mention they will use an already running Pulseaudio.
I think the proper solution is either:
- run Pulseaudio *once* and never again (when logging in)
- fix Pulseaudio's self-detection so that it works when the first instance is still initializing
As for running Pulseaudio as a specific user, I wonder what would happen when multiple users are logging onto a system at the same time. Would this not create a similar conflict with each user's Pulseaudio trying to use the ALSA devices at the same time?