On 05/20/2014 04:08 AM, Edward K. Ream wrote: > Have you googled for ways of suppressing these > errors?
Now I have. The only suggestion I found was a very bad suggestion: redirect stderr to /dev/null. I doubt that there is any way to suppress these errors. The glib developers refuse to fix the problem. See https://bugzilla.gnome.org/show_bug.cgi?id=362749 > And just to confirm, you don't actually see any problem with the code > (except for the messages themselves), right? I have not observed any bad program behavior that I think is in any way related to the GTK-Critical error messages. As is noted in the above bugzilla thread, because glib does check for bad parameters, it renders harmless otherwise fatal bugs in application code. But as is noted in the above bugzilla thread and in several other discussions on the Internet, the GTK-Critical error messages almost certainly indicate that someone is calling GTK functions with bad parameters. The mod_scripting.py is probably doing something that it should not do. My best guess is that button styling is the problem. -- Segundo Bob [email protected] -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
