Can not open decrypted kmy file with Flatpack version of KMyMoney

Help
1

Now I’m using KMyMoney from Flatpak (Flathub) instead AppImage. My kmy-File is encrypted and I can open this file with the AppImage version.

After installing KMyMoney 5.2.1 via Flatpak I can’t open my kmy-File with following error message:

Cannot read the file: /home/user/myAccount.kmy /run/build/kmymoney/kmymoney/plugins/xml/xmlstorage.cpp:413

I try to save a decrypted kmy-File with AppImage. This uncrypted can I use with the Flatpak version. But if I encrypt this file with Flatpak an reopen it, I get the same error message.

This are the components in Flatpak version:

KMyMoney: 5.2.1
Alkimia: 8.2.1 (build against 8.2.1)
Aqbanking: Unbekannt (build against 6.9.1)
Gpgme: Unbekannt (build against 1.24.3)
Gwenhywfar: Unbekannt (build against 5.14.1)
KDiagram: Unbekannt (build against )
libical: Unbekannt (build against 3.0.20)
libofx: Unbekannt (build against 7.0.4)
SQLCipher: Unbekannt (build against 3.46.1)
KDE Frameworks: 6.22.0
Qt: 6.10.1 wird verwendet und gebaut wurde mit 6.10.1
Flatpak
KDE Flatpak runtime (Wayland)
Build ABI: x86_64-little_endian-lp64
Kernel: linux 6.17.0-8-generic

This are the components of AppImage version

KMyMoney: 5.2.1-6e26843
Alkimia: 8.2.70 (build against 8.2.70)
Aqbanking: Unbekannt (build against 6.9.1)
Gpgme: Unbekannt (build against 2.0.0)
Gwenhywfar: Unbekannt (build against 5.14.1)
KDiagram: Unbekannt (build against )
libical: Unbekannt (build against 3.0.20)
libofx: Unbekannt (build against 7.0.4)
SQLCipher: Unbekannt (build against 3.20.1)
KDE Frameworks: 6.22.0
Qt: 6.10.1 wird verwendet und gebaut wurde mit 6.10.1
AppImage
Ubuntu 25.10 (Wayland)
Build ABI: x86_64-little_endian-lp64
Kernel: linux 6.17.0-8-generic

What could be the problem or how can I get more information about the problem?

This is only the output of console if I run KMyMoney with “flatpak run org.kde.kmymoney”

Open file QUrl("file:///home/user/kym.kmy")
kf.notifications: Failed to play sound with canberra: Not available
2

Hello,
it might help the developer team to know which distribution your software (flatpak and appimage) is running on.

3

That’s correct. :slight_smile:

PRETTY_NAME="Ubuntu 25.10"
NAME="Ubuntu"
VERSION_ID="25.10"
VERSION="25.10 (Questing Quokka)"
VERSION_CODENAME=questing
4

I do not personally use any Flatpaks so this is mainly a guess, but I think flatpak use sandbox protection of the file system. By opening the un-encrypted file you might be explicitly granting permission, but accessing an encrypted file requires that not only the application itself access the file, but also a different application to do the unencryption. I would hunt through the flatpak configuration/settings to see if you can explicitly allow access to the encrypted file.

1 Like
5

I’m not able to reproduce the problem. Using the flatpak from Flathub and the AppImage from Index of /ci-builds/office/kmymoney/5.2/linux, I can save an encrypted XML file with either and open it with either flatpak or AppImage. I’m on openSUSE Tumbleweed, but that shouldn’t matter for flatpak or AppImage.

One difference between the builds is the flatpak uses GPGME 1.24.3 and the AppImage has 2.0.0. I’m not sure if some GPG keys would work with 2.0.0 but not 1.24.3? But I’m not sure why you can encrypt a file with the flatpak but not open it again. I can work at updating GPGME in the flatpak anyway to see if that makes a difference.

1 Like
6

For the nightly flatpak:

and Flathub:

I’m not sure if that will fix your problem, but it needed to be done sometime anyway.

1 Like
7

Thanks for this helpful posts. My solution is overpowered. :wink:

I switch from Ubuntu to Arch Linux with Plasma. Now all works fine and I can’t load/save the encrypted file without problems.