Bug 477082 - Clock widget's seconds not actually aligned to seconds
Summary: Clock widget's seconds not actually aligned to seconds
Status: RESOLVED DUPLICATE of bug 392476
Alias: None
Product: plasmashell
Classification: Plasma
Component: Digital Clock (show other bugs)
Version: 5.27.9
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-16 10:59 UTC by Stephen Horvath
Modified: 2023-11-16 20:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
A screenshot of the clock widget with a Konsole window running `watch -n 0.1 date`, the clock widget is a second behind. (24.66 KB, image/png)
2023-11-16 10:59 UTC, Stephen Horvath
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen Horvath 2023-11-16 10:59:09 UTC
Created attachment 163212 [details]
A screenshot of the clock widget with a Konsole window running `watch -n 0.1 date`, the clock widget is a second behind.

SUMMARY
The Clock Widget with seconds enabled can be up to a whole second behind (see attachment).
For performance reasons I am okay if it doesn't tick *exactly* on the second, but I'd hope it to be not that noticeable (e.g. maybe it syncs up once a minute, and has a ~1000ms interval after then?)

STEPS TO REPRODUCE
1. Have the clock widget with shown seconds added somewhere
2. Load up another clock, I just used `watch -n 0.1 date`
3. Compare the clocks

OBSERVED RESULT
The clock usually doesn't tick anywhere near exactly on the second, but rather sometime after.

EXPECTED RESULT
The clock would be visually in time with any other clock on the system.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
Sorry if this is a very minor issue, I just noticed it while waiting for an exam to start, and it was all I could think about.
Comment 1 Nate Graham 2023-11-16 20:54:38 UTC

*** This bug has been marked as a duplicate of bug 392476 ***