Hi, Just compiled and installed the latest amarok. Installation went smoothly. However, when I tried to run it, I saw a popup with a progress bar that kept resetting. After 10-15 minutes, I cancelled it and got an error box with the following text (the text was in Polish, below there's my translation): Amarok couldn't find the plugin collection. Probably it has been installed with a wrong prefix, please fix your installation by executing: $ cd /path/to/source/code/of/amarok $ su -c "make uninstall" $ cmake -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` && su -c "make install" $ kbuildsycoca4 --noincremental $ amarok More information can be found in README file. To get more help, join #amarok on irc.freenod.net. I guess I've got all the information I need from this message, but I suppose it's not correct, so I decided to report it. As I can't use amarok at all now, I set the priority to critical. Reproducible: Always
$ amarok --debug amarok: BEGIN: App::App() amarok: BEGIN: void App::continueInit() amarok: BEGIN: EngineController::EngineController() amarok: END__: EngineController::EngineController() [Took: 0s] amarok: BEGIN: void EngineController::initializePhonon() amarok: [EngineController] Tick Interval (actual): 100 amarok: END__: void EngineController::initializePhonon() [Took: 0.43s] amarok: BEGIN: MainWindow::MainWindow() amarok: BEGIN: void CollectionManager::init() amarok: [PluginManager] Plugin trader constraint: "[X-KDE-Amarok-framework-version] == 60 and [X-KDE-Amarok-plugintype] == 'collection' and [X-KDE-Amarok-rank] > 0" amarok: [CollectionManager] Received [ "0" ] collection plugin offers amarok: [CollectionManager] No Amarok plugins found, running kbuildsycoca4. amarok: BEGIN: virtual int App::newInstance() amarok: BEGIN: static void App::handleCliArgs() amarok: END__: static void App::handleCliArgs() [Took: 0s] amarok: END__: virtual int App::newInstance() [Took: 0s]
Well, after upgrading all of KDE 4.5.5 and restarting the machine, it started working all of sudden. You guys decide if it makes the bug report invalid or not :)
Well since it works now we can't do much I guess
