Bug 1566741

Summary:	Date entry in GNUCash 3.0 in F28 is completely unusable in Persian
Product:	[Fedora] Fedora	Reporter:	Hedayat Vatankhah <hedayatv>
Component:	gnucash	Assignee:	Bill Nottingham <notting>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	28	CC:	notting, notting
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-21 04:16:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Hedayat Vatankhah 2018-04-12 22:03:15 UTC

Description of problem:
The Date column in an accounts data entry is completely useless. I cannot select today at all. With every click, it jumps to another year! Also, using -/+ buttons to go to prev/next day doesn't work! both of them decrease the year field.

Also, just clicking on a row will change its date!

Summary: it is completely useless!

Version-Release number of selected component (if applicable):
gnucash-3.0-1.fc28.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Run GnuCash
2. Create a new file
3. Go to an account and try to enter a new row

Or
Open an existing file (From GnuCash 2.6)
Open an account and select a row and see its date is modified


Actual results:


Expected results:


Additional info:

Comment 1 Hedayat Vatankhah 2018-04-13 19:32:24 UTC

Tried with export LC_TIME=en_US.UTF-8, and it worked fine.
The bug happens when LC_TIME=fa_IR.UTF-8 (and probably some other locales).

Comment 2 Bill Nottingham 2018-04-14 04:52:32 UTC

I've reproduced this, but only for Farsi so far - other RTL languages such as Hebrew and Arabic work.

Sent upstream https://bugzilla.gnome.org/show_bug.cgi?id=795247.

Comment 3 Hedayat Vatankhah 2018-04-14 13:14:47 UTC

Thanks :)

Comment 4 Bill Nottingham 2019-02-21 04:16:54 UTC

This got fixed in 3.2.