dx-packages team mailing list archive
-
dx-packages team
-
Mailing list archive
-
Message #25749
[Bug 1362341] Re: OneTime alarms are not automatically dismissed or delete after they are triggered
This bug was fixed in the package indicator-datetime -
13.10.0+15.04.20141208-0ubuntu1
---------------
indicator-datetime (13.10.0+15.04.20141208-0ubuntu1) vivid; urgency=low
[ Charles Kerr ]
* Don't log an error if powerd isn't available on the system. (LP:
#1384714)
* Add support for x-canonical-alarm and x-canonical-disabled tags in
VTODO categories so that disabled alarms will not be displayed. (LP:
#1387231)
* Change notifications for calendar events s.t. the sound is
nonrepeating and the notification is temporary, not requiring user
interaction to disappear. (LP: #1320880)
* After a one-time Ubuntu alarm's notification is displayed, disable
the alarm. (LP: #1362341)
-- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx> Mon, 08 Dec 2014 23:09:20 +0000
** Changed in: indicator-datetime (Ubuntu)
Status: In Progress => Fix Released
--
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/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 indicator-datetime package in Ubuntu:
Fix Released
Status in ubuntu-clock-app package in Ubuntu:
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