Bug 186013

Summary:	Analog clock (plasmoid) changes speed of the seconds hand
Product:	[Unmaintained] plasma4	Reporter:	Thomas Thym <ungethym>
Component:	widget-clock	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	aseigo, karaluh, over1pixel
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Video of the "jumping" clock

Description Thomas Thym 2009-03-03 09:19:37 UTC

Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    SuSE RPMs

When seconds are displayed in the analog clock widget the jump not exactly every second. The same behavior has the binary clock.
The digital clock is working correctly. 

If you add the 3 widgets side by side you see that binary and analog clock are changing simultaneously (but wrong) and the digital clock correctly and not in sync with the other two.

Comment 1 Aaron J. Seigo 2009-03-04 00:06:47 UTC

sorry, it goes forward once per second, as close to the second as it can get .. but it's not guaranteeably perfect for any number of reasons.

Comment 2 Thomas Thym 2009-03-04 13:30:08 UTC

Created attachment 31765 [details]
Video of the "jumping" clock

Hi Aaron,
sorry for my imprecise description and thanks for your quick response. 

The behavior of the clock isn't always "wrong". Today in the morning the seconds jumped every second. Now (lunchtime) the strange behavior returned. Unfortunately I don't know how to reproduce it. 
This attachment is a screencast I made. 

Sure this is not a priority bug.

I'm not a coder but perhaps it has something to do with those memory bugs (182900 and 184394). The strange second jumps are associated with rising memory usage of Plasma (so far as I can say now). And I try to figure out if it is linked to the fact if I have Internet access or not.

Comment 3 Christian 2009-04-30 10:02:23 UTC

*** Bug 191076 has been marked as a duplicate of this bug. ***

Comment 4 Dario Andres 2009-05-25 17:19:52 UTC

*** Bug 194033 has been marked as a duplicate of this bug. ***