to amarok engine to use from GNOME in main

Bug #15023 reported by Mathieu Lorentz
14
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Fix Released
Medium
Jonathan Riddell

Bug Description

I have installed the standard Ubuntu on a Dell Inspiron 8200. The sound is
working fine. I still have the basic package list in sources.list.
I installed the amarok package -- synaptics installed amarok-arts to satisfy
dependencies. When I first start the system, it says that it does not find a
sound engine. Then amarok starts. I can go in the menu Settings and choose
Configure Amarok. There I can select the sound engine arts Engine, the only one
available. After that, if I open and play an OGG or MP3, no sound comes out but
the scope shows activity as if sound was playing...
Is this a dependence problem ? Is the sound engine missing or conflicting with
Gnome sound engine ?

Revision history for this message
Mathieu Lorentz (matlo-iit) wrote :

I removed the keyword kubuntu because I'm not using kubuntu but the standard
hoary ubuntu, with Gnome. I just tried to install amarok on this configuration.
I think my system has nothing to do with kubuntu. Or does it ?

Revision history for this message
Matt Zimmerman (mdz) wrote :

Please leave the keyword field as it is; it is a tool for coordinating
development work. The amarok package is maintained by the Kubuntu team.

Revision history for this message
Olivier Magere (olivier-magere) wrote :

same here. Amarok doesn't work with the aRts engine (which works fine
otherwise). it works fine with the xine engine that is configured to use ALSA
(just as the aRts engine by the way)

Revision history for this message
Mathieu Lorentz (matlo-iit) wrote :

Actually Artsd does not work apparently. If I start it with artsdcontrol for
instance, it gives the same error message as when I start Amarok:
Sound server informational message:
Error while initializing the sound driver:
device: default can't be opened for playback (Device or resource busy)
The sound server will continue, using the null output device.

Revision history for this message
Chris Halls (halls) wrote :

(In reply to comment #4)
> Actually Artsd does not work apparently.
[...]
> device: default can't be opened for playback (Device or resource busy)

Right, my guess is that esd already has the sound device open. If you replace amarok-arts with
amarok-xine does it work?

Revision history for this message
Mathieu Lorentz (matlo-iit) wrote :

OK, I got it to work thanks to your comment Chris.
I installed amarok-engines, I don't think it was in the original packages list.
It's probably in Universe or something. Then new engines show up in the Amarok
sound system list. I selected GStreamer Engine, with Output plugin = esdsink.
And it works...
There's probably something to fix in the amarok package, so that it installs the
amarok-engines aswell.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Perhaps 'amarok-gstreamer' can be moved to main?

Revision history for this message
Kai F. Lahmann (kl) wrote :

if you want amarok under gnome, you can NOT use the arts-Plugin (as arst can't run there). You eigher need xine or gstreamer. So one of
these 2 should move into main.

Revision history for this message
Kai F. Lahmann (kl) wrote :

make the problem clear..

Revision history for this message
Barry deFreese (bddebian) wrote :

Can someone please clean up this report? Is there an actual bug or not? Thank you.

Changed in amarok:
status: Unconfirmed → Needs Info
Revision history for this message
Barry deFreese (bddebian) wrote :

Scratch that last comment. amarok-xine is in main in Dapper. Thank you.

Changed in amarok:
status: Needs Info → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.