Ubuntu
indicator-datetime package

  1. Bug #1295237
  2. Comment #3

Comment 3 for bug 1295237

Revision history for this message
Dave Morley (davmor2) wrote :

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