David
I'm not sure I understand the significance of much of your second
paragraph but ...
I have installed Ubuntu 21.04 on a different machine and installed
GnuCash 4.4 thereon and the behaviour I reported earlier is NOT
apparent. Using my customary practice of cloning an earlier share
purchase I am able to modify the numerical details (number of shares,
price of the shares and the total price) and get sensible results albeit
I don't always get the "which do you want to change" question.
I then removed GnuCash from my main machine and reinstalled it but the
errant behaviour I noted persists.
As I am 99.9% certain that the data and the GnuCash package on each
machine are identical my suspicion falls on the set up on my main
machine. I don't think it's the X Org/Wayland settings that are to blame
(I get identical behaviour whichever I choose).
Thus, I suspect that I need to reinstall Ubuntu on my main machine (but
that's not lightly undertaken even having had lots of practice of ding
it in the past). In the meantime using the old, painfully slow second
machine for GnuCash will have to suffice.
For what it's worth: the errant machine is running Ubuntu 21.04 (with
all security patches installed) with Gnucash 4.4 and F::Q 1.49; I always
install GnuCash using Synaptic and the standard repositories for the
version of Ubuntu installed.
Of course, if there's any further information I can provide I will be
happy to do so.
Eric Coates
==============================
On 28/07/2021 16:19, David Carlson wrote:
So far there has been no useful information presented in this thread,
at least that I can find now that I am looking at it with Gmail on my
laptop . While I am not a developer, I have been working closely with
them on a couple of possibly related problems. Clearly there is a
problem which needs to be documented in a fresh bug report.
It appears that Eric Coats' problem as he originally presented it
relates mostly to changes that GnuCash made in some releases in the
3.x and 4.x series in the behavior of the logic surrounding the
process of balancing the exchange rates applied when transactions are
created with multiple currencies and/or securities. There is a lot of
interaction that may or may not be consistently applied if the
transaction creation is done manually, by cloning a previous
transaction or by the Since Last Run assistant, and possibly other
nuances as well. This was complicated by a clarification of the
actual action that happens when the "Nearest in Time" method is
selected vs when the new "Nearest Before" method is selected as
described in https://bugs.gnucash.org/show_bug.cgi?id=743753
<https://bugs.gnucash.org/show_bug.cgi?id=743753>. Release 4.6 also
contained a fix<https://bugs.gnucash.org/show_bug.cgi?id=797928
<https://bugs.gnucash.org/show_bug.cgi?id=797928>> that was supposed
to resolve problems with the Since Last Run assistant that may have
impacted this in an unforeseen way.
It may be necessary for Eric to provide a very detailed description of
which version of GnuCash he is actually using including whether if is
a flatpak version or user compiled, then keystroke-by-keystroke to get
the inconsistent result. Then, if it is possible to resolve them as a
work-around for the current release by adjusting exchange rates, for
example, we should get a handle on the problem.
The share/price/value relationship is a separate issue which is a
little awkward but not known to be broken and probably does not apply
to Eric's problem.
--
David Carlson
_______________________________________________
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.
