Bug 409075

Summary: Rendering crashes
Product: [Applications] kdenlive Reporter: Herrmanius <flowrist>
Component: Rendering & ExportAssignee: 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
SUMMARY
Rendering not working at all. 

STEPS TO REPRODUCE
1. Add clip to timeline
2. try to export in any way

OBSERVED RESULT

Rendering crashed: 

Rendering of /home/user/projects/kdenlive/untitled.webm crashed

qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.


OS VERSION
Ubuntu 18.04.2
Kdenlive 19.04.2.f
Comment 1 Herrmanius 2019-06-23 13:31:17 UTC
Export works fine in Appimage 19.04.2.e
Comment 2 emohr 2019-06-24 16:08:35 UTC
Delete Kdenliverc and/or kdenlive-appimagerc and try again. See here: https://community.kde.org/Kdenlive/Configuration
Comment 3 Dan Thompson 2020-11-02 04:34:16 UTC
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.
Comment 4 emohr 2020-11-02 16:06:31 UTC
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?
Comment 5 Herrmanius 2020-11-04 18:24:28 UTC
Problem doesn't occur anymore in 20.08.2 64bit appimage on Linux.
Comment 6 Dan Thompson 2020-11-04 19:42:22 UTC
(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.