Bug 1319399
Summary: | "Could not find plugin 'GStreamer' for application 'amarok'" | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Martin Kho <rh-bugzilla> |
Component: | amarok | Assignee: | Rex Dieter <rdieter> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 24 | CC: | jgrulich, kim-rh, pradhanphy, rdieter, smparrish |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-04-20 23:16:52 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Martin Kho
2016-03-19 12:55:53 UTC
Same problem here. Running into debugging mode gives this warning. -- WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded or possibly, https://bodhi.fedoraproject.org/updates/FEDORA-2016-d3a880fb8c we're sorting out a qt4 plugin issue for some stuff built erroneously by gcc6 *** This bug has been marked as a duplicate of bug 1327360 *** amarok, phonon, phonon-backend-gstreamer all have the proper qt buildkey now: buildkey=x86_64 linux g++-4 full-config So, it's problem is apparently something other than the issue tracked in bug #1327360 , re-opening See latest bug #1327360 , comment, but it would appear the latest batch of builds in fact did not fix the problem (but introduced yet another different/incompatible QT_BUILD_KEY). Short version: this issue is (still) probably a dup of bug #1327360 , but I'll double/triple check it this time before marking it as such confirmed fixed qt/phonon takes care of this, remarked as dup, updates coming soon *** This bug has been marked as a duplicate of bug 1327360 *** |