Editing a single type alarm after the alarm has gone of results in the alarm not ringing

Bug #1321294 reported by Nekhelesh Ramananthan
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Indicator Date and Time
Invalid
Undecided
Unassigned
Ubuntu Clock App
Invalid
High
Unassigned
Ubuntu UI Toolkit
Invalid
Undecided
Unassigned

Bug Description

This is a bug which could be due to the SDK, clock app, EDS or indicator-datetime. As a result I would like to do investigations in these projects and determine the exact cause of this.

Steps to reproduce this bug:
1. Create a single type alarm to ring in the next 3-4 minutes
2. Wait for that alarm to ring.
3. After dismissing the alarm, edit the alarm and set it to ring in the next 3-4 minutes.

What happens:
The alarm does not ring the second time. It is shown as enabled in the clock app, but it still doesn't ring. The updated alarm can also be seen in the indicator-datetime.

What should happen:
well if the one time alarm is intended to ring only once, then the alarm status should be shown correctly. If possible, the alarm should be deleted in that case. If not, then after editing, it should also ring the second time.

description: updated
Changed in ubuntu-clock-app:
milestone: alarm-blockers → rtm
Revision history for this message
Nekhelesh Ramananthan (nik90) wrote :

I am unable to reproduce this bug anymore. Marking invalid.

Changed in indicator-datetime:
status: New → Invalid
Changed in ubuntu-clock-app:
status: Triaged → Invalid
Changed in ubuntu-ui-toolkit:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.