Time keeping problem is ir software or hardware?
 

What keeps changing my desktop clock 12 hr time to 24 hr time and losing correct time in the hardware clock?
When the desktop time changes I check BIOS clock and notice that it can either be the same or different.
I'm using Mint14Cinnamon. I set desktop to non network and close Date &Time settings. I work with programs on the computer a while and go back to Date&Time settings and Network setting is checked. This can happen also when shutting down and re booting.
I've reset CMOS by removing battery and 20 minutes later replace the battery with new one said to be good until 2015.
I just got this board back from a second RMA for previous two boards having same/similar problems.
Is Mint broken? Is motherboard in need of a 3rd RMA? Should I go back to Windoze?
Use to be an Ubuntu user until they flaked it out with Unity. It seems Mint is doing th same with it's desktop options.
Bring back the desktop used in Ubuntu 10.04 and 10.10 please...
I swear since Ubuntu 10.04 Linux has gone the way of Windoze. Thanx if you can help!!!%:))SW
This is a year old build: TA75M/A4-3300/8gbKingstonPC3HyperX1333/Seagate1tb/LGcd/dvd drive/ Antec Basiq430w.

Please post your thread in only one forum. Posting a single thread in the most relevant forum will make it easier for members to help you and will keep the discussion in one place. This thread is being closed because it is a duplicate.

Ubuntu is Linux, but Linux is not Ubuntu. The direction Ubuntu is going is not true for all of Linux.

Now that that is out of the way, you say you have used both Ubuntu and Mint, but you do not say if the time issue was a problem with both systems. If the problem does not exist with Windows, it is unlikely a hardware issue. If the problem has only existed with Mint, then that is where the problem lies. Switching between 12 and 24 time is probably due to something in the system's or GUI's time settings. At this time, the only guess I can venture is a relationship with;
Not synchronising with internet time? If so, try network instead of non-network, and see what happens.