Bug 520749 - Skrooge can't load skg file after org.kde.Platform update
Summary: Skrooge can't load skg file after org.kde.Platform update
Status: RESOLVED FIXED
Alias: None
Product: skrooge
Classification: Applications
Component: general (other bugs)
Version First Reported In: Trunk from git
Platform: Flatpak Linux
: NOR major
Target Milestone: 25.1.0
Assignee: Stephane MANKOWSKI
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-05-28 06:07 UTC by skierpage
Modified: 2026-05-29 21:23 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description skierpage 2026-05-28 06:07:29 UTC
DESCRIPTION
Skrooge nightly (org.kde.skrooge//master) and from Flathub (org.kde.skrooge//stable) would not open my .skg file. When I entered the correct password it would report error.

The problem went away when I downgraded the KDE runtime org.kde.Platform from "build of org.kde.Sdk, Fri May 22" (as reported by `flatpak info org.kde.Platform/x86_64/6.10` to a previous version, "build of org.kde.Sdk, Thu Apr  2".

This matches complaints on discuss.kde.org at https://discuss.kde.org/t/skrooge-flatpak-2-6-1-20-database-errors-on-debian-13-trixie-cannot-open-create-files/44187 though they started in February.

STEPS TO REPRODUCE
1. flatpak update
2. flatpak run org.kde.skrooge//master path/to/my.skg

OBSERVED RESULT
Doesn't accept my password.
Terminal shows
```
##WARNING: QSqlDatabase: can not load requested driver 'SKGSQLCIPHER', available drivers: SKGSQLCIPHER QSQLITE
##WARNING: QSqlDatabase: can not load requested driver 'SKGSQLCIPHER', available drivers: SKGSQLCIPHER QSQLITE
##WARNING: QSqlDatabasePrivate::removeDatabase: connection 'SKGDATABASE_1' is still in use, all queries will cease to work.
##WARNING: QSqlDatabasePrivate::addDatabase: duplicate connection name 'SKGDATABASE_1', old connection removed.
... (last three lines repeat on each password entry attempt)
```

EXPECTED RESULT
Should open.

SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a terminal window):
KDE Plasma Version: 6.6.5
KDE Frameworks Version: not sure, the runtime says "“build of org.kde.Sdk, Fri May 22 07:14:38 AM UTC 2026, 058dd6612"
Qt Version: ditto

ADDITIONAL INFORMATION
I followed https://docs.flathub.org/docs/for-users/downgrading to downgrade:
   % flatpak update --commit \
        49bc183da466bec44bab4f6f641cab401584d1ee30872b428f46c3b8066527d3g  \
        runtime/org.kde.Platform/x86_64/6.10

This could be related to all the shenanigans getting SQLCipher to work, or something else.
Comment 1 Stephane MANKOWSKI 2026-05-28 15:45:45 UTC
Hi,

I think we have this kind of issue because:
1- The internal Qt driver for sqlcipher is based on a *private* Qt header
2- If this file is modified, then the binary compatibility could be broken
3- The driver is no more loadable
4- Skrooge fails with this error

I will push a fix to remove this dependency on private header.
Comment 2 Stephane MANKOWSKI 2026-05-28 15:46:34 UTC
Git commit 7e754e05240fab0b1c94268c8fce1194a11f258e by Stéphane MANKOWSKI.
Committed on 28/05/2026 at 15:46.
Pushed by smankowski into branch 'master'.

Skrooge can't load skg file after org.kde.Platform update

M  +1    -0    CHANGELOG
M  +55   -66   skgsqlcipher/q6sql_sqlite.cpp
M  +9    -2    skgsqlcipher/q6sql_sqlite_p.h

https://invent.kde.org/office/skrooge/-/commit/7e754e05240fab0b1c94268c8fce1194a11f258e
Comment 3 skierpage 2026-05-29 21:23:56 UTC
(In reply to Stephane MANKOWSKI from comment #2)
> Git commit 7e754e05240fab0b1c94268c8fce1194a11f258e by Stéphane MANKOWSKI.
> Committed on 28/05/2026 at 15:46.

I un-reverted to the latest May 22 build of the KDE runtime with `flatpak update runtime/org.kde.Platform/x86_64/6.10`, which printed the error "Error: Error deploying: Directory not empty" but completed, and now `flatpak run org.kde.skrooge//master path/to/my.skg` works with no error 🥳.

But the stable flatpak on Flathub remains broken until it gets the fix (or users downgrade the KDE runtime as I describe).