dx-packages team mailing list archive

[Charles Kerr <charles.kerr@xxxxxxxxxxxxx>]

** Changed in: indicator-datetime (Ubuntu)
       Status: New => Invalid

** Changed in: ubuntu-clock-app (Ubuntu)
       Status: New => Invalid

-- 
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/1424924

Title:
  recurring alarms disappear from indicator (but not clock-app) after
  first kick

Status in indicator-datetime package in Ubuntu:
  Invalid
Status in qtorganizer5-eds package in Ubuntu:
  Fix Released
Status in ubuntu-clock-app package in Ubuntu:
  Invalid

Bug description:
  I'm not sure yet what's causing this, but the symptom is for
  ~/.local/share/evolution/tasks/${foo}@ubuntu-phablet/tasks.ics to have
  entries whose rrule looks like this:

  > RRULE;X-EVOLUTION-ENDDATE=19700101T000000Z:FREQ=WEEKLY;COUNT=32639;
  >  BYDAY=MO,TU,WE,TH,FR
  > SUMMARY:Weekday wakeup

  When is should look more like this:

  > RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR

  Alarms appear / trigger again after manually editing tasks.ics to
  remove the invalid X-EVOLUTION-ENDDATE and COUNT values, then
  restarting evolution-calendar-factory and indicator-datetime.

  ENDDATE's clearly coming from a (time_t)0. Not sure about 32639, but
  it's INT16_MAX - 128, so we've got that.

  Edit: this doesn't appear to be the full story -- if I create a brand
  new recurring alarm it works correctly even though the epoch ENDDDATE
  is present. For me they disappeared later, after a few days had passed
  and the system had been rebooted dozens of times. I'll see if I can
  reproduce the bug and, if so, how to reproduce it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1424924/+subscriptions