Comment 13 for bug 1190146

Hi Everyone, I added an option to compile, using libsqlite as a system shared library. That code is forked off upsteam above. The option itself, is --with-sqlite-source=system,packaged.

With that the lintian error for libsqilte is no longer present, but I did introduce a bug it seems. When compiled using the shared libsqlite option, on running, it starts up with the message
"Nightingale has detected that your Library is corrupt and cannot be read.........Your media files are safe and will not be deleted, but you'll need to rescan them"

Choosing the "Delete and Restart"option results in the same message.
* It is triggered when using the system shared libray, it works fine when reverting back to the packaged option like it is now.
*tested on Debian Sid, and Ubuntu 14.04. Same message.

Updated the pastebin http://pastebin.com/hwUtNuY1 with the latest GDB backtrace, I suspect it is triggering a thread race condition somewhere, looking into it, any pointers / tips?