Sx editor crash, (continuing saga)

Sun Jan 11 18:18:03 EST 2015

Sun, 11 Jan 2015 08:32:17 
<E858F5B3-88CB-4D8E-B173-5F4CF55C0203 at gmail.com>  Peter Kiessling 
<pjkiess at gmail.com>

> John
> Good Job.
Before I  tried to open Gnwucash under 2.4.x, I opened under 2.6.5 and 
then went to Actions>scheduled transaction>since last run> and the list 
comes up.  Selected the transaction you labelled as troublesome and 
noted that I had selected  <postpone> and that the date associated was 
1969. ( I don?t know where that came from.) In that SX screen I 
changed options and selected <to create> and then <ok>.  Lo and behold I 
could now get into SX editor and no transaction for 1969 was created. 
Same thing happens if I say <ignore>.  Calendar editor window opens as 
expected. When I go to the troublesome transaction in the now open 
editor then go to <toolbar><scheduled> and try and delete the offending 
transaction Gnwucash crashes.  At this point I have transaction 
editor(SX) now available but I cannot delete the original  transaction 
and it does not have the <postpone> label. I do get a new crash report 
after I try to delete it and Gnucash crashes.
Bottom line: You astutely  labeled the  offending transaction. I think 
the root cause has something to do with my selection of <postponed>. 
Whatever happened I now can?t get rid of the transaction although the 
SX editor seems to be Ok. Doug is my younger brother.  He?ll be happy 
to know he is now a permanent part of my financial  records.
As you have the data file maybe you can see that same interesting 
behavior.
Pete

Theoretically an SX is a transaction that works with a time difference.

That is certainly the view maintained over in dev.

Logically either the transaction is wrong or the schedule is wrong.

You tell us which and see the dev people think.

-- 
Wm...

> On Jan 11, 2015, at 10:08 AM, Wm <wm+gnc at tarrcity.demon.co.uk> wrote:
> 
> Sun, 11 Jan 2015 08:32:17 <E858F5B3-88CB-4D8E-B173-5F4CF55C0203 at gmail.com>  Peter Kiessling <pjkiess at gmail.com>
> 
>> John
>> Good Job.
> Before I  tried to open Gnwucash under 2.4.x, I opened under 2.6.5 and then went to Actions>scheduled transaction>since last run> and the list comes up.  Selected the transaction you labelled as troublesome and noted that I had selected  <postpone> and that the date associated was 1969. ( I don?t know where that came from.) In that SX screen I changed options and selected <to create> and then <ok>.  Lo and behold I could now get into SX editor and no transaction for 1969 was created. Same thing happens if I say <ignore>.  Calendar editor window opens as expected. When I go to the troublesome transaction in the now open editor then go to <toolbar><scheduled> and try and delete the offending transaction Gnwucash crashes.  At this point I have transaction editor(SX) now available but I cannot delete the original  transaction and it does not have the <postpone> label. I do get a new crash report after I try to delete it and Gnucash crashes.
> Bottom line: You astutely  labeled the  offending transaction. I think the root cause has something to do with my selection of <postponed>. Whatever happened I now can?t get rid of the transaction although the SX editor seems to be Ok. Doug is my younger brother.  He?ll be happy to know he is now a permanent part of my financial  records.
> As you have the data file maybe you can see that same interesting behavior.
> Pete
> 
> Theoretically an SX is a transaction that works with a time difference.
> 
> That is certainly the view maintained over in dev.
> 
> Logically either the transaction is wrong or the schedule is wrong.
> 
> You tell us which and see the dev people think.
> 

Wm,

The deferredInstance element of the SX record in question is corrupt; see https://bugzilla.gnome.org/show_bug.cgi?id=672760.

Regards,
John Ralls

------------------------------

Message: 6
Date: Sun, 11 Jan 2015 10:22:04 -0800
From: John Ralls <jralls at ceridwen.us>
To: Peter Kiessling <pjkiess at gmail.com>
Cc: gnucash-user at gnucash.org
Subject: Re: Sx editor crash, (continuing saga)
Message-ID: <F73471EC-3352-4628-A1F7-AB9C21647911 at ceridwen.us>
Content-Type: text/plain; charset=utf-8

I?m not able to replicate the crash on delete, but deleting the SX also doesn?t mark the book dirty. Could you post the stack trace portion of the crash report? You can view it in /Applications/Utilities/Console.app; just find the bit that looks like 
Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000

VM Regions Near 0:
--> 
   __TEXT                 0000000000001000-0000000000015000 [   80K] r-x/rwx SM=COW  /Applications/Gnucash 2.6.5-6.app/Contents/MacOS/Gnucash-bin

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libgncmod-gnome-utils.dylib   	0x00277e0e gnc_dense_cal_draw_to_buffer + 2270
1   libgncmod-gnome-utils.dylib   	0x0027b04f gdc_reconfig + 127
2   libgncmod-gnome-utils.dylib   	0x0027af9b gnc_dense_cal_configure + 43
3   libgtk-quartz-2.0.0.dylib     	0x02239221 _gtk_marshal_BOOLEAN__BOXED + 129
4   libgobject-2.0.0.dylib        	0x0296a3bd g_closure_invoke + 365
5   libgobject-2.0.0.dylib        	0x02978e20 signal_emit_unlocked_R + 1008
6   libgobject-2.0.0.dylib        	0x02979d57 g_signal_emit_valist + 2775
7   libgobject-2.0.0.dylib        	0x0297a389 g_signal_emit + 41
8   libgtk-quartz-2.0.0.dylib     	0x0235b65d gtk_widget_event_internal + 589
9   libgtk-quartz-2.0.0.dylib     	0x0235efe8 gtk_widget_event + 168
10  libgtk-quartz-2.0.0.dylib     	0x021b8e7e gtk_drawing_area_send_configure + 78
?

and paste it into an email. The example is from your earlier crash report.

Regards,
John Ralls

1/11/15
I had deleted the crash reports I got last night.  After rebooting this morning I also am unable to recreate the crash.  The Offending transaction did delete. 
A minor event was that despite the deletion of the SX ( a change) Gnucash allowed me to close it without saving, so that on reopening the transaction was back. Is that what you mean with “ marking the book dirty”? I deleted it again (no crash) and then created a test register transaction so that the save icon became active.  That got rid of it.
The previous version of gnucash seemed rigged so that even a sneeze asked for a save, which was good for me.
Thanks to John and others for the help.
Is there a way to get a printable report of all the SX’s and their settings?
Pete