Registered Member
|
LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:lsb-2.0-amd64:lsb-2.0-noarch:lsb-3.0-amd64:lsb-3.0-noarch:lsb-3.1-amd64:lsb-3.1-noarch:lsb-3.2-amd64:lsb-3.2-noarch:lsb-4.0-amd64:lsb-4.0-noarch:lsb-4.1-amd64:lsb-4.1-noarch
Distributor ID: Mageia Description: Mageia 1 Release: 1 Codename: frites In my system amarok does not index the folders of music in spite of indications - the indexing process starts, but consumes the entire memory resources |
KDE CWG
|
It sounds as if you might have some missing MySql packages, which are used for the database internally. Also required is libmysqld compiled with fPIC. I'm not sure what they would be called in Mageia - you might ask your packagers.
Also, you might try running amarokcollectionscanner from the console, when Amarok isn't running, and see what sort of output you get. http://amarok.kde.org/wiki/Batch_Mode for more details. |
Registered Member
|
|
KDE CWG
|
Piotrekw1, what files were you lacking? I ask so that others searching the forum might find the answer they need. Also, please tip off your Mageia packagers to fix up the package.
Thanks! PS: Also, please click the green checkmark, to mark the problem as solved. |
Registered Member
|
|
Registered Member
|
Don't think, that the problem was caused by missing MySQL workbench application. This app has nothing, but really nothing to do with amarok. Probably there were missing packages installed, because of dependancies.
m0nk
If men could get pregnant, abortion would be a sacrament.
|
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot]