amarok 1.4.5 will not build collection

[Joel Cunningham]

Binary package hint: amarok

I'm on ubuntu feisty and got the new amarok today (1.4.5). I fired it up and remembered that had gotten rid of some of my music and my collection needed updating. So I tried the new feature, update collection and it didn't appear to do anything. The I ran rescan collection and it acted like it was going to start scanning, but then it didn't anything. So I figured might be something with the database (I'm using SQLlight). So I shutdown amarok and tried reloading it and under the collection tab, it just says "building collection database..."

See that the amarok process wasn't actual doing anything, I shut it down and deleted my entire .kde folder (resetting all my kde settings). Fired up amarok and told it where my collection and it just sits there, using no cpu and definitely not building my collection.

[Anderson (amg1127)]

I can confirm this bug with Amarok 2:1.4.5-0ubuntu.

Amarok 2:1.4.4-0.3ubuntu4 works.

[Josh (hashbrowncipher)]

Confirming report by slithy

Updated to 1.4.5 today and Amarok will no longer build collection. I am using MySQL and when i press either rescan or update collection nothing happens. It shows 0 percent progress and then, poof, the progressbar is gone.

[Andrew Ash (ash211)]

It definitely sounds like this is a confirmable event. We just need to figure out what's making it run slowly like this. Let's take a look at the command line output with the command `amarok > ~/amarokoutput.txt`.

Once the amarok screen appears immediately click rescan collection and wait a bit. Then close amarok with Engage -> Quit. Please attach the file ~/amarokoutput.txt

Thanks

[Tony H (tenacubus)]

Also confirmed with amarok 2:1.4.5-0ubuntu1.

I had the same thing happen with both my sqlite and mysql libraries. when I tried to rescan instead of just update my entire collection just disappeared.

[Tony H (tenacubus)]

There is no command line output by the way. I tried that and all I got is the following:

Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokap
p.

when looking for the command line output of amarokapp instead all I got was:

STARTUP

[Andrew Ash (ash211)]

Hmm, I'm not sure what to do if there's no cli output. We'll have to wait for someone more experienced to come along.

[Kevin Becker (kevinbecker)]

I'm seeing the exact same problem. I downloaded the source tarball from amarok.kde.org and installed that. It works perfectly. Whatever changes are made for ubuntu packaging caused this problem.

[Andrew Ash (ash211)]

I know removing stack smashing protection was made in hopes of fixing collection scanner crashes:

https://launchpad.net/ubuntu/+source/amarok/+bug/81768

[Toni Helenius (toni-helenius)]

Do you need any more confirmation? I can confirm this bug also on Feisty as described :(

[jaapkroe (jaapkroes)]

Another confirmation,

I tried with files on every partition and hdd possible (all are ext3) and tried with SQlite as well as psql.
On a fully update and upgraded system.

I'm now gonna try the tarball from http://download.kde.org/stable/amarok/1.4.5/src

[Anderson (amg1127)]

I think I discovered a workaround. :-D

As root,do:

# ln -s /usr/lib/amarok/amarokcollectionscanner /usr/bin

After this, my collection is full again.

[Anthony Mercatante (tonio)]

Thanks for this !
Looks like a packaging issue indeed.
I'll try to get a fixed package uploaded toonight

[Bruno (bruno666-666)]

Thanks a lot Anderson,

Your workaround perfectly works :-)

[Anthony Mercatante (tonio)]

Latest upload fixes the issue