Nice to hear that it's fixable. The pricedb entries have unreasonable
precision and was fixed a few months ago, but existing entries remain. This
is still a worthwhile bug to fix.
On Sun, 28 Jun 2020 at 14:43, Lipp F. wrote:
> Hi Christopher,
>
> Your suggestion about verifying pricedb was inval
Hi Christopher,
Your suggestion about verifying pricedb was invaluable. I cannot thank you
enough.
I was able to identify the security responsable by disabling sub-accounts,
one by one, until I was left with only the one generation the error. I have
checked pricedb for that specific security and
Hi Lipp
The usual approach is to file a bug in bugs.gnucash.org
Include the exact version used (3.10?)
Also you are using pricedb - it would be worth reviewing the pricedb
entries around 9th July and add this to the bug report.
C
On Sat, 27 Jun 2020 at 14:28, Lipp F. wrote:
> Wondering if anyone
