Clock app alarms ignores the day set by the user

Bug #1319401 reported by Nekhelesh Ramananthan
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Ubuntu Clock App
Fix Released
Critical
Zsombor Egri
Ubuntu UI Toolkit
Fix Released
Critical
Zsombor Egri
ubuntu-ui-toolkit (Ubuntu)
Fix Released
Undecided
Unassigned
Vivid
New
Undecided
Unassigned

Bug Description

As of Utopic #26, the clock app does not take into account the day set by the user while creating a single type alarm. Instead it always creates the alarm for today. This does not happen with recurring alarms.

Steps to reproduce:
1. Create a single type alarm
2. Set the day to anything other day than today
3. Save alarm

Notice that the saved alarm is set to ring today and not on the day you chose. The alarm time is correct. Only the day is incorrect. There are no errors during the alarm save operation.

On using the SDK sample app which sets the alarm date object with the correct date and time, then the alarm is saved correctly. So it seems that the alarm.daysOfTheWeek property is being silently ignored by the SDK Alarms API.

Related branches

Zsombor Egri (zsombi)
Changed in ubuntu-ui-toolkit:
assignee: nobody → Zsombor Egri (zsombi)
milestone: none → june-2014
importance: Undecided → Critical
description: updated
Revision history for this message
Nicholas Skaggs (nskaggs) wrote :

nik90, how was this discovered?

Revision history for this message
Nekhelesh Ramananthan (nik90) wrote :

@nskaggs, Previously the AP tests were failing due to the SDK regression https://bugs.launchpad.net/bugs/1316736. However after looking at today's AP results, I noticed that the single alarm test was failing consistently. On looking through the console output, it seems the alarms are created for today instead of the day chosen during the testing causing it to fail. After some digging, I came to the conclusion and created this bug report. Zsombor will looking at this bug report this week and confirm if it is due to the SDK or the EDS.

Zsombor Egri (zsombi)
Changed in ubuntu-ui-toolkit:
status: New → Confirmed
Zsombor Egri (zsombi)
Changed in ubuntu-ui-toolkit:
status: Confirmed → In Progress
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:~ubuntu-sdk-team/ubuntu-ui-toolkit/staging at revision None, scheduled for release in ubuntu-ui-toolkit, milestone Unknown

Changed in ubuntu-ui-toolkit:
status: In Progress → Fix Committed
Changed in ubuntu-clock-app:
status: Confirmed → Fix Committed
Zsombor Egri (zsombi)
Changed in ubuntu-ui-toolkit:
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-ui-toolkit (Ubuntu):
status: New → Confirmed
Changed in ubuntu-ui-toolkit (Ubuntu):
status: Confirmed → Fix Released
Changed in ubuntu-clock-app:
milestone: alarm-blockers → rtm
Changed in ubuntu-clock-app:
assignee: nobody → Zsombor Egri (zsombi)
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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