aMule Forum
English => en_Bugs => Topic started by: lorey on April 01, 2009, 04:12:20 PM
-
I've noticed these Gtk-CRITICAL errors ever since I started to use aMule (versions 2.1.3 through 2.2.3). The last error is repeated thousands of times in what seems to be an endless loop. Any idea how to stop them from appearing?
I'm using amd64 Debian testing, aMule 2.2.3 and libwxgtk 2.8.7.1
These can be found at: /home/username/.xsession-errors
(amule:6198): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_CONTAINER (container)' failed
(amule:6198): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_CONTAINER (container)' failed
** (amule:6198): CRITICAL **: smooth_draw_box_gap: assertion `height >= -1' failed
-
Try a current wxWidgets version first (which is 2.8.10).
-
Debian does not currently have the latest 2.8.10 version but these errors also happened in Debian etch which had version 2.6.3.2
Could it be more like a strict standards programming notice? (More like a notice rather than an error.)
-
Debian does not currently have the latest 2.8.10 version
So you should complain at Debian.
-
I uninstalled the old libwxgtk and amule. I then installed all necessary packages, compiled and installed libwxgtk 2.8.10 and amule 2.2.4 exactly as described at: http://www.amule.org/wiki/index.php/HowTo_Compile_In_Debian#Compile_and_install_aMule
But I still get those same errors.
Definitely, amule says that version 2.8.10 being used (I removed the old version anyway):
2009-04-06 13:41:49: Starting aMule 2.2.4 using wxGTK2 v2.8.10
I'm using GNOME, just in case this has anything to do with it.
-
Is there any visual impact (graphical glitches or something) ?
-
There are no glitches nor visual impact. The only thing is that the /home/username/.xsession-errors file gets filled up with about 5000 repeated errors until that file reaches the limit and does not accept anymore errors.
-
Seems to be a GTK bug. Wireshark apparently has it too, someone there has hacked GTK (http://www.wireshark.org/lists/wireshark-dev/200804/msg00351.html) to do away with the problem.
-
In case anybody is interested, bug is reported at bugzilla.
http://bugzilla.gnome.org/show_bug.cgi?id=587224
-
Yeah, and they are not convinced I see.
We do not call GTK functions directly. wxWidgets does. So it might be an interaction problem between wx and GTK. Hard to say whose fault.