Bug 112110

Summary: Collection remains empty while scanning does seem to work (collection.db stays empty)
Product: [Applications] amarok Reporter: Rutger Claes <rgc>
Component: generalAssignee: Amarok Developers <amarok-bugs-dist>
Status: RESOLVED NOT A BUG    
Severity: major CC: mueller
Priority: NOR    
Version: 1.3   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Rutger Claes 2005-09-06 11:14:41 UTC
Version:           1.3 (using KDE 3.4.2, Debian Package 4:3.4.2-3 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.12c01

First of all, this problem started when I upgraded from KDE 3.3 to 3.4.2 using the official Debian unstable packages.  If this is a Debian unstable related problem, please let me know.

If I scan all of my collection, and I tail -f my .kde/share/apps/amarok/collection_scan.log I see all my mp3 files passing by.  When the scanning stops, there is an informative message in the collection_log.log file.
However, the collection tab remains completely empty.  I tried removing the entire collection.db file and tried again, same result.

I've queried the collection.db file using sqlite3 and this is the result:

rutger@nimbus:~/.kde/share/apps/amarok$ sqlite3 collection.db
SQLite version 3.2.5
Enter ".help" for instructions
sqlite> .tables
album            directories      related_artists  year
amazon           genre            statistics
artist           images           tags
sqlite> SELECT * FROM album;
sqlite> SELECT * FROM artist;
sqlite> SELECT * FROM genre;
sqlite> SELECT * FROM images;
sqlite> SELECT * FROM tags;
sqlite> SELECT * FROM directories;
sqlite> .quit

So it seems my database stays empty.  I've checked my amarok settings and the Sqlite backend is chosen, not the mysql one.

Using the left file tab and dragging a file from the filesystem to the playlist works.

    Thanks in advance,
        Rutger Claes
Comment 1 Alexandre Oliveira 2005-09-06 12:52:39 UTC
SQlite 3.2.5 doesn't allow access from different threads, something amaroK uses all the time. Just downgrade the SQlite package, or compile amaroK yourself, or wait for the fix, the debian guy was making another package.

You can read more about the SQLite issue here: http://www.sqlite.org/cvstrac/tktview?tn=1272 and http://www.sqlite.org/cvstrac/chngview?cn=2521 .
Comment 2 Dirk Mueller 2006-01-08 20:57:06 UTC
http://www.sqlite.org/cvstrac/tktview?tn=1272  points out that this is an amarok bug, not a sqlite3 bug. 

Comment 3 Alexandre Oliveira 2006-01-09 00:41:13 UTC
And it's fixed for 1.4.
On 1.3, use internal, it won't be fixed, as it requires too deep changes.