Bug reports

Bug reports are handled by Mantis bug tracker [2].

If you have a crash at Kdenlive startup or when trying to play a video file, please follow this steps (and read the rest of the page too)

If you compiled Kdenlive / MLT yourself, make sure you followed all steps described in our instructions [3]
Check that you don't have several versions of MLT installed
Try playing your video file with FFmpeg's player. From a terminal: ffplay myvideo.mpg
Try playing your video file with MLT's player. From a terminal: melt myvideo.mpg
Download this simple project file (containing color clips): test_file.kdenlive [4] and play it with MLT's player: melt test_file.kdenlive

Include the results of the 4 above steps in your bug report, and always tell us which Kdenlive and MLT version you have!

Step 1: Upgrade to Kdenlive latest release

Please upgrade to the latest released versions of Kdenlive and MLT. We not not answer bug reports for old Kdenlive versions (unless they are still reproducible in latest version).

If your distribution does not offer packages of the latest Kdenlive and MLT versions, please check our download page for tips about upgrading [5].

Step 2: Query open issues

Query open issues [6] on Mantis bug tracker.

Reading the bug page:

New or Feedback is a reported bug, which needs more feedback.
Acknowledged means that the bug is reported by several users or by core members.
Confirmed means that the bug is reproducible.
Assigned means that a developer is handling the bug.
Fixed means that the bug was fixed in development version.

Step 3: Report a bug

Before reporting bugs, read the user manual and search the forums for answers. Do not report bugs on Kdenlive < 0.9, which are deprecated.

If you are not running the latest development release, check recently solved issues [7], as your problem might already be fixed in the development version.

To report a bug create an account [8] on Mantis bug tracker. Log in and submit an issue [9].

For the bug report to be useful, please try to provide the following informations:

Precise steps to reproduce the bug
If the bug crashes Kdenlive, provide a backtrace.

How to get useful crash information (backtrace)

Please install the following packages: gdb, kdenlive-dbg, libmlt-dbg (package names may slightly change depending on your distro).
When Kdenlive crashes, if the KDE crash handler dialog pops up, you can copy the data it provides.

Otherwise, from a terminal, type:
gdb kdenlive run
Kdenlive will start, then you can trigger the bug. When Kdenlive crashes, go to your terminal window and type:
thread apply all bt
Then press enter until you see the full data. Copy the log to a file and attach it to the bug report

Step 4: Register your camcorder

Look at our camcorder database [10]. If you camcorder is not in the database, install the latest Kdenlive / MLT to check compatibility and add your camcorder [11] in the list.

For any Mpeg2/Mpeg4 and H264 this is important that you upload RAW footage (coming directly from camcorder) somewhere on Internet. This will allow users to benchmark their computer using this file and also help us understand some bugs. A 5 seconds footage is enough. Do not upload large files of more than 20 Mb.

As regards audio synchronization, video rendering and other issues, we will not answer support request unless your camcorder is in the list and that minimum footage is available somewhere to reproduce bugs.