Kdenlive/Manual/BugReporting: Difference between revisions

Revision as of 11:57, 1 July 2015

Other languages:

Bug reports

Bug reports are handled by the KDE Bugtracking System. (The old Mantis bug tracker is in archive mode.)

If you have a crash at Kdenlive startup or when trying to play a video file, please follow these 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

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 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 will 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 installation page for tips about upgrading.

Step 2: Query open issues

Query open issues on KDE 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 the Kdenlive forum.

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

To report a bug create an account on Kde bug tracker. Log in and submit an issue.

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

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: Upload some sample RAW footage

For any Mpeg2/Mpeg4 and H.264 files it is important that you upload RAW footage (coming directly from the camcorder) somewhere on Internet. This will allow users to benchmark their computer using this file and also help us understand some bugs. Five seconds of footage is enough. Do not upload files larger than 20 MB.

As regards audio synchronization, video rendering and other issues, we will not answer support requests unless a minimum amount of footage is available somewhere to reproduce bugs.

MLT bug reports

Bugs in the MLT part of the system can be reported here (Kdenlive is a front end to the Media Loving Toolkit (MLT))

@@ Line 61: / Line 61: @@
 <!--T:20-->
-To report a bug [https://bugs.kde.org/createaccount.cgi create an account] on Kde bug tracker . Log in and  [https://bugs.kde.org/enter_bug.cgi?format=guided submit]  an issue.
+To report a bug [https://bugs.kde.org/createaccount.cgi create an account] on Kde bug tracker. Log in and  [https://bugs.kde.org/enter_bug.cgi?format=guided submit]  an issue.
 <!--T:21-->
@@ Line 67: / Line 67: @@
 <!--T:22-->
-*Precise steps to reproduce the bug
+*Precise steps to reproduce the bug.
 <!--T:23-->