Although I would not generally agree to that (IMO, too much information can also obfuscate the important points), in this case it indeed doesn't hurt. It's just that, as an answer to my post, I somehow interpreted those instructions as intended for me. Just had to defend myself

Well, I just finished re-emerging wxGTK 2.4.2-r3 and aMule without support for gtk2 and unicode. Gee, gtk is so much uglier than gtk2

But if it works better, guess that's more important... I'm curious whether this will actually solve the problem, and after thedude's post, I'm quite confident indeed

While I was at it, I also emerged amule 2.0.0_rc8 instead of amule 1.2.8. I intended to wait for wxGTK 2.5.3 to be stable, but as I emerged it without gtk2 and unicode anyways now, why not?
I will report on my experiences with this new configuration later
