OpenShot shuts down when pressing Cancel button on Length tab (properties dialogue box)

[JR]

I've just installed OpenShot from the new experimental PPA (0.9.53) onto Karmic 32-bit. If I right-click a clip in the timeline, go to properties and then the Length tab, pressing Cancel to navigate away from the dialogue box just shuts OpenShot straight down. It was fine if I clicked cancel on the first tab in that popup box. Just let me know how I can send you some more useful information.

Thanks. Great project - my wife will be very pleased when we get the wedding video edited down!!

[Jonathan Thomas (jonoomph)]

Try running OpenShot from the terminal:
$ openshot

When it crashes, see if any error messages are in the terminal. Also, check
the "System Log" and see if any strange errors are logged.

Thanks,
-Jonathan

On Mon, Nov 9, 2009 at 3:50 PM, JR <email address hidden> wrote:

> Public bug reported:
>
> I've just installed OpenShot from the new experimental PPA (0.9.53) onto
> Karmic 32-bit. If I right-click a clip in the timeline, go to properties
> and then the Length tab, pressing Cancel to navigate away from the
> dialogue box just shuts OpenShot straight down. It was fine if I clicked
> cancel on the first tab in that popup box. Just let me know how I can
> send you some more useful information.
>
> Thanks. Great project - my wife will be very pleased when we get the
> wedding video edited down!!
>
> ** Affects: openshot
> Importance: Undecided
> Status: New
>
> --
> OpenShot shuts down when pressing Cancel button on Length tab (properties
> dialogue box)
> https://bugs.launchpad.net/bugs/479564
> 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:
> I've just installed OpenShot from the new experimental PPA (0.9.53) onto
> Karmic 32-bit. If I right-click a clip in the timeline, go to properties and
> then the Length tab, pressing Cancel to navigate away from the dialogue box
> just shuts OpenShot straight down. It was fine if I clicked cancel on the
> first tab in that popup box. Just let me know how I can send you some more
> useful information.
>
> Thanks. Great project - my wife will be very pleased when we get the
> wedding video edited down!!
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openshot.developers<https://launchpad.net/%7Eopenshot.developers>
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~openshot.developers<https://launchpad.net/%7Eopenshot.developers>
> More help : https://help.launchpad.net/ListHelp
>

[JR (jonathanrodgers-hotmail)]

Below is what was in the terminal window. If I started OpenShot and tried the behaviour, it was fine - I needed to change a value in Length, Apply this change, then go back into it and cancel. The only thing in the log files around the same time (could be completely unrelated) was: Nov 10 06:02:54 desktop pulseaudio[1563]: ratelimit.c: 2 events suppressed.

GenerateXML for an Effect
on_txtOut_value_changed
on_btnClose_clicked
on_frmClipProperties_destroy
on_mnuClipProperties_activate
on_txtIn_value_changed
on_txtOut_value_changed
on_cboKeyFrame_changed
on_cboSimpleSpeed_changed
GenerateXML for an Effect
on_btnCancel_clicked
The program 'openshot' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 177 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.)

Thanks

[Jonathan Thomas (jonoomph)]

You have found a bug, but I'm finding it difficult to reproduce. Can you
come up with detailed step by step instructions to reproduce the problem.
Don't leave any action out.

For example,
1) add clip to timeline
2) open properties
3) change Length / IN from 10 to 8
4) click cancel

etc...

Thanks for your help.
-Jonathan

On Tue, Nov 10, 2009 at 12:10 AM, JR <email address hidden> wrote:

> Below is what was in the terminal window. If I started OpenShot and
> tried the behaviour, it was fine - I needed to change a value in Length,
> Apply this change, then go back into it and cancel. The only thing in
> the log files around the same time (could be completely unrelated) was:
> Nov 10 06:02:54 desktop pulseaudio[1563]: ratelimit.c: 2 events
> suppressed.
>
> GenerateXML for an Effect
> on_txtOut_value_changed
> on_btnClose_clicked
> on_frmClipProperties_destroy
> on_mnuClipProperties_activate
> on_txtIn_value_changed
> on_txtOut_value_changed
> on_cboKeyFrame_changed
> on_cboSimpleSpeed_changed
> GenerateXML for an Effect
> on_btnCancel_clicked
> The program 'openshot' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadWindow (invalid Window parameter)'.
> (Details: serial 177 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.)
>
> Thanks
>
> --
> OpenShot shuts down when pressing Cancel button on Length tab (properties
> dialogue box)
> https://bugs.launchpad.net/bugs/479564
> 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:
> I've just installed OpenShot from the new experimental PPA (0.9.53) onto
> Karmic 32-bit. If I right-click a clip in the timeline, go to properties and
> then the Length tab, pressing Cancel to navigate away from the dialogue box
> just shuts OpenShot straight down. It was fine if I clicked cancel on the
> first tab in that popup box. Just let me know how I can send you some more
> useful information.
>
> Thanks. Great project - my wife will be very pleased when we get the
> wedding video edited down!!
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openshot.developers<https://launchpad.net/%7Eopenshot.developers>
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~openshot.developers<https://launchpad.net/%7Eopenshot.developers>
> More help : https://help.launchpad.net/ListHelp
>

[JR (jonathanrodgers-hotmail)]

I couldn't always reproduce it consistently even by following the same steps. But one way was:
1. Open project
2. Open properties
3. Change speed to 2x
4. Click apply
5. Change speed to 1x
6. Click apply
7. Go to Length
8. Make no change, click Apply => crash

I get an error when I open OpenShot:
/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

Below are a few more (different) error messages at the time of crash:
GenerateXML for an Effect
on_btnClose_clicked
on_frmClipProperties_destroy
The program 'openshot' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 219 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.)
Segmentation fault

GenerateXML for an Effect
on_btnClose_clicked
on_frmClipProperties_destroy
The program 'openshot' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 163 error_code 9 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

[Jonathan Thomas (jonoomph)]

This was fixed in version 1.0. Thanks!