Red Hat Bugzilla – Bug 192802
Update to amarok ver. 1.4.0 breaks gstreamer-10 audio-output
Last modified: 2007-11-30 17:11:33 EST
Description of problem:
After the recent update of amarok to ver. 1.4.0 the only audio-output option
available is helix. gstreamer-10 is not recognized by amarok.
Version-Release number of selected component (if applicable):
KDE: 3.5.2-0.2.fc5 Red Hat
Steps to Reproduce:
1.Upgrade amarok to ver. 1.4.0
Before amarok is started, a message box appears that it needs RealPlayer for
proper helix-support and that the audio-output options should be reconfigured.
The next message box (which only appears one time at the first start-up after
the upgrade) indicates a problem with the gstreamer-10 plugin. In the
audio-output options helix is the only available plugin.
amarok should work with gstreamer-10.
Gstreamer was disabled in Amarok 1.4 final by the Amarok devs, see line 25 in
*** Bug 192831 has been marked as a duplicate of this bug. ***
*** Bug 192905 has been marked as a duplicate of this bug. ***
> Gstreamer was disabled in Amarok 1.4 final by the Amarok devs, see line 25 in
If gst-10 has been disabled and the only available engine is helix, then there
should be a dependency on HelixPlayer in the SPEC-file. If one upgrades to the
current version and has HelixPlayer not installed it breaks amaroks audio-output.
That's right, I've fixed this, update pending (-5.fdr5)
*** Bug 193037 has been marked as a duplicate of this bug. ***
*** Bug 193463 has been marked as a duplicate of this bug. ***
Then there is no reason to build this package for eg. x86_64, where there is no
There has been a regression, gstreamer support has disappeared again. Since I
can't reopen this bug, I've opened a new one: bug #204745.
Also, why was this closed as NOTABUG? If it was broken and then was fixed, it
was a bug and it should have been closed as CURRENTRELEASE or NEXTRELEASE?
What I fixed was the dependency on HelixPlayer, which was not the subject of
this bug. Thus the NOTABUG.
*** Bug 204745 has been marked as a duplicate of this bug. ***