SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm leaving this here mostly as an info in case anyone else has the problem, because I am aware that it's possible the currently released version doesn't have the problem that I had with git version.
Had to recompile sqlite 3.20.0 with -DSQLITE_ENABLE_FTS3_TOKENIZER=1 for Clementine to correctly update the music database and stard, otherwise it was dying with "Unable to update music library database".
I'm leaving this here mostly as an info in case anyone else has the problem, because I am aware that it's possible the currently released version doesn't have the problem that I had with git version.
Had to recompile sqlite 3.20.0 with -DSQLITE_ENABLE_FTS3_TOKENIZER=1 for Clementine to correctly update the music database and stard, otherwise it was dying with "Unable to update music library database".
this is the wrong way of fixing it
file a bug report at Clementine
there is a reason why the fts3 tokenizer interface became disabled,
Code:
SQLITE_ENABLE_FTS3_TOKENIZER
This option enables the two-argument version of the fts3_tokenizer() interface. The second argument to fts3_tokenizer() is suppose to be a pointer to a function (encoded as a BLOB) that implements an application defined tokenizer. If hostile actors are able to run the two-argument version of fts3_tokenizer() with an arbitrary second argument, they could use crash or take control of the process.
Because of security concerns, the two-argument fts3_tokenizer() feature was disabled beginning with Version 3.11.0 (2016-02-15) unless this compile-time option is used. Version 3.12.0 (2016-03-29) added the sqlite3_db_config(db,SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER,1,0) interface that activates the two-argument version of fts3_tokenizer() for a specific database connection at run-time.
Clementine had already 18 month to update their code, maybe nobody told them about this? you should point them to the correct solution,
this is, query the version of sqlite at application start up, if it is older than ... enabling this option explicit per connection as stated in the documentation
Hey guys, sorry! I didn't write for making a request for -current or for filing a bug!
I just wrote what I did for making things work in case someone else had the same problem.
Wasn't aware that the option had been deprecated on purpose, and the info didn't come out during the investigation I did.
I just found a thread saying that the error comes out because the option is not enabled in sqlite, and so I enabled it.
Hey guys, sorry! I didn't write for making a request for -current or for filing a bug!
I just wrote what I did for making things work in case someone else had the same problem.
Wasn't aware that the option had been deprecated on purpose, and the info didn't come out during the investigation I did.
I just found a thread saying that the error comes out because the option is not enabled in sqlite, and so I enabled it.
My apology for not realizing the situation.
From my own personal experience I don't think people like unasked for solutions to random software building issues posted concerning current outside the current slackbuilds thread on here. Its best to keep the solutions to ourselves or in that thread. There needs to be a disclaimer somewhere.
I personally think it was nice of you to offer a way to build the software in case someone finds it useful. I prefer Quod Libet but nightingale was my favorite.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.