Bug 26861 - libx264 and libx265 are missing for Kdenlive
Summary: libx264 and libx265 are missing for Kdenlive
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2020-06-26 12:58 CEST by Ojangu
Modified: 2020-07-09 19:38 CEST (History)
0 users

See Also:
Source RPM: kdenlive
CVE:
Status comment:


Attachments

Description Ojangu 2020-06-26 12:58:55 CEST
Description of problem:
Kdenlive can't find libraries for MP¤ and MP3. message: libx264 and libx265 are missing.
Two weeks ago all things with this libx... are correct.
Comment 1 David Walser 2020-06-26 15:45:06 CEST
Do you still have the tainted media enabled?

Source RPM: kdenlive.rpm => kdenlive
Keywords: (none) => NEEDINFO

Comment 2 Lewis Smith 2020-06-29 22:24:25 CEST
Yes, you do need to confirm the tainted repos.
I have just done a theoretical check, and the bug is not valid if Tainted are enabled:
$ urpmq --requires-recursive kdenlive | grep lib64x26
 lib64x264_155
 lib64x265_188
$ urpmq --whatrequires-recursive lib64x264_155 | grep kdenlive
 kdenlive
$ urpmq --whatrequires-recursive lib64x265_188 | grep kdenlive
 kdenlive

Resolution: (none) => INVALID
Summary: libx264 and libx265 are missing => libx264 and libx265 are missing for Kdenlive
Status: NEW => RESOLVED

Comment 3 Ojangu 2020-07-02 20:13:49 CEST
i have same results, but anyway in kdenlive libx264 and 265 is not suported. it happens also in odher computer after updates

Resolution: INVALID => (none)
Status: RESOLVED => REOPENED

Comment 4 David Walser 2020-07-02 23:27:14 CEST
Because you didn't enable tainted.

Resolution: (none) => INVALID
Status: REOPENED => RESOLVED

Comment 5 Ojangu 2020-07-09 19:38:21 CEST
Thanks, today after mlt-kdenlive update more problems on renering part are not

Resolution: INVALID => FIXED


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