Comment 49 for bug 116870

Revision history for this message
adam kumpf (kumpf) wrote :

I realize there is a bit of dispute over whether or not this is a bug in GLib or the applications that are using GLib, but regardless, it seems to have an effect on a handful of programs. Could this be a case of an older bug in GLib that was "fixed" but possibly now breaks existing apps that depended on that bug?

For the app I am running (JOGL/SWT in Java) the warning message is not just a nuisance, it is immediately followed by a stack trace and the end of my program's happy execution. :(