After looking through the code, Pat's thoughts in comment 14 seem right to me.
For indicator-datetime's part, it can pass the system bus into the object constructor instead of making an asynchronous call to fetch it. This narrows the dangerous interval in datetime between wakeup and calling requestSysState -- though, NB, I'm not able to reproduce this bug in testing and so I'm not able to determine how much this change ameliorates it. Outside of indicator-datetime, this might be a question for repowerd wrt ensuring that, after system wakeup, apps have a chance to respond to the wakeup before the system goes back to sleep. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1588526 Title: [mako] Alarm doesn't ring when screen locked Status in Canonical System Image: Incomplete Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Hello, I noticed couple of time, difficult to reproduce that the alarm does not ring at the correct time but ring as soon the screen is on. Mako Rc-proposed bq-aquaris R324. Regards Edit : to make ring the phone i just need to wake up the phone and the alarm start to ring. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
