jacen wrote:Hi, I have the same problem using Mandriva 2006 and Amarok 1.4.2.

Mandriva 2006 + Amarok 1.4.2 is giving me a similar problem.  Difference is it gets to 99%, then nothing happens, no collection created.

I've tried putting my files on different partitions, tried scanning a single 20 file directory and tried removing amarokrc but it's not adding them to the collection.  The directory is clearly being scanned as it takes some time to do this.  Are there any dcop commands that could be used to test this?

Unless there is a simple quick fix I'm going to drop back to 1.4.0 as it was working fine for me.  Amarok is a great program and this release may be working for most people but if it doesn't work for me, I'll downgrade until I find a later version that works.

Well, the NFS quick fix has now failed.....It worked for a day or two and suddenly a third of my collection was gone....Colection scan gives the same errors as before....

Guess I'll wait till the next version comes about.

Same problem here.

1.4.1 worked just fine with my samba share from my Windows machine, now it's broken with 1.4.2.  There's just too many of these errors to "weed them out" of my collection; it stops at 8% and the errors just get more frequent from there.  The thing is, as far as I can tell, there's nothing wrong with the files being stalled on themselves.  They play just fine under on both my Windows and Linux Machines, but amaroK cannot index them without failing.

This is an example of the errors I get:

"Sorry, the Collection Scan was aborted, since too many problems were encountered.

Advice: A common source for this problem is a broken 'TagLib' package on your computer. Replacing this package may help fixing the issue.

The following files caused problems:

/home/prospero/smb4k/SERVER/Music Drive/Compressed Audio/Electronic/Underworld/Underworld - Beaucoup Fish/05) Underworld - Winjer.mp3"

Please, please, please.  There has to be some kind of fix for this.  amaroK is now almost useless to me because no collection can be built.

If there's no fix, can someone tell me the easiest way to roll back ot version 1.4.1?

I'm using Kubuntu Dapper.  Thanks.

There's a bug in 1.4.2 that makes the scanner stop after 2 crashes instead of 20. We're going to provide a patch for distro packagers to fix this.

The fix is trivial:

http://websvn.kde.org/trunk/extragear/m ... &r2=578922

Thanks for the followup, Mark....I recompiled and all is well again.

Bill

I was wondering if someone could help me to get this fixed.  I've spent probably about 6 hours working on getting amaroK runng properly again, with no luck. 

I built and installed version 1.4.1 from source, but I couldn't get it to start up properly, and I honestly don't have enough experience to troubleshoot the problem, so I just uninstalled 1.4.1 with "make unistall" and reinstalled 1.4.2 with my package manager.  It works, but it exhibits the same problem I was having before as described above.

I really appreciate all the hard work that goes into this player, and I understand that a patch is on the way to distribution packagers, but I'm stuck here in the mean time.  Is there any way someone could walk me through either fixing it by recompiling or suggest a way to fix the tags that it's stalling on?

I would GREATLY appreciate it.

OK, after upgrading to the latest CVS build using Amarok-svn, it's now stalling out after 20 errors instead of only 2.  However, I'm getting 20 fricken errors now when with version 1.4.1, I never recieved any error dialog like this at all!  So I still can't build my collection and therefore amaroK is fatally crippled.  Oh, and visualizations are, of course, greyed-out again.

Sigh.

WHAT is going on here?  Nothing about my music collection has changed since I was using 1.4.1 perfectly fine; I haven't changed anything about the structure, the tags, the filesystem, etc.  Hell, I haven't even added any new songs!

Something else is causing this, and I'm so frustrated that I'm ready to tear my hair out.  Please help me.

And if you're not able to help me out, could you PLEASE explain to me how to go back to version 1.4.1?

I recently saw a commit that changed the number of allowed crashes from 2 to 20. Not sure which was in 1.4.2. But folks having trouble might try SVN and see if that helps.

The number of allowed crashes was changed to 20 and (updated from SVN) now it gives simple 20 errors before stalling.
1.4.1 has worked flawlessly under Kubuntu and now after upgrade is amarok basically useless for me.
Please, do something about it.

Ok...For you folks having trouble getting things back in order, try this:

-    uninstall any amarok package you may have installed with your package manager (yum, rpm,apt,adept,whatever)

-     

Code: Select all

rm ~/.kde/share/config/amarokrc

-     

Code: Select all

rm -rf ~/.kde/share/apps/amarok/

These step will ensure that you get a CLEAN install!  Very important!

-      do your ./configure with whatever options you use, compile with make......before make install, do a make uninstall (as root)to clean up any old stuff then do the make install step (also as root).

Now,  before you run amarokapp, and if you use mysql, wipe out your amarokdb tables, or create a new mysql database....

Now, start amarok with amarokapp from the console (to see if it errors out)

For some reason I have to cancel the firstrun wizard because it crashes the app and I have to repeat the process. So, Cancel the first runwizard and configure amarok manually from the  Settings-->Configure Amarok--->collection  menu

hopefully this will work.  There are still some pretty bad bugs in this version...at least with my fedora based distro, for instance, I get playlist xml errors and have to frequently rebuild my playlist....Sometimes mysql uses 100% cpu for a LONG time....and there may be more....

REMOVING THE AMAROKDB FROM MYSQL seems to help get rid of the collection errors....for some reason that database doesn't get cleaned out each time you do a collection scan  WHY IS THIS???

Good luck,
Bill

Your instructions are GREATLY appreciated, bblood!

While I wasn't able to get 1.4.2 to build a collection, not matter what I tried, I was able to completely remove amaroK and its configuration/database files and install 1.4.1 from source.  It's working flawlessly again, much to my great pleasure.

I feel the need to reiterate that this problem was NOT caused by the max restarts parameter being 2 rather than 20, nor was it (seemingly) caused by taglib, which I did not touch.  This was something else introduced in the way 1.4.2 builds a collection database. 

I really, really hope this issue will be addressed in 1.4.3, as I simply cannot use 1.4.2 at all.

The only thing I didn't try that interests me is recompiling taglib from the latest source.  I didn't do this simply because I don't know how, and I've spent enough time (probably around 10-12 hours) troubleshooting this issue as it is.

Thanks for all of your help.

Hello,

we still have the same problem in 1.4.3

Also, maybe it can help, Ihave some images in the folders scanned, and some of these images are also in the error message of amarok.

By the way my files are on a reiser4 partition, and I'm using Kubuntu.