> If the workaround is to make amarok not use pulseaudio in kubuntu this
> is hardly a fix for gnome users who are using pulseaudio. Surely we need
> to patch whatever this "abysmal behaviour" in pulseaudio is instead.
However, according to Geoffrey's feedback, he has:
I'd like feedback from other people experiencing the symptom described in
the bug's description. Please try the four steps that I just described.
Then, while Amarok is running (after restarting it), please check the
output from `sudo fuser -v /dev/dsp* /dev/snd/*'.
It should be fairly clear that PulseAudio is not the culprit if the
symptom is reliably reproducible after the procedure is followed and
PulseAudio has been verified not to be running.
On Sun, 5 Apr 2009, Conan wrote:
> If the workaround is to make amarok not use pulseaudio in kubuntu this
> is hardly a fix for gnome users who are using pulseaudio. Surely we need
> to patch whatever this "abysmal behaviour" in pulseaudio is instead.
However, according to Geoffrey's feedback, he has:
1) disabled PulseAudio autospawn;
2) killed PulseAudio;
3) restarted Amarok;
4) reproduced the symptoms.
I'd like feedback from other people experiencing the symptom described in
the bug's description. Please try the four steps that I just described.
Then, while Amarok is running (after restarting it), please check the
output from `sudo fuser -v /dev/dsp* /dev/snd/*'.
It should be fairly clear that PulseAudio is not the culprit if the
symptom is reliably reproducible after the procedure is followed and
PulseAudio has been verified not to be running.