Clock

[pedora]

This app STILL doesn't work?!?

I searched the forum and still no 'fix.' This is the *only* distro I have tried/used that doesn't have a time on my desktop.

Fedora is becoming Mickey Mouse.

[pedora]

Any reason no one cares to work on certain issues? Examples: the pathetic clock that doesn't work... the live usb application that also doesn't work...

[leigh123linux]

Please don't double post again.

[newiLuvatar]

clock is working just fine here, and if I remember correctly, it always has (since fc4...)

[pedora]

clock is working just fine here, and if I remember correctly, it always has (since fc4...)
I don't think so.

I just searched the forum and several people were discussing how you can't change the time or settings.

I added the widgit for the clock, 'Digital Clock' and the local time is wrong. I don't see any way to change it. I am using Fedora KDE.

You should be able to set or reset the time. It's a GUI!

---------- Post added at 11:27 AM CST ---------- Previous post was at 11:26 AM CST ----------

I guess I can't ask for support since I'll just be told by a few people that it already works.

That's what happened when I asked for support for the Live USB iso application.

[leigh123linux]

I don't think so.

I just searched the forum and several people were discussing how you can't change the time or settings.

I added the widgit for the clock, 'Digital Clock' and the local time is wrong. I don't see any way to change it. I am using Fedora KDE.

You should be able to set or reset the time. It's a GUI!

---------- Post added at 11:27 AM CST ---------- Previous post was at 11:26 AM CST ----------

I guess I can't ask for support since I'll just be told by a few people that it already works.

That's what happened when I asked for support for the Live USB iso application.


Post #2 that you claim is a support question is just another pathetic rant IMO as there is no relevant info or issue defined.


P.S Your Live USB question was also a double post.

http://forums.fedoraforum.org/showthread.php?t=237934

[beaker_]

Both big and little hands are pointing to lunch here. I suggest you change the time on that pc.

[pedora]

Post #2 that you claim is a support question is just another pathetic rant IMO as there is no relevant info or issue defined.


P.S Your Live USB question was also a double post.

http://forums.fedoraforum.org/showthread.php?t=237934
I meant to change it from a rant to a question. I am curious what the answer is as to why it is so difficult to use a clock.

I didn't think the usb question was a double post. Someone replied saying it works and someone else replied saying to use a certain method but I responded that I tried it already. If you read any of the responses in the usb threads, I am saying I tried the built-in application in Fedora and also UNetbootin both in Linux AND in Windows. Each method which totals three (if you want to be technical) doesn't work with Fedora 12. At least, on my machine. I created it on a powerful desktop and could not boot it on a Thinkpad T41.

As for the clock, I am more intrigued and surprised that the clock program is so buggy (imho). Or incomplete. It might be a KDE thing but I have KDE in other distros and the clock works. The time is right and I believe the time settings can be changed. I'll double check, though. I was just hoping someone had an explanation about the clock.

---------- Post added at 01:00 PM CST ---------- Previous post was at 12:57 PM CST ----------

Both big and little hands are pointing to lunch here. I suggest you change the time on that pc.
'Can't change the time on the analog clock, 'can't change the time on the digital clock. Why should I change the time on the PC when the time on other states (i.e. operating systems) are correct? At min., I can adjust the setings. This shouldn't be a 'hardware' problem and it isn't.

P.S. my clock displays '8.0*' right now... I guess it's not lunch time, it's breakfast.. :-/

[Keith1]

login as root
at the command prompt type chkconfig ntpd on.
then type reboot

[smr54]

You might also be able to avoid the reboot with

ntpdate pool.ntp.org

Then

service ntpd start
chkconfig ntpd on

Afraid I can't offer much more than that--I use fluxbox and the clock is fine. Is it possible that you have it set to UTC and you want it at localtime and vice versa.

Speaking as a relative newcomer to the forums, my impression is quite different than yours--while some problems may not be solved, the majority of questions here seem to be answered rather quickly.

[pedora]

I'll try these, thanks.

I don't really like ranting but sometimes it is frustrating. I agree, some questions are answered really quickly, imho.

Maybe some topics aren't as interesting or it's not as crucial to get them fixed. I would suppose that maybe some *problems* aren't as common but I can't help but think a lot of people like having the time on their computer among other things. I am a bit disappointed that the usb topic is not more heavily discussed. I thought it is cool to be able to boot up live media at a much faster speed than CD or DVD.

---------- Post added at 01:55 PM CST ---------- Previous post was at 01:48 PM CST ----------

You might also be able to avoid the reboot with

ntpdate pool.ntp.org

Then

service ntpd start
chkconfig ntpd on

Afraid I can't offer much more than that--I use fluxbox and the clock is fine. Is it possible that you have it set to UTC and you want it at localtime and vice versa.

Speaking as a relative newcomer to the forums, my impression is quite different than yours--while some problems may not be solved, the majority of questions here seem to be answered rather quickly.
I'm not sure which command but one of them gave me an error:

SELinux is preventing rpcbind (rpcbind_t) "setgid" rpcbind_t.

---------- Post added at 01:58 PM CST ---------- Previous post was at 01:55 PM CST ----------

The time was correct when I looged in as root but it didn't change when I logged back in as user. The time is still wrong.

[scott32746]

Something you can also look at is your hardware clock.
# hwclock
Something could be syncing up with hardware clock and if it is wrong then it would make the clock on your desktop wrong.

[pedora]

Something you can also look at is your hardware clock.
# hwclock
Something could be syncing up with hardware clock and if it is wrong then it would make the clock on your desktop wrong.
# hwclock
bash: hwclock: command not found

[smr54]

Hrrm, that's odd. Try /sbin/hwclock. Seems to be part of the util-linux package, at least in CentOS. If you don't have that package, install it.

[pedora]

Hrrm, that's odd. Try /sbin/hwclock. Seems to be part of the util-linux package, at least in CentOS. If you don't have that package, install it.
It was my fault that I got the bash: command not found? I forgot the 'su -'

However, I still have a problem: this was my output:
# hwclock
Tue 19 Jan 2010 09:15:22 AM EST -0.391155 seconds

My time is now 2:15pm or 14:15? But, the time on the desktop is '04:17' and hwclock gave 9:15AM.

I don't know what is going on but although I might be clueless here, there shouldn't be this much trouble with a clock and the time.

[smr54]

Hrrm.....

Firstly, I suspect that your hardware is set to UTC. Out of curiosity, are there other distributions on it? Note that if you have, say, Ubuntu, by default, it uses UTC. When a Linux (or Windows) system closes, it sets the hardware clock to its time. This can result in something like--having Fedora at local time. Then, you boot Ubuntu, and when it closes, it sets the hardware clock back to UTC. Then, when you boot Fedora, your clock is 5 hours off (if you're in the Eastern Standard time zone) because Fedora thinks your hardware clock is set to local EST when it's actually set to UTC.

Hrrm--but then, it should be 5 hours behind, not ahead--I think.

Please do the following--but no guarantees--it just seems that something is off somewhere. In Fedora, check the file /etc/adjtime. Make sure that the last line is LOCAL, not UTC.

Now, I'm not familiar with Gnome, but try clicking the clock, setting it correctly, to 2:30 or whatever it is by the time your read this. Make sure it's PM (or 14:30 if you use 24 hour time). Make sure the time zone is correct, IIRC, there's a separate tab for that. Make sure that use GMT or use UTC or whatever it is, is NOT checked off. When that's all done, reboot. When you reboot, go into your system's BIOS and see if the clock is set to local time, that is 14:whatever. (If you see this before 15:00 of course.) :)

Then, boot and see if Fedora has the right time and if hwclock gives the right time. (Also, be sure that ntpd is set to start at boot as per earlier instructions.)

Please post back and see if any of this helps. The 5 hour difference is the difference between UTC and EST, but EST is -0500, not +.

It could also be, of course, a bad CMOS battery.

[pedora]

Just now, I checked the GUI 'Date and Time.' Note, I use the KDE edition of Fedora. The time is correct, as of now, 14:50.

EDIT: I guess the previous commands given 'fixed it.' The timezone set for EST or local gives 14:5x now. Thanks! I repeat, the clocks added as widgits are now giving local EST.

Thanks, smr54 and all who replied! :)

So, a previous distro set the hardware clock? Windows is able to assess the time its own way then? Because, I think it was the correct time last time I booted XP.

Does that mean I have to run those commands every time I boot Kubuntu (I have Kubuntu installed) or Debian (I have, also)?

[smr54]

Heh--dontcha love it? Ubuntu, in its default installation, doesn't give you the choice (though the alternative CD with a curses based install does allow you to choose UTC or localtime. I haven't used Debian in years--back when I used it, it too, had a curses based install and you could choose.

As far as I know, every O/S/Distro will set the hardware clock on shutdown, so if Windows, for example, is running local, and Ubuntu UTC, you'll always run into the problem.

In Ubuntu, the only way I know to change it is to edit /etc/defaults/rcS and change UTC or whatever it is from UTC=yes to UTC=no. (Or something similar, I'm not looking at Ubuntu right now. Hopefully, that gives you enough information to recognize the file and what should be changed.)

What I do is this. If I install Ubuntu (on various laptops, I usually put in both Fedora and Ubuntu), after installing Ubuntu, I edit the file---hrrm, I haven't done this in a bit, but it seems to me that I was able to do it before the reboot after installation--going into /mnt, or something. I'm afraid I don't remember.)

At any rate, even if I'm not able to change it before that reboot, where it will reset the machine's hardware clock, I do this.

At reboot, I go back into the BIOS and set it to localtime. Then, I boot into Fedora (which is already localtime.) Then, I mount the Ubuntu partition and edit the /etc/defaults/rcS. Then, I can boot into Ubuntu. It might have the wrong time at that point (I don't remember, I'm afraid), but if it does, I just set it using ntpdate and after that, all is good.