Strange orphan behavior on creating new transactions

[Mark Johnson]

Is it perhaps this one:
http://bugzilla.gnome.org/show_bug.cgi?id=166101
?

Transactions can disappear if you change the split anchoring that 
transaction to the register you currently have open.  Once the 
transaction has no splits belong to the register's account, it no longer 
belongs there, and disappears.  This behaviour is "correct", but I 
believe confusing to the user.
(See http://bugzilla.gnome.org/show_bug.cgi?id=301264)

If it is this bug, there is a work-around: never change the account name 
which anchors the transaction to this register.  Not even if you place 
another split anchoring the transaction to the account!  Only change the 
amount of the split anchoring the transaction to the account.  I've 
developed this as a habit, and have not triggered the above bug since.

I do see from the comments that it was observed as recently as 1.9.2.

Mark


Adam Rosi-Kessel wrote:

>I've just started noticing a strange behavior with 2.0.1-1 (in Debian
>Sid).
>
>Sometimes, when adding a transaction, the transaction disappears
>immediately after I enter it. I have to go look for it, and it turns out
>the half that should have been visible from the account I was in is now
>assigned to Orphan-USD.
>
>When I edit the transaction with a split and move it back to the account
>it was supposed to come from, the balance for that line always reads 0.00
>no matter what the actual balance is. Subsequent items calculate the
>balance as if that item never happened.
>
>Seems pretty clearly a bug -- just wondering if anyone else has noticed
>or has ideas about how to avoid.
>_______________________________________________
>gnucash-user mailing list
>gnucash-user at gnucash.org
>https://lists.gnucash.org/mailman/listinfo/gnucash-user
>-----
>Please remember to CC this list on all your replies.
>You can do this by using Reply-To-List or Reply-All.
>
>  
>