Description of problem: PackageKit-gstreamer-plugin does not find any needed media-codecs even if the RPMfusion-repo is installed and enabled. Version-Release number of selected component (if applicable): PackageKit-gstreamer-plugin-0.6.19-3.fc15.x86_64 How reproducible: Always Steps to Reproduce: 1. Play any unsupported media (mp3, wma, quicktime...) 2. PackageKit-gstreamer-plugin then is searching for plugins but will not find any Expected results: PackageKit-gstreamer-plugin should find the codecs (gstreamer-ffmpeg for example) as in F14.
I see this only with mp3 files. When other media first are played, the codecs will be found.
confirmed, same issue here. packagekit verbose information didn't help much though. but the totem output did help: it searches for: ** Message: PackageKit: structure: gstreamer0.10(decoder-audio/mpeg)(mpegaudioversion=1)(mpegversion=1)(layer=3)()(64bit) note the mpegaudioversion=1 while what the package actually provides is gstreamer0.10(decoder-audio/mpeg)(mpegversion=1)(layer=3)()(64bit) note the mpegversion=1 so it looks for mpegaudioversion, while the package only has mpegversion. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This is a problem that has been in the design of the automatic plugin installation from the start and has so far been ignored because it didn't happen (or nobody noticed). The upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=588783 The short version is: When a "subfeature" (GStreamer calls that a structure field) is not provided by a plugin, GStreamer assumes it handles any of those values, but RPM does not. So if we request "gstreamer0.10(decoder-audio/mpeg)(mpegaudioversion=1)(mpegversion=1)(layer=3)()(64bit)" and a plugin provides "gstreamer0.10(decoder-audio/mpeg)(mpegversion=1)(layer=3)()(64bit)", for GStreamer this would be a compatible match. Even "gstreamer0.10(decoder-audio/mpeg)()(64bit)" would be a compatible match. Now I have no idea about RPM to know if it can be made to treat these things the same way. If we can't, the only option I can come up with is changing the RPM provides line to not include the subfeatures. This will make more plugins match a certain query, even ones that cannot support the given format, but it will never fail to list any that can actually support a given format. And thinking about it, that seems like a way better solution.
*** This bug has been marked as a duplicate of bug 680809 ***