That's a very old version of ntfs-3g.  They've had six stable releases
since then, fixing bugs ranging from metadata issues, permissions
problems, and even corruption.  Again:  Google is your friend.

What version of TagLib do you have installed?  When was the package
built?

Amarok won't keep scanning the collection if there's no
amarokcollectionscanner process going, so if amarokcollectionscanner
disappears at 59% it maybe died and didn't actually scan your whole
collection.

You should look in the directory ~/.kde/share/apps/amarok/ and see
what's there.  There are normally some collection scanner-related files
in there.  If you watch that directory when you start a full scan, and
you watch those files (i.e. with "tail -f"), you might see it getting
stuck and using huge memory on a particular file or group of files.  If
this is the case, try moving that file(s) out of your collection
directory and try the scan again, and see if it gets past that point
without the huge memory usage issue.  If it does it may hang up on
another file...rinse and repeat.

See how that goes; if it does help, then we should find a way for you to
get that file(s) to me so that I can do some debugging on it.

-- 
Rebuilding collection eats up too much memory
https://bugs.launchpad.net/bugs/133554
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to