2011-11-27, 05:24 AM
cncb Wrote:I thought you had some kind of change ready for the next release that would avoid this problem. Is that not the case?I have attempted a work around, but given I've not been able determine the cause or reproduce it here, I have no way to know if this will help until it's in the hands of users that see the problem. I not certain enough claim the problem is definitely fixed in the next release.
As Martin says though, getting the next release out will put me back in state where I can provide patches to collect more logging etc, which will be a big help if the problem is still present.