Bug 422430

Summary: Kdenlive hangs after changing title clips that exist in the timeline
Product: [Applications] kdenlive Reporter: Riskable <riskable>
Component: User Interface & MiscellaneousAssignee: Jean-Baptiste Mardelle <jb>
Status: RESOLVED WORKSFORME    
Severity: crash CC: fritzibaby
Priority: NOR Flags: fritzibaby: timeline_corruption+
Version First Reported In: 20.04.1   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: output from 'gdb kdenlive run'

Description Riskable 2020-06-03 18:51:36 UTC
Created attachment 129031 [details]
output from 'gdb kdenlive run'

SUMMARY
If I try to edit a title clip that's already been placed in the timeline kdenlive hangs.  This happens regardless of threading/GPU rendering settings.  Doesn't matter what I configure in kdenlive, actually (I tried changing all sorts of settings to see if I could isolate the problem).

STEPS TO REPRODUCE
1. Add a video and some title clips to the timeline.
2. Edit one of those title clips.


OBSERVED RESULT
It hangs forever until I kill it.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux 5.4.0 (Kubuntu 20.04)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
Installed kdenlive from ppa:kdenlive/kdenlive-stable.

Here's the text on the console right before it happened (the gdb output is attached):

[New Thread 0x7fff037fe700 (LWP 510654)]
[Thread 0x7fff03fff700 (LWP 510653) exited]
[Thread 0x7fff56e69700 (LWP 510605) exited]
[Thread 0x7ffefffff700 (LWP 510652) exited]
[Thread 0x7fff3cff1700 (LWP 510651) exited]
[New Thread 0x7fff3cff1700 (LWP 510657)]
MUTEX LOCK!!!!!!!!!!!! setmodel
MUTEX UNLOCK!!!!!!!!!!!! setmodel
MUTEX LOCK!!!!!!!!!!!! loadEffects COUNT:  0
QFSFileEngine::open: No file name specified
[Thread 0x7fff56668700 (LWP 510606) exited]
// SETTING CLIP PROPERTIES:  QMap(("force_reload", "2")("xmldata", "<kdenlivetitle duration=\"300\" LC_NUMERIC=\"en_US.UTF-8\" width=\"1920\" height=\"1080\" out=\"299\">\n <item type=\"QGraphicsTextItem\" z-index=\"0\">\n  <position x=\"34\" y=\"586\">\n   <transform>1,0,0,0,1,0,0,0,1</transform>\n  </position>\n  <content line-spacing=\"0\" shadow=\"1;#64000000;3;10;10\" font-underline=\"0\" box-height=\"360\" font-outline-color=\"0,0,0,255\" font=\"MineCrafter 3\" letter-spacing=\"0\" font-pixel-size=\"74\" font-italic=\"0\" alignment=\"1\" font-weight=\"50\" font-outline=\"3\" box-width=\"1195.56\" font-color=\"0,143,209,255\">Reading back\nLast Statement\nfrom memory buffer...</content>\n </item>\n <startviewport rect=\"0,0,1920,1080\"/>\n <endviewport rect=\"0,0,1920,1080\"/>\n <background color=\"0,0,0,0\"/>\n</kdenlivetitle>\n"))
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3939, resource id: 36466677, major code: 40 (TranslateCoords), minor code: 0
################### JOB finished:  56
Comment 1 Riskable 2020-06-03 18:53:08 UTC
I uploaded a video demonstrating the problem here:

https://gfycat.com/wigglyhandycaracal

(make sure you enable audio so you can hear my commentary)
Comment 2 emohr 2020-09-08 16:41:48 UTC
Please try with the current Kdenlive AppImage version 20.08.0 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.

WARNING: Version 20.08.0 has a new project type that is not backwards compatible... so you won't be able to use older versions to open new files.
Comment 3 Bug Janitor Service 2020-09-23 04:33:13 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 4 Bug Janitor Service 2020-10-08 04:33:17 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!