Hi, I have 28.5 GB of music on an NTFS partition shared between linux and windows.  I wanted to reorganize my collection's directory structure, and it seemed Amarok could do this. I started it off, but amarok went all grey (no icons, just a grey window).  Amarok is still running at 100% of the cpu according ti top, but I don't have confidence that its actually doing anything...  Is there any way to check its progress, or see if its hung up? I don't want to interrupt it if its still processing. I'm nervous now that I should have made a more recent backup of my music library.

I looked at some of the new directories its making. They are empty of any music files, so I'm confused, and worried its getting mixed up somehow.

Thanks for any advice...

I'm having the same issue on Fedora 10 on an ext3 partition with Amaroc 2.0.1.  Gray screen, 100% utlitization on a single core.  It is creating empty directories, but I haven't seen any files moved.

Status indicators really need to be added to this function.

It appears that it does this during the directory creation phase.  I've been able to process small batches of files and noticed that the screen doesn't refresh while building the directories -- this is before the status bar is displayed showing that it is copying/moving files.

If it runs up against a file that it can't process during the directory building phase then it just gets lost and doesn't recover gracefully.

confirming this bug on amd64, amarok 2.0.1.1, debian kde 4.1.4, phnon xine backend (standard, no changes made).

It does exactly what you're trying to describe but in fact it doesn't freeze, it just gets slower and slower and slower... I'm currently trying to organize some 2000 or so files and the first ones 'copied' really fast (I'm running amarok in debug mode) but it's really slow now (after 3 hours of waiting), the console output says 50s at the moment... it might be even linked to the progressbar thingie and not the actual copying but I'm no expert in this.

Please look at this thread and give us an update on this because I can imagine that some folks freak out when they see the program 'freezing' when handling real data. to those, I can only say that no data is lost (for me so far, that is).

Thanks, bye!

I tried a couple of different things.  First, I gave it a folder of about 7200 files, all of them mp3 format.  It ran for over 72 hours.  At the end it would create a new folder about every 3 minutes.  It never did get to copying files.

Finally, I gave up and had it move the files in batches of between 100 and 200.  Doing it this way it processed all 7200 songs in about 1/2 hour.