Amarok playback on pulse-audio breaks when another application makes a sound

[Vertago1]

I will have amarok playing music, and as soon as I start skype, a wine application, or flashplayer the output of amarok gets broken and I have to close it, and open it before it works again. I think it is related to pulse audio but it may be a problem with amarok.

I noticed this problem in earlier versions of kubuntu but it has persisted into the Lucid beta.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: amarok 2:2.3.0-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Fri Apr 2 13:29:04 2010
EcryptfsInUse: Yes
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: amarok

[Gabe Gorelick (gabegorelick)]

You're right it is possibly a pulseaudio bug. Reassign it to the pulseaudio package if you get this bug in another application besides amarok.

[Vertago1 (vertago1)]

It affects browser plugins too, it needs to be reassigned to pulse audio.

[Jean-Sebastien Gosselin (jsgosselin)]

I'm experiencing this behavior too, but I'm not sure if it is really related to pulse-audio.

I have observed it only happens when I use the Xine Backend in Phonon. When I switch to Gstreamer, everything seems to work fine.

[Bill Fraser (bfraser)]

I am having this problem too, with the Xine backend in Phonon. If I try to switch to the Gstreamer backend, however, Amarok segmentation faults every time I start it as described in https://bugs.launchpad.net/ubuntu/+source/phonon/+bug/566367.

According to https://bugs.kde.org/show_bug.cgi?id=232068#c52 on the upstream bug, this is at least in part a problem with Kubuntu's packages as they are broken.

Amarok now refuses to produce any sound (even with the Xine backend) as it seems to think there is a problem with the device, so I have resorted to using Audacious which plays through pulse just fine.

[Harald Sitter (apachelogger)]

We changed the default Phonon backend a while ago, which should have fixed this issue.