Running amarok-1.4-beta1 using KDE 3.4.2 level \"b\" on SuSE 10.0. This machine used to be SuSE 9.3 and I upgraded, rather than reinstalled it. After that upgrade, amarok hasn\'t worked, refusing to allow anything to be put into the playlist. Recently, I ran a series of upgrades and a dist-upgrade (I use apt at the moment). I had hopes that my amarok troubles would be alleviated. No such luck.

On application start (I ran it from a terminal to catch whatever output there was), amarok seems to start OK, but there are a couple warmings and one error:

:~> amarok
amaroK: [Loader] Starting amarokapp..
amaroK: [Loader] Don\'t run gdb, valgrind, etc. against this binary! Use amarokapp.
kdecore (KAction): WARNING: KActionCollection::KActionCollection( QObject *parent, const char *name, KInstance *instance )
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
QPainter::begin: Cannot paint null pixmap

When the app does open, it begins a collection scan immediately. The progress indicator, however, stopes at 1%. A moment of two later, a dialog box opens indicating a Collection Scan error:

Sorry, the Collection Scan was aborted, since too many problems were encountered. The following files caused problems:

It then lists over a dozen files in the MP3 directory. Any attempt to add a file to the active playlist, or just \"Play File\", fails. It doesn\'t generate any other errors in the terminal window.

There is one other piece of information that is probably relevant: attempts to play music files with XMMS fail as well, for the same reason. It yields no error, but the application refuses to allow any file to be added to the playlist.

Any suggestions? I apologize for not including a trace, but I\'m kind of a noob in this type of troubleshooting. If there\'s a good man page, Wiki, or something that will guide me through getting the data, I can get that.

Additional information:

When attempting manually add a song to the playlist, the terminal output contains this:

:~> Very strange! got a DCOPReplyWait opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyDelayed opcode, but we were not waiting for a reply!

Yet more information:

I forgot to mention I\'m using the sqlite engine. I wanted to check what version, so I ran across what may be a problem:

:~> rpm -qa | grep sqlite
sqlite-3.2.2-5
sqlite2-2.8.16-5

Shouldn\'t I only need one?