Hello,

I'm trying Skrooge under a new install of Fedora 26. ('New' meaning fresh install with updates applied and system restarted.) First some background:

a) At site https://skrooge.org/download we are advised "The recommended way is to install Skrooge using your distribution's package management tool."
b) Following this direction, used dnf to install skrooge under Fedora 26.
c) Skrooge.org lists Latest Stable Version of skrooge-2.8.1
d) Version installed via dnf is skrooge-2.4.0-3
e) Launching Skrooge results in this message:
"This application can not (sic) run correctly because the SQLite version of the system (3.16.2) is not aligned with the SQLite version embedded in Qt (3.19.3). You should rebuild Qt with the option -system-sqlite."

Now the questions:
1) Given that install via package management tool dnf wasn't successful out of the box, shall I remove it and download and build version latest stable 2.8.1 from Skrooge.org?
2) If not, how would one go about rebuilding Qt?
3) If I rebuild Qt in this way, may it break other things on my system?
4) Would it be wiser to just wait a few weeks, until whomever is managing the Fedora repos gets the versions of SQLite better matched?

Please advise. Primarily interested in replies from people who have solved this under Fedora 26 or who have run into similar issues in the past. Thanks!

Hi,
I speak as main developer of Skrooge

Pineapple wrote:Hello,

I'm trying Skrooge under a new install of Fedora 26. ('New' meaning fresh install with updates applied and system restarted.) First some background:

a) At site https://skrooge.org/download we are advised "The recommended way is to install Skrooge using your distribution's package management tool."
b) Following this direction, used dnf to install skrooge under Fedora 26.
c) Skrooge.org lists Latest Stable Version of skrooge-2.8.1
d) Version installed via dnf is skrooge-2.4.0-3
e) Launching Skrooge results in this message:
"This application can not (sic) run correctly because the SQLite version of the system (3.16.2) is not aligned with the SQLite version embedded in Qt (3.19.3). You should rebuild Qt with the option -system-sqlite."

It means that your version of Qt has an embedded version of sqlite and this version of sqlite is not aligned with the sqlite of your system.
This is strange because most of the time Qt is built with the option to use the system sqlite.

Pineapple wrote:Now the questions:
1) Given that install via package management tool dnf wasn't successful out of the box, shall I remove it and download and build version latest stable 2.8.1 from Skrooge.org?

You can do that if you are skills to build applications.

Pineapple wrote:2) If not, how would one go about rebuilding Qt?

Not a good idea.

Pineapple wrote:3) If I rebuild Qt in this way, may it break other things on my system?

That's why this is not a good idea. Skrooge is easier to build than Qt, and not risky.

Pineapple wrote:4) Would it be wiser to just wait a few weeks, until whomever is managing the Fedora repos gets the versions of SQLite better matched?

Could be but I don't know Fedora packaging, so not sure.
You can may be open an incident for Fedora Packager to package the last version (2.8.1).

Pineapple wrote:
Please advise. Primarily interested in replies from people who have solved this under Fedora 26 or who have run into similar issues in the past. Thanks!

I plan to open an incident with the Fedora Packager. Thanks for the informative reply!

This bug has been resolved and the solution has been pushed to the repo for Fedora 26 stable. Those interested may view details here:

a) Bugzilla bug detail
https://bugzilla.redhat.com/show_bug.cgi?id=1475629

b) Bodhi update detail
https://bodhi.fedoraproject.org/updates ... 4161fb8236

Thanks to all involved parties!

This problem cropped up again after a Fedora kernel update on August 15th. The packager could use your input on whether or not to add sqlite as an explicit dependency for skrooge. See the last few messages here for detail:

https://bugzilla.redhat.com/show_bug.cgi?id=1475629

Please let us know. Thanks!

Hi,

Just to clarify:
1- Skrooge uses QSql API and sqlite API. So, the sqlite version used through Qt ans the sqite version of the system must be aligned.
2- So, Skrooge compares the sqlite version of Qt (retrieved by SQL) with SQLITE_VERSION (#define in sqlite3.h).

Because SQLITE_VERSION is a #define, Skrooge compares the current sqlite version of Qt with the sqlite version used at build time.
If you change the version of Sqlite, you need to rebuild Skrooge else you will have the error.

I can solve this by comparing current sqlite version of Qt with sqlite3_libversion() (runtime version)
Do you think this will solve your issue?

Regards.

Thanks for the quick response! That's an excellent suggestion. I've shared it with the Fedora packager for their input. (Their other idea is to enforce an sqlite dependency.) Will let you know their feedback.

I haven't received a reply from the packager on that yet. However, I wanted to go ahead and mention another issue with Skrooge on Fedora 26.

The trouble is that I've another computer here running Ubuntu 17.04 with Skrooge. On Ubuntu 17.04, the Skrooge version used with the distro is Skrooge-2.7.0-1. On Fedora 26, the Skrooge version distributed with that distro is Skrooge-2.4.0-4. This is all peachy until you try to enter accounts and transactions on Skrooge 2.7.0, save, and then later open on Skrooge 2.4.0 under Fedora.

This results in the following message:
"[ERR-14]: Oups, (sic) this file seems to be corrupted"

It offers to attempt recovery and fails:
"[ERR-5]: Impossible to recover this file"

However, the file is fine. If we open it under Skrooge 2.7.0 under Ubuntu, everything is there and intact.

This answers a question and raises a question. The question answered is whether modifying the sqlite check with solve the problem in Fedora. The trouble is that the Skrooge version distributed with Fedora is so old that anything the developers modify in the current version isn't going to help Fedora users for a long while. This means that the Fedora packagers should go ahead with adding an sqlite dependency for their bug fix.

The question raised is why is Fedora distributing such an old version of Skrooge? That seems odd. Usually inter-operation with applications (e.g. Libreoffice, Thunderbird, etc.) doesn't present an issue as the versions distributed with Ubuntu latest and Fedora are similar.

Hi,

Just for information:

• Skrooge 2.4.0 has been published in May 2016.
• Skrooge 2.7.0 has been published in Jan 2017. This version contains a very important correction forcing to use sqlcypher instead of sqlite. That's why you have the error message when you try to use a document saved in 2.7.0 with 2.4.0.
• The last version is the 2.9.0 published in Aug 2017.
• Due to changes in data model, most of the time, it's not possible to open a Skooge document with an older version of Skrooge.

To be clear with you, I don't understand why Fedora is still on a so old version containing important security hole (corrected on 2.7.0).
My advice is to package the last version 2.9.0.

Concerning the issue with the sqlite (or sqlcypher) version, I think my proposal will solve the issue. The patch is very simple and could be applied on all version of Skrooge >= 2.7.0.

Regards.

Yes, I agree that your fix sounds best. I'll work to convince Fedora packagers to include the latest Skrooge 2.9.0. If that fails, I'll try to encourage them to at least upgrade to Skrooge 2.7.0. Many thanks for the quick and helpful replies.

The packagers are busy now: working on Fedora 27. I'm pleased to report, though, that the branch that'll become Fedora 27 appears to utilize Skrooge 2.8.1. Fedora 27 is anticipated to ship in late October.

The development version of Fedora--aka Rawhide--is currently experimenting with Skrooge 2.9.0. They're having build problems with it but are working to fix. If successful, Skrooge 2.9.0 (or newer) would become part of Fedora 28.

Hopefully this information is of some use. Thanks again for your advice and guidance!