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

[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.