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 725406 - Can't set april 2nd as transaction date
Can't set april 2nd as transaction date
Status: RESOLVED DUPLICATE of bug 724211
Product: GnuCash
Classification: Other
Component: Windows
2.6.1
Other Windows
: Normal normal
: ---
Assigned To: gnucash-win-maint
gnucash-win-maint
Depends on:
Blocks:
 
 
Reported: 2014-02-28 16:44 UTC by David
Modified: 2018-06-29 23:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David 2014-02-28 16:44:45 UTC
I can't set april 2nd as date for a transaction from the account transactions tab. This seems to apply to any year.

Environment:

- GnuCash 2.6.1 (x86) on Windows 7 (64-bit).
- The GnuCash instance is localized as es_MX (mexican spanish) and date format is "dd/mm/yyyy".
- PostgreSQL 9.3.2 installed on same host as GnuCash.

Behavior:

- If I type "02/04/2014", it reverts to "01/04/2014" (april 1st).
- If I type "31/03/2014" and then press key "+", it doesn't forwards to april 1st, it stays on march 31. For any other date, "+" and "-" works perfectly.
- If I keep "+" pressed from a former date, it rolls until it stops at april 1st and advances no more.
- If I keep "-" pressed from a later date, it rolls until it stops at april 1st and advances no more.
- If I press the arrow button to display the date picker popup and click on "2" (april 2nd), two different behaviors may happen:
  1) it has no effect and the date is not changed.
  2) the popup closes but the date keeps unchanged.
- The saved date in the database is "01/04/2014" (april 1st).

I tested it again saving the file as XML and set en_US as locale (both for UI and date format) and the bug is still present.
Comment 1 John Ralls 2014-02-28 16:58:58 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 724211 ***
Comment 2 David 2014-03-02 09:48:38 UTC
Nice! Thanks. Is there any date for the next relase?
Comment 3 John Ralls 2014-03-02 14:37:49 UTC
Today, if all goes well. The Windows release is still building at the moment.
Comment 4 John Ralls 2018-06-29 23:27:40 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=725406. Please update any external references or bookmarks.