touch-packages team mailing list archive

[Nekhelesh Ramananthan <krnekhelesh@xxxxxxxxx>]

** Also affects: ubuntu-clock-app
   Importance: Undecided
       Status: New

** Changed in: ubuntu-clock-app
     Assignee: (unassigned) => Nekhelesh Ramananthan (nik90)

** Changed in: ubuntu-clock-app
   Importance: Undecided => High

** Changed in: ubuntu-clock-app
       Status: New => Confirmed

** Changed in: ubuntu-clock-app
    Milestone: None => ota-1

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

Title:
  OneTime alarms are not automatically dismissed or delete after they
  are triggered

Status in the base for Ubuntu mobile products:
  Confirmed
Status in The Date and Time Indicator:
  In Progress
Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in ubuntu-clock-app package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu RTM:
  New

Bug description:
  Steps to reproduce:
  1. Create a one time alarm to ring in a few minutes
  2. Let the alarm ring
  3. Dismiss the alarm

  What happens:
  The OneTime alarm is still shown as enabled and as a result shows the wrong status in the clock app. The alarm is no longer shown in the indicator-datetime.

  What should happen:
  The OneTime alarm is either disabled or deleted from the alarm model.

  The clock app cannot disable the alarm since most likely the clock app
  is not even open at the time the alarm is triggered. Since the alarm
  is no longer shown in the indicator-datetime, my intuition tells me
  that indicator-datetime and EDS did its job. Its now up to the SDK
  Alarms API to update the alarm model correctly.

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