Bug 181380 - Plasma clock doesn't update immediately when system time modified.
Summary: Plasma clock doesn't update immediately when system time modified.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-clock (show other bugs)
Version: 4.7.0
Platform: Compiled Sources Unspecified
: LO normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 171120 209308 259242 274625 281495 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-01-20 10:18 UTC by Davide Ferrari
Modified: 2018-06-08 19:53 UTC (History)
11 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Davide Ferrari 2009-01-20 10:18:13 UTC
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.
Comment 1 Dario Andres 2009-01-21 02:05:40 UTC
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.
Comment 2 Aaron J. Seigo 2009-01-21 08:01:10 UTC
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) ... 
Comment 3 Aaron J. Seigo 2009-05-19 11:30:11 UTC
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 :)
Comment 4 Nick Shaforostoff 2009-05-23 00:51:14 UTC
a related bug is bug 171120
Comment 5 Daniel Hahler 2009-05-24 19:29:52 UTC
Confirming as per comments.
Comment 6 Beat Wolf 2009-10-05 12:21:26 UTC
*** Bug 209308 has been marked as a duplicate of this bug. ***
Comment 7 John Layt 2010-01-03 14:19:58 UTC
Edit title to be clearer.
Comment 8 Nicolas L. 2010-06-07 01:01:06 UTC
*** Bug 171120 has been marked as a duplicate of this bug. ***
Comment 9 Toralf Förster 2010-06-28 20:47:37 UTC
However If I move the mouse cursor over this panel, it is irritating that 2 different times are shown.
Comment 10 Toralf Förster 2010-11-09 20:26:49 UTC
(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 ...
Comment 11 Dario Andres 2010-12-10 21:40:59 UTC
*** Bug 259242 has been marked as a duplicate of this bug. ***
Comment 12 Aaron J. Seigo 2011-05-31 23:15:27 UTC
*** Bug 274625 has been marked as a duplicate of this bug. ***
Comment 13 Dario Andres 2011-09-10 13:03:07 UTC
*** Bug 281495 has been marked as a duplicate of this bug. ***
Comment 14 Shaun Reich 2012-01-10 20:31:17 UTC
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...
Comment 15 Nate Graham 2018-06-08 19:53:09 UTC
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