Bug 409096 - kdenlive crashes when putting new clips into project
Summary: kdenlive crashes when putting new clips into project
Status: RESOLVED NOT A BUG
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface & Miscellaneous (other bugs)
Version First Reported In: 19.04.2
Platform: Other Linux
: NOR critical
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-23 22:33 UTC by Christoph
Modified: 2019-06-26 17:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:
fritzibaby: timeline_corruption+


Attachments
attachment-20922-0.sig (228 bytes, application/pgp-signature)
2019-06-24 23:03 UTC, Christoph
Details
attachment-15192-0.sig (228 bytes, application/pgp-signature)
2019-06-25 22:49 UTC, Christoph
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph 2019-06-23 22:33:10 UTC
SUMMARY
Every time, when I try to open new clips and put it to a project, kdenlive crashes.

STEPS TO REPRODUCE
1. Start kdenlive
2. Put new clips to it
3. Kdenlive ends and closes its window

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Voidlinux, Kernel 4.18.7_1 x86_64
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: KDE Frameworks 5.59.0
Qt Version: Qt 5.11.3 (kompiliert gegen 5.11.3)

ADDITIONAL INFORMATION

Language set to german.

When I reduce the size (height) of the main window to max. 935 pixel, the program does not crash, but when the window size is above 935 pixel, the program crashes everytime, when I try to add new clips. Instead of opening the file selector, the program ends.

Here are the last status lines from the bash:

-----------snip--------------

QWidget::setMinimumSize: (effect_list/QDockWidget) Negative sizes (0,-1) are not possible
QWidget::setMinimumSize: (transition_list/QDockWidget) Negative sizes (0,-1) are not possible
Loading bin playlist...
//////////////////////
Trying to construct 5 tracks.
////////////////////////////////
SUSPICIOUS: we weren't expecting a producer when parsing the timeline
qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 746, resource id: 39845946, major code: 153 (Unknown), minor code: 11
/////////// starting to add bin clips
kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator" not found
kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator" not found
kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator" not found
kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator" not found
/////////// found list ()
/////////// creatclipsfromlist () true "-1"
/////////// creatclipsfromlist return false
/////////// starting to add bin clips
kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator" not found
kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator" not found
Bus-Zugriffsfehler
Comment 1 emohr 2019-06-24 15:53:34 UTC
Please try with the current Kdenlive AppImage version 19.04.2f to see if there are any packaging issues https://files.kde.org/kdenlive/release/ 

If the problem/issue doesn't occur when using the AppImage, then it's your configuration or packaging.
Comment 2 Christoph 2019-06-24 23:03:37 UTC
Created attachment 121120 [details]
attachment-20922-0.sig

Hello emohr,

thank you for your quick answer. This version works, but it seems to be
a completely different version, because I am not able to change it to
my personal layout.

I have deleted now the following files resp. directories in my home
directory:

~/.local/share/kdenlive
~/.cache/kdenlive
and
~/.config/kdenliverc

Kdenlive (the "original" one) still crashes, when trying to open the
fileselector-box for adding clips. It also crashes when trying to set
to full screen.

I know one of the maintainers of Void-Linux, and he told me some time
ago, that they always compile the programs with the standard options,
which the developers recommend. And they never put any modifications to
the programs …

Greetings from
Christoph


emohr <bugzilla_noreply@kde.org> schrieb:

> https://bugs.kde.org/show_bug.cgi?id=409096
> 
> emohr <fritzibaby@gmx.net> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Flags|                            |timeline_corruption+
>                  CC|                            |fritzibaby@gmx.net
> 
> --- Comment #1 from emohr <fritzibaby@gmx.net> ---
> Please try with the current Kdenlive AppImage version 19.04.2f to see
> if there are any packaging issues
> https://files.kde.org/kdenlive/release/ 
> 
> If the problem/issue doesn't occur when using the AppImage, then it's
> your configuration or packaging.
>
Comment 3 emohr 2019-06-25 18:26:28 UTC
This seems a packaging issue (packaging Kdenlive is very tricky). 

I suggest you work with the AppImage or with the PPA. 

- What is the problem you have reconfigure your desired layout?
- Could you post here a screenshot of your desired layout?
Comment 4 Christoph 2019-06-25 22:49:06 UTC
Created attachment 121146 [details]
attachment-15192-0.sig

emohr <bugzilla_noreply@kde.org> schrieb:

> https://bugs.kde.org/show_bug.cgi?id=409096
> 
> --- Comment #3 from emohr <fritzibaby@gmx.net> ---
> This seems a packaging issue (packaging Kdenlive is very tricky). 
> 
> I suggest you work with the AppImage or with the PPA. 
> 
> - What is the problem you have reconfigure your desired layout?
> - Could you post here a screenshot of your desired layout?

Dear Emohr,

it seems to work now! I wanted to send you an image of my desired
layout, when I had to realize, that I obviously had deleted it
accidentally yesterday by trying to change different parts of my
configuration. After that, I deleted all of kdenlive’s actual temporary
and config-files again, made a new system-update (where some bibs have
been renewed – unfortunately, I haven’t noticed, which ones) and
restarted the computer. After that, kdenlive works without a crash
yet. :-)

Thank you for your commitment! It looks, that you where right, and
there was indeed a fault in my configuration.

Sincerely yours,
Christoph
Comment 5 emohr 2019-06-26 17:42:45 UTC
Glad to hear it works. Yes, on Linux I see a lot of configuration or packaging issues.

If you don't mind I close this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number.