[kmymoney] [Bug 453254] KMyMoney is not closed completely and blocks dismounting of an encrypted volume where the *.kmy-file was saved.

[Paul]

https://bugs.kde.org/show_bug.cgi?id=453254

--- Comment #17 from Paul <zy.wpnir at sunrise.ch> ---
Hi Ralf and Stephen

Thanks a again.

Ralf seems to have had the right idea! Dismounting is only blocked when 
opening kmymoney via double click on the *.kmy-file on the encrypted file!
quote

Therefore, the remaining reason for the reported problem could be/*that
kmymoney was started from a path inside the Veracrypt container*/  and the
leftover
processes are blocking unmounting. Or another program like explorer could be
blocking the unmount.

unquote

However, there seems to be another bug in the program when opening 
kmymoney via start menu without having previously mounted the 
VERYcrypt-drive; see below SECOND and THIRD way

What did I do:

  * downloaded 64 bit-version 5.1.2 from your snapshot-link
  * extracted all files and copied them to the installation directory
    where 5.0.6 was installed (I renamed all 5.0.6-directories first!)
  * AVAST did not block anything; I previously added an exception to the
    installation directory of 5.0.6 (now 5.1.2) in AVAST


*FIRST way*

  * started kmymoney with your start.bat-file
  * my *.kmy-file on the previously mounted VERAcrypt-drive opened correctly
  * made some changes in the *.kmy-file and saved it
  * exited kmymoney
  * after 5-6 seconds dismounted the VERAcrypt-drive
  * result: it dismounts immediately as expected
  * shutdown the computer


*SECOND way*

  * restarted the computer
  * mounted the VERAcrypt-drive
  * doubleclicked the *.kmy-file
  * made some changed in the *.kmy-file and saved it
  * after 3 minutes dismounted the VERYcrypt-drive
  * result: error message as before, i.e. only a forced dismount is possible
  * forced dismounting of the VERYcrypt-drive
  * *after 10 minutes I opened kmymoney via the start menu without
    previously mounting the VERYcrypt-drive*
  * *result: kmymoney does not open; it hangs somewere; it's freezed*
  * shutdown the computer


*THIRD way*

  * restarted the computer
  * mounted the VERAcrypt-drive
  * started kmymoney via the start menu
  * my *.kmy-file on the previously mounted VERAcrypt-drive opened correctly
  * made some changes in the *.kmy-file and saved it
  * exited kmymoney
  * after 5-6 seconds dismounted the VERAcrypt-drive
  * result: it dismounts immediately as expected
  * *after a few minutes I opened kmymoney via the start menu again 
    without previously mounting the VERYcrypt-drive*
  * *result: ***kmymoney *does not open; it hangs somewere; it's freezed*


After closing kmymoney I checked via Task Manager what program-parts are 
still active. In all three ways the same parts where still active (see 
enclosure).

So the solution for me is either way 1 or way 3 😉

Hope the above helps to find the possible bug(s).

Kind regards
Paul

NB: I am just programming in Visual Basic 6 starting with BASICA in the 
year 1984😂; so my process-knowledge is not as deep as yours, sorry.



Am 04.05.2022 um 14:56 schrieb Ralf Habacker:
> https://bugs.kde.org/show_bug.cgi?id=453254
>
> --- Comment #15 from Ralf Habacker<ralf.habacker at freenet.de>  ---
> (In reply to Paul from comment #14)
>> Created attachment 148557 [Details]
>> kmymoney-still_active_parts.JPG
> It turns out that kwinshutdown*.exe is not included in version 5.0.6, so these
> processes are not killed after 5 seconds by default. Since this tool is
> included in the current snapshot, you need to download a newer snapshot from
> https://kmymoney.org/snapshots.php  to fix this issue.
>
> Using kmymoney 5.0.6 and procexp
> (https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer), I
> verified that the running kmymoney.exe and all background processes involved do
> not have an open file handle to the kmymoney file in use, even if it is stored
> in a local Veracrypt container.
>
> Therefore, the remaining reason for the reported problem could be that kmymoney
> was started from a path inside the Veracrypt container and the leftover
> processes are blocking unmounting. Or another program like explorer could be
> blocking the unmount.
>
> You can find this out with procexp and the menu item Find->"Find Handle or DLL"
> by entering the drive letter e.g. "a:\".
>
> If the problem is kmymoney or a involved background process, only a newer
> snapshot will help.
>

-- 
You are receiving this mail because:
You are the assignee for the bug.