touch-packages team mailing list archive

[Łukasz Zemczak <1411171@xxxxxxxxxxxxxxxxxx>]

I was just wondering: is this also causing issues in vivid as well? We
have an Ubuntu task for this bug here and this change didn't land in
vivid, which is a requirement in case of reproducibility.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1411171

Title:
  Repeating alarms appear disabled in clock app after it went off once

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  In Progress
Status in indicator-datetime package in Ubuntu RTM:
  Fix Released

Bug description:
  krillin #198

  Repeating alarm is disabled after the first time it goes off.

  Test Case:
  1. Setup a repeating alarm (everyday from Monday to Friday for example) and enable it
  2. Close the clock app
  3. Wait until it goes off
  4. Dismiss it (and wait maybe 1 min or 2 so indicator is updated with next occurrence)
  5. Resume the device
  6. Launch the clock app
  7. Go the alarms and verify the status of the alarm

  Actual Result:
  The alarm is disabled but it shows in the indicator.
  The next and next-next occurrences of the alarm are scheduled correctly. 

  Expected Result
  Alarm is still enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411171/+subscriptions