Revision as of 10:14, 20 July 2019 by Claus chr (talk | contribs)(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff) Other languages:English • dansk • français • português do Brasil • русский • українська Contents 1 Bug reporting 1.1 Step 1: Upgrade to Kdenlive latest release 1.2 Step 2: Query open issues 1.3 Step 3: Report a bug 1.3.1 How to get useful crash information (backtrace) 1.4 Step 4: Upload some sample RAW footage 1.5 MLT bug reports Bug reporting 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 instructions below 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 indicate 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. Developers 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 installation page for tips about upgrading. Step 2: Query open issues Query open issues on the KDE bug tracker. Reading the bug page: Bug report can have the following statuses: UNCONFIRMED CONFIRMED ASSIGNED REOPENED RESOLVED NEEDSINFO VERIFIED CLOSED Bug report can have the following resolutions: FIXED INVALID WONTFIX LATER REMIND DUPLICATE WORKSFORME MOVED UPSTREAM DOWNSTREAM WAITINGFORINFO BACKTRACE UNMAINTAINED 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 the 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, developers 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)). ← Useful Resources ↑ Back to menu ↑ Credits and License → Retrieved from "https://userbase.kde.org/index.php?title=Kdenlive/Manual/BugReporting&oldid=436008" Categories: KdenliveMultimedia This page was last edited on 20 July 2019, at 10:14. Content is available under Creative Commons License SA 4.0 unless otherwise noted.