Bug 415697

Summary:	UI freezes when clicking a second clip
Product:	[Applications] kdenlive	Reporter:	Rui Zhao <renyuneyun>
Component:	User Interface & Miscellaneous	Assignee:	Jean-Baptiste Mardelle <jb>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	fritzibaby
Priority:	NOR	Flags:	fritzibaby: timeline_corruption+
Version First Reported In:	19.12.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Rui Zhao 2019-12-30 00:01:27 UTC

SUMMARY

The UI freezes when clicking a second clip. It doesn't matter what the clip is.

STEPS TO REPRODUCE
1. Open kdenlive
2. Import some clips or open an existing project
3. Click a clip
4. Click another clip

OBSERVED RESULT

UI freezes

EXPECTED RESULT

Nothing strange happen, only the second clip is selected


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: N/A
(available in About System)
KDE Plasma Version: N/A
KDE Frameworks Version:  19.12
Qt Version: 5.14.0

ADDITIONAL INFORMATION

Running kdenlive from terminal, and the log seems to indicate there are race conditions:

QPoint(0,1061)
MUTEX LOCK!!!!!!!!!!!! setmodel
MUTEX UNLOCK!!!!!!!!!!!! setmodel
MUTEX LOCK!!!!!!!!!!!! loadEffects: 
/// GOT AUDIO TRACKS:  (7)
QPoint(0,789)


Every QPoint(0,xxx) appears after a click with other lines following it.

Comment 1 Rui Zhao 2019-12-30 00:04:05 UTC

For clarity: the terminal outputs provided are the final outputs. Nothing more shows up, and the kdenlive UI freezes. However, Ctrl-C on terminal works as expected (so does kill command).

Comment 2 Rui Zhao 2019-12-31 14:34:22 UTC

After being pointed out from archlinux bbs, deleting ~/.config/kdenliverc makes this problem disappear.
https://bbs.archlinux.org/viewtopic.php?id=246411

So could this be a problem of changing config format / content?

Comment 3 emohr 2020-01-05 17:47:25 UTC

Deleting kdenliverc is not a problem. Sometimes the file gets "corrupt".

It seems it works. 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.