Bug 18195 - kdenlive installs incorrectly and cannot render
Summary: kdenlive installs incorrectly and cannot render
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Juan Luis Baptiste
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-13 00:50 CEST by Vladimir Zawalinski
Modified: 2018-10-07 15:56 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Vladimir Zawalinski 2016-04-13 00:50:01 CEST 
Description of problem:

kdenlive 09.9.10 (kde development platform 4.14.5) installs expecting to find melt at /usr/bin/melt6.

Melt for Mageia 5 is found at /usr/bin/melt.  Therefore trying to render anything returns 'could not find melt'.

Changing the melt location to the correct one in 'settings' fixed the problem.  However, since this package is maintained by Mageia, this failure should not occur.
Barry Jackson 2016-04-13 01:02:48 CEST

CC: (none) => zen25000

Comment 1 Marja Van Waes 2016-04-15 14:32:07 CEST 
Assigning to maintainer.

CC: (none) => marja11
Assignee: bugsquad => juan.baptiste

Comment 2 Marja Van Waes 2018-04-24 19:00:35 CEST 
Hi Vladimir,

Thank you for having taken the needed time to report this issue!

We regret if this issue didn't get fixed.

Closing as OLD, because Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed.

Marja
Comment 3 Marja Van Waes 2018-10-07 15:56:29 CEST 
(In reply to Marja Van Waes from comment #2)

> 
> Closing as OLD, because Mageia 5 has officially reached its End of Life on
> December 31st, 2017

Now really closing :-/

Resolution: (none) => OLD
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.