Summary: | Collection remains empty while scanning does seem to work (collection.db stays empty) | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Rutger Claes <rgc> |
Component: | general | Assignee: | 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
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 . http://www.sqlite.org/cvstrac/tktview?tn=1272 points out that this is an amarok bug, not a sqlite3 bug. And it's fixed for 1.4. On 1.3, use internal, it won't be fixed, as it requires too deep changes. |