Bug 426394 - The editing timeline can be ruined by dragging a video and holding the lower part of the timeline
Summary: The editing timeline can be ruined by dragging a video and holding the lower ...
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface & Miscellaneous (other bugs)
Version First Reported In: 20.08.0
Platform: Flatpak Linux
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-11 07:20 UTC by Fernando M. Muniz
Modified: 2022-06-20 09:21 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:
fritzibaby: timeline_corruption+


Attachments
The glitch being executed. (100.30 KB, image/png)
2020-09-11 07:20 UTC, Fernando M. Muniz
Details
Video of the glitch being executed. (20.08.03) (1.54 MB, video/mp4)
2020-11-06 12:03 UTC, Fernando M. Muniz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Fernando M. Muniz 2020-09-11 07:20:12 UTC
Created attachment 131554 [details]
The glitch being executed.

SUMMARY


STEPS TO REPRODUCE
1. Drag a video by holding the click on it
2. Hold it above the lower part of the editing timeline

OBSERVED RESULT
It softlocks Kdenlive because now you can't see the timeline to edit your video.

EXPECTED RESULT
I expected to only move videos sideways in the timeline.

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

ADDITIONAL INFORMATION
Comment 1 emohr 2020-09-13 14:39:29 UTC
I can't do that on Windows. Can you try with the current Kdenlive AppImage version 20.08.1 to see if there are any packaging issues https://files.kde.org/kdenlive/release/
Comment 2 Fernando M. Muniz 2020-11-06 12:03:40 UTC
Created attachment 133080 [details]
Video of the glitch being executed. (20.08.03)
Comment 3 Julius Künzel 2021-04-02 09:47:57 UTC
Thanks for your report! I can confirm this behavior with 20.12.3
Comment 4 Fernando M. Muniz 2022-06-20 09:21:18 UTC
The glitch seems to have been fixed.