Your message dated Sat, 6 Jun 2009 21:10:27 +0200
with message-id <[email protected]>
and subject line RE:Gtk-CRITICAL lines when starting amule
has caused the Debian Bug report #503066,
regarding Gtk-CRITICAL lines when starting amule
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
503066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503066
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: amule
Version: 2.2.1-1
Severity: minor
Debian testing
linux-image 2.6.26-8
amd64
When starting amule, there are 2 Gtk-CRITICAL lines. Theses lines do not have
any noticeable effects on the program.
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
ListenSocket: Ok.
(amule:10510): Gtk-CRITICAL **: gtk_container_remove: assertion
`GTK_IS_CONTAINER (container)' failed
(amule:10510): Gtk-CRITICAL **: gtk_container_remove: assertion
`GTK_IS_CONTAINER (container)' failed
Loading temp files from /home/myusername/.aMule/Temp.
Loading PartFile 2 of 2
All PartFiles Loaded.
--- End Message ---
--- Begin Message ---
This bug report has nothing to do with amule. The error only appears when
the amule user is using certain GNOME desktop themes. A bug report about
this has been sent to the developers of GTK.
--- End Message ---
