Bug 171897 - Setting the correct time more accurately
Summary: Setting the correct time more accurately
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_clock (show other bugs)
Version: 4.1
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: Paul Campbell
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-30 11:49 UTC by Tony White
Modified: 2009-04-10 23:41 UTC (History)
1 user (show)

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


Attachments
screeny of the dialogue (108.46 KB, application/octet-stream)
2008-09-30 11:52 UTC, Tony White
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tony White 2008-09-30 11:49:46 UTC
Version:            (using KDE 4.1.1)
OS:                Linux
Installed from:    Fedora RPMs

I know most people will use an ntp server but if you are offline, You can't.

When you set the time using the menu in system settings, Once you click apply another dialogue box appears asking for the root password.
By the time you have typed the password in and confirmed it some time has passed (Seconds,) Providing a less than acurate guessing game with the setting of the system time.

When setting the time, Accuracy is important.

I would like to see the clock starting from when the apply button is clicked so there is no delay.
Not after the password for root is put in and then applied.

The clock could run from when the apply button is pressed and after the password is confirmed, The correct time setting should then applied by grabbing the running time.

It's a strange wish but it's easy to set the system time on windows in a similar way so I think kde should be able to do it and more.
Comment 1 Tony White 2008-09-30 11:52:34 UTC
Created attachment 27617 [details]
screeny of the dialogue
Comment 2 Tony White 2008-10-01 09:12:27 UTC
http://doc.trolltech.com/4.2/timers.html
Comment 3 Dario Andres 2009-04-10 23:41:31 UTC
This was fixed on KDE4.2.x+
The fix was not ported to the KDE4.1.x branch.
Thanks