FS#60989 - sqlcipher 4.0.0-1 stops skrooge 2.16.2-1 being able to open non-password protected files.

Attached to Project: Community Packages
Opened by Mark Clegg (mclegg) - Thursday, 06 December 2018, 18:06 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Thursday, 20 December 2018, 19:46 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jaroslav Lichtblau (Dragonlord)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
sqlcipher upgrade breaks skrooge

With sqlcipher-4.0.0-1, skrooge-2.16.2-1 is unable to open existing data files, complaining that they must be password protected, when in fact they are not. This suggests the data file is corrupt but this is not the case.

Downgrading sqlcipher back to 3.4.2-1 restores the expected functionality allowing the files to be opened.

Additional info:
* skrooge 2.16.2-1
* sqlcipher 4.0.0-1 / 3.4.2-1


Steps to reproduce:
Install skrooge-2.16.2-1 and sqlcipher-4.0.0-1 (current versions at time of posting).
Open an existing non-password protected data file. A password is requested.
Downgrade sqlcipher back to 3.4.2-1 and the file can now be opened normally.
This task depends upon

Closed by  Jaroslav Lichtblau (Dragonlord)
Thursday, 20 December 2018, 19:46 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in skrooge-2.17.0-2
Comment by Antonio Rojas (arojas) - Saturday, 08 December 2018, 08:41 GMT
https://cgit.kde.org/skrooge.git/commit/?id=c66fb6b2e49cfa9e3fc8144408cfa7bf3d7e3988
https://cgit.kde.org/skrooge.git/commit/?id=42dfd616606e6c5e20d0c107ac4a0780570cb196
Comment by Jaroslav Lichtblau (Dragonlord) - Monday, 10 December 2018, 18:39 GMT
skrooge-2.16.2-3 in community-testing now, does that one improve the situation?
Comment by Mark Clegg (mclegg) - Monday, 10 December 2018, 19:23 GMT
Downloaded and installed from community-testing, sorry, no difference. Still need to downgrade sqlcipher to 3.4.2-1 to open files.
Comment by Bennett Piater (ClawOfLight) - Monday, 10 December 2018, 19:40 GMT
I can confirm 2.16.2-3 in community-testing doesn't fix this.
Comment by Christoph Vogtländer (gordin) - Monday, 10 December 2018, 19:49 GMT
I tried to test this. The version I see in community-testing is skrooge-2.16.2-2.
This version of skrooge in community-testing is linked against Qt 5.12 which does not seem to be available in neither community-testing nor testing (tried to update "qt5-base").

How do I get skrooge-2.16.2-3?
Comment by Mark Clegg (mclegg) - Monday, 10 December 2018, 20:31 GMT
@Christoph: Wait for testing to replicate to the mirrors, or download from here... https://www.archlinux.org/packages/community-testing/x86_64/skrooge/ and install using: pacman -U skrooge-2.16.2-3-x86_64.pkg.tar.xz
Comment by Christoph Vogtländer (gordin) - Monday, 10 December 2018, 20:31 GMT
Nevermind, my mirrorlist was out of date
Comment by Christoph Vogtländer (gordin) - Monday, 10 December 2018, 20:36 GMT
I can also confirm that 2.16.2-3 in community-testing doesn't fix this
Comment by Jaroslav Lichtblau (Dragonlord) - Monday, 17 December 2018, 19:58 GMT
So, new version, new try.
skrooge-2.17.0-1 in community-testing
Comment by Mark Clegg (mclegg) - Monday, 17 December 2018, 20:08 GMT
Sorry - still the same :-( Prompted for password where no password set.
Comment by Jaroslav Lichtblau (Dragonlord) - Monday, 17 December 2018, 20:48 GMT
Hm, sorry to hear :(
Might make sense to open an extra upstream bug with the errors received then.
The two patches included in the previous and current build seem not to have any impact on resolution of this issue.
Comment by Christoph Vogtländer (gordin) - Monday, 17 December 2018, 23:21 GMT
I will reopen https://bugs.kde.org/show_bug.cgi?id=401878
Comment by Christoph Vogtländer (gordin) - Thursday, 20 December 2018, 12:10 GMT
Upstream found a possible solution.

@Jaroslav Lichtblau: would you be able to create a new test build including https://cgit.kde.org/skrooge.git/commit/?id=b370575abe8d80b90e4552f1c027c9b58947a9f1
Comment by Jaroslav Lichtblau (Dragonlord) - Thursday, 20 December 2018, 17:52 GMT
skrooge-2.17.0-2 in community-testing repo
sqlcipher was also updated to v4.0.1
Comment by Christoph Vogtländer (gordin) - Thursday, 20 December 2018, 18:27 GMT
I can confirm that skrooge-2.17.0-2 works and is able to open the old files. Thank you.
Comment by Mark Clegg (mclegg) - Thursday, 20 December 2018, 18:42 GMT
I also can confirm 2.17.0.2 works with sqlcipher 4.
Many thanks.
Comment by Jaroslav Lichtblau (Dragonlord) - Thursday, 20 December 2018, 19:45 GMT
Awesome, thanks for the quick confirmation. Glad it works again.
Cheers!

Loading...