Description of problem: On viewing certain websites with videos, Epiphany prompts a PackageKit prompt: 'PackageKit-gstreamer-plugin requires an additional plugin to decode this file. The following plugin is required: H.264. Do you want to search for this now?' The options are 'cancel' and 'search' 'search' prompts to install: - gstreamer-crystal-hd (no gstreamer1) - gstreamer1-plugins-bad-free[1] - gstreamer1-vaapi 'install' prompts: 'The package that is trying to install is already installed' Version-Release number of selected component (if applicable): epiphany-3.14.2-2.fc21.x86_64 gstreamer1-1.4.4-1.fc21.x86_64 How reproducible: Every time for certain websites. Steps to Reproduce: 1. go to http://www.nieuwsblad.be/sportwereld/cnt/dmf20141127_01398835 2. click play 3. Actual results: Popup to install already-installed packages. Expected results: One of: - an attempt to install the actually needed plugins - a prompt saying "plugin unavailable" - play the video Additional info: H.264 is, I believe, actually provided by gstreamer1-plugins-ugly (/usr/lib64/gstreamer-1.0/libgstx264.so) . This is installed. Related: https://bugzilla.redhat.com/show_bug.cgi?id=1051635 https://bugs.webkit.org/show_bug.cgi?id=135972 [1] Really? a webbrowser plugin wants to install something that's known-bad?
I can confirm this bug; codec installation in F21 is completely borked in the way described in comment #0, 100% reproducible for me with or without rpmfusion installed. I've checked with our gstreamer expert and he thinks this is most likely not a WebKit bug, so reassigning to PackageKit. It was also completely broked in F20, but differently-so: in F20 PackageKit would claim that codec installation was successful, but then ask the user to install the exact same codecs again and again forever when trying to watch a video. So F21 is probably an improvement in that at least there's an error message. (In reply to Berend De Schouwer from comment #0) > [1] Really? a webbrowser plugin wants to install something that's known-bad? It means the codecs are shoddy in some way and therefore unsupported, but that's better than no codec at all. See [1] if you're curious about the naming scheme. [1] http://gstreamer.freedesktop.org/releases/gst-plugins-bad/1.4.4.html
Oh, example video: anything on YouTube: e.g. http://www.youtube.com/watch?v=UZ_L3b7osx4
I can usually play youtube videos :) But not this one: not available in my country (government or google bug; not a packagekit bug)
gstreamer-crystal-hd and gst-vaapi shouldn't be an option for auto-installation (they need to disable the addition of Provides for MPEG-4), and possibly be installed by default (for the crystalhd one), as it should work out of the box if the system has such hardware.
(In reply to Bastien Nocera from comment #4) > gstreamer-crystal-hd and gst-vaapi shouldn't be an option for > auto-installation (they need to disable the addition of Provides for > MPEG-4), I have filed bug 1184975 and bug 1184977.
I agree that both gst-crystalhd/vaapi shouldn't provides h264 capability. (patch welcomed). Both depend on hardware that might or might not be present at runtime (thinking of a livemedia). I also think that having them installed by default would be the way to go, but having gst-vaapi by default often lead to issue (specially reported with firefox) when used hit hardware specifics issues. That was probably removed from the default set. I will try to set if things settle with libva 1.5.x branch Also one question about , is there a plan to rename to gstreamer over gstreamer1 at some point (removing obsolete alternate gst version). Does the detection plugin rely on the package name to discover the appropriate version ? (as #c1 suggests) ?
This has been resolved in GNOME 3.16 in Fedora 22.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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.
Looks like it is resolved for me in F23.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.