RE: Sx editor crash, (continuing saga)

RE: Sx editor crash, (continuing saga)

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

Re: Sx editor crash, (continuing saga)

>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.

Re: Sx editor crash, (continuing saga)

> On Jan 11, 2015, at 10:08 AM, Wm <[hidden email]> wrote:
>
> Sun, 11 Jan 2015 08:32:17 <[hidden email]> Peter Kiessling <[hidden email]>
>
>> 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.
>

Re: Sx editor crash, (continuing saga)

> On Jan 11, 2015, at 8:32 AM, Peter Kiessling <[hidden email]> wrote:
>
> 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.
>

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

Re: Sx editor crash, (continuing saga)

> 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 <[hidden email]> wrote:
>
> Sun, 11 Jan 2015 08:32:17 <[hidden email]> Peter Kiessling <[hidden email]>
>
>> 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.
>

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

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

Re: Sx editor crash, (continuing saga)

Is there a way to get a printable report of all the SX’s and their
settings?

Which backend are you using?

If it is XML the answer is probably "no, not easily" unless you have
access to a natural, popular and broadly implemented XML query language.
I think we'd have heard about it by now.

More hopefully, if it is one of the SQLs then ask more specifically and
you'll get some help, I use SQLite and Postgres and might be able to
translate MySql at a push, chances are someone else will pick it up if
it is MySql specific.

From where I am the query is simple, which bit are you having difficulty
with?

Re: Sx editor crash, (continuing saga)

On 1/13/2015 12:31 PM, Wm wrote:

> Sun, 11 Jan 2015 15:18:03
> <[hidden email]> Peter Kiessling
> <[hidden email]>
>
> Is there a way to get a printable report of all the SX’s and their
> settings?
>
> Which backend are you using?
>
> If it is XML the answer is probably "no, not easily" unless you have
> access to a natural, popular and broadly implemented XML query
> language. I think we'd have heard about it by now.
>
> More hopefully, if it is one of the SQLs then ask more specifically
> and you'll get some help, I use SQLite and Postgres and might be able
> to translate MySql at a push, chances are someone else will pick it up
> if it is MySql specific.
>
> From where I am the query is simple, which bit are you having
> difficulty with?
>

I think that should be a feature as a normal part of GnuCash. I also
think that it should be possible to get a nicely formatted list of the
settings for all custom reports.