After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 587224 - aMule fills .xsession-errors file
aMule fills .xsession-errors file
Status: RESOLVED INCOMPLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
2.16.x
Other All
: Normal minor
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2009-06-28 19:23 UTC by Joe Bassis
Modified: 2010-07-10 02:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Joe Bassis 2009-06-28 19:23:11 UTC 
Please describe the problem:
aMule fills the .xsession-errors file with these errors. The last error is repeated until the error file is full. I'm using Debian testing, GNOME and aMule 2.2.5.

aMule developer says bug in GTK: http://www.amule.org/amule/index.php?topic=16736.0

Steps to reproduce:
1. start aMule
2. .xsession-errors file gets filled up

Actual results:
(amule:3114): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_CONTAINER (container)' failed

(amule:3114): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_CONTAINER (container)' failed

** (amule:3114): CRITICAL **: smooth_draw_box_gap: assertion `height >= -1' failed

Expected results:
No errors should appear in .xsession-errors file.

Does this happen every time?
Yes.

Other information:
Different GNOME Themes produce different errors inside the .xsession-errors file. These errors have been happening for years, it seems nobody reported these errors before.
Comment 1 Matthias Clasen 2009-06-28 20:17:56 UTC 
What makes you think that this is a GTK+ problem ?
Comment 2 André Klapper 2009-06-28 21:56:05 UTC 
Quoting from the amule ticket:
"Seems to be a GTK bug. Wireshark apparently has it too, someone there has hacked GTK to do away with the problem.":
http://www.wireshark.org/lists/wireshark-dev/200804/msg00351.html
Comment 3 Matthias Clasen 2009-06-28 22:24:06 UTC 
"Seems to be a GTK bug" is not convincing at all, unless it is accompanied by a test case or a clear description of what actually goes wrong. I am not going to digg through some app devel archives, to find some alleged private gtk patch.

If there is a GTK+ problem at all (and I am not seeing any indication of that yet), it should have already been reported here...