[GNC] postpone reconciliation broken: ignores my changes

[John Ralls]

That means that it didn't actually crash, it quit "normally" where "normally" is what the OS thinks is normal, not necessarily what the rest of us do.

Regards,
John Ralls


> On Feb 7, 2019, at 4:40 PM, Michael Hendry <hendry.michael at gmail.com> wrote:
> 
>> On 7 Feb 2019, at 17:22, John Ralls <jralls at ceridwen.us> wrote:
>> 
>> 
>> 
>>> On Feb 7, 2019, at 12:52 AM, Colin Law <clanlaw at gmail.com> wrote:
>>> 
>>> On Thu, 7 Feb 2019 at 07:37, Michael Hendry <hendry.michael at gmail.com>
>>> wrote:
>>> 
>>>>> On 3 Feb 2019, at 14:59, Jamestk <davidjamestk at hotmail.co.uk> wrote:
>>>>> 
>>>>> Ira me again, this seems to be happening on v3.4
>>>>> 
>>>>> Changes made by ticking entries are no longer saved after opting to
>>>>> postpone, anyone else noticed this?
>>>> 
>>>> 
>>>> A slightly different (but perhaps connected?) reconciliation problem
>>>> happened to me yesterday.
>>>> 
>>>> I’m using version 3.4 on iMac with High Sierra.
>>>> 
>>>> I reconciled 9 separate statements with their corresponding accounts on
>>>> Tuesday. In some instances I had to enter transactions which appeared on
>>>> the statement but for which I didn’t have a receipt (e.g. contactless
>>>> travel charges), and found I couldn’t do this without postponing (this is
>>>> possible in 2.6.16). Once I’d made these entries I was able to go back and
>>>> complete the reconciliation.
>>>> 
>>>> Yesterday morning I reconciled a single account, marked it complete,
>>>> clicked “Save” and quit Gnucash - I was going to be out all day, and wasn’t
>>>> planning to do any more work on the books. The unusual aspect was the quick
>>>> sequence of finishing the reconciliation, clicking Save and Quit - usually
>>>> I would tidy up the papers before shutting down. The Mac itself was left
>>>> running.
>>>> 
>>>> In the evening I decided to reconcile another couple of statements, but
>>>> when I started Gnucash I got the lock-file warning, but overrode it because
>>>> there was no other instance of Gnucash running, only to find that the
>>>> reconciliation from the morning hadn’t been saved.
>>>> 
>>>> A number of minor corrections I’d made to transactions during the session
>>>> have been recorded.
>>>> 
>>>> I suppose it’s possible that I hit Cancel instead of Finish at the end of
>>>> the reconciliation, but I’ve never made this error since I started using GC
>>>> in 2010.
>>>> 
>>> 
>>> I think it more  likely that is a different issue, it sounds more as if GC
>>> crashed for some reason so had not saved the data.
>> 
>> Right, and if so there should be a crash report in /Applications/Utilities/Console.
>> 
>> Regards,
>> John Ralls
> 
> Can’t find one related to this problem, but did find an earlier one relating to the failure of 2.6.3 (before you fixed it, John), which would suggest that I’m looking in the right place.
> 
> The first 20-odd lines of that report follow.
> 
> Michael
> 
> 
> Process:               Gnucash-bin [10851]
> Path:                  /Applications/Gnucash2.6.3.app/Contents/MacOS/Gnucash
> Identifier:            org.gnucash.Gnucash
> Version:               ???
> Code Type:             X86 (Native)
> Parent Process:        ??? [1]
> Responsible:           Gnucash-bin [10851]
> User ID:               501
> 
> Date/Time:             2019-01-29 11:28:05.325 +0000
> OS Version:            Mac OS X 10.13.6 (17G4015)
> Report Version:        12
> Anonymous UUID:        6E4C0EFC-2FF3-6AA3-4C59-DBC3DB6D08BC
> 
> Sleep/Wake UUID:       7C6A5C36-4914-4581-8EAD-7280B55B0DF1
> 
> Time Awake Since Boot: 140000 seconds
> Time Since Wake:       92000 seconds
> 
> System Integrity Protection: enabled
> 
> Crashed Thread:        0
> 
> Exception Type:        EXC_CRASH (SIGABRT)
> Exception Codes:       0x0000000000000000, 0x0000000000000000
> Exception Note:        EXC_CORPSE_NOTIFY
> 
> Termination Reason:    DYLD, [0x4] Symbol missing
>