| Summary: | collectiondb infinite loop on start | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Michael Buesch <mb> |
| Component: | general | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | spam |
| Priority: | NOR | ||
| Version First Reported In: | 1.4.2 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Michael Buesch
2006-08-27 14:32:02 UTC
Looks like your sqlite database isn't correctly built. Have you at any point tried to downgrade Amarok? This generally messes the database up. Anyway, the fix should be simple: rm ~/.kde/share/apps/amarok/collection.db I downgraded it _after_ the issue appeared.
So that's not the cause.
> Anyway, the fix should be simple: rm ~/.kde/share/apps/amarok/collection.db
As I wrote. This does not help.
I deleted everything in ~/.kde/share/apps/amarok and also
~/.kde/share/config/amarokrc
SVN commit 577765 by mkossick:
make sure that we don't access uninitialised variables
BUG: 133072
M +6 -2 collectiondb.cpp
--- trunk/extragear/multimedia/amarok/src/collectiondb.cpp #577764:577765
@@ -5761,7 +5761,8 @@
{
QStringList values;
- int error, rc;
+ int error;
+ int rc = 0;
const char* tail;
sqlite3_stmt* stmt;
int busyCnt = 0;
@@ -5787,6 +5788,7 @@
Debug::error() << sqlite3_errmsg( m_db ) << endl;
Debug::error() << "on query: " << statement << endl;
values = QStringList();
+ break;
}
else
{
@@ -5851,7 +5853,8 @@
int SqliteConnection::insert( const QString& statement, const QString& /* table */ )
{
- int error, rc;
+ int error;
+ int rc = 0;
const char* tail;
sqlite3_stmt* stmt;
int busyCnt = 0;
@@ -5876,6 +5879,7 @@
Debug::error() << k_funcinfo << " sqlite3_compile error:" << endl;
Debug::error() << sqlite3_errmsg( m_db ) << endl;
Debug::error() << "on insert: " << statement << endl;
+ break;
}
else
{
This fixes the issue. Thank you very much! *** Bug 133450 has been marked as a duplicate of this bug. *** |