Version: (using Devel) Installed from: Compiled sources Using KDE 4.2 RC1 on Kubuntu. If I have a digital clock plasmoid in the panel set with minute resolution (so, no seconds displayed) and I change the clock by another mean (say, ntpdate), the clock won't be update until the next minute comes. So for example if I have my digital clock showing 10:02 AM, I run ntpdate and I get my system date updated to 10:05 AM, the clock will still show 10:02 for about a minute, then it jumps to 10:06.
clock.cpp:486 int Clock::updateInterval() const { return m_showSeconds ? 1000 : 60000; } In order to fix this cases, the plasmoid should retrieve the engine data always at 1000msecs or use the default setting and "detecting" that kind of changes (>1 minute of difference), do know if the last is possible.
waking up once a second to catch what minute it is would be excessive; we try and minimize wake ups. as far as detecting time changes, that's probably the way to go (and should happen in the engine) ...
after further looking around, it seems there is no reliable way to get notified of system updates that are done "behind our back" without polling, which really isn't an option. what we can eventually do is limit the pain, as we do with time zone changes, by having kded emit a dbus signal whenever the time is changed the date and time control panel. sounds like a nice thing for 4.4 (along with putting the date and time panel in the clock config itself :)
a related bug is bug 171120
Confirming as per comments.
*** Bug 209308 has been marked as a duplicate of this bug. ***
Edit title to be clearer.
*** Bug 171120 has been marked as a duplicate of this bug. ***
However If I move the mouse cursor over this panel, it is irritating that 2 different times are shown.
(In reply to comment #3) > by having kded emit a dbus signal whenever the time is changed the date and > time control panel. > > sounds like a nice thing for 4.4 (along with putting the date and time panel in > the clock config itself :) I'm wodnering whether this is implemented in the mean while ...
*** Bug 259242 has been marked as a duplicate of this bug. ***
*** Bug 274625 has been marked as a duplicate of this bug. ***
*** Bug 281495 has been marked as a duplicate of this bug. ***
btw, the kernel recently got timer notifications enabled. So we can sign up for a signal when the kernel's time itself gets changed and change time when that happens, preventing wakeups. As far as where this is going to be implemented, I thought I heard somebody mention about implementing it...
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham