Bug 986054 - gstreamer1-plugins-good 1.1.2 breaks banshee streaming radio, 1.0.7 is OK
gstreamer1-plugins-good 1.1.2 breaks banshee streaming radio, 1.0.7 is OK
Product: Fedora
Classification: Fedora
Component: gstreamer-plugins-good (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Benjamin Otte
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-07-18 17:23 EDT by Valdis Kletnieks
Modified: 2015-06-29 08:06 EDT (History)
1 user (show)

See Also:
Fixed In Version: gstreamer1-plugins-good 1.1.4-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-06-29 08:06:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Valdis Kletnieks 2013-07-18 17:23:00 EDT
Description of problem:
After upgrading to 1.1.2, trying to start up streaming of internet audio in Banshee fails:

[Info  17:04:24.384] nereid Client Started
[Info  17:04:24.424] GStreamer version, gapless: True, replaygain: False
[Error 17:04:29.186] GStreamer resource error: NotFound

and the attempt to stream the station fails.

Backing off to 1.0.7 gets this instead:

[Info  17:04:57.467] nereid Client Started
[Info  17:04:57.505] GStreamer version, gapless: True, replaygain: False

and the streaming works fine.

I've stared at an strace of the banshee process, and a diff of the 'rpm -qlp' output for the 1.0.7 and 1.1.2 rpms, not seeing anything obvious like a smoking-gun .so not being found just before the error message is issued.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:
Comment 1 Fedora End Of Life 2013-09-16 10:37:52 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
Comment 2 Valdis Kletnieks 2013-09-17 13:48:17 EDT
Was ready to close this one, as 1.1.4-1 has landed in Rawhide and that version works.

However, I'm not sure what version Fedora 20 is going to ship with - if somebody can tell me, I'll test that version and see if the problem is present.
Comment 3 Fedora End Of Life 2015-05-29 05:11:52 EDT
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 Fedora End Of Life 2015-06-29 08:06:20 EDT
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.