On Tue, May 20, 2014 at 4:06 PM, Segundo Bob <[email protected]> wrote:
> 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 Imo, the attitude of the developers merits the sarcasm at the end, not that it helps the OP :-) Hehe, I just barely refrained from saying so on the glib list. > ...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. It's really hard to debug an error message that I don't see, on a system that I don't have, and that nobody else can duplicate. Maybe assigning stderr to /dev/null is the most reasonable workaround. Anyone else have any other ideas? This is an issue that merits a solution. Edward -- 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.
