Bug 497282

Can you check if using a version from https://cdn.kde.org/ci-builds/office/kmymoney/master/windows/ (you need the x86_64.exe version) makes a difference?

Created attachment 176606 [details]
attachment-2843505-0.html

Hi Thomas,

It worked the first time.

I saved as my file under a new name. I closed KMM. I reopened KMM and it 
asked me a password. I entered my passwork and my file openned with the 
new file name.

I closed KMM and reopenned it. It didn't ask me for a password!

Why?

Le 14/12/2024 à 09:23, Thomas Baumgart a écrit :
> https://bugs.kde.org/show_bug.cgi?id=497282
>
> Thomas Baumgart<tbaumgart@kde.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Status|REPORTED                    |NEEDSINFO
>           Resolution|---                         |WAITINGFORINFO
>
> --- Comment #1 from Thomas Baumgart<tbaumgart@kde.org> ---
> Can you check if using a version from
> https://cdn.kde.org/ci-builds/office/kmymoney/master/windows/ (you need the
> x86_64.exe version) makes a difference?
>

Created attachment 176608 [details]
attachment-2845998-0.html

I was to quick with my answer.

I closed my computer and strat again.

It asking me for a password each time I am openning KMM.

Problem solved.

Thanks


Le 14/12/2024 à 09:23, Thomas Baumgart a écrit :
> https://bugs.kde.org/show_bug.cgi?id=497282
>
> Thomas Baumgart<tbaumgart@kde.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Status|REPORTED                    |NEEDSINFO
>           Resolution|---                         |WAITINGFORINFO
>
> --- Comment #1 from Thomas Baumgart<tbaumgart@kde.org> ---
> Can you check if using a version from
> https://cdn.kde.org/ci-builds/office/kmymoney/master/windows/ (you need the
> x86_64.exe version) makes a difference?
>

Since I have installed the new version, it takes a lot of time to KMM to open, close to 1 minutes. Why?

Created attachment 176723 [details]
KMM opening

I suspect this to have something to do with gpg and/or your local environment. Can you check if the loading time is similar if you store the file as .kmy (compressed but not encrypted) or different?

Created attachment 176746 [details]
impossible d'ouvrie le fichier

(In reply to Gilles Guertin from comment #7)
> Created attachment 176746 [details]
> impossible d'ouvrir le fichier

Opening a normal file is instantly. Opening an encrypted file takes for ever. Actually, this morning, I cannot open my encrypted file (see attachment)

(In reply to Gilles Guertin from comment #8)
> (In reply to Gilles Guertin from comment #7)
> > Created attachment 176746 [details]
> > impossible d'ouvrir le fichier
> 
> Opening a normal file is instantly. Opening an encrypted file takes for
> ever. Actually, this morning, I cannot open my encrypted file (see
> attachment)

As you know, I am using Gpg4win version 4.4.0 for the gpg. I really think that this software is the problem. I cannot find an other software.
Can you suggest an other software?

I tested this on a Win10 box I have access to. KMyMoney Version 5.1.80-f7943e4, Gpg4Win 4.3.1.  I noticed, that it takes a while for the key management to start (until the dialog for the GPG passphrase comes up) after initial application launch but I can write and read encrypted files without problems. I don't know if a newer version of Gpg4Win causes these problems. Does someone with enough knowledge about Windows have the bandwidth to analyze this problem? I ran out of time for this year.

(In reply to Thomas Baumgart from comment #10)
> I tested this on a Win10 box I have access to. KMyMoney Version
> 5.1.80-f7943e4, Gpg4Win 4.3.1.  I noticed, that it takes a while for the key
> management to start (until the dialog for the GPG passphrase comes up) after
> initial application launch but I can write and read encrypted files without
> problems. I don't know if a newer version of Gpg4Win causes these problems.
> Does someone with enough knowledge about Windows have the bandwidth to
> analyze this problem? I ran out of time for this year.

So that everybody have the same informations, I am using KMyMoney version 5.1.3-eef04f1 in french. I am also using Windows 11 in french.
I was able to generate a key by using Kleopatra which is installed together with Gpg4win version 4.4.0 by default.
Does someone has an alternative to gpg4win (Kleoatra)?
Am I the only one in the word to save a KMM file with a password?

I'm wondering if the start of Kleopatra also takes a long time.

(In reply to Ingo Klöcker from comment #12)
> I'm wondering if the start of Kleopatra also takes a long time.

The start of Kleopatra is normal. It search for a certificat but it takes only 3 to 4 seconds.

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

(In reply to Bug Janitor Service from comment #14)
> 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15
> days. Please provide the requested information, then set the bug status to
> REPORTED. If there is no change for at least 30 days, it will be
> automatically closed as RESOLVED WORKSFORME.
> 
> For more information about our bug triaging procedures, please read
> https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.
> 
> Thank you for helping us make KDE software even better for everyone!

Hi Janitor.
This bug is in NEEDSINFO since 15 days simply because nobody can help me not because it is RESOLVED. They ran out of hours... The bug is still alive.

Well, /they/ are so far unable to reproduce the problem. Since the beginning of the year, the KDE CI/CD system does not produce anymore windows versions from the code, so another obstacle on the road. I will leave this open so that the janitor (by the way a bot which does not react to your message) does not kick in again.