aMule Forum
English => en_Bugs => Topic started by: MrTom on January 13, 2004, 03:32:41 PM
-
Hello, since I failed my installation of the last kernel (2.4.22-26) on Mandrake 9.2 I got this error at anytime : "can't find length of the file on file descriptor 11 (error 22 : Invalid argument)"
Even if I click on "OK" it reappears again and again and again... until I can turn off aMule, and get the error message again and again and again...
I tried several other versions : 1.2.1, 1.2.3 and 1.2.4 and the pb is still present.
Maybe someone can help me! Thanks!
(also i would like to uninstall completely aMule but I can't find where it is installed - parameters are saved even if /.amule has been deleted)
-
it has smth with the files u dl to do .. try to put file after file to your temp dir, relaunch amule and look when it happens ..
greets
delta
-
Check the folder. does it have spaces or not-standard chars?
-
Yes the folder have spaces... i'll try to rename it without it.
-
i have the same problem.
and its not a folder problem :
/usr/local/data dor my incomig folder, and
/usr/local/data_temp for my temp folder
i use the amule 1.2.3-1 in a SID debian, i will upgrade to 1.2.4-1 to see if the problem persists.
one more thing, wouldnt it be more useful to put the string of the name of the file that is associated to the file descriptor that cause the problem ?
-
Yes it is not a problem folder, i rename them and i still got the error. i don't know what to do and i'm afraid to have the same problem if i add new files (i could have been an error on old files).
-
one more thing, wouldnt it be more useful to put the string of the name of the file that is associated to the file descriptor that cause the problem ?
We can't. It's wxGTK error, not amule :P
Well, it's kinnda strange. I'll think about it and repost here.
-
according to dselect my version of wxGTK is 2.4.2.4, maybe that can help find the problem
-
2.4.2.4 ?
-
well ... that's the number dselect gives to me ...
i just see something in xterm when the error comes :
Error in lseek : invalid argument
and that repeat forever
and the mule is going on well in background ... the value of download rate is refreshing and i'm dowloading and uploading as if there were no errors.
-
the infamous lseek bug.
I think is time to fix it, guys! lol
-
I use the version of wxGTK which is available on the download page of the website. Actually, the error does not last forever, it ends after some minutes. And as ekureuil said it amule keeps on downloading. The error on my computer began with the 1.2.3 version and now on every version I could install.
-
uhm, k.. w'll take a look at it
-
I found something really strange today... i re-installed my computer at the beginning of the week and i had no error. But today, i went to the preferences panel and turned on the "prompt on exit" option, and the error message came back forever! I managed to turn it off, and the error disappeared. Interesting isn't it?
Update : well, the error appeared again... it doesn't work :)) sorry !
-
huh.. thx!
-
Originally posted by MrTom
well, the error appeared again... it doesn't work :)) sorry !
-
Hi all.
I've got the same problems. I'm using Mandrake 9.2. If I change linux distr, will I solve it?
-
so... isn't fixed in 1.2.5 ?
-
Originally posted by Nemo
Hi all.
I've got the same problems. I'm using Mandrake 9.2. If I change linux distr, will I solve it?
i have suse 9.0 and never got the msg ..
-
I've installed aMule 1.2.5 and got this error (error 22: invalid argument). I really don't know how to solve it. Trying another linux distribution?
-
I don't think another distri will solve it. I had used Mandrake, too and never got this error.
Before that it was RedHat also with no error.
And now on Gentoo even no error. So I think the problem is located somewhere else. Trying to post your system config here.
e.g. fstab, .eMule, ldd amule, etc...
So we can see if there is a problem with your config...
Greetings
Galizah
-
I am getting the same error on a Suse 8.2 system, but only when I am trying to download a file > approx. 2 GB. I have verified it and I can reproduce the error by selecting a big file.
-
But is not this bug fixed in version 1.2.6?
I run amule on Mdk10 and my client also present this problem...
-
got the same errors coming up in 2.0.0rc3.
i too am downloading a file > 2GB
this only started happening after re-compiling glibc, etc, with nptl (native posix threads)...
recompiling amule didn't help, going to recompile wxGTK and post results.