3.0-118-gd2ef5fd0f+ (2018-04-28) Deterministic/repeatable: - Switch tabs to a different account. - Start typing. Effect: Crash It seems on switching tabs, the date field in the current transaction seems to have focus, but is not selected. Note: In previous versions, this wasn't a crash, but had the same underlying problem: focus wasn't where it appeared. (In 2.6, typing when switching accounts resulted in the register of an account not visible on the screen being updated.) If you tab before typing (then back-tab to get back to the date), gnucash will not crash. Nor if you click instead of immediately typing.
I can't replicate this crash. Please attach a crash report from Console.
Created attachment 372888 [details] Crash report, 6/29/18 I'm attaching 3 crash reports which I believe to all be the same. I'm 100% certain the June 29th crash report is from this bug, and 90% certain the others are.
Created attachment 372889 [details] Crash report, 6/14/18
Created attachment 372890 [details] Crash report, 6/14/18 additional
You've edited out some important information. Please attach the whole file.
I haven't edited anything out, that's everything, but I when I went back into console the same reports look very different. Attaching a new crash shortly.
Created attachment 372891 [details] Crash report, 6/29/18, additional I realize the log indicates: """ terminating with uncaught exception of type boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::gregorian::bad_year> >: Year is out of valid range: 1400..10000 """ ...realize that if I had pressed the tab key first, this wouldn't have crashed. (I had to go through and fix the year out of range issues before I started using this version of gnucash, I had a couple of stock prices that had bad years) This is reproducible (for me). - Open gnucash - Press "1" - Crash (Note that when gnucash opens, it's open to a register, so I should be editing a date field)
Ah, that's been fixed in 3.2. Please test it.
Acknowledged and verified successfully. Apologies for filing a dupe.
Not actually a dupe, the problem was reported on the mailing list.
