[kmymoney] [Bug 396285] When opening a mymoney file from smb:// share saving fails and destroys all data to 0Bytes!

kde at solis3.org kde at solis3.org
Sun Jul 8 10:58:02 BST 2018


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

--- Comment #4 from kde at solis3.org <kde at solis3.org> ---
Ok, the plot thickens... 

But dont write this off just yet because KMyMoney < 5 on Mint 18.3 works fine
with the same remote share.  

KMyMoney 5 does create a lot of files .1~ .2~ etc on save. In fact it creates 3
such files when saving the file only once. This seems Odd.

In addition, those files ARE created on the failing remote, its just they all
become zero length. So permissions seems unlikely (as the files could not be
created at all). Compatibility with a new save mechanism or naming seems
likely. The original file and the created .1~ etc all are zero length after a
save (with the error). 

Either, this is a Mint 19 (Ubuntu 1804) issue with mounted shares or MyMoney5
with a specific samba.

So lets do some tests.

Remote A, Synology Diskstation DS1817+ running latest DSM 6.2-23739 (the
problem remote)
Remote B, Mint 18.3 (Ubuntu 16.04) with Samba 2:4.3.11+dfsg 0ubuntu0.16.04.13
Mint A (18.3) standard install with KMyMoney 4.6.6
Mint B (19.0) standard install with KMyMoney 5.

Test 1.  Mint A saving to Remote A. OK
Test 2.  Mint B saving to Remote A. NOK, error and all files become zero
length.
Test 3.  Mint B saving to Remote B. OK.
Test 4.  Mint B (running Kymoney 4) to Remote A. How to test???

Test 4 seems to be the critical test since it will prove its KMyMoney 5 and not
a Mint 19 issue. However I do not have KMyMoney 4 on this machine.  I will
investigate and report.

So, this is a compatibility issue with Synology, however lets not get all
excited and blame Synology right now since the old KMyMoney works.

I think something has changed in the way KMyMoney 5 saves and this is causing
the issue with Synolgoy.  It does create a lot of files and truncating to zero
length is a little clue perhaps.

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


More information about the KMyMoney-devel mailing list