[SOLVED] Bug Report: Task Bar Clock???

Bug Report: Task Bar Clock

I think I may have found a bug in Zorin 32-bit. . .

"24-hour time" incorrectly reports time after 1259 hours.

For instance - 9:00 PM (USA time) in 24-hour time mode should be reported: 2100 hours. Instead, it is reported as: 9:00.

Any resolve available for this issue?

Thank you in advance!

~erko

------------------------------------------------------

lek-HP-Pavilion-dv1000-EH454UA-ABA

Ubuntu
Release 11.04 (natty)
Kernel Linux 2.6.38-13-generic
GNOME 2.32.1

Hardware
Memory: 2.0 GiB
Processor: Intel(R) Pentium(R) M processor 1.60GHz

System Status
Available disk space 80.2 GiB

I am using Zorin 5.2 32bit. I have just tested the clock settings and it works just fine.

Does the problem appear after a certain period of time?

Have you set the "time&date settings" to manual or to automatic by the internet?

Hi "madvinegar!"

It needs to be scrutinized after 1259 hours (12:59 PM). So, 1:00 PM should actually report as: 1300 hours.

I noticed last evening (and that is why I mentioned here) that 2100 (9:00 PM) hours was being reported as 9:00.

I have the 'Time & Date' set for: "Automatically from the Internet."

Thank you so much for your time & effort!

~erko

Try setting it to manual and see if that improves the problem.

Also, I am guessing that there may be a non-agreement between your clock settings and your regional formats in language support. Check that as well.

Finally, have you installed zorin in parallel with any other OS?

Hi "madvinegar!"

I don't know what to say or how to explain it, but now the Zorin Task Bar Clock, in 24-Hour mode, is reporting time accurately, namely: 15:49 (for 3:49 PM).

I'll try to remember to make it a point to look at Zorin around the 2100 hour time to see if it'll repeat the anomaly from what it reported last evening.

So, by tomorrow, if all is well, I'll mark this one "SOLVED" and sheepishly apologize for wasting anybody's and everybody's time and effort over this.

Thank you so much!

~erko

Hi " madvinegar!"

I've checked the clock's performance again, once at 2110 hours (reported accurately as: 21:10 hours), 04-11-12, and again now - 0133 (reported accurately as: 01:33 hours), 04-11-12.

The clock is obviously now doing exactly what it is supposed to do. Therefore, I cannot explain the anomaly initially reported. I can only report what I saw here is what I saw, back then.

Bottom line, Zorin system clock seems to be 'A-OK,' now, and I humbly apologize for causing a stir of undue time and effort on your part. Sorry!

I'm marking this issue "SOLVED."

~erko

Glad that you got it fixed (or it fixed itself...)
In any case, all seems to be ok now, and this is what matters!