Description of problem: Since version 3.11 of sqlite the custom tokenizers are disabled by default. see https://www.sqlite.org/fts3.html#section_8_1 Because of security concerns, SQLite version 3.11.0 only enabled the second form of the fts3_tokenizer() function when the library is compiled with the -DSQLITE_ENABLE_FTS3_TOKENIZER option. In earlier versions it was always available. This breaks the first start of geary after installation. Version-Release number of selected component (if applicable): 3.11 How reproducible: every time every start of geary Steps to Reproduce: 1. Install a fresh and updated fedora 24 2. Install geary (dnf install geary) 3. Start geary and setup a valid email account Actual results: geary gives an network error and terminates Expected results: Geary starts with my mailbox working Additional info: Resolved by recompiling sqlite with the buildflag '-DSQLITE_ENABLE_FTS3_TOKENIZER'
This is important because it prevents Geary users from adding new accounts, and hence breaks Geary for both new and existing users. It's effectively a regression in SQLite since this functionality was working fine in SQLite 3.10 and earlier, and it's difficult for the user to fix since it's a build-only option. As a result most other distros have already added `-DSQLITE_ENABLE_FTS3_TOKENIZER` to their package builds to fix this. To rectify this issue, SQLite 3.12 allows enabling of the two-arg version of fts3_tokenizer() at runtime via the C API, and Geary master will do this if SQLite 3.12 is detected at built time. So to unbreak Geary in Fedora 24, either this build flag needs to be set, or SQLite upgraded to 3.12 and Geary upgraded 0.11 (due to be released this weekend).
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.