aMule Forum
English => en_Bugs => Topic started by: Underpass on September 22, 2007, 09:29:28 AM
-
Hello, sorry if this question is already been asked, I did not manage to find an answer.
I tried successfully to compile a CVS versione of aMule on Debian (testing). I noticed that when I alter some values in the connection options but then I set them at the former values - and sometimes even only "touching" the connection panel without actually moving anything - I get the message saying that the program has to be restarted because TCP and UDP settings are changed.
Upon restarting the program, the connection options are lost and reset to default values (i.e. TCP 4662, UDP 4672, upload =10, etc.)
Creating a new profile by moving the .aMule directory had no effect
Now I'm using aMule-CVS-20070907, but the problem still remains in the aMule-CVS-20070922
Thanks in advance and have a good weekend.
-
Hi,
this is a part of the problem holding back the release of aMule 2.2.0. So far it only happened on Debian and Ubuntu Gutsy based system, I was unable to reproduce it with my "bleeding edge" Archlinux system.
Some more questions: What version of wxwidgets are you using? Do you use geoip (country flags) and/or UPnP?
-
First of all, thanks alot for having answered me - I thought my question was rather stupid... :)
What version of wxwidgets are you using?
Now that's strange... I changed my machine a few days ago - I bought a new one - and I'm using wxWidget 2.8.5. But on the box I had before, I was using 2.8.4 and I don't seem to remember that problem. Thank you for this hint, I'll try to revert back to 2.8.4 and will let you know.
Do you use geoip (country flags) and/or UPnP?
Sorry, I don't know what geoip actually is - so I don't think I'm using it. Is it some sort of ./configure option?
However I'm not using uPnP, even if I compile with normal flags so I see that option in the connection panel
Forgive me if I can't be more accurate, but I'm not the "hacker kind"... ;)
But if I can do anything, just ask, and I will try.
Bye.
-
Ok. I've been testing, albeit not intensively.
I downloaded wxGTK 2.84 and compiled with these options, following the wiki:
/configure --prefix=/opt/amule --with-gtk --enable-unicode --enable-optimise
then I downloaded the last CVS and compiled with these options:
./configure --prefix=/opt/amule/ --enable-debug --disable-optimize --with-wx-config=/opt/amule/bin/wx-config
which is the way I compiled until now (the uPNP support is included, the geoip is not ;))
From what I've been able to see the problem doesn't show anymore, so it could be originated by the wxGTK 2.8.5
Please let me know what you think about it, for I'm quite interested. Thanks :)
-
Same here with CVS-20070923 and wxGTK 2.8.5 on FreeBSD 7-CURRENT.
UPnP compiled but disabled, no GeoIP.
It happens on Preferences->Connection tab.
It looks like the interface shows modified values but then when I click 'OK' it somehow enters the defaults (in case of ports).
Everything is OK if I "touch" every value I changed - in my case Bandwidth Limits, Line Capacities and TCP/UDP ports.
(by touching I mean change it +1 and then -1 with buttons)
Let me know if there's any informations needed.
Karol
-
OK, I'm able to reproduce this now (using 2.8.5 as well, but I believe that this occurred for Kry with 2.8.4 already) and I'll dig a bit deeper in the source trying to fix this ASAP.
Thanks a lot for your reports, it helps a lot!
-
If you still care.. Happened with amuled on NetBSD (wxBase 2.8.0), amulegui on openSuSE 10.2 (wxGTK 2.8.5).
-
Just the same problem on SLAMD64, wxWidgets 2.8.5.
I noticed this problem after a crash: when I restart amule after a crash I notice that line capacity values and upload/download limits are set to different values than mine (if I remember well "3" for upload/download capacity, "10" as upload bandwidth limit... I don't remember the value set for download limit).
I do not remember if other values changed.
Oh, I was forgetting: I use aMule-CVS 20070924
Bye,
Mr Hyde
-
He...funny, it also happened to me on solaris x86, using aMule SVN from September 15th, and wxGTK 2.8.4, but I noticed just after a crash, so I thought something had gone wrong with the file.
Regards.
-
I guess I'm going to have a lot of fun with it...:(
-
With new wxGTK 2.8.6 and the latest CVS source the problem doesn't seem to occur (Debian Lenny)
Bye ;)
-
With new wxGTK 2.8.6 and the latest CVS source the problem doesn't seem to occur (Debian Lenny)
Same for Debian Etch (aMule svn-2007-08-27).
-
So, all people using wx 2.8.6 do NOT have this problem? I'll have to upgrade my system first to try it out on Linux, and recompile wxMSW as well...
-
As regards me and my SLAMD64: upgraded wxWidgets to 2.8.6 and the problem seems gone.
Bye,
Mr Hyde
-
Maybe this is right for a specific compile of wx. I use wx 2.8.3 and don't have this problem. Maybe it's caused by a (de)activated option for wx compile or some wx <--> <otherlib> compat problem.
-
hi all!
I use the wonderful Vollstrecker's CVS on my Elive (debian testing) and if i try read the files comments or enter in "preferencies" amule crash.
wx 2.8.3 & today CVS
Sorry if this isn't the same problem of this thread.
bye
-
Vollstrecker, the bug affects only versions 2.8.4 and 2.8.5 of wxWidgets.
-
k, I just thought about packaging 2.8.6, but if the 2.8.3 still works, I can wait till the official maintainer does that. I just hope he doesn't package one of these two versions.