New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clementine not start #47
Comments
In Octopi go to Tools > SysInfo and paste the returned link here please. |
ok, this is |
I can finally reproduce (in live mode), so no more info needed from you at this time, will keep you posted here at what I find. |
@hefistion |
Issue found, it is new sqlite, no longer having tokenizer support. A rebuild sqlite 3.11 with tokenizer support will be in the [build] repo shortly |
thank you very much, now works fine |
Unconditionally re-enabling support for custom FTS3/FTS4 tokenizers reintroduces security vulnerability which was worked around by SQLite upstream by disabling this feature: From documentation of SQLite: SECURITY WARNING: If a version of the fts3/4 extension that supports the two-argument form of fts3_tokenizer() is deployed in an environment where malicious users can run arbitrary SQL, then those users should be prevented from invoking the two-argument fts3_tokenizer() function. This can be done using the authorization callback, or by disabling the two-argument fts3_tokenizer() interface using a call to sqlite3_db_config(db,SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER,0,0)." SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER was backported in Gentoo to SQLite 3.11: I added potential patch for Clementine in clementine-player/Clementine#5297. |
Thanks for looking into this. It was known why SQlite disabled toknizer support, but no fix could be found up to now for Clementine. |
Fixed with SQLite 3.12.0 and patched Clementine https://github.com/KaOSx/apps/blob/master/clementine/tokenizer.diff |
Clementine not start and this the message from konsole:
I have new binutils and mariadb packages
[carlos@Acer-E5 ~]$ pacman -Q binutils binutils 2.26-2
a window appears with a tab Developer Information
The text was updated successfully, but these errors were encountered: