Indicator shows "Tomorrow" for an alarm happening today when checked after midnight

Bug #1549783 reported by Neil McPhail
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
indicator-datetime (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

BQ E4.5 (krillin) running OTA9.1

I have 2 recurring alarms set for 0730 and 0800. If I pull down the clock indicator bar after midnight, the 0730 alarm is listed as "Tomorrow". The Clock app lists the alarm correctly (although, if I rememebr correctly, there was previously a bug where the clock app would get this wrong too). The alarm functions correctly, but the indicator is unsettling.

Steps to reproduce bug:
1. Create an alarm for *tomorrow morning*, say at 08:00 AM using the clock app.
2. When you swipe down the datetime indicator, it should correctly say that the alarm is scheduled for tomorrow 08:00 AM.
3. Open the system-settings app, and manually change the time to after midnight, say 02:00 AM next day.
4. Now swipe down the datetime indicator and it still says alarm scheduled for tomorrow 08:00 AM instead of "08:00AM".
5. Reopen the clock app and you will notice that it correctly say alarm is scheduled to run in another 6 hours (08:00AM minus 02:00AM)

Revision history for this message
Neil McPhail (njmcphail) wrote :
Revision history for this message
Neil McPhail (njmcphail) wrote :
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in indicator-datetime (Ubuntu):
status: New → Confirmed
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.