The little clock in the lower right was working fine until I had to boot another OS on the same machine. When I tried to reset it in Kwheezy it would not stay set. I gave up and now it randomly bounces between local time and GMT each time I boot. When I hover the mouse over the clock it always says the dispalyed time is local whether it is actually local or GMT.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can say with confidence this is not a bug in Debian wheezy, and therefore Kwheezy.
Basically, when you install any OS, the hardware clock can either be set to local time or UTC. Kwheezy actually let's you choose at installation which one this is. So if you dual-boot you should align the 2 OS's to the same. Otherwise they will keep changing the time to suit one another. Kwheezy uses ntpd by default, a daemon that updates the clock from a time-keeping server on the internet.
Earlier versions of windows were always local time, but I think Vista upwards can be changed. I'm not sure of the default though. Some other Linux distros will let you choose, some will set it one or the other for you.
Also, the preferences for the KDE Plasma applet clock in the bottom right will help you get what you want. Right click on it and select "Digital Clock Settings", then "Timezones". Tick the ones you want to appear in the hover over, and select the clock deafults to: local time. Then in the KDE time and date settings select your timezone and apply the setting.
It's just about getting the right settings. Kwheezy will set it up correctly if you answer the questions at installation correctly.
It's your dual-boot that's complicating things. Come to think of it: these days about 70% of kwheezy support queries and problems pertain to dual-boot. I don't recommend dual-booting myself, especially not on the same drive. But there's nothing wrong with it if you know what you're doing. I would rather recommend using VirtualBox for the secondary OS, especially if it's Windows. If the intent is to take a distro for a test drive, an external HDD would be a good choice. First disabling the internal HDD in BIOS in case the installer decides to mess up the primary OS's MBR.
Sorry, I digress and risk being patronising.
Last edit: Euan Thoms 2014-03-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, so I monitored this for some time, and confirmed that the displayed time bounces between local and GMT even when I do NOT boot another OS between Kwheezy sessions. Now I have doubly confirmed it because GRUB suddenly has only Kwheezy as a boot option -- all the other OSs have disappeared. Yet yesterday GMT was displayed and today local time. I don't mind being randomly tossed back and forth across the Atlantic but I do need to be able to boot Windows from time to time. Googling I see ways to bring a dead GRUB back to life but I am not sure how to redo the installation process where GRUB searches your hardware rather than its own files to find OSs. Is there a way to redo the installation?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure what's happening, my 3 machines are fine. When this happens, can you check the output of the "date" command (from terminal). maybe it's just the KDE clock that's bouncing.
More thought on the time issue. I think I saw something like once on one of my machines. But not for a long time now. All I did to fix it was re-assure some settings in 'Digital Clock Settings" (bottom right of panel) and "Adjust Time and Date".
Digital Clock Settings:
In time zones, untick everything and select Clock defaults to: Local. then Apply, OK.
Adjust Time and Date:
In Time Zone, select your time zone and apply.
Now once it all looks good, you may add back any additional time-zones in Digital Clock Settings. Check date command shows correct time.
It stabilized for me, no iddea what caused it. It must be a Debian thing, maybe triggered by updates. I don't think anything in Kwheezy development would have effected this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am having this same problem, always one hour ahead on reboot, no matter how many times I reset the timezone etc.
Not a huge spoiler, but looks embarassing when trying to convince someone to maybe switch from Windows.
Excellent distro otherwise.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The little clock in the lower right was working fine until I had to boot another OS on the same machine. When I tried to reset it in Kwheezy it would not stay set. I gave up and now it randomly bounces between local time and GMT each time I boot. When I hover the mouse over the clock it always says the dispalyed time is local whether it is actually local or GMT.
I can say with confidence this is not a bug in Debian wheezy, and therefore Kwheezy.
Basically, when you install any OS, the hardware clock can either be set to local time or UTC. Kwheezy actually let's you choose at installation which one this is. So if you dual-boot you should align the 2 OS's to the same. Otherwise they will keep changing the time to suit one another. Kwheezy uses ntpd by default, a daemon that updates the clock from a time-keeping server on the internet.
Earlier versions of windows were always local time, but I think Vista upwards can be changed. I'm not sure of the default though. Some other Linux distros will let you choose, some will set it one or the other for you.
You can change the Kwheezy hardware clock setting by following the wiki on the Kwheezy website:
http://www.kwheezy.com/en/weblog/2013/08/02/set-hardware-clock-local-time/
Also, the preferences for the KDE Plasma applet clock in the bottom right will help you get what you want. Right click on it and select "Digital Clock Settings", then "Timezones". Tick the ones you want to appear in the hover over, and select the clock deafults to: local time. Then in the KDE time and date settings select your timezone and apply the setting.
It's just about getting the right settings. Kwheezy will set it up correctly if you answer the questions at installation correctly.
It's your dual-boot that's complicating things. Come to think of it: these days about 70% of kwheezy support queries and problems pertain to dual-boot. I don't recommend dual-booting myself, especially not on the same drive. But there's nothing wrong with it if you know what you're doing. I would rather recommend using VirtualBox for the secondary OS, especially if it's Windows. If the intent is to take a distro for a test drive, an external HDD would be a good choice. First disabling the internal HDD in BIOS in case the installer decides to mess up the primary OS's MBR.
Sorry, I digress and risk being patronising.
Last edit: Euan Thoms 2014-03-03
OK, so I monitored this for some time, and confirmed that the displayed time bounces between local and GMT even when I do NOT boot another OS between Kwheezy sessions. Now I have doubly confirmed it because GRUB suddenly has only Kwheezy as a boot option -- all the other OSs have disappeared. Yet yesterday GMT was displayed and today local time. I don't mind being randomly tossed back and forth across the Atlantic but I do need to be able to boot Windows from time to time. Googling I see ways to bring a dead GRUB back to life but I am not sure how to redo the installation process where GRUB searches your hardware rather than its own files to find OSs. Is there a way to redo the installation?
Hi friends!
I am reporting the same phenomenom here, my lap has one HDD dedicated to kwheezy 1.4 or 1.5? and there is no way to adjust local time vs GMT
I'm not sure what's happening, my 3 machines are fine. When this happens, can you check the output of the "date" command (from terminal). maybe it's just the KDE clock that's bouncing.
To set hardware clock to local time look at the wikis here: http://www.kwheezy.com/en/weblog/2013/08/02/set-hardware-clock-local-time/
As for grub: type the following as root (terminal):
As long as you drives are attached, it should pick up the other OSes and add them to Grub menu. If not, try adding them manually.
http://askubuntu.com/questions/54439/how-do-i-add-another-distribution-to-grub2
Maybe you need to add boot flag to the other root filesystems. Do you have os-prober installed?
More thought on the time issue. I think I saw something like once on one of my machines. But not for a long time now. All I did to fix it was re-assure some settings in 'Digital Clock Settings" (bottom right of panel) and "Adjust Time and Date".
Digital Clock Settings:
In time zones, untick everything and select Clock defaults to: Local. then Apply, OK.
Adjust Time and Date:
In Time Zone, select your time zone and apply.
Now once it all looks good, you may add back any additional time-zones in Digital Clock Settings. Check date command shows correct time.
It stabilized for me, no iddea what caused it. It must be a Debian thing, maybe triggered by updates. I don't think anything in Kwheezy development would have effected this.
I am having this same problem, always one hour ahead on reboot, no matter how many times I reset the timezone etc.
Not a huge spoiler, but looks embarassing when trying to convince someone to maybe switch from Windows.
Excellent distro otherwise.