Remove amarok-artsd
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| amarok (Ubuntu) |
Fix Released
|
Critical
|
Jonathan Riddell | ||
Bug Description
I request that the amarok-artsd engine to be removed from the package
I request that the amarok-artsd engine to be removed from the package. It is known to be buggy, and it is currently unmaintained*. It also has been removed from 1.3.x.
In its place, I request that the amarok package _require_ (not just suggest) the amarok-gstreamer engine.
Also, I request that the amarok-gstreamer package require gstreamer0.80-mad, gstreamer0.
* http://
| Changed in amarok: | |
| assignee: | nobody → jr |
| JasonCohen (jcohen07) wrote | #1 |
| Jonathan Riddell (jr) wrote | #2 |
| Changed in amarok: | |
| status: | New → Fixed |
I definitely agree that alsasink or esdsink should be used by default. The default output plugin is currently osssink which is really horrible. It often complains that /dev/dsp is being used even when no other programs are playing sound. In addition, it doesn't work with ESD and therefore prevents all other programs and gnome from producing sounds. Either alsasink or esdsink would allow for multiplexing.
While I'm not sure if I would recommend completely removing amarok-artsd it certainly shouldn't be the default engine. As the author stated, the arts plugin isn't being maintained and it constantly crashed for me when I used it. Both the gstreamer and xine engines are far more stable and reliable.
I think that amarok should depend on gstreamer0.8-vorbis and gstreamer0.8-alsa and recommend gstramer0.8-mad. While I would like amarok to depend on gstramer0.8-mad so users wouldn't be upset when they can't play their MP3s, it's simply impossible. A package in main must have all its dependencies satisfied through main/restricted repositories. If amarok did depend on gstreamer0.8-mad, amarok would effectively be uninstallable for users who choose to only use fully supported packages. This is unacceptable.