This is an example of a failed alarm: (process:6560): Indicator-Datetime-DEBUG: adding appointment 'Alarm' '' (process:6560): Indicator-Datetime-DEBUG: RangePlanner 0x1a08228 got 1 appointments (process:6560): Indicator-Datetime-DEBUG: time to delete task 0x1ad72a0 (process:6560): Indicator-Datetime-DEBUG: adding appointment 'Alarm' '' (process:6560): Indicator-Datetime-DEBUG: RangePlanner 0x1a09500 got 1 appointments (process:6560): Indicator-Datetime-DEBUG: time to delete task 0x1aa0c30 (process:6560): Indicator-Datetime-DEBUG: adding appointment 'Alarm' '' (process:6560): Indicator-Datetime-DEBUG: RangePlanner 0x1a0e398 got 1 appointments (process:6560): Indicator-Datetime-DEBUG: ClockWatcher 0xbe92d450 calling pulse() due to appointments changed (process:6560): Indicator-Datetime-DEBUG: time to delete task 0x1acd3d8 (process:6560): Indicator-Datetime-DEBUG: ClockWatcher 0xbe92d450 calling pulse() due to clock minute_changed
(process:6560): libnotify-WARNING **: Failed to connect to proxy (process:6560): Indicator-Datetime-WARNING **: Unable to show snap decision for 'Alarm': Timeout was reached -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295237 Title: Sometimes alarms trigger at xx seconds past their time and dismiss on snap doesn't stop the ringing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295237/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
