Bug 435306

Thanks for your report! Are you sure your work is completely lost? First of all you should save your work from time to time (or has kdenlive saved the file after the freeze?). But even if you have forgotten to save, kdenlive creates automated backups if you open your last saved version you should be asked on reopen if you want to recover from the backup. If not you can try to go to menu Project > Open Back File and see if there are other backups.

Unfortunately we can't do anything to solve the crash because your report is not very specific. It would be helpful to know what your last action before the freeze was. A crash log would be even better (e.g. by running kdenlive from the command line). If you use GPU mode (movit) please disable it.

Please check if my tips help you and if you can provide more information.

Yeah I didn't know you can just run kdenlive on the terminal to track things, the docs are a little confusing cause I only found gdb no kdenlive-dbg and limit-dbg will probably report next time, are you guys planning a feature like in the kde settings where you can allow kde to send detailed system info and usage statistics

And what about the Backup Files. Could you recover your work?

(In reply to Julius Künzel from comment #3)
> And what about the Backup Files. Could you recover your work?

it's okay doing it from the start allowed me to refine some stuff

(In reply to Julius Künzel from comment #1)
> Thanks for your report! Are you sure your work is completely lost? First of
> all you should save your work from time to time (or has kdenlive saved the
> file after the freeze?). But even if you have forgotten to save, kdenlive
> creates automated backups if you open your last saved version you should be
> asked on reopen if you want to recover from the backup. If not you can try
> to go to menu Project > Open Back File and see if there are other backups.
> 
> Unfortunately we can't do anything to solve the crash because your report is
> not very specific. It would be helpful to know what your last action before
> the freeze was. A crash log would be even better (e.g. by running kdenlive
> from the command line). If you use GPU mode (movit) please disable it.
> 
> Please check if my tips help you and if you can provide more information.

How Do You Even Debug Kdenlive, i Tried gdb but it says "no debug symbols found in kdenlive"

no debug symbols found in kdenlive is not necessarily a problem. You need to run

$ gdb kdenlive

then if you see something like

(gdb)

you need to type "r" and hit enter. Now you can reproduce a crash if you see "(gdb)" again type "bt full" ENTER to get the backtrace.

Please update to the latest version of Kdenlive available on https://kdenlive.org/download and check if this report is still relevant. 

We have detailed (updated) instructions on how to debug Kdenlive here now: https://kdenlive.org/en/bug-reports/

(In reply to Julius Künzel from comment #7)
> Please update to the latest version of Kdenlive available on
> https://kdenlive.org/download and check if this report is still relevant. 
> 
> We have detailed (updated) instructions on how to debug Kdenlive here now:
> https://kdenlive.org/en/bug-reports/

It was just really an error with packaging in the distro i used when this occurred, Thanks for all the work y'all have done to make Kdenlive better!

(In reply to Julius Künzel from comment #7)
> Please update to the latest version of Kdenlive available on
> https://kdenlive.org/download and check if this report is still relevant. 
> 
> We have detailed (updated) instructions on how to debug Kdenlive here now:
> https://kdenlive.org/en/bug-reports/

This isn't relevant anymore cause i tried the Manjaro and this never happened again.

Thanks for letting us know!