Mailinglist Archive: opensuse-factory (1210 mails)
| < Previous | Next > |
Re: [opensuse-factory] bad clock
- From: "Larry Stotler" <larrystotler@xxxxxxxxx>
- Date: Sun, 2 Nov 2008 10:51:57 -0400
- Message-id: <9bb996600811020651k63aeb043pab0963de31b8647f@xxxxxxxxxxxxxx>
On Sun, Nov 2, 2008 at 10:02 AM, Felix Miata <mrmazda@xxxxxx> wrote:
I dunno. Both my laptops have the correct time(which is how I knew
that the time had changed since my son's watch has said the wrong
time) when I got up. Both are running 11.0 and KDE3.x
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
Can anyone confirm that the time zone offset bug is back again in 2.6.27.4-2
beta 4 & KDE3? I'm in EST, where offset is -0500 currently. Every time I
boot, the clock shows a net offset of -1000, even though the local time
correctly stored in the BIOS is @ -0500, and /etc/adjtime contains LOCAL on
last line. I configured my clock by right click on KDE3 Kicker clock to use
"set date & time automatically". It put no uncommented pool servers in
/etc/ntp.conf, but even when I add server 0.pool.ntp.org and 1.pool.ntp.org
either manually or using YaST2 date/time config the wrong behavior remains.
I dunno. Both my laptops have the correct time(which is how I knew
that the time had changed since my son's watch has said the wrong
time) when I got up. Both are running 11.0 and KDE3.x
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |