On Tuesday 17 November 2009 18:52:00 Alex Schuster wrote: > Alan McKinnon writes: > > On Monday 16 November 2009 21:40:42 Alex Schuster wrote: > > > Alan McKinnon writes: > > > > I get errors like this whenever amarok updates the collection: > > > > > > > > amarok: [ERROR!] GREPME MySQL query failed! No database > > > > selected on "INSERT INTO images SELECT * FROM images_temp;" > > > > > > Not here. Sometimes the collection gets screwed up a little, but I do > > > not get any output when re-scanning the collection. > > It just happened again. I added a new folder to my /data/mp3 hierarchy > (metal), put some folders of music into it, marked it as collection folder > and told amarok to re-scan the collection. When I search for 'metallica', > it finds 'Rapoon'. When I drag a metallica album folder directly into > amarok, it shows the album's name correctly, but the artist is 'Rapoon'. > > I unmarked all of my collection's folders, let amarok re-scan, and now the > collection is empty. I added all the folders again, scanned, and I have > the same problem. > > I deleted ~/.kde4/share/apps/amarok/mysqle, started amarok and let it > scan, now all is fine again. Seems I have to do this once in a while.
To me, that is intolerable on production code with a version number of 2.2.0. It' supposed to be mature, it's not supposed to trash it's own data store! What o you think would happen if Firefox dumped it's browser history and cookies once a week in sync with phases of the moon? If any vendor tried to sell me crap code like that at work, they would be out the door on their arse [snip] > > Amarok, it was nice knowing you. One day you might build and play music > > again on all sane systems out there. Meanwhile, I think I want to hear > > songs play so some other player is going on this machine and you are > > coming off. > > What about using amarok 1.4, until 2.x works fine for you? 1.4 links to kdelibs-3.5 right? I just spent nearly a year getting rid of 3.5 apps... > Mine does not work any longer, though. Just noted this when I started it > to compare with the 2.2 one, did not do this a while ago. > /usr/kde/3.5/bin/amarok immediately throws an 'illegal instruction' error. > Huh? I did not change my CFLAGS, they are "-march=k8-sse3 -mfpmath=sse -O2 > -pipe -fomit-frame-pointer" on a AMD Athlon 4850e. The k8-sse3 should be > sane, gcc -Q --help=target -march=native lists it. I am not sure where I > got the -mfpmath=sse from. I rebuilt amarok 1.4, and get the same error, > probably somewhere in kdelibs or such stuff. Strange. Let's see if this > happens with other stuff, too. that looks like you built amarok with binutils-2.20. It affects many apps. Try downgrade binutils, rebuild offending apps and see if it makes a difference. Or you could try rebuild current binutils with USE=gold. I have no idea what it does, but there's a few references on b.g.o. about this working in some cases. -- alan dot mckinnon at gmail dot com
