Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 230743 - gnucash transaction entry window description field misbehaves
Summary: gnucash transaction entry window description field misbehaves
Alias: None
Product: Fedora
Classification: Fedora
Component: gnucash
Version: 6
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-02 17:00 UTC by P Jones
Modified: 2014-03-17 03:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-03-02 17:31:07 UTC
Type: ---

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 380384 0 None None None Never

Description P Jones 2007-03-02 17:00:37 UTC
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 17:31:07 UTC
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 18:33:01 UTC
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.