| Summary: | Rendering crashes | ||
|---|---|---|---|
| Product: | [Applications] kdenlive | Reporter: | Herrmanius <flowrist> |
| Component: | Rendering & Export | Assignee: | Jean-Baptiste Mardelle <jb> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | dan_j_thompson, flowrist, fritzibaby |
| Priority: | NOR | Flags: | fritzibaby:
timeline_corruption+
|
| Version First Reported In: | 19.04.2 | ||
| Target Milestone: | --- | ||
| Platform: | Appimage | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 19.04.2.e | |
| Sentry Crash Report: | |||
|
Description
Herrmanius
2019-06-23 13:23:11 UTC
Export works fine in Appimage 19.04.2.e Delete Kdenliverc and/or kdenlive-appimagerc and try again. See here: https://community.kde.org/Kdenlive/Configuration I ran into a similar problem on Windows. I had previously used 20.04.1_standalone on this machine, and was trying to use 20.08.2_standalone. Deleting all the configuration files resolved the problem for me. Although there is a workaround, I think this is a pretty bad problem--it would completely discourage a newcomer, or really anybody who is not comfortable with digging through a bug tracker for clues. Thank you for the feedback. Which error message pops up? There are probably 2 ways to solve it: deleting all configuration files (as you did) or go to help -> click on "reset configuration*. Depends which error pops up Kdenlive could catch it and run the reset configuration by themselves, maybe with a question like "to solve the issue configuration will be reset" -> OK/Cancel. What are your thoughts? Problem doesn't occur anymore in 20.08.2 64bit appimage on Linux. (Seems dubious to resolve as "fixed", since I repro'ed the problem.) emohr: Sorry; I don't have the exact text of the error available any longer--after I deleted all the config, the error went away. Intercepting the error and offering to reset config for you would be a good step... it would prevent people from getting completely blocked. But of course the ideal solution would be to properly upgrade config so that you don't end up with the situation in the first place. But even if we implemented the ideal solution... there is always a possibility of a mistake there (a mistake during config upgrade). So it may still be good to have the "do you want to try resetting configuration to see if it helps?" safety net as well. |