Bug 230743 - gnucash transaction entry window description field misbehaves
gnucash transaction entry window description field misbehaves
Product: Fedora
Classification: Fedora
Component: gnucash (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 2007-03-02 12:00 EST by P Jones
Modified: 2014-03-16 23:05 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-03-02 12:31:07 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Desktop 380384 None None None Never

  None (edit)
Description P Jones 2007-03-02 12:00:37 EST
Description of problem: Multiple unexpected (compared to gnucash 1.8.x series)
behavior issues with the "Transfer Funds" window, accessed by Ctrl+T or menu
Actions > Transfer... See step by step below.

Version-Release number of selected component (if applicable): gnucash 2.0.2,
2.0.4, 2.0.5 FC6 versions

Steps to Reproduce:
1. Open gnucash file
2. Select an account to transfer money from
3. Ctrl+T for "Transfer funds" window
4. Enter amount (works fine), tab to date (works fine), tab to Num (works fine),
tab to Description (problems start).
5. Start typing a description; after the first letter is typed, gnucash fills in
the field with a previously entered description. If a second letter is typed,
the second letter is placed before the description that gnucash remembered. For
example, I intend to type in "John"; I type "J", gnucash enters "Junk", I type
"o", and now on the description line I have "oJunk". Subsequently typed letters
will be entered in front of the description that gnucash remembered. At the end
of my example, I would have "ohnJunk".
Actual results:

Expected results:

Additional info:
Comment 1 Bill Nottingham 2007-03-02 12:31:07 EST
This is something that is unlikely to be fixed in Fedora before it's fixed
upstream. You can track the upstream status of this issue at:

Comment 2 P Jones 2007-03-02 13:33:01 EST
Figured that. I'll paddle upstream and follow along there. Thanks for the link Bill.

Note You need to log in before you can comment on or make changes to this bug.