Hi kornell,
Welcome to our forum.
This problem used to happen to me when I used Fedora 5, but now I use Suse and I don't remember it happening again. This could be related aMule (of course), to a bad wx package (sometimes distros screw it) or even a problem in glibc (most unlikely).
Are you sure you are compiling aMule with the wx that you compiled yourself? Maybe you are linking to the distro's wx, and that could explain. I usually install my self compiled wx in my home directory and link aMule explicitly with it. I do it like this:
Compile wx and install in my home dir:
./configure --enable-debug --disable-optimise --enable-debug_flag --enable-debug_info --enable-debug_gdb --with-opengl --enable-gtk2 --enable-unicode --enable-largefile --prefix=/home/myuser/usr/local/wxWidgets-2.8.6 && make && make install
Compile aMule linked to my wx:
./configure --enable-ccache --with-denoise-level=3 --enable-debug --disable-optimize --enable-verbose --enable-geoip --enable-cas --enable-wxcas --enable-amule-gui --enable-webserver --enable-amulecmd --enable-amule-daemon --with-wx-config=/home/myuser/usr/local/wxWidgets-2.8.6/bin/wx-config && LD_LIBRARY_PATH=/home/myuser/usr/local/wxWidgets-2.8.6/lib/ make
Run aMule:
LD_LIBRARY_PATH=/home/myuser/usr/local/wxWidgets-2.8.6/lib/:/home/myuser/usr/local/libupnp/lib/ LANG=en_US.UTF-8 trunk5/src/amule
I never "make install" aMule on my system because I have too many versions here to test, so it would make no sense. On the other hand, nothing is in the system paths, so I have to use these environment variables as prefix. But that also guarantees that I am using the packages that I want. Maybe you should give it a try.
Cheers!
PS: Nevermind about your google english, makes perfect sense to me. Maybe because I am brazilian
