Live CD changes BIOS clock
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I use a laptop that usually runs Windows XP. To try out Ubuntu 9.10 on it, I booted Ubuntu from the Live CD, selecting the boot screen's menu item "Try Ubuntu without any change to your computer". Ubuntu booted up; I played around with it for a while; everything went fine so far. Although Ubuntu's clock was set to different time than Windows' -- GMT I guess -- that was no problem for the purpose of trying it out.
The problem appeared when I shut down Ubuntu and rebooted into Windows: The system clock still showed the time to which Ubuntu had changed it. I had to correct it by updating Windows' system time. Ubuntu had changed the computer's BIOS clock.
Now, I admit that from a narrowly technical point of view, this bug in itself isn't a big deal. After all, it's almost trivial to work around. Nevertheless, it _is_ a serious problem for me that this behaviour breaks the deal Ubuntu had offered me before I booted it: "Try Ubuntu _without_
Best regards,
Thomas.
ProblemType: Bug
Architecture: i386
Date: Wed Dec 16 17:50:45 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/yelp
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: yelp 2.28.0-0ubuntu2
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: yelp
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
(gnome-
(gnome-
(nautilus:3389): Eel-CRITICAL **: eel_preferences
(polkit-
(yelp:3561): Yelp-WARNING **: Failed to load config file: No such file or directory
Same experiment with a LiveCD created from the latest download this evening.
I agree with Thomas that if one promises not to touch a user's computer, one should not touch a user's computer.