openshot.developers team mailing list archive

[Romano Giannetti <romano.giannetti@xxxxxxxxx>]

It happens to me too. Just installed openshot after removing kdenlive to
give it a try. The first time it happened, it started again after I
removed the ~/.openshot directory. Now it happened again, and removing
the .openshot directory does not help. At the start I have the esame
error but with different codes:

The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 28 error_code 2 request_code 132 minor_code 19)

The first time it happened while clicking on a track thumbnail to
disable audio which the resize tool selected. I clicked various times
before understanding the problem, and then it crashed.

-- 
subsequent crashes directly after start. worked first
https://bugs.launchpad.net/bugs/517191
You received this bug notification because you are a member of OpenShot
Developers, which is subscribed to OpenShot Video Editor.

Status in OpenShot Video Editor: New

Bug description:
Version 1.0.0 on ubuntu 9.10 german

After following the hints to solve the mlt.py problem, i got it to work from new ppa. When I cut my first video and imported H264 and AVCH in 720p and fullhd, it crashed when trimming the AVCH fullhd 1080i on the timeline. 

after this crash I get following error at every start. Also reinstalled (apt-get autoremove and install).

openshot
Added /usr/share/openshot to system path
--------------------------------
   OpenShot (version 1.0.0)
--------------------------------
/usr/share/openshot/windows/SimpleGladeApp.py:340: GtkWarning: gtk_toolbar_set_icon_size: assertion `icon_size != GTK_ICON_SIZE_INVALID' failed
  return gtk.glade.XML(self.glade_path, root, domain)
A new frmMain has been created
The program 'openshot' 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 47 error_code 2 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.)
Segmentation fault


Many thanks for your great work - it looks pretty impressive!

Timo