Program crashes at startup
@peterson
Submitted by Peterson Silva Assigned to Peterson Silva @peterson
Description
Steps to reproduce:
I just started the program and it crashed.
Stack trace:
I don't know if this is a stack trace - I followed the link but found no pitivi-dbg package - but I think this could be useful.
I tried running pitivi from a terminal and the error message was this:
peterson@marvin:~$ pitivi
The program 'pitivi' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 167 error_code 2 request_code 140 minor_code 19)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
So I did what it suggested and that's what I found:
peterson@marvin:~$ pitivi --sync
DMO dll supports VO Optimizations 0 1
DMO dll might use previous sample when requested
Total Unfree 60 bytes cnt 1 [(nil),0]
Traceback (most recent call last):
File "/usr/lib/pitivi/python/pitivi/ui/sourcefactories.py", line 362, in _fileAddedCb
self._addFactory(factory)
File "/usr/lib/pitivi/python/pitivi/ui/sourcefactories.py", line 352, in _addFactory
factory.getPrettyInfo(),
File "/usr/lib/pitivi/python/pitivi/objectfactory.py", line 171, in getPrettyInfo
stl.append(self.video_info_stream.getMarkup())
File "/usr/lib/pitivi/python/pitivi/objectfactory.py", line 564, in getMarkup
templ = templ % (self.dar * self.height , self.height, float(self.framerate))
File "/usr/lib/pitivi/python/pitivi/pitivigstutils.py", line 53, in fraction_mul
raise TypeError
TypeError
The program 'pitivi' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 2448 error_code 3 request_code 3 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Other information:
Few times I managed to open the app, but when I did I couldn't import anything, and then the program crashed again...
Imported from https://bugzilla.gnome.org/show_bug.cgi?id=533180