Unable to enable one time alarm after it has gone off

Bug #1407079 reported by Jonas G. Drange on 2015-01-02
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Clock App

Bug Description

I'm on Mako, using 15.04 (r58).

Steps to reproduce:
1. Create an alarm and activate it
2. Let it go off
3. Re-enable alarm

What happens:
The alarm is re-enabled, but the main screen is not showing any active alarms.
Going back into the alarm screen shows no enabled alarms.
The alarm does not ring.

What should have happened:
The alarm should have been activated and rung.

Nekhelesh Ramananthan (nik90) wrote :

Thanks for taking the time to report this bug to improve the clock app. I can confirm this bug on my vivid test phone. I suspect the issue to be due to 2 reasons,

1. In Vivid alone, the alarms backend is undergoing a major transition (for performance and other reasons) and thereby the Alarms backend has a bug where it doesn't accept alarm times when an alarm is being edited. I have reported that bug upstream against the Ubuntu SDK at https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1401883

2. Due to a local bug in the clock app where it does not automatically update the alarm time as reported at https://bugs.launchpad.net/ubuntu-clock-app/+bug/1413027

I have a fix for #2 which is being pushed into RTM. Unfortunately I *cannot* push the fix to vivid yet due to #1 being present on vivid.

But I will keep an eye out on this.

In the mean time, I recommend using the ubuntu-rtm images for daily usage.

Changed in ubuntu-clock-app:
status: New → Confirmed
milestone: none → ota-2
no longer affects: ubuntu-clock-app/utopic-14.10
Changed in ubuntu-clock-app:
milestone: 3.4 → 3.3
no longer affects: ubuntu-clock-app/vivid-15.04
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints