GNUcash crashes on save - losing all changes

[James Leone]

minfrin at sharp.fm wrote:

> John Zoetebier wrote:
>
>> Of course, your changes are not saves due to folder and file 
>> permissions.
>> This has nothing to do with GnuCash issue.
>
>
> If Gnucash segfaults for any reason, even due to user error, it is a 
> Gnucash issue.
>
> The correct behaviour should be to tell the user the file could not be 
> saved at that location, then offer a new location to save to.
>
> Remember that human interfaces to software are like customer services 
> representatives in a company. The customer may be wrong, but that 
> doesn't give the representative leave to simply cut the customer's 
> phone call off.
>
>> I feel, the first mistake was to ignore a valid error message, that 
>> you should have checked in the first place.
>
>
> Never assume any reasonable behaviour from the user. If Gnucash 
> allowed the user past the load-a-locked-file point, it is responsible 
> for behaving sanely after that.
>
> Remember what you might have thought was a mistake, might not have 
> been, as the user may have had better knowledge than gnucash of the 
> status of the lockfile.
>
> Regards,
> Graham

Although to developers this may seem wrong, I do think that this 
attitude, this viewpoint will help Linux gain ground on the desktop. I 
hope that developers will be able to cast aside the obvious unfairness 
to the developer to allow the end user to achieve more.

I do thank the developers very much, and, only wish additional capacity 
for longsuffering to allow the maximum amount of people to benefit from 
their work.

JL