aMule Forum
English => en_Bugs => Topic started by: sidamos on July 23, 2004, 12:09:37 PM
-
HI!
I upgraded from 1.2.8 to 2.0.0rc5.
When I start it, it displays a dialog box about resetting the locale and it writes this into the shell and then hangs (replaced my user hash by x...):
Initialising aMule
Userhash loaded: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
*** UDP socket at 4665
*** TCP socket at 4662
*** UDP socket at 0
I even deleted preferences.dat, but that did not help.
Suse 9.0, KDE 3.1.
Any idea?
Thanks!
Thomas
-
rm ~/.eMule
then restart aMule.
Greetings!
-
HI!
You mean rm ~/.aMule, right?
Then I lose my user hash and credits, right?
Thomas
-
HI!
Ah, ~/.eMule is a file, not a dir. Because of this, I did not find it, first.
Deleting that file does not help. The only difference is, that it then also prints "No cryptkey.dat found, creating", but it still does not open the window.
If I delete the ~/.aMule dir, then it opens the window and starts rehashing all files (why rehash?).
But then I lose my user has, credits, etc.
Any other idea?
Thanks!
Thomas
-
sure, if you delete ~/.aMule directory, you are deleting all the data stored by aMule
if you delete ~/.eMule you are just deleting the preferences settings (no hashes, no credits, nothing, only preferences).
I bet you should delete ~/.aMule/clients.met
Let's see if that works. Try it and restart aMule.
Greetings!
-
HI!
Yes, it works, if I delete clients.met. Is this a bug, that I have to do this?
Thomas
-
Well, it's sort of a bug. It sometimes happens that for some reason, when updating aMule to a next version, clients.met (the credits file) is broken.
But anyway, not a serious bug, really.
I'm gald you have aMule working now ;-)
Greetings!
-
Originally posted by Jacobo221
Well, it's sort of a bug. It sometimes happens that for some reason, when updating aMule to a next version, clients.met (the credits file) is broken.
It happened to me after upgrading to RC5. I ran it for a while -- nice, quite a bit more stable than RC3 -- but when it did crash once, it refused to start again. Deleting ~/.eMule finally fixed it. Before, I had obtained RC4a and RC3 in source again (used the RPMs before) and found that with the same config, RC4a wouldn't start, but RC3 did.
I'm not sure I want to get into debugging this, but just maybe after I finished this month's programming job...
cheers!
Lunkwill
-
sure it'd be nice if you did :-)
thnx!