what show you the file /etc/sysconfig/clock and the command 'date' ?

/etc/sysconfig/clock

UTC=false
ARC=false
ZONE=Europe/Paris

date

dim. mai 13 15:26:22 CEST 2012

I see this as well, with a New York timezone (GMT-4) showing localtime - 4.  Resetting the timezone to something else, exiting draktime, and going back in and resetting it to New York appears to fix this.  Possibly related to bug#4944.

CC: (none) => ftg

I've seen this as well I think, as did MrsB, but we both thought we may have misselected something, but this seems to be more than just user error now... increasing severity

Priority: Normal => High
Severity: normal => major

Can you find out what your /etc/localtime file says?

It's a binary file, and it should essentially match what the, well localtime is. Generally speaking you can copy (or hardlink) the file from /usr/share/zoneinfo.

e.g. on my machine I have Europe/London set:

$ md5sum /usr/share/zoneinfo/Europe/London /etc/localtime
410c65079e6d14f4eedf50c19bd073f8  /usr/share/zoneinfo/Europe/London
410c65079e6d14f4eedf50c19bd073f8  /etc/localtime

Mine correctly is set to /usr/share/zoneinfo/Europe/Amsterdam. I think the problem is that it assumes my hardware clock is in localtime while I have it running on UTC. I don't think I was asked at install time if my hardware clock is set to local time or UTC.

Do you have ntpd running/installed?

In theory, the kernel will do localtime -> hw clock sync every 12 minutes when ntp is running.

my config :

one PC
2 os :
- my everyday os mandriva 2010.2 i586
 + ntp (Europe|France: fr.pool.ntp.org)
 + zone Europe/Paris

clock file :

UTC=true
ARC=false
ZONE=Europe/Paris

- mageia 2 for testing purpose
 + zone Europe/Paris

clock file :

UTC=false
ARC=false
ZONE=Europe/Paris

$ md5sum /usr/share/zoneinfo/Europe/Paris /etc/localtime
07c4012a5a941cd20bd4baab9b10e3f4  /usr/share/zoneinfo/Europe/Paris
07c4012a5a941cd20bd4baab9b10e3f4  /etc/localtime

during mageia installation installer does not ask for user any question about clock time

(In reply to comment #7)
> Do you have ntpd running/installed?
> In theory, the kernel will do localtime -> hw clock sync every 12 minutes when
> ntp is running.

No, I haven't (fyi, this was during a plain DVD install without choosing or deselecting any exotic options).

(In reply to comment #6)
> Mine correctly is set to /usr/share/zoneinfo/Europe/Amsterdam. I think the
> problem is that it assumes my hardware clock is in localtime while I have it
> running on UTC. I don't think I was asked at install time if my hardware clock
> is set to local time or UTC.

This has been my experience as well.  I believe that the install has historically assumed UTC unless it finds a Windows partition, in which case it assumes localtime.

Out of curiosity, does inst(In reply to comment #9)
> No, I haven't (fyi, this was during a plain DVD install without choosing or
> deselecting any exotic options).

Out of curiosity, does installing and starting ntpd.service make things work more smoothly (you may have to start it manually after reboot just now as I just realised I hadn't pushed an update for this package after a change in a different package)

(In reply to comment #11)
> Out of curiosity, does installing and starting ntpd.service make things work
> more smoothly (you may have to start it manually after reboot just now as I
> just realised I hadn't pushed an update for this package after a change in a
> different package)

I didn't reboot yet, but install ntp and doing systemctl start ntpd.service sets the time correctly.

(In reply to comment #11)

> Out of curiosity, does installing and starting ntpd.service make things work
> more smoothly (you may have to start it manually after reboot just now as I
> just realised I hadn't pushed an update for this package after a change in a
> different package)

I always select ntp in the Summary part of install, but I didn't check to see whather it had been started.  It's possible that the mucking around with MCC draktime as described in bug#4944 started it.

*** Bug 5965 has been marked as a duplicate of this bug. ***

CC: (none) => isolde

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

I never had problems with time in any rc or pre2 with LXDE (didn't try KDE), but now I have a problem in 2 final with KDE. It still works well in LXDE.

Which DEs did you use when you had this problem?

CC: (none) => marja11

i use kde

mageia 2 x86_64

pb still there

cc'ing kde team

Anyone who didn't yet say which DE is used when seeing this bug, please say so.

So far episteme, Carolyn (from the duplicate) and I have it in KDE, I do *not* have it in LXDE

Keywords: NEEDINFO => (none)
CC: (none) => anaselli, balcaen.john, dmorganec, lmenut, nicolas.lecureuil, watersnowrock
Hardware: i586 => All
Summary: mageia2rc, wrong clock time => wrong clock time in KDE
Whiteboard: (none) => MGA2TOO

I'm not getting this problem regularly with KDE and in fact I thought it had been solved, but a few days ago I went out shopping and when I came back the clock applet had changed to showing an hour earlier, even though the date and time settings were still correct.  I rebooted, same again.  The following day the problem had gone and I haven't had it again since.

Carolyn

Mageia 3 alpha 2

using kde

pb still there

Funny, i haven't had it till yesterday when it was one hour later. I restarted
ntp and all went ok. Today is ok again. 

KDE env, x86_64 arch on norebook.

Angelo

i complete my comment #21

i installed mageia 3 alpha 2 x86_64
then
i open for the first time a kde session
then
i see clock indicates 10 h 23 instead of 11 h 23

i use mandriva 2010.2 i586 as my main distribution with ntpd on the same pc where i test mageia 3

i understand the pb.

my every day os mandriva 2010.2 write the utc time in the hardware clock.

mageia assume hardware clock time is local time (Paris,FR) and does not add 1 h
then display utc time instead of local time

but in another pc hardware clock may be local time.

there is no way to know if it is local time or utc time
then
the sole solution (as mandriva installation does) is too ask for the user what is the right time by displaying :

- hardware clock time
- hardware clock time + 1

obviously this must be generalized  with localization time shifting and saving energy time shifting

You can choose bios set to UTC or local time at the summary stage of the installer.

I just filed https://bugs.mageia.org/show_bug.cgi?id=9562 as an independant bug since it is clearly (exclusively ?) related to how the digital clock applet displays the time. But it looks like these 2 bugs are related.

CC: (none) => juergen.harms

@Juergen: since M3 installer will not be fixed, please change whiteboard to 5beta1 if it is still seen there, or alternatively kindly close it. Thanks v.m.

No answer

Status: NEW => RESOLVED
CC: (none) => thierry.vignaud
Resolution: (none) => OLD