< Back to IRCAM Forum

om X ERROR on Linux

OpenMusic
#1

Hi

I am wondering if some Linux users had this kind of error which seems the equivalent on the MacOSX version but in X style. I ask this in order to try to debug the problem.

X ERROR
Display: “:0 {Lispworks}”
Error: BadGC (invalid GC parameter)
Major opcode of failed request: 60 (X_FreeGC)
ResourceID: 0x1625668 (23221864)

X ERROR
Display: “:0 {Lispworks}”
Error: BadLength (poly request too large or internal Xlib length error)
Major opcode of failed request: 73 (X_GetImage)

Killed

It kills the process after sometime…

Thanx
K

#2

Hi Karim. No, can’t recall that error. This has nothing to do with OM (but might be a bug in lw someplace). What’s sure is it’s something with the connection with your X-server.

Some questions:

  • what window-manager are you using?
  • are you running your client (OM) on a local host, or over a network (ie. ssh -X somehost)
  • where does the error show up - in the system logs, in OMs listener, in your terminal? If there’s some context, please send more of the log.
#3

Anders,

Yes of course , you’re right!

I am running enlightenment17 (as a window manager). It could be the reason.
And it is a LW error of course. Same thing in Om mac version. It happened after a drag&drop.
But to tell you the truth i worked all afternoon with OM same config it worked like a charm !
It’s just great. So funny code om errors, due to code writting, donno should ask Jean about that.

For the 2nd question no i was running it on local. LAunched OM from terminal And the error log i pasted was from the terminal nothing else regarding xwin error.

And of course enlightenment sometimes, although handles gnome, sometimes ressources are not correctly handled. So it might be the reason.

Something else i noticed, but that i think you know, it’s the loop window things.
When openned, the connections seems missing. It is just a matter of refreshing the window.

Thanx a lot for this great port!

K

#4

Right. If you’re able to pinpoint the behavior more precisely, please send me info, esp. related to the particular X setup you run at that instant, ie. which clients and server are involved.

The error-message suggests some low-level bug during packets sent between X and the client (OM or some other client you might be ‘dragg’-ing from/to).

Vs. the refreshment of the drawings: yes, the callbacks may be a bit sloppy at times. Hoping to get things running cleaner in OM-7.0.

Cheers, and thanks for all bug reports!