| Summary: | clock mismatch | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Kris <krisgamrat> |
| Component: | tdebase | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED INVALID | ||
| Severity: | major | CC: | bugwatch, krisgamrat, michele.calgaro |
| Priority: | P5 | ||
| Version: | R14.0.x [Trinity] | ||
| Hardware: | Other | ||
| OS: | Debian Squeeze | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
|
Description
Kris
2012-11-28 14:21:30 CST
Working fine here (Slackware). I have the ntpd running. I do not have "Set date and time automatically" enabled/checked. You're using nightlies, correct? What distro? What is the time difference? What happens when you disable/uncheck "Set date and time automatically" and save the clock that way? (In reply to comment #1) > Working fine here (Slackware). I have the ntpd running. I do not have "Set date > and time automatically" enabled/checked. > > You're using nightlies, correct? Right. > What distro? Debian 6.0 "Squeeze". > What is the time difference? Five hours ahead of the panel clock. > What happens when you disable/uncheck "Set date and time automatically" and > save the clock that way? Makes no difference. It's still five hours ahead when I open it up again. Running ntpd won't work for me because I can't garuntee a consisten Internet connection to my laptop. I normally have the "Set date and time automatically" "un"checked for the same reason. I was only using that as a way of testing if it would fix it, but it makes no difference -- always five hours ahead of the panel clock when I re-open it. Strange bug. :( I'm changing this to Debian Squeeze as I don't have the problem in Slackware. No problem here in Debian/Jessie. Kris, do you still have this problem? Can you post some steps to reproduce it? Working fine here. I can reproduce the behavior described in the bug report if I have more than 1 time zone setup in the clock configuration and displaying one of them in the clock applet. This does not seem to be a bug, just wrong user configuration. |