I've compiled Amarok 1.4 from source using the directions in the README. However I receive this error when trying to launch amarok from a terminal:

I'm running Slackware 10.2 with KDE 3.5.2. I had the same issue with KDE 3.4.

Has anybody else seen this?

i'd rather wait for official packages from Pat, or you can try to use the binary packages from LinuxPackages.net. It's already available

I went ahead and installed the Amarok 1.4 package from linuxpackages.net. I've had trouble with that package before with kde 3.4, but with kde 3.5 it seems to work fine. Strange that the compilation route failed.... Thanks.

the official amaroK packages from Pat has just arrived along with other packages as well. You might want to get them also. It's in the -current tree

The official amarok package in -current also gives the sound-engine plugins error message when it is first started. Click OK, and it will quit. Restart it and it should work. At least, mine did.

My only problem with it so far, is that it seems to have forgotten my old settings, including what I have played already and how often. Last night I listened to the album I am listening to now, but amarok 1.4 "Fast Forward" is telling me I never listened to it before. I am hoping that this is just temporary while amarok 1.4 builds databases of my collection and my listening history. We'll see.

I have been playing with amarok for the better part of the last two hours or so. The initial error message about the sound-engine plugins also included a bit about updating the configuration database. That has resulted in amarok losing its record of my collection, and repeated scans of the collection have not brought it back. I can still play music using playlists, which I assume are scanned in every time amarok launches and which I assume don't have to be scanned for tags or the like. This problem seems to have a bit of a history, since there are bug reports on the KDE site of amarok 1.3.7 "losing" collections after it has been running for a while.

Given the problems I am having with the upgrade to 1.4, I recommend that if you haven't upgraded, wait until 1.4.1 is released or until Pat releases a second version of amarok 1.4.

I have deleted the collection.db, collection_scan.files and collection_scan.log to see if that works. I'll report back on what I find out, but right now, I am considering downgrading back to the last official slack-current release version if I can.

I removed collection.db, collection_scan.log and collection_scan.files and restarted amarok. When it started again, it began scanning my collection and that scan seems to have worked.

Still, it does not seem to be a particularly well-behaved upgrade.

hm.. i will rethink again to upgrade my amaroK, since i haven't upgrade it yet (but i have download them). Thanks Hussar for the tips

is the constant updating collection every minute normal. its been doing this for awhile. is it because my collection is so hugh

It was doing it to me, yeah. Using the command `ls -1 music/*.m3u | wc -l` I get 562, so that's what, maybe 5700 mp3 files. Altogether it is 27G.

One of the funny things I noticed was, it didn't appear to be changing the collection.db file as it was updating. Run `ls -l .kde/share/apps/amarok/collection.db` and note the size and modification time of the file. Now wait a couple of minutes and do it again. Have the size and modification time changed? Mine hadn't.

Also, after a while, all I got was a notice in the Collection window asking for my patience while amarok scanned my collection - even when there was no progress bar showing.