Bug 473684 - Sequence lost 4 hours of edits
Summary: Sequence lost 4 hours of edits
Status: RESOLVED WORKSFORME
Alias: None
Product: kdenlive
Classification: Applications
Component: Rendering & Export (show other bugs)
Version: 23.04.3
Platform: Flatpak Linux
: NOR critical
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-23 13:28 UTC by Hyuri
Modified: 2024-03-19 03:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:
hyuri.pimentel: timeline_corruption+


Attachments
Project File (1.56 MB, application/xml)
2023-08-23 13:28 UTC, Hyuri
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Hyuri 2023-08-23 13:28:46 UTC
Created attachment 161139 [details]
Project File

SUMMARY
I'm not sure what exactly what to report. I lost 4 hours of work. I duplicated a timeline and worked on it for 4 hours, closed the app, and when I opened it again, the sequence had been restored to the state when I first duplicated it, before I changed anything.

The sequence in question is "CUT_ROUGH". It was originally duplicated from "SELECT_3", before I spent 4 hours working on it.

I opened the project file in a text editor and noticed there are two "CUT_ROUGH" tractors. So it gives me a glimmer of hope that my edited sequence might be hidden there in the file somewhere.

If anyone who knows how to navigate the project file could take a look in the file and see if there is indeed another sequence and it can be restored, that would really save me right now.

STEPS TO REPRODUCE
1. Duplicate sequence
2. Work on duplicated sequence for 4 hours — save.
3. Close app, and re-open
4. See how the sequence is restored to a previous state and the work is lost.

OBSERVED RESULT
Sequence restored to a previous state.

EXPECTED RESULT
All the work I did in the sequence kept and save.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Pop!_OS 22.04
(available in About System)
Gnome Version: 42.9
KDE Frameworks Version: 5.109.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
Comment 1 diekuhrannte@web.de 2024-02-18 18:16:35 UTC
Hello Hyuri,
can you please report whether the problem still exists? Or can we close the bug report?
Comment 2 Bug Janitor Service 2024-03-04 03:46:58 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 3 Bug Janitor Service 2024-03-19 03:46:36 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!