[kmymoney] [Bug 453254] KMyMoney is not closed completely and blocks dismounting of an encrypted volume where the *.kmy-file was saved.
Paul
bugzilla_noreply at kde.org
Wed May 4 12:57:03 BST 2022
https://bugs.kde.org/show_bug.cgi?id=453254
--- Comment #13 from Paul <zy.wpnir at sunrise.ch> ---
Hi Ralf
Today, it does not work anymore (enclosures).
I will do forced dismounting in VERAcrypt and it's OK for me.
Kind regards
Paul
Am 03.05.2022 um 11:39 schrieb Ralf Habacker:
> https://bugs.kde.org/show_bug.cgi?id=453254
>
> --- Comment #9 from Ralf Habacker <ralf.habacker at freenet.de> ---
> (In reply to Paul from comment #7)
>> Created attachment 148526 [details]
>> attachment-13375-0.html
>>
>> Hi again
>>
>> After sending the email below, I opened my *.kmy-file with the
>> reinstalled version 5.0.6., made some changes, saved changes and closed
>> KMyMoney. Then I waited approx. 5 seconds and dismounted the encrypted
>> drive and astonishly I worked without any problem and did not ask me
>> whether I want to do a "forced dismounting".
>>
>> No idea why!
> This should be the normal behavior as on starting kmymoney the watchdog named
> kwinshutdown.exe is started and terminates any background processes 5 seconds
> after kmymoney has been closed (see share/autostart/kwinshutdown.desktop).
>
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the KMyMoney-devel
mailing list