New 'could not move to library' bug
 

There appears to be a new bug:

In addition to the illegal characters - LimeWire will occasionally throw this error message up for all files that have been added to the download queue.

This has happened to me once - closing and restarting LimeWire fixed the problem.

I don't know what triggered it - When it happened, any new file I added to the download queue threw up the 'could not move to library' error as soon as it tried to start the download (i.e. at the point where it had connected to the server and was attempting to start the download (presumably as LimeWire tried to create the file in the incomplete folder).

It appeared to me that files that were already in my download queue were able to initiate transfer without problem - but I can't be absolutely certain that the downloads were from scratch rather than a continuation of a previous download.

I haven't yet been able to replicate the problem. But reports in the download conference suggest that other people may have experienced the same problem (it is not yet clear whether their problems are solely due to illegal characters or this bug).

Mark

I had this bug in previous versions. Files in my download queue would instantly jump to 100% (without really downloading anything) and the 'Could not move to library' message would appear. This error would happen with every subsequently selected file but , as you said, restarting Limewire solved the problem. In my case, the problem didn't appear to be related to illegal characters.

Funnily enough , I haven't yet encountered this bug LW2.5.5

It can be caused by illegal characters, even if the file, you are downloading doesn't seem to contain any, - especially if LimeWire is trying to swarm and the second filename of the second location that is not displayed by the GUI contains illegal characters.

Yes, naming a shared file with typically invisible null characters (ASCII 0) may present a problem, but I haven't tested how LimeWire handles this situation.

Granted on the illegal characters bit - but this bug isn't an illegal character bug (although it might be triggered that way).

Once the bug kicks in - *all* new download requests 'cannot be moved to library'. When this happened to me, some 30-40 files complained of this in rapid succession. They were various files from various locations - the chances that the all really did contain illegal characters are very low.

Mark