Public bug reported:
Binary package hint: pitivi
When adding a video clip to the timeline pitivi crashes with the error
below. The same video clip works on Lucid, I suspect this is related to
rgba in gtk.
(pitivi:7794): GStreamer-CRITICAL **: Could not convert static caps "image/png,
width = (int) [ 16, 4096 ], height = (int) [ 16, 4096 ], framerate = (fraction)
[ 0.0, MAX ]"
Traceback (most recent call last):
File "/usr/lib/pitivi/python/pitivi/discoverer.py", line 682, in
_newDecodedPadCb
self._newVideoPadCb(pad)
File "/usr/lib/pitivi/python/pitivi/discoverer.py", line 631, in
_newVideoPadCb
gst.element_link_many(pngenc, pngsink)
gst.LinkError: failed to link pngenc0 with filesink0
Traceback (most recent call last):
File "/usr/lib/pitivi/python/pitivi/timeline/track.py", line 891, in
_compositionDurationChangedCb
self.emit('duration-changed', duration)
File "/usr/lib/pitivi/python/pitivi/signalinterface.py", line 145, in emit
*args, **kwargs)
File "/usr/lib/pitivi/python/pitivi/signalinterface.py", line 119, in emit
res = cb(*ar, **kw)
File "/usr/lib/pitivi/python/pitivi/timeline/timeline.py", line 1482, in
_trackDurationChangedCb
self._updateDuration()
File "/usr/lib/pitivi/python/pitivi/timeline/timeline.py", line 1488, in
_updateDuration
self.emit('duration-changed', duration)
File "/usr/lib/pitivi/python/pitivi/signalinterface.py", line 145, in emit
*args, **kwargs)
File "/usr/lib/pitivi/python/pitivi/signalinterface.py", line 119, in emit
res = cb(*ar, **kw)
File "/usr/lib/pitivi/python/pitivi/ui/mainwindow.py", line 974, in
_timelineDurationChangedCb
self._setBestZoomRatio()
File "/usr/lib/pitivi/python/pitivi/ui/mainwindow.py", line 720, in
_setBestZoomRatio
ideal_zoom_ratio = ruler_width / float(timeline_duration / gst.SECOND)
ZeroDivisionError: float division
Gdk-ERROR **: The program 'pitivi' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 46 error_code 8 request_code 132 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.)
aborting...
Trace/breakpoint trap
** Affects: pitivi (Ubuntu)
Importance: Medium
Status: New
** Tags: gtk-csd
** Changed in: pitivi (Ubuntu)
Importance: Undecided => Medium
--
crashes when adding video clips
https://bugs.launchpad.net/bugs/586390
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
