amarok will not play any music

[Tim Lunn]

Just upgraded to Jaunty.

When I start amarok, it says is cannot access the sound device. As a result there is no sound when I try to play any music,

error message
"The audio playback device HDA Intel ALC1200 is unavailable"

Description: Ubuntu jaunty (development branch)
Release: 9.04

amarok:
  Installed: 2:2.0.2mysql5.1.30-0ubuntu2

[Andrew Ash (ash211)]

The development branch of Jaunty was a long time ago now. Tim, can you please update your Jaunty install and give it a shot again? Please report back with the version of Amarok you're using (''apt-cache policy amarok''), whether other audio apps are working or not, and what sound settings you're using on Amarok.

Thanks!

[Myriam Schweingruber (myriam)]

Tim, your problem is due to the fact you use pulseaudio, which is apparently a packaging error, as it should not be there in Kubuntu 9.04. Remove Pulseaudio, make sure you use the phonon-xine-backend and have the codecs installed and it will work. This will be solved differently in the next Kubuntu version anyway

Not an Amarok bug, so reasigning to pulseaudio.

[Tim Lunn (darkxst)]

Except I am using ubuntu not kubuntu.

Sent from my phone

On 17/07/2009, at 6:26 PM, Myriam Schweingruber <<email address hidden>
 > wrote:

> Tim, your problem is due to the fact you use pulseaudio, which is
> apparently a packaging error, as it should not be there in Kubuntu
> 9.04.
> Remove Pulseaudio, make sure you use the phonon-xine-backend and have
> the codecs installed and it will work. This will be solved differently
> in the next Kubuntu version anyway
>
> Not an Amarok bug, so reasigning to pulseaudio.
>
> --
> amarok will not play any music
> https://bugs.launchpad.net/bugs/351485
> You received this bug notification because you are a direct subscriber
> of the bug.

[Andrew Ash (ash211)]

Tim, please update and let us know whether this is still an issue on the newest version of Amarok. Thanks!

Possibly related to bug 349847.

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as requested in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the "Status" column, and change the status back to "New". Thanks again!