The program 'openshot' received an X Window System error

[Kees Serier]

I installed 0.9.43(through PPA) some time ago on a freshly installed Ubuntu 9.10 Beta.
It crashed immediatly with the X Window System error.
I today upgraded to 0.9.52 experimental through PPA.
Encounterd the missing /usr/lib/libmlt++.so.2 bug as descibed by Pablo.
Finally started openshot, but with the same crash.
I deconfigured compiz and configured metacity.
Started openshot again but it crash again :-(

See console output below:

Added /usr/share/openshot to system path
--------------------------------
   OpenShot (version 0.9.52)
--------------------------------
/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 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 41 error_code 11 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.)

kees@ace:~$ ps -ef|grep metacity
kees 3023 2932 0 18:55 ? 00:00:01 /usr/bin/metacity

mlt-python 0.4.7d is installed.
I'm running Ubuntu 9.10 with the latest update on an Acer 1354 Laptop with a Athlon mobile XP 2800+ processor with 2 GB,

Thanks in advance,

Kees

[Jonathan Thomas (jonoomph)]

Please try the experimental PPA (detailed on the website). This should fix
this.

Thanks,
-Jonathan

On Fri, Nov 6, 2009 at 12:18 PM, Kees Serier <email address hidden> wrote:

> Public bug reported:
>
> I installed 0.9.43(through PPA) some time ago on a freshly installed Ubuntu
> 9.10 Beta.
> It crashed immediatly with the X Window System error.
> I today upgraded to 0.9.52 experimental through PPA.
> Encounterd the missing /usr/lib/libmlt++.so.2 bug as descibed by Pablo.
> Finally started openshot, but with the same crash.
> I deconfigured compiz and configured metacity.
> Started openshot again but it crash again :-(
>
> See console output below:
>
>
> Added /usr/share/openshot to system path
> --------------------------------
> OpenShot (version 0.9.52)
> --------------------------------
> /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 'BadAlloc (insufficient resources for operation)'.
> (Details: serial 41 error_code 11 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.)
>
> kees@ace:~$ ps -ef|grep metacity
> kees 3023 2932 0 18:55 ? 00:00:01 /usr/bin/metacity
>
> mlt-python 0.4.7d is installed.
> I'm running Ubuntu 9.10 with the latest update on an Acer 1354 Laptop with
> a Athlon mobile XP 2800+ processor with 2 GB,
>
> Thanks in advance,
>
> Kees
>
> ** Affects: openshot
> Importance: Undecided
> Status: New
>
> --
> The program 'openshot' received an X Window System error
> https://bugs.launchpad.net/bugs/476760
> 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 installed 0.9.43(through PPA) some time ago on a freshly installed Ubuntu
> 9.10 Beta.
> It crashed immediatly with the X Window System error.
> I today upgraded to 0.9.52 experimental through PPA.
> Encounterd the missing /usr/lib/libmlt++.so.2 bug as descibed by Pablo.
> Finally started openshot, but with the same crash.
> I deconfigured compiz and configured metacity.
> Started openshot again but it crash again :-(
>
> See console output below:
>
>
> Added /usr/share/openshot to system path
> --------------------------------
> OpenShot (version 0.9.52)
> --------------------------------
> /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...

[Kees Serier (a-serier)]

Hi, I just upgraded, but with the same result, it's a stuburn one I guess.

kees@ace:~$ openshot
Added /usr/share/openshot to system path
--------------------------------
   OpenShot (version 0.9.53)
--------------------------------
/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 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 33 error_code 11 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() functi

Regards,

Kees

[Pierre Antoine Baillon (pabaillon)]

Same problem on UBUNTU LUCID 4.10 Open shot 1.1.3

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 26 error_code 2 request_code 133 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.)
Erreur de segmentation

I can restart the project but when i play it, they crash again. I must restart the computer.

[sven nilsson (takayama123)]

Process no longer exists: 9056. Creating new pid lock file.
A new frmMain has been created
state saved
on_frmMain_key_press_event
project modified: Opened project
state saved
on_frmMain_key_press_event
on_frmMain_key_press_event
on_frmMain_key_press_event
project modified: Changed visibility of track
state saved
on_tlbSeekForward_clicked
on_tlbPlay_clicked called with self.tlbPlay
on_tlbPlay_clicked called with self.tlbPlay
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 138 error_code 2 request_code 133 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.)

I get this similar error message (quite random) when i open one project and working in it.
Im running ubuntu 10.04.

[clay (gavin-clayshot)]

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.)

[Jonathan Thomas (jonoomph)]

Are you able to view any video successfully inside OpenShot? Perhaps by
double clicking a video or audio clip and previewing it? Is it
easily reproducible or does it happen in a very random manner? Thanks!

On Wed, Oct 13, 2010 at 5:50 AM, clay <email address hidden> wrote:

> 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.)
>
> --
> The program 'openshot' received an X Window System error
> https://bugs.launchpad.net/bugs/476760
> 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: Incomplete
>
> Bug description:
> I installed 0.9.43(through PPA) some time ago on a freshly installed Ubuntu
> 9.10 Beta.
> It crashed immediatly with the X Window System error.
> I today upgraded to 0.9.52 experimental through PPA.
> Encounterd the missing /usr/lib/libmlt++.so.2 bug as descibed by Pablo.
> Finally started openshot, but with the same crash.
> I deconfigured compiz and configured metacity.
> Started openshot again but it crash again :-(
>
> See console output below:
>
>
> Added /usr/share/openshot to system path
> --------------------------------
> OpenShot (version 0.9.52)
> --------------------------------
> /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 'BadAlloc (insufficient resources for operation)'.
> (Details: serial 41 error_code 11 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 com...

[Kees Serier (a-serier)]

  I'll have a try after upgrading my workstation tot 10.10 and OpenShot
1.2.2, this weekend.
Haven't done any video editing since.

Op 15-10-10 22:10, Jonathan Thomas schreef:
> Are you able to view any video successfully inside OpenShot? Perhaps by
> double clicking a video or audio clip and previewing it? Is it
> easily reproducible or does it happen in a very random manner? Thanks!
>
> On Wed, Oct 13, 2010 at 5:50 AM, clay<email address hidden> wrote:
>
>> 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.)
>>
>> --
>> The program 'openshot' received an X Window System error
>> https://bugs.launchpad.net/bugs/476760
>> 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: Incomplete
>>
>> Bug description:
>> I installed 0.9.43(through PPA) some time ago on a freshly installed Ubuntu
>> 9.10 Beta.
>> It crashed immediatly with the X Window System error.
>> I today upgraded to 0.9.52 experimental through PPA.
>> Encounterd the missing /usr/lib/libmlt++.so.2 bug as descibed by Pablo.
>> Finally started openshot, but with the same crash.
>> I deconfigured compiz and configured metacity.
>> Started openshot again but it crash again :-(
>>
>> See console output below:
>>
>>
>> Added /usr/share/openshot to system path
>> --------------------------------
>> OpenShot (version 0.9.52)
>> --------------------------------
>> /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 'BadAlloc (insufficient resources for operation)'....

[clay (gavin-clayshot)]

For me this has been a random problem. And after running without problem at first. After several install/uninstalls (now only in Arch) I can still only use OS as root and not in my user account.

Right clicking a file to open in OS has the same effect, namely opening OS for a split second before disappearing.

Trying to retrack my actions in Arch and earlier in 10.04 and 10.10 - I think this may have started after using OS in full screen mode. This may just be my old brain grasping for hope but is there a command for starting OS in a un-maxed window again?

[clay (gavin-clayshot)]

AAAAHHHHHHHHHH.......

I changed my theme from Metacity to something else that was in the Appearance Preferences and it worked!!

..... For a little while!

After un-maxing the window to normal size and then closing to restart OS again it now do the the same as before - only smaller!

Never count your chickens.....

[clay (gavin-clayshot)]

The new Terminal output -

--------------------------------
   OpenShot (version 1.2.2)
--------------------------------
Traceback (most recent call last):
  File "/usr/bin/openshot", line 57, in <module>
    main()
  File "/usr/lib/python2.6/site-packages/openshot/openshot.py", line 65, in main
    app = frmMain(project=current_project, version=info.SETUP['version'])
  File "/usr/lib/python2.6/site-packages/openshot/windows/MainGTK.py", line 280, in __init__
    self.project.RefreshXML()
  File "/usr/lib/python2.6/site-packages/openshot/classes/project.py", line 263, in RefreshXML
    self.form.timelinewindowRight.window.set_cursor(gtk.gdk.Cursor(150))
AttributeError: 'NoneType' object has no attribute 'set_cursor'

[Olivier Girard (eolinwen)]

I wish to have a precision. Your theme that you have changed, it was for Gnome or a theme of Openshot ?
Thanks.

[clay (gavin-clayshot)]

Thankyou.
It was a gnome theme.
I have been unsucessful since dispite downloading a few more.

I know have two Terminal outputs;

--------------------------------
   OpenShot (version 1.2.2)
--------------------------------
state saved
Not the primary instance of OpenShot. Not starting queue watcher thread.
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.)

AND, the previous output posted. It changes according to the Gnome theme used.
I get this output when OS flashes the screen for a split second before closing again.

The previous output posted using a different theme no longer starts OS for that split second flash, nothing at all, the terminal also freezes (not the computer though).

I hope this helps.

[Andy Finch (fincha)]

The error "AttributeError: 'NoneType' object has no attribute 'set_cursor'" can usually be fixed by deleting the settings file in ~/.openshot.

[clay (gavin-clayshot)]

SOLVED !

Deleting these three files in the hidden .openshot folder has indeed solved the problem for me.

sequence.mlt
config.xml
pid.lock

Best wishes and thank you very much for your help.

[Olivier Girard (eolinwen)]

Wonderful. Two things , first in the second output of the terminal you was having two sessions of Openshot open and you can remove the folder .openshot, it will be create automatically at each launch of Openshot (when he is destroy).
Thanks

[clay (gavin-clayshot)]

I think all is becoming clear. A run-down of my experience with 'The Blender Edition' of OpenShot.

My problems started whilst using Ubuntu Studio 10.04 and then 10.10rc. After moving to Arch the problem still continued.

Previous to Blender I had no problems at all. OpenShot was 99.9% stable. With the coming of OS 1.2.2 and Blender titles things started to go wrong.

My problem is that I like testing and playing with different settings and frequently open and close OS to see which setting is more suitable for the task in hand etc. When Blender was added there is more for me to play with, and more to go wrong.

Initially on my own and also my sons computer things went OK but slowly. Blender started to leave several processes running in the background, probably due to both of us trying out the different title effects. I have just duplicated this error on my Xubuntu laptop after adding blender to OS. Hitting the cancel button during a render appeared to stop the render – but left it running in the background and leaving the laptop running slowly. Strangely, it has not happened again after a laptop reboot. Our desktops would not have been rebooted after upgrading OS to 1.2.2.

To recap on my experience;

1)OpenShot has proved itself 99.9% to me as an excellent VE.
2)Problems started with Blender;
 a)Computer slowed due to background processes not stopping as requested (now solved/known about)
 b)OpenShot failed to start -xwindow errors/multiple sessions running (now solved) that I will also blame onto Blender as after testing Blender again - the same thing happened again.

I note that OpenShot 1.2.2 Never had any issues running on my Arch root account. This I expect is solely due to the fact that I never fully tested (read as used Blender) anything as root.

My concerns are that if my experiences are like other average OpenShot users it could damage the reputation of this up and coming wonderful video editor. Using Blender titles within OpenShot stops the
effective working within OpenShot anyway due to processor power being diverted, so perhaps a separate OpenShot title program that wont interfere with video editor itself is called for?

Whatever happens please don't let a heavyweight application damage the future editions of OpenShot.
Best wishes to all.

[Olivier Girard (eolinwen)]

Thanks for the feedback. Same if we have done a lot of tests, we are not infallible. We have need some testers like you who test a lot our project. And we must create a better test 's protocol too. I have already seen that with Jonathan.

 That 's right that the Blender API python is not yet stable. But we belkieve in Blender project. Personally, i was having less problems with the alphas that the beta. it was a reason why we have a lot hesitated before to come out this version. But this feature is so great...... The pleasure wined against the reason :)

Your judgment is interesting and right. And promise, we will not do again but it was so great...

Best regards.

[Launchpad Janitor (janitor)]

[Expired for OpenShot Video Editor because there has been no activity for 60 days.]

[vedavata (vedavrata)]

state saved
The program 'openshot' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 25 error_code 11 request_code 149 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.)

Linux Mint 15.
Linux dell-xps 3.8.0-27-generic #40-Ubuntu SMP Tue Jul 9 00:17:05 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

ii openshot 1.4.3+0+740+66+301~raring1 all Create and edit videos and movies
ii openshot-doc 1.4.3+0+740+66+301~raring1 all Help manual for OpenShot Video Editor