[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lmi] GTK warnings
From: |
Greg Chicares |
Subject: |
Re: [lmi] GTK warnings |
Date: |
Fri, 1 Jul 2022 16:00:30 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 |
On 7/1/22 15:16, Vadim Zeitlin wrote:
> On Thu, 30 Jun 2022 19:47:11 +0000 Greg Chicares <gchicares@sbcglobal.net>
> wrote:
[...]
> GC> (lmi_wx_shared:79710): Gtk-WARNING **: 19:32:24.395: Drawing a gadget
> with negative dimensions. Did you forget to allocate a size? (node tab owner
> GtkNotebook)
>
> I don't see this one, using GTK 3.24.34. Could you please tell me what do
> I need to do to see it?
To reproduce:
File | New | Illustration
OK
That gives me ten instances of the warning quoted above, followed by
one instance of the one below:
> GC> (lmi_wx_shared:79710): Gtk-CRITICAL **: 19:32:24.402:
> gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar
I don't think we should suppress all GTK diagnostics...
> Calling GTKSuppressDiagnostics() would be trivial, of course, if you're
> ready to do it.
...because someday we might actually get one that's not merely noise.
I have very much the same experience with 'meld'. For example:
$meld /srv/chroot/lmi_bookworm_5/opt/lmi/free/src/lmi
/srv/chroot/lmi_bookworm_5/opt/lmi/src/lmi 2>&1 |less
elicits a very large number of lines like this:
2022-07-01 15:45:47,481 CRITICAL Gtk: gtk_widget_get_scale_factor: assertion
'GTK_IS_WIDGET (widget)' failed
Attempting to capture them all in a file, like this:
>eraseme 2>&1
fails, producing a zero-byte file. I have the impression that
GTK might be sending messages to someplace like /dev/tty .
Piping into 'less' as above, I see a screenful of those messages,
but if I try scrolling 'less', they all vanish. It's still useful
to pipe into 'less' because it provides a place for messages to go
instead of filling up my terminal scrollback buffer, but then I
still have to quit 'less', so lately I've been running
meld ...arguments... 2>&1 >/dev/null &
It's been this way with 'meld' since approximately forever.
Maybe the only reason I don't see those messages with other GUI
apps is that I launch them from xfce menus.
My conclusion is that these GTK messages might be useful if they
indicate actual problems in code I write, to the extent that it's
possible to fix them; but otherwise, GTK is just defectively noisy.