https://bugs.kde.org/show_bug.cgi?id=426048
h.k.gh...@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #29 from h.k.gh...@gmail.com --- (In reply to farid from comment #28) > (In reply to h.k.ghost from comment #27) > > (In reply to farid from comment #26) > > > (In reply to h.k.ghost from comment #25) > > > > (In reply to farid from comment #24) > > > > > Created attachment 136391 [details] > > > > > No profile > > > > > > > > > > I downloaded the attached video and upon importing it I got the > > > > > following > > > > > prompt. Wether I continue or cancel I am unable to reproduce the > > > > > crash. > > > > > > > > > > Could you please test with the latest daily builds and see if you can > > > > > reproduce? > > > > > > > > Since I'm not sure where, exactly, to find the daily builds (see my > > > > prior > > > > responses asking for proper locations), I went ahead and tried this > > > > version: > > > > https://files.kde.org/kdenlive/release/kdenlive-20.12.1c-x86_64.appimage > > > > > > Great so the issue is not in the latest stable nor in the daily builds: > > > https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/ > > > lastSuccessfulBuild/artifact/ > > > > > > > > I made a few attempts, but did not observe the problem this time. Note > > > > that > > > > the reproducibility of this issue has not always been consistent... > > > > > > I would suggest to close the issue then if you don't mind and reopen it if > > > you ever encounter the crash again. Cheers. > > > > I'd like to wait until I do some actual work with this or newer versions > > before I go ahead and close it. When issues get fixed "magically" without no > > one showing up and saying "I found the root cause of the problem, it was X, > > the fix was Y, and it's in commit Z", I tend to be a bit more cautious. > > > > Cheers. > > Ok, fair enough. Next big release is 21.04 due next month hope you can try > it till then. Will mark this as needs info so we can come back to it after a > while. We are undergoing an initiative to clean out tracker as it is > saturated with old bugs. I worked yesterday on a small project that included changes in clip speeds and did not observe the issue, either. It seems like it can be closed as resolved/fixed. If I encounter it again, I'll reopen. -- You are receiving this mail because: You are watching all bug changes.