After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 773367 - Codec installation fails with "Unable to find requested software"
Codec installation fails with "Unable to find requested software"
Status: RESOLVED NOTGNOME
Product: gnome-software
Classification: Applications
Component: General
3.25.x
Other Linux
: Normal major
: ---
Assigned To: GNOME Software maintainer(s)
GNOME Software maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-10-22 22:40 UTC by gnome.vrb
Modified: 2018-01-22 14:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description gnome.vrb 2016-10-22 22:40:32 UTC 
I am trying to install ALAC ( Apple Lossless Audio ) encoder, provided by gstreamer1.0-libav. If I manually do "apt-get install gstreamer1.0-libav", all works fine, and encoding works. But, auto codec installation fails.

Example:
--------

Running the following command,

/usr/bin/gstreamer-codec-install "gstreamer|1.0|rhythmbox|Apple Lossless Audio (ALAC) encoder|encoder-audio/x-alac" 

invokes gnome-software, which fails with "Unable to find requested software"

Expected result: gnome-software should prompt for installing "gstreamer1.0-libav" package.

/var/log/daemon.log:
--------------------

Oct 23 04:00:29 unstable PackageKit: what-provides transaction /1334_daddeade from uid 1000 finished with success after 2029ms
Oct 23 04:00:29 unstable PackageKit: get-details transaction /1335_babeddcd from uid 1000 finished with success after 518ms
Comment 1 Strangiato 2017-08-28 13:31:27 UTC 
Same problem on Arch running totem 3.24 and software 3.24.3.
Software does not find gst-libav required by totem.
Comment 2 Sebastien Bacher 2017-08-30 07:22:54 UTC 
That's a problem on Ubuntu as well using 3.25.90, it has been reported on https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1712979
Comment 3 Richard Hughes 2018-01-22 14:54:53 UTC 
I can't reproduce on Fedora, sorry. There was a PackageKit issue that was fixed a long time that sounds like this, but I don't remember more details.