Bug reporting

From Pitivi wiki
Jump to: navigation, search

Welcome, testers! Bug reporting and feature requests are done using GNOME's Bugzilla interface. You will need a bugzilla account to file bugs and comment on them. See the "Example queries" section at the end of this page for some useful links for searching Pitivi's bug list.

Attention! There are some known performance problems in some of our older releases.
See also our troubleshooting page.

Remember to take a look at the existing list of bugs/feature requests to see if your problem has already been reported (hint: use the control+F functionality of your browser!).

Contents

Example queries


Special searches


Providing debugging information

Sharing sample files for testing

In some cases we might ask you to share sample media files with us to debug a particular issue. If you don't have your own hosting space, we have a FTP account with unlimited space available for this purpose, provided by idmark.ca.

Stack traces for crashes

When reporting a crash, it would be good to provide a stack trace. See GNOME's Getting Traces instructions for some comprehensive documentation and tips on the subject.

For those of you who already know how to install the relevant debug packages etc, we provide you with some simple reminders below of commands that can be particularly useful in Pitivi's context.

When you want to "attach" to an existing Python process (useful for deadlocks, where the application will be hung instead of crashed):

gdb python THE_PITIVI_PROCESS_NUMBER

or if you are running 0.94 or newer (development version as of summer 2014):

gdb python3 THE_PITIVI_PROCESS_NUMBER

In normal cases where you want to run the system-wide installed Pitivi entirely in gdb from the start:

gdb python
set pagination 0  # avoids the need to press Enter to "scroll"

run /usr/bin/pitivi

or to run a development version from inside the build tree:

gdb python3
set pagination 0  # avoids the need to press Enter to "scroll"

run bin/pitivi

And then, you can either use "bt full" or "thread apply all bt" to get the backtrace you want.

Debug logs

When you need to know what’s going on inside pitivi, you can launch it with a debug level. In loggable.py, there are five levels: ( ERROR, WARN, FIXME, INFO, DEBUG, LOG ) = range(1, 7). As such, if you want to see errors and warnings only, you launch

PITIVI_DEBUG=2 bin/pitivi

...and if you want to see everything you do

PITIVI_DEBUG=6 bin/pitivi

If that's "too much" and you want to focus on particular parts of the code, you can do so. For example, you can get output from the "Timeline" and "MediaLibraryWidget" classes only:

PITIVI_DEBUG=timeline:6,medialibrarywidget:6 bin/pitivi


Here are various examples of commands you can use to generate detailed debug logs that include not only Pitivi's debug output, but also GStreamer's:

A basic log can be obtained by running:

PITIVI_DEBUG=*:5 GST_DEBUG=2 bin/pitivi > debug.log 2>&1


To get debugging information from GNonlin, you could use:

PITIVI_DEBUG=5 GST_DEBUG=3,gnl*:5,python:5 bin/pitivi > debug.log 2>&1

The information most likely to be useful would probably be the debug info from GES in addition to Pitivi's:

PITIVI_DEBUG=5 GST_DEBUG=ges:5 bin/pitivi > debug.log 2>&1;

Some additional tips:

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox