https://bugs.kde.org/show_bug.cgi?id=386292
--- Comment #2 from Christoph Feck <cf...@kde.org> --- It crashes in libvidstab.so when parsing motions file, not sure if that is created by MLT. I suggest to report this issue to MLT developers via https://github.com/mltframework/mlt/issues Relevant part of the backtrace: #0 0x00007ffff03c6cdf in __GI__IO_vfscanf () at /usr/lib/libc.so.6 #1 0x00007ffff03d60c6 in __isoc99_fscanf () at /usr/lib/libc.so.6 #2 0x00007fffc40babbd in restoreLocalmotion () at /usr/lib/libvidstab.so.1.1 #3 0x00007fffc40bad96 in vsRestoreLocalmotions () at /usr/lib/libvidstab.so.1.1 #4 0x00007fffc40bb128 in vsReadFromFile () at /usr/lib/libvidstab.so.1.1 #5 0x00007fffc40bb1cb in vsReadLocalMotionsFile () at /usr/lib/libvidstab.so.1.1 #6 0x00007fffbed9e7d7 in () at /usr/lib/mlt/libmltvidstab.so #7 0x00007ffff71d5b52 in mlt_frame_get_image () at /usr/lib/libmlt.so.6 #8 0x00007ffff71ec70b in () at /usr/lib/libmlt.so.6 #9 0x00007ffff71d5b52 in mlt_frame_get_image () at /usr/lib/libmlt.so.6 #10 0x00007ffff6fbb27e in Mlt::Frame::get_image(mlt_image_format&, int&, int&, int) () at /usr/lib/libmlt++.so.3 -- You are receiving this mail because: You are watching all bug changes.