GNOME Bugzilla – Bug 110606
Save failure is not reported
Last modified: 2018-06-29 20:30:53 UTC
Upon upgrading from mandrake 9.0 to mandrake 9.1, I also upgraded from Gnucash 1.6.x to 1.8.1 . I was not happy with my former username on my old installation, so for my new installation I created a new user name. I kept my gnucash files on a partition that was not formatted during the upgrade. I was pleased to find that my new installation with the newer version of gnucash was able to open my old gnucash files. After reinstalling, I proceeded to add transactions to my old files. I click on the save button after almost every transaction entry. After a few weeks, I closed gnucash and reopened it only to find that all my changes since my upgrade had not been saved. After I discovered this, I opened gnucash from a command prompt, and found that when I tried to save, the following message was printed to the command line "unable to chmod xxx.qif - operation not permitted". If the save command fails, the user should be warned with some sort of message box.
*** Bug 119976 has been marked as a duplicate of this bug. ***
note to people reading this bug: chmod will no longer cause the save to fail, however if there is an actual save failure the user should be notified.
related: bug 105668 (not reporting failure to save when partition is full)
*** Bug 105669 has been marked as a duplicate of this bug. ***
Current svn does give a helpful error dialog when it's unable to save. At least, I tested when the file is in a read-only directory. BTW, setting the file read-only is insufficient, since gnucash will happily save over it anyway.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=110606. Please update any external references or bookmarks.