casper isn't touching the clock at boot time.
ntpdate is triggered by ifupdown which sets the clock to the right time. The
timezone is going to be UTC until a location is selected in ubiquity at which
point the clock will change to reflect the timezone change.
I think the current behaviour is co
** Changed in: casper (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/105519
Title:
livecd clock is (inevitably) wrong
To manage notifications about this
Instead of setting the system clock (which appears to be 436535) can the
LiveCD not just read the system clock? If it's wrong once the LiveCD is
booted I imagine (I'm new) that Ubuntu can be used to set it manually.
(Posted a similar comment in 436535 since while not the same the
solution might be
Agree with Tormod Volden : the live CD should not modify the hardware clock.
See https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/436535 which might
be a duplicate
--
livecd clock is (inevitably) wrong
https://bugs.launchpad.net/bugs/105519
You received this bug notification because you a
The live CD should absolutely not touch the hardware clock, that would
be a separate bug.
BTW, disregard my comment 5, it turned out to be the ext3/4 journal
replay issue, now solved.
--
livecd clock is (inevitably) wrong
https://bugs.launchpad.net/bugs/105519
You received this bug notification
Karmic:
The life CD seems to change the hardware clock to UTC, with the side effect,
that Vista has UTC after the session.
And Vista doesn't even recognize (which is not the fault of Ubuntu, I
know )
IMHO it would be better to leave the time unchanged, because on a live
CD session the real exact
There is also a problem if you mount a disk using the live CD, and then
boot back into a normal installation. If you are in a UTC+something
timezone, the last mounted timestamp will be in the future, and a file
system check will be unnecessarily run.
--
livecd clock is (inevitably) wrong
https://
** Also affects: casper (Guadalinex)
Importance: Undecided
Status: New
--
livecd clock is (inevitably) wrong
https://bugs.launchpad.net/bugs/105519
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
dhcp has a timezone option. I might not be widely used, but dhclient on
the livecd should be configured to request timezone or location or
whatever the option is. Then if the server does support it, you're all
set.
DHCP also supports a list of NTP servers, although that's not so
necessary since
Henrik Nilsen Omma writes ("[Bug 105519] Re: livecd clock is (inevitably)
wrong"):
> One option would be to not show the clock in the Live session ...
That would be an improvement, I think.
Ian.
--
livecd clock is (inevitably) wrong
https://bugs.launchpad.net/bugs/105519
You rece
Unless we can devise some clever way for the Live CD system to figure
out where you are, this will often be wrong for people with UTC system
clocks, indeed.
One option would be to not show the clock in the Live session ...
** Changed in: casper (Ubuntu)
Importance: Undecided => Low
Stat
** Tags added: iso-testing
--
livecd clock is (inevitably) wrong
https://bugs.launchpad.net/bugs/105519
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
gnome-panel is using the system timezone
** Changed in: casper (Ubuntu)
Sourcepackagename: gnome-panel => casper
--
livecd clock is (inevitably) wrong
https://bugs.launchpad.net/bugs/105519
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for U
13 matches
Mail list logo
