Started in Ubuntu Studio 10.04 and then 10.10RC
I'm trying out Arch Linux now (Metacity) and the same thing happend - bummer.
Strangely (or not) it still works for me in the Arch root account.
I never had these problems (in Ubuntu) with earlier versions of OpenShot (I think I was using the PPA for the past year).
For me this is so unfortunate. 1.1, 1.3 were so good but now version 2 has this problem for me as well as seemingly running slower than older versions on both the Ubuntu and Arch installs.
My output;
--------------------------------
OpenShot (version 1.2.2)
--------------------------------
Process no longer exists: 11296. Creating new pid lock file.
state saved
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 53 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.)
Same problem here with 2.2
Started in Ubuntu Studio 10.04 and then 10.10RC
I'm trying out Arch Linux now (Metacity) and the same thing happend - bummer.
Strangely (or not) it still works for me in the Arch root account.
I never had these problems (in Ubuntu) with earlier versions of OpenShot (I think I was using the PPA for the past year).
For me this is so unfortunate. 1.1, 1.3 were so good but now version 2 has this problem for me as well as seemingly running slower than older versions on both the Ubuntu and Arch installs.
My output;
------- ------- ------- ------- ---- ------- ------- ------- ----
OpenShot (version 1.2.2)
-------
Process no longer exists: 11296. Creating new pid lock file.
state saved
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 53 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.)