Version: 1.4.2 (using KDE KDE 3.5.2) Installed from: Ubuntu Packages OS: Linux When using amarok 1.4.2-0ubuntu2~dapper1 (the official dapper-backports packages) or the latest packages from imbrandon.com (1.4.2-0ubuntu2), amarok does not start. Here is the output from amarok: $ amarok Amarok: [Loader] Starting amarokapp.. Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp. amarok: BEGIN: App::App() amarok: BEGIN: void App::fixHyperThreading() amarok: Workaround not enabled amarok: END__: void App::fixHyperThreading() - Took 0.0016s amarok: END__: App::App() - Took 0.012s amarok: BEGIN: void App::continueInit() amarok: BEGIN: EngineBase* EngineController::loadEngine(const QString&) amarok: [PluginManager] Plugin trader constraint: [X-KDE-Amarok-framework-version] == 26 and [X-KDE-Amarok-plugintype] == 'engine' and [X-KDE-Amarok-name] != 'void-engine' and [X-KDE-Amarok-rank] > 0 amarok: [PluginManager] Plugin trader constraint: [X-KDE-Amarok-framework-version] == 26 and [X-KDE-Amarok-plugintype] == 'engine' and [X-KDE-Amarok-name] == 'void-engine' and [X-KDE-Amarok-rank] > 0 amarok: [PluginManager] Trying to load: libamarok_void-engine_plugin amarok: amarok: PluginManager Service Info: amarok: --------------------------- amarok: name : <no engine> amarok: library : libamarok_void-engine_plugin amarok: desktopEntryPath : amarok_void-engine_plugin.desktop amarok: X-KDE-Amarok-plugintype : engine amarok: X-KDE-Amarok-name : void-engine amarok: X-KDE-Amarok-authors : (Max Howell,Mark Kretschmann) amarok: X-KDE-Amarok-rank : 1 amarok: X-KDE-Amarok-version : 1 amarok: X-KDE-Amarok-framework-version: 26 amarok: amarok: END__: EngineBase* EngineController::loadEngine(const QString&) - Took 0.13s amarok: BEGIN: CollectionDB::CollectionDB() amarok: BEGIN: void CollectionDB::initialize() amarok: [ThreadWeaver] Creating pthread key, exit value is 0 amarok: BEGIN: SqliteConnection::SqliteConnection(const SqliteConfig*) amarok: [CollectionDB] [WARNING!] Database versions incompatible. Removing and rebuilding database. amarok: END__: SqliteConnection::SqliteConnection(const SqliteConfig*) - Took 0.0027s amarok: [CollectionDB] [ERROR!] [virtual QStringList SqliteConnection::query(const QString&)] sqlite3_compile error: amarok: [CollectionDB] [ERROR!] no such table: tags amarok: [CollectionDB] [ERROR!] on query: SELECT COUNT( url ) FROM tags LIMIT 1 OFFSET 0; amarok: [CollectionDB] [ERROR!] [virtual QStringList SqliteConnection::query(const QString&)] sqlite3_compile error: amarok: [CollectionDB] [ERROR!] no such table: tags The following part is repeated infinitely: ********************************************** amarok: [CollectionDB] [ERROR!] on query: SELECT COUNT( url ) FROM tags LIMIT 1 OFFSET 0; amarok: [CollectionDB] [ERROR!] [virtual QStringList SqliteConnection::query(const QString&)] sqlite3_compile error: amarok: [CollectionDB] [ERROR!] no such table: tags ********************************************** The error persists even if the database or .kde/share/amarok and .kde/share/config/amarokrc are deleted (minues the "Database versions incompatible. Removing and rebuilding database." warning, of course). Killing amarok leaves a 0-byte collection.db behind. If amarok 1.3.9 is started first, then uninstalled, amarok 1.4.2 will report the same SQLerror with a different table name. The above bug prevents from starting amarok 1.4.2 on Kubuntu 6.06.1 LTS for PPC at all. Here is some more version information: $ dpkg -l | grep amarok ii amarok 1.4.2-0ubuntu2 versatile and easy to use audio player for K ii amarok-xine 1.4.2-0ubuntu2 xine engine for the amaroK audio player $ amarok --version Qt: 3.3.6 KDE: 3.5.2 Amarok: 1.4.2 $ dpkg -l | grep sqlite ii libsqlite0 2.8.17-0ubuntu1 SQLite shared library ii libsqlite3-0 3.2.8-1ubuntu1 SQLite 3 shared library ii python-sqlite 1.0.1-4ubuntu1 python interface to SQLite 2 ii python2.4-sqlite 1.0.1-4ubuntu1 python interface to SQLite 2 ii sqlite 2.8.17-0ubuntu1 command line interface for SQLite
*** This bug has been marked as a duplicate of 133072 ***
Adaran, 1.4.2-0ubuntu2 does not yet have patchset1. ubuntu3 will have it.