Version: 2.0.96 (using 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 125", KDE:KDE4:Factory:Desktop / openSUSE_11.1) Compiler: gcc OS: Linux (x86_64) release 2.6.27.21-0.1-default Amarok imports collection (can be seen in teh status message at the bottom), but the collection never shows. The message that Amarok shows in the collection window is the "Local Collection" icon with a "counting" message underneath. Let is run overnight, still no collection. If files are dragged from the "Files" window to the playlist they play just fine.
I have same problem with identical versions of Amarok and KDE, but in 32-bit openSUSE 11.1.
Same problem here, during the "Calculating" there is no higher CPU usage, hard disk LED also doesn't blink, but there is a problem with mysql when I run it with --debug flag: amarok: BEGIN: ScanManager::ScanManager(SqlCollection*) amarok: END__: ScanManager::ScanManager(SqlCollection*) - Took 9.5e-05s amarok: [ERROR!] MySQL library initialization failed. amarok: [ERROR!] GREPME MySQLe query failed! mysql_embedded: unknown option '--loose-skip-innodb' on "init" amarok: [PluginManager] Trying to load: "libamarok_collection-daapcollection" amarok: [PluginManager] Using amarok 2.1-SVN, KDE 4.2.3
This debug output strongly indicates a packaging problem: Apparently the MySQL version on your system is unsuitable for Amarok. Please report this problem to SUSE directly. They might be able to fix the packaging in an update.
It was not so much that the MySQL version is unsuitable, it was that Amarok during install does not check whether MySQL is installed at all (still a packaging issue). Manually installing MySQL solved the problem.
Hum, that's a bit frustrating to hear, as SUSE has had this missing dependency problem for ages... I had thought they'd fixed it by now :(
In my case I compiled Amarok with mysql from svn and probably later ubuntu updater overwrited mysql. But I believe it's still Amarok problem also, before "Counting" it should display "Connecting to db..." or after error "DB Error" or "MySQL error".
Hi all, I am facing the same problem with Amarok 2.1. I can't really tell if this is an OpenSuse or an Amarok issue, but I don't get why this bug is marked as "RESOLVED". Anyway, if I run Amarok with --debug, I get many MYSQLe erros, such as this one: amarok: BEGIN: void DatabaseUpdater::createTemporaryTables() amarok: [ERROR!] Tried to perform query on uninitialized MySQLe amarok: [ERROR!] Tried to perform query on uninitialized MySQLe amarok: [ERROR!] Tried to perform query on uninitialized MySQLe Tried to perform query on uninitialized MySQLe amarok: [ERROR!] Tried to perform escape() on uninitialized MySQLe amarok: [ERROR!] Tried to perform insert on uninitialized MySQLe amarok: [ERROR!] Tried to perform escape() on uninitialized MySQLe
Sorry, I've just figured out that I was missing the "mysql" package. I've just retrived the mysql-5.0.67-12.15 package from OpenSuse and now Amarok is OK
I ran into the same issue two days ago. Amarok should really show an error message when mysql is not available. If it doesn't, most of the UI will simply "not work" which is extremely annoying.
(In reply to comment #9) > I ran into the same issue two days ago. Amarok should really show an error > message when mysql is not available. If it doesn't, most of the UI will simply > "not work" which is extremely annoying. Aaron, please check with your distribution, Amarok needs an embedded mysqle, the dependencies are clearly documented and if the distribution does not package this correctly, we can do nothing about it.
You can show an error instead of starting a half-lived version. But I'm also reporting an error ... at least I'll try but the package comes from the openSUSE build service (i.e. an half-official source) and I have to report it by mail to someone I found in the changelog :(
I have been experiencing the same problem for months (openSUSE factory) Is it possible that openSUSE has been shipping an dysfunctional combination of Amarok / MySQL for such a long time? Is the bug already reported in openSUSE?
For all those openSUSE users who can't get rid of this bug despite installing all possible mySQL-Packages: I could only solve this problem by installing the package amarok-2.1.60git20090813-3.1 from some community repo. Suddenly everything seems to work.