Bug 171120 - update clock immediately after waking up from sleep
Summary: update clock immediately after waking up from sleep
Status: RESOLVED DUPLICATE of bug 181380
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (show other bugs)
Version: 4.1
Platform: openSUSE Unspecified
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 197233 199404 222421 228217 235463 285436 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-09-15 20:21 UTC by Nick Shaforostoff
Modified: 2011-11-01 18:57 UTC (History)
9 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Shaforostoff 2008-09-15 20:21:33 UTC 
Version:            (using KDE 4.1.1)
Installed from:    SuSE RPMs

i did suspend2ram, then woke the system up and the clock showed old time for about the minute (until minutes were ++). solid should have wakeup notification for this.
Comment 1 Alan Jenkins 2008-10-19 18:25:33 UTC 
An alternative might be to use a QT equivalent of the POSIX clock_nanosleep(CLOCK_REALTIME, TIMER_ABSTIME, &next_minute, NULL)

In other words, perhaps there's some way to wait for "the next minute" on the system clock, instead of (or in addition to) waiting for 60 seconds subjective time.
Comment 2 Dario Andres 2009-05-22 23:21:14 UTC 
Do you think this should be marked as duplicate of bug 181380 ? Thanks
Comment 3 Nick Shaforostoff 2009-05-23 00:50:42 UTC 
no it isn't. both bugs require calling same slot in clock widget, though ;)
Comment 4 Dario Andres 2009-06-24 20:36:22 UTC 
*** Bug 197233 has been marked as a duplicate of this bug. ***
Comment 5 Lukas 2009-07-08 12:11:38 UTC 
*** Bug 199404 has been marked as a duplicate of this bug. ***
Comment 6 Dario Andres 2010-01-12 19:42:59 UTC 
*** Bug 222421 has been marked as a duplicate of this bug. ***
Comment 7 Dario Andres 2010-02-23 23:58:40 UTC 
*** Bug 228217 has been marked as a duplicate of this bug. ***
Comment 8 Pascal d'Hermilly 2010-02-24 00:12:24 UTC 
Also, you could check each second, if the date/hour/minute had been changed unexpectedly since last check. (e.g. minute-change at second 33).
Of course, this is not as pretty as a signal from solid, should such exist.
Comment 9 John Layt 2010-04-27 17:49:43 UTC 
*** Bug 235463 has been marked as a duplicate of this bug. ***
Comment 10 Nicolas L. 2010-06-07 01:01:06 UTC 
related to bug 181380 ( which have some more infos )

*** This bug has been marked as a duplicate of bug 181380 ***
Comment 11 Christoph Feck 2011-11-01 18:57:28 UTC 
*** Bug 285436 has been marked as a duplicate of this bug. ***