After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 125576 - amounts missing from one side of transactions
amounts missing from one side of transactions
Status: VERIFIED INCOMPLETE
Product: GnuCash
Classification: Other
Component: Register
1.8.x
Other Linux
: Normal normal
: ---
Assigned To: David Hampton
Chris Shoemaker
Depends on: 130451
Blocks:
 
 
Reported: 2003-10-27 07:29 UTC by g mottster
Modified: 2018-06-29 20:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description g mottster 2003-10-27 07:29:25 UTC
it appears i have a situation where the amounts are missing from one side
of some of my transactions.

for example in my credit card account i have several transactions to the
dining account, but in the dining account, several of those same
transactions appear to have no amount.

if one of these transactions is brought forward as template in the process
of entering a new transaction, the new transaction has the same problem.

i have had some success in entering new transactions that were ok and
deleting the bad ones.

but now i have a situation where i am trying to enter a transaction with 3
splits, and repeatedly i get a bad transaction!  (gnucash-1.8.7)
Comment 1 Derek Atkins 2003-10-30 05:26:53 UTC
How were these transactions entered into GnuCash?

Are the accounts of the same commodity type?

Are there any messages on the terminal where you ran Gnucash?
Comment 2 g mottster 2003-10-30 07:32:09 UTC
entered either via register or general ledger.  the most contrived
method for entering transactions i have done a few times is to use a
transaction that is similar in a different account, start a new
transaction that autocopies it, press split, change the current
account split to a different account, and accept the transaction, such
that it disappears from the current register window and appears in the
other account.  i am not saying that these transactions were entered
in this way, tho it is possible.

funny you should ask, these transactions do involve one US$ account
and one UK£ account.

launch gnucash:
Warning: xaccTransScrubCurrency: no common transaction currency found
Warning: xaccTransScrubCurrency: no common transaction currency found

whenever i open any account, even one with no transactions:
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion

whenever entering a transaction and a previous transaction is matched,
even if both parts of the transaction are US$, when i press tab out of
the description field:
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion

upon accepting the new (either single or multi currency) transaction:
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion
Error: gnc_mbstowcs: bad multi-byte conversion
Error: gnc_quickfill_insert: bad text conversion

press save:
** CRITICAL **: file sixtp-dom-generators.c: line 93
(commodity_ref_to_dom_tree): assertion `c' failed.
Comment 3 g mottster 2003-11-05 06:39:39 UTC
seems that i'm only occationally able to enter a 3 way, two currency
transaction that's ok, more usually at least one of the account views
has amounts missing.

do you think this has something to do with my datafile, or can you
reproduce it outright?
Comment 4 g mottster 2004-05-08 12:26:53 UTC
just tripped over this bug again, using 1.8.8 now for awhile, don't see this bug
everyday.

this time it happened while trying to expand a simple same-currency transaction
to a 3 way split.  or at least i thought it was same-currency.  turns out, when
i ask for "Edit Exchange Rate", it *does* bring up the dialog, for *both* of the
original 2 parts of the transaction, showing exchange rate of "1".  in other
words, it appears to be a transaction that *is* doing currency conversion, from
the same currency to the same currency.

and i bet i know how i got some such transactions lying around.  when entering a
transaction, getting an autocopy from an existing transaction that does do
currency conversion, and then when i change the account to a same-currency
account, i end up with a same-currency double-currency-converting transaction.

that's merely to explain how the pre-existing, so far harmless transaction must
have got there.  now, when i try to add a 3rd split to such a transaction, i
quite often (always?) will get the behaviour where one of the splits has no
amount, and can't be fixed, except by deleting the transaction.
Comment 5 Chris Shoemaker 2006-03-17 18:44:11 UTC
I think it's 80% likely that this is just fall-out from bug#130451 but since I'm not sure I'm marking this bug as depending on 130451 instead of closing as a dup.
Comment 6 Christian Stimming 2006-09-04 11:45:36 UTC
Does this issue also occur in the 2.0.x versions? Development on 1.8.x has
stopped, so please upgrade to 2.0.x (most current is 2.0.1) and see whether
this problem still occurs.
Comment 7 Christian Stimming 2006-10-02 13:00:36 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 8 John Ralls 2018-06-29 20:38:22 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=125576. Please update any external references or bookmarks.