subsequent crashes directly after start. worked first

Bug #517191 reported by Timo Goetze
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OpenShot Video Editor
Invalid
Undecided
Unassigned

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

Tags: segfault
Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

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.

Revision history for this message
Olivier Girard (eolinwen) wrote :

Just a question. What are your actual version of Openshot ?
Thanks

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

I installed from the ppa repository, current one:

(0)pern:~% wajig versions openshot
openshot/karmic uptodate 1.0.0-1

I have tried to start it with a remote X sessions and it seems to work. So maybe it left something wrong in the X Server state that make it crash when restarted. In that PC I have an ATI card (fglrx driver).

Tomorrow (I have it installed on the PC at work) I will try to kill/restart X to see if it starts working again.

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

Ok, no need to restart X. After starting openshot via remote, I was back to the office and it started again without problem. So I suppose is some piece of status that stays in the Xserver and make it crash only in certain condition.

Any hint on how to debug it if it happens again?

Revision history for this message
Olivier Girard (eolinwen) wrote :

Two questions :
Have you compiz running ?
Have you a graphic card AMD ? i have had some strange results with on Jaunty then on Karmic it's perfect.

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

Yes, AMD card with "normal" effect, so compiz is running, and ubuntu Karmic.

Andy Finch (fincha)
Changed in openshot:
status: New → Incomplete
tags: added: segfault
moimael (moimael)
Changed in openshot:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.