aMule Bug Tracker - aMule
View Issue Details
0000229aMuleSharedfilespublic2004-12-10 10:562005-02-01 22:36
Raph 
Kry 
normalminoralways
closedopen 
2.0.0-rc7 
 
0000229: Change permission Warning when Writing transferred files into FAT32 partition Incoming directory.
A FAT32 partition is set for Incoming Directory, but not for Temp (ext3)
When a downloaded file is finished, it copies it from Temp to Incoming Directory.
A warning message says that it can't change file permissions.
The progress bar never become green and I can't clear Transfert list correctly.
distrib Debian Sarge with latest updates.
Kernel Linux 2.6.8-1-smp.
FR_fr locale.
No tags attached.
related to 0000248closed Kry probleme w/ unicode on fat partitions 
Issue History
2004-12-10 10:56RaphNew Issue
2004-12-29 23:53KryNote Added: 0000478
2005-01-06 15:57kubrickNote Added: 0000482
2005-01-06 16:05KryRelationship addedrelated to 0000248
2005-01-06 18:25KryNote Added: 0000491
2005-01-07 10:43kubrickNote Added: 0000494
2005-01-11 01:28KryStatusnew => assigned
2005-01-11 01:28KryAssigned To => Kry
2005-01-19 18:20KryNote Added: 0000523
2005-02-01 22:36KryStatusassigned => closed
2005-02-01 22:36KryNote Added: 0000588

Notes
(0000478)
Kry   
2004-12-29 23:53   
Did I break it again? damm :)
(0000482)
kubrick   
2005-01-06 15:57   
Check if these files that aMule can't finalize contains in their filename non-unicode characters, if yes try to remove them, if you can't, move them to a different category who writes on an ext3 partition an then copy it in the wished partition after removing the non-unicode charaters. It worked 4 me...
(0000491)
Kry   
2005-01-06 18:25   
Do you see the "Incoming dir is placed on a FAT32 partition. Disabling chmod to avoid useless warnings." on your aMule log?
(0000494)
kubrick   
2005-01-07 10:43   
yes I see it
(0000523)
Kry   
2005-01-19 18:20   
Still working on it. I think it's solved but will sync it with the tarballs soon.
(0000588)
Kry   
2005-02-01 22:36   
It was related to non-ascii finlanames. To avoid it, you will ahve to use a unicoded version of the 2.0.0 release, when it's out :)