Bug 400013

Summary:	kdenlive freezes on Wayland when its window is resized and dragged
Product:	[Applications] kdenlive	Reporter:	Patrick Silva <bugseforuns>
Component:	User Interface & Miscellaneous	Assignee:	Jean-Baptiste Mardelle <jb>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	fritzibaby, notuxius
Priority:	NOR	Flags:	fritzibaby: Brainstorm+
Version First Reported In:	18.12.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Patrick Silva 2018-10-19 00:11:07 UTC

STEPS TO REPRODUCE
1. open kdenlive under Plasma Wayland session
2. resize kdenlive window by dragging some border
3. drag kdenlive window

OBSERVED RESULT
kdenlive freezes

EXPECTED RESULT
kdenlive does not freeze

SOFTWARE VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.14.1
Qt Version: 5.12.0 beta2
KDE Frameworks Version: 5.51.0

Comment 1 Alexander Mentyu 2018-10-22 16:18:46 UTC

Reproducible sometimes, Kdenlive hangs after double click on it's titlebar for maximization, or after changing it's window size
 
Operating System: KDE neon Developer Edition
KDE Plasma Version: 5.14.80
Qt Version: 5.11.1
KDE Frameworks Version: 5.52.0

Comment 2 emohr 2018-12-24 10:41:26 UTC

Just a guess: Try with the AppImage 18.12.0c. Make sure you delete Kdenliverc files as described here: https://community.kde.org/Kdenlive/Configuration . Maybe you have a Version conflict.

Comment 3 Patrick Silva 2018-12-25 17:54:03 UTC

I can't reproduce with AppImage 18.12.0c.
However the problem persists with 18.12 installed from Arch repositories even after I delete files indicated in your link.

Comment 4 emohr 2019-01-08 19:01:56 UTC

Try with deleting .config/kdenlive-appimagerc and .config/kdenlive-appimage folder contents.

Comment 5 Patrick Silva 2019-01-10 11:57:26 UTC

(In reply to emohr from comment #4)
> Try with deleting .config/kdenlive-appimagerc and .config/kdenlive-appimage
> folder contents.

I can't reproduce with AppImage 18.12.0c anymore.

Comment 6 emohr 2019-01-20 14:33:50 UTC

It seems the problem is solved. We closed this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number.