Bug 408635

Summary: libc wrong version
Product: [Applications] kdenlive Reporter: EssJay1
Component: Setup & InstallationAssignee: Vincent PINON <vpinon>
Status: RESOLVED NOT A BUG    
Severity: normal CC: fritzibaby
Priority: NOR Flags: fritzibaby: timeline_corruption+
Version First Reported In: 19.04.2   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Wrong libc version

Description EssJay1 2019-06-13 05:10:33 UTC
Created attachment 120837 [details]
Wrong libc version

SUMMARY
Can't install because "Error: Dependency is not satisfiable: Libc (>=2.29)


SOFTWARE/OS VERSIONS
Linux Mint 19.1 Cinnamon 4.0.10
 

ADDITIONAL INFORMATION
See attachment
Comment 1 emohr 2019-06-13 16:00:54 UTC
Please try with the current Kdenlive AppImage version 19.04.2d to see if there are any packaging issues https://files.kde.org/kdenlive/release/ 


If the problem/issue doesn't occur when using the AppImage, then it's your configuration or packaging.
Comment 2 EssJay1 2019-06-18 20:29:09 UTC
Thought you'd like to know that the new "appimage" worked fine. It was the old "deb" installer that I had trouble with.

The "appimage': When I tried to import a project, it said: "The project file uses some GPU effects.  GPU acceleration is not currently enabled.  Do you want to convert the project to a non-GPU version?  This might result in data loss."  In spite of the message, rendering worked fine.  I also used processing threads of 4.  That, too, worked fine.

In the "Playback" option in "Configure Kdenlive", I couldn't click on "use GPU processing (Mount library) - restart Kdenlive to apply".  It also displayed "Use GPU processing (Movit library):GPU processing needs MLT compiled with Movit and Rtaudio modules."  I believe I have these modules as the older "deb" version must have used them or I wouldn't have the GPU message.
Comment 3 emohr 2019-06-19 16:17:09 UTC
On the AppImage, GPU acceleration is switched off due to many issues we have. Dev working on a re-integration of GPU acceleration.

We close this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number.