| Summary: | kdenlive 18.12.1 quits while editing video on timeline. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Ezequiel Partida <ezequiel_partida> |
| Component: | RPM Packages | Assignee: | KDE maintainers <kde> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | fri, marja11, nikos769, ouaurelien |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kdenlive-20.12.0-1.mga8.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Ezequiel Partida
2019-02-06 20:51:14 CET
I just delted kdenliverc from ~/.config and it seems to be working just fine. Probably something wrong on the kdenliverc config file. Got the problem again. Once I deleted kdenliverc file, I ran kdenlive and I got a message about GPU acceleration and I dissable it. If I reenable it from Settings / Configure kdenlive / Playback / Use GPU processing (Movit library) - restart kdenlive to apply... it will crash again. this time I get this error while running from konsole: [ezequiel@zekelapx01 ~]$ kdenlive Loading effects from "/usr/share/kdenlive/effects" GL error 0x501 (GL_INVALID_VALUE) at filter_glsl_manager.cpp:396 Aborted (core dumped) Hello again, This is a know bug not relate with Mageia. https://bbs.archlinux.org/viewtopic.php?pid=1822263 https://forum.kde.org/viewtopic.php?f=265&t=136986 Using GPU Processing Movit Library is very unstable. I will close this threat.
Marja Van Waes
2019-02-07 08:16:42 CET
CC:
(none) =>
marja11 Or maybe this is a QT problem: https://www.dedoimedo.com/computers/kdenlive-19-08-review.html The bug is still there in kdenlive 19.04.0 Mageia 7, 64bit (and I don't have that "movit" enabled, or, maybe, not even installed) Sometimes it freezes when you click on the timeline, sometimes after you have just imported a clip (video). Meaning, the application is not usable. At some point, as you're working with it, most likely, kdenlive will freeze on you. Been using kdenlive for a few years, and it is like this: some releases are good and stable, some are full of bugs and problems. Could kdenlive packager check that, and choose not to update kdenlive to a certain version? Or does kdenlive need to follow all the other kde updates? By the way, the "Severity" of the bug needs correction. CC:
(none) =>
nikos769 I just tested the appimage... kdenlive-19.12.3-x86_64.appimage kdenlive 19.12.3 again, in Mageia 7, 64bit I managed to import all clips, but when I started working with the timeline, kdenlive, soon, froze. This are the last lines at the terminal [bash 4.4]$ ./kdenlive-19.12.3-x86_64.appimage ... ################### JOB finished 81 ################### JOB finished 88 ################### JOB finished 85 ################### JOB finished 89 ################### JOB finished 14 ################### JOB finished 10 ################### JOB finished 22 - - -Deleting effect list widget - - -Deleting transition list widget ** * DEREGISTERING TIMELINE CLIP: 9 ** * DEREGISTERING TIMELINE CLIP: 8 deleting core QMutex: destroying locked mutex QMutex: destroying locked mutex QMutex: destroying locked mutex QMutex: destroying locked mutex QMutex: destroying locked mutex QMutex: destroying locked mutex QMutex: destroying locked mutex QMutex: destroying locked mutex QMutex: destroying locked mutex QMutex: destroying locked mutex QMutex: destroying locked mutex So, an update probably won't fix the problem. I dont use Kdenlive myself. A quick couple pointers: Is there a fouron that could be consulted? Search https://kdenlive.org/en/bug-reports/ and chime in if you find similar issue, if not found please create one. If found or created please att keyword UPSTREAM here in Mageia bugs, and URL. I noticed there are elder versions of Appimages to test/use in https://files.kde.org/kdenlive/release/ CC:
(none) =>
fri fouron -> forum Since this has been reported against a past Cauldron version, and that we are at kdenlive-20.12.0-1.mga8 version, Such bug should be reported upstream at bugs.kde.org if still present. We are not involved in development of this application. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Adding current SRPM version. Closing as OLD. CC:
(none) =>
ouaurelien |