Originally posted by stefanero
did you run ldconfig after install?
When I install libraries manually (make install), I run ldconfig, but not after installing RPMs. I thought the package took care of that kind of thing...
and did you remove teh old wxGTK rpms?
Of course. According to locate,
libwx_gtk_adv-2.6.so.0 is not on anywhere my system.
That being said, perhaps there is some version mixing going on. When I have a moment, I will try to delete everything and start again from scratch.
However, I am wondering if there is some kind of memory leak problem in 2.1. which is causing it to crash after a few hours. For example, at the start of my last session with 2.1, before reverting to 2.0, amule's virtual memory footprint was ~130m. After six or so hours, however, my system started drastically slowing down; not in CPU activity but disk activity. According to top, amule's memory footprint had grown to 489m. Because amule was no longer responding I had to kill it in a terminal window. Several days previously, I had experience a similar situation; that time, amule's VM footprint had grown in the course of less than 18 hours to a whopping 744m.
I have not seen that kind of problem with 2.0. For example, it has now been running ~20 hours and is using 133MB. I admit I may be a "heavy" user; I am sharing ~1300 files (=571GB) with upload bandwidth of 80kB/s, but 2.0 seems to handle this ok.
If there is anyway I can help you identify the memory problem with 2.1, please let me know.
