Bug 530495

Summary: yast2-ntp configure shows incorect values
Product: [openSUSE] openSUSE 11.2 Reporter: Jan Albrecht <jan.albrecht>
Component: YaST2Assignee: Jiří Suchomel <jsuchome>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: forgotten_tAfYx3p_c_, mvidner
Version: Factory   
Target Milestone: ---   
Hardware: x86-64   
OS: SUSE Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: screenshot after "Synchronize now"

Description Jan Albrecht 2009-08-12 17:39:55 UTC
Created attachment 312350 [details]
screenshot after "Synchronize now"

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-1.2 Firefox/3.5.2 GTB5

If I use the yast2-ntp module to configure time and date on openSuSe 11.2  Milestone 5 the values are displayed in false order.

Choose i.e. de.pool.ntp.org as NTP server, use "Synchronize now".
Result:

Date is shown in "Current Time" fields:

Current Time in HH:MM:SS Format
                                                     2009? 08??? 12???

Time is shown in "Current Date" fields.

Current Date in DD-MM-YYYY Format
                                                     17??? 31??? 19???

Nevertheless values are accepted by the system and set to correct date and time.
If you use yast2-ntp again, again the values are displyed in the wrong fields.

Reproducible: Always

Steps to Reproduce:
See BUG inital text to reproduce.
Comment 1 Martin Vidner 2009-09-02 12:29:16 UTC
Interesting. To reproduce:
# yast timezone, Change
y2log says:
2009-09-02 14:26:53 <1> nekobasu(11605) [YCP] Timezone.ycp:755 GetDateTimeMap dparts ["2009", "09", "02", "14", "26", "53"] ret $["day":"53", "hour":"2009", "minute":"09", "month":"26", "second":"02", "year":"14"]
Comment 2 Jiří Suchomel 2009-09-02 12:51:41 UTC
Interesting, indeed.
Fixed in yast2-country-2.18.16
Comment 3 Gabriele Mohr 2009-10-13 08:22:03 UTC
*** Bug 530154 has been marked as a duplicate of this bug. ***