I had a strange problem where I tried to uninstall a version of amarok I built from GIT and install the current amarok from debian testing. Then I got that dreaded error message about collection plugins missing.
I could not figure out how to get rid of the message except by git pull to the current master and building again from source. Then I tried running it. I got that dreaded message *again* about collection plugins missing. it told me to run kbuildsycoca --nonincremental but I forgot to do it and just ran amarok again. Second time running it, it worked! And further, I should say, today's amarok 2.4-git is very nice, many other annoying bugs are gone! On Fri, Jan 15, 2010 at 8:10 AM, Martin Steigerwald <mar...@lichtvoll.de> wrote: > Am Freitag 15 Januar 2010 schrieb Mark Kretschmann: >> On Fri, Jan 15, 2010 at 12:36 PM, Martin Steigerwald >> >> <mar...@lichtvoll.de> wrote: >> > Am Freitag 15 Januar 2010 schrieb Jeff Mitchell: >> >> On 01/15/2010 05:56 AM, Martin Steigerwald wrote: >> >> > A kbuildsycoca4 --noincremental *after* installing Amarok 2.2.2 >> >> > then did the trick. The one I ran before upgrading Amarok did not. >> >> >> >> Well, right. Because the plugin versions changed. Running a >> >> kbuildsycoca with the old plugin versions installed isn't going to >> >> update the cache with the new plugin version information... >> >> >> >> > IMHO manually this shouldn't be necessary. >> >> >> >> I'm not sure when it's supposed to kick off manually or not. I do >> >> believe it's run on login, so a logout/in should probably have fixed >> >> it. >> >> >> >> I know on Gentoo at least they tried for a while to run >> >> kbuildsycoca4 after ebuild installation, but I guess it requires a >> >> running X server for some reason so they aborted that. (Maybe *that* >> >> would be something good to ask about in an upstream bug report.) >> > >> > Hmmm, I am not so sure it does. At least it runs via SSH from my T42 >> > to my T23 without DISPLAY=:0. >> > >> > So it would be a good idea if the package post-install runs >> > kbuildsycoca4 --noincremental? But how to reliably detect for which >> > users? Well if its run after a login it would need to run it for each >> > logged in KDE user. >> >> Normally, this happens automatically. Not sure what went wrong there >> on your system. > > Ok, thanks for information. I probably could reproduce it as long as > rdiff-backup carries Amarok 2.2.1 files, but as long as it just happened > for one user and one machine its probably not worth the effort. Tell me > whether you would be interested in that. > > Otherwise let's see how it goes with Amarok 2.2.3 then. ;-) > > Amarok 2.2.2 is working fine so far. Thanks for the update ;). > > -- > Martin 'Helios' Steigerwald - http://www.Lichtvoll.de > GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 > > _______________________________________________ > Amarok mailing list > Amarok@kde.org > https://mail.kde.org/mailman/listinfo/amarok > > _______________________________________________ Amarok mailing list Amarok@kde.org https://mail.kde.org/mailman/listinfo/amarok
