search for: gdk_x_error

On kde, gtk-window-decorator segfault everytime a minimised "Konqueror download window" close it self... Running with --sync fix the problem so no way to have a backtrace :( Cedric

...ammers: 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.) Jarmo

...rs: 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.) [09:33 root at tux:root]# -Solaris 9 box root at sun bin# gvim --sync Gdk-ERROR **: BadAtom (invalid Atom parameter) serial 364 error_code 5 request_code 20 minor_code 0 Gdk-ERROR **: BadAccess (attempt to access private resource denied) serial 365 error_code 10 request_code 10...

...ammers: 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.) When I inverse the order of calls, I no longer seem to get issues. (See R-cairoDevice-relimp.txt) require(cairoDevice) require(relimp) showData (iris) Initially I got issues with 'playwith' and 'Rcmdr', but managed to pin down to 'cairoDevice' and 'tcltk...

...ammers: 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.) Konqueror doesn't crash but doesn't display the image and print : X Error: BadAlloc (insufficient resources for operation) 11 Major opcode: 53 Minor opcode: 0 Resource id: 0x26003c3 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 Mi...

...rs: 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.)" Just checked the Red Hat errata link: https://rhn.redhat.com/errata/RHSA-2008-0031.html and it says: "[Updated 18th January 2008] The original packages distributed with this errata had a bug which could cause some X applications to fail on 32-bit platforms. We have up...

...ammers: 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.) ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=15666&group_id=35

...ammers: 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 error doesn't occur until the code hits pygame.display.flip(), which makes it rather difficult to work out exactly which part is causing the problem. I'm using the menu widget in the game I am working on and it works perfectly, so it's obviously not the entire toolkit...

...rogrammers: 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 crash and error are very similar in case of 'RGtk2': require(tcltk) require(RGtk2) ReturnVal <- tkmessageBox(title="Greetings from R TclTk",message="Hello, world!",icon="info",type="ok") ### click "ok" to get the crash...

Hi Graham, Your guess is right. The event loop stuff is handled differently on Windows than on Unix-like OSes. There is a hook, called tcl_do that is hard-coded into the R Windows GUI. It is called whenever the console is idle. RGtk2 is able to hook into that to process GTK+ events. The problem is that the two packages replace each other's handler. So in this case tcltk is blocking GTK+ from