Bug 406102 - Can't open or save projects
Summary: Can't open or save projects
Status: RESOLVED WORKSFORME
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface (show other bugs)
Version: unspecified
Platform: Flatpak Linux
: NOR major
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-01 05:38 UTC by hardcoreburnz
Modified: 2021-04-22 04:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
fritzibaby: timeline_corruption+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hardcoreburnz 2019-04-01 05:38:25 UTC
SUMMARY
The Open and Save dialogs do nothing in the Flatpak version of Kdenlive on Ubuntu 18.04.  (Import and other dialogs work fine).  So there is no way to save projects, and the only way to open projects may be to drag into the Kdenlive window.  Also, if I close the window, Kdenlive asks if I'd like to save the project.  If I hit yes, nothing also happens.

The Appimage version does not have this issue (though it has other issues I'll file separate bugs for).

STEPS TO REPRODUCE
1. Goto File > Open, or File > Save, or File > Save As.

OBSERVED RESULT
Nothing happens.

EXPECTED RESULT
An Open or Save As (file browser) dialog pops up and allows a user to open or save project files.

SOFTWARE/OS VERSIONS
Ubuntu version:  18.04
Flatpak version: 1.0.7
Kdenlive version: 18.12.2

ADDITIONAL INFORMATION
Comment 1 emohr 2019-04-01 16:41:13 UTC
I’m not sure if the Flatpak is complete. I see many issues have happened due to bad packaging... .  

Try the Flatpak from here: https://flathub.org/apps/details/org.kde.kdenlive. 

If this Flatpak has the same issue, try with the AppImage 18.12.1b from the Kdenlive download page.
Comment 2 hardcoreburnz 2019-04-02 04:31:46 UTC
Unfortunately, that latest Flatpack version you linked is the version with the issue.

I've also used the AppImage version.  This AppImage version does not have the missing dialog box issues; however, it is packaged with a 2-year old version of ffmpeg (version 3.3.4).  This means I cannot use hardware acceleration to render proxy files or final files.  And attempting to override this old ffmpeg with my local version of ffmpeg 4.x results in an error.

I am doing 4K edits.  Even using proxies and preview rendering with my 8-core 4000mhz machine with 32GB of ram and an AMD Vega 64 video card, Kdenlive is probitively slow.

So my current options are either to use an unusably slow Kdenlive that's 100% CPU driven (AppImage), or to use a much more performant (and usable) version, but without the ability to save or open projects (Flatpak) until either of these is resolved.

I hope this feedback helps drive things in the right direction.  Let me know what additional feedback, tests, or information I can provide.
Comment 3 emohr 2019-04-02 18:13:00 UTC
I assume you enabled MOVIT. MOVIT is not really working (lot of bugs). The not working open/save dialog could be coming from that. 

You can try with the refactoring version because some “MOVIT” bugs are solved there. But you have to compile by yourselves at the moment as there is a Nightly-Build AppImage only. https://community.kde.org/Kdenlive/Development. 

One person is working on the openGL implementation at the moment.
Comment 4 hardcoreburnz 2019-04-03 04:24:45 UTC
Sorry, but your assumption is not correct.  I did NOT enable MOVIT, and I don't think this has anything at all to do with OpenGL.

When referring to hardware acceleration, I am referring explicitly to the encoding part only (for proxy files and/or the final output).  Not to effects, transitions, etc. (which I recognize are CPU driven, unfortunately).

Custom encoding profiles pass flags to ffmpeg.  With the right flags, ffmpeg will use hardware acceleration to create proxy video files & exported video files.  And I have verified this works properly when ffmpeg 4.x is used in Kdenlive.  But (again, to clarify), using ffmpeg 4.x does not work in the current AppImage version, which is packaged with ffmpeg 3.3.4--and manually specifying an ffmpeg path results in an error.

But even without custom encoding profiles, the Open / Save dialogs (for the overall project) do not pop up in the FlatPak version.  This means that I cannot open or save any projects in FlatPak Kdenlive.  And I cannot use hardware acceleration for proxy file & export file rendering in AppImage Kdenlive.
Comment 5 Corey O'Connor 2019-04-03 21:03:54 UTC
Hi hardcoreburnz,

Thanks for the report!

There appears to be two issues here:

1. The open and save dialogs do not open when using the flatpack version.
2. The ffmpeg hardware acceleration decoding is not working with the AppImage version. Presumably due to an old version of FFMPEG.

Is that correct?

We'll keep this ticket for issue 1. A second ticket for issue 2. If you have not already created a ticket then feel free to reply here and I'll split the tickets.
Comment 6 hardcoreburnz 2019-04-07 20:46:41 UTC
This is correct.  I hope these are relatively simple to update, but please let me know if I can help with any more system information or tests.

Thank you!
Comment 7 hardcoreburnz 2019-04-08 05:37:44 UTC
BTW, I have not opened a second ticket; but in case it helps for issue #2 (old version of FFMPEG), when I do try to point to a newer ffmpeg installed on my machine, the error I get is:


/usr/bin/ffmpeg: relocation error: /usr/lib/x86_64-linux-gnu/libgnutls.so.30: symbol asn1_der_decoding2 version LIBTASN1_0_3 not defined in file libtasn1.so.6 with link time reference
Comment 8 emohr 2021-03-05 18:25:46 UTC
As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

Please try with the current Kdenlive AppImage version 20.12.2  https://download.kde.org/stable/kdenlive/20.12/linux/
Comment 9 Bug Janitor Service 2021-03-20 04:33:41 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 10 hardcoreburnz 2021-03-23 03:11:39 UTC
I have just tried again, and the issue still appears to be there.  The latest version I tried with is 20.12.3, on Ubuntu 18.04.


If I go to File >> Open, or File >> Save As, nothing happens.  No dialog box pops  up.
Comment 11 emohr 2021-03-23 17:03:19 UTC
Please update Ubuntu to 20.04 it could be some inconstancy with QT.
Comment 12 hardcoreburnz 2021-03-23 22:24:26 UTC
Upgrade my entire operating system just to accommodate a several-years-old bug in one application?  No thank you.
Comment 13 Bug Janitor Service 2021-04-07 04:33:23 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 14 Bug Janitor Service 2021-04-22 04:33:24 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!