On Thu, Oct 17, 2019 at 1:06 PM Adrien Monteleone <[email protected]> wrote: > If you really wanted to track this down, you could grep the various 2.6.x > dependencies against those logs to see if any of them were updated in the > time interval that would account for the change in behavior.
If someone else wants to analyze my update logs, I am probably willing to provide a copy. (I doubt the update logs contain any confidential information.) > The downside here is multiple dependencies could have been updated. So > without some debugging/error info reported in the tracefile, stderr or > elsewhere, you’d have to roll them all back, pin all but one, and then > manually update one each at a time until you find the culprit. (and then it > might be a combo of culprits!) Indeed, there is not much clarity. I am familiar with tracking down bugs, and I am averse to trying to track this one down (due to the quantity of work likely involved). I cannot even reliably reproduce the freezes. > Really, you’ll need some actual error message to go any further if more than > one was updated. (and certainly if none were) Probably a bunch were updated. I don't update regularly, and the last time I ran GnuCash was in early September. So you have at least a six-week window in which a new package (or packages) could have come out. Possibly longer depending on when I last updated. Thanks again! -Parke _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
