In one sense, fixing the bug is easy: if the query fails in BaseSqlTableModel::select(), it shouldn't try to use the results, i.e. there should be a "return;" or something after line 206 (relative to the current 1.11 branch).
However, the database shouldn't be locked during library-rescan to the point where higher-priority functions, like user interaction, get blocked. Fixing that is undoubtedly more work, and I only recently started hacking the code, so don't expect much out of me very soon...but I'm keen to try :-)
This looks like a duplicate of bug #870128 to me, i.e. https:/ /bugs.launchpad .net/mixxx/ +bug/870128 .
In one sense, fixing the bug is easy: if the query fails in BaseSqlTableMod el::select( ), it shouldn't try to use the results, i.e. there should be a "return;" or something after line 206 (relative to the current 1.11 branch).
However, the database shouldn't be locked during library-rescan to the point where higher-priority functions, like user interaction, get blocked. Fixing that is undoubtedly more work, and I only recently started hacking the code, so don't expect much out of me very soon...but I'm keen to try :-)