https://bugs.kde.org/show_bug.cgi?id=453254
Bug ID: 453254
Summary: KMyMoney is not closed completely and blocks
dismounting of an encrypted volume where the
*.kmy-file was saved.
Product: kmymoney
Version: 5.0.6
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kmymoney-de...@kde.org
Reporter: zy.wp...@sunrise.ch
Target Milestone: ---
Created attachment 148487
--> https://bugs.kde.org/attachment.cgi?id=148487&action=edit
active processes and remaining files
SUMMARY
***
KMyMoney is not closed completely and blocks dismounting of an encrypted volume
where the *.kmy-file was saved.
***
STEPS TO REPRODUCE
1. open/mount an encrypted volume/drive with VERACRYPT
2. open a *.kmy-file stored in the encrypted volume with KMyMoney
3. do some changes in *.kmy-file
4. save *.kmy-file
5. exit KMyMoney with a click on "X"
6. wait a couple of minutes
7. dismount volume in VERACRYPT
OBSERVED RESULT
volume can not be dismounted "because files are in use by another program";
unless a "forced dismount" is done
EXPECTED RESULT
- volume should be dismounted
SOFTWARE/OS VERSIONS
Windows: 10
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
Following processes of KMyMoney are still active after closing KMyMoney:
-kioslave5.exe
-klauncher5.exe
It seems to me, that one or both of these process block the *.kmy-file and
prevent dismounting of the VERACRYT-volume.
After forced dismounting, a *.kmy.n~ remains in the encrypted volume (see
attachment)
--
You are receiving this mail because:
You are watching all bug changes.
