Bug 391017 - AppImage fails to access Lumas when loading project
Summary: AppImage fails to access Lumas when loading project
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: Installation (show other bugs)
Version: 17.12.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Vincent PINON
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-24 18:37 UTC by Dominik Leiner
Modified: 2018-05-31 21:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dominik Leiner 2018-02-24 18:37:49 UTC
I had created a project, using the AppImage Kdenlive-17.12.0d-x86_64. At one position in the project, I have used a composite transition with wipe "symmetric_clock.pgm". This worked fine, incl. rendering.

However, when I open the project, I get this "Clip error":

Luma File: /tmp/.mount_AWD1kz/usr/share/kdelnlive/lumas/HD/symmetric_clock.pgm

I can only open the project after removing the clip. The wipe method of the transition than changes to "none".

If i then save the project, close kdenlive, start a new instance from the AppImage, and load the project, a new temporary mount path is reported where the pgm file is not found.

I could, of course, create a copy of the pgm file into my project folder an use that one. However, it was easier, if kdenlive stored a path relative to the own folder.
Comment 1 Jean-Baptiste Mardelle 2018-04-10 19:20:19 UTC
Thanks for your report. It should be fixed in git, I will upload a new AppImage in 1-2 days so you can test.
Comment 2 Jean-Baptiste Mardelle 2018-04-11 18:37:14 UTC
18.04 RC AppImage has just been uploaded here:
https://files.kde.org/kdenlive/unstable/kdenlive-18.04-rc.AppImage.mirrorlist

Could you test and confirm that the issue is fixed ?
Thanks
Comment 3 Christoph Feck 2018-05-09 22:41:15 UTC
If you can provide the information requested in comment #2, please add it.
Comment 4 Christoph Feck 2018-05-31 21:39:07 UTC
No response; let's assume it is fixed. If you still see this issue, please add a comment, or re-open the bug.