PIN-locked phone becomes unresponsive after simultaneous alarms

Bug #1354406 reported by Alan Pope 🍺🐧🐱 🦄
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
indicator-datetime (Ubuntu)
Invalid
High
Charles Kerr
unity-notifications (Ubuntu)
New
High
Unassigned
unity8 (Ubuntu)
Fix Released
High
Mirco Müller

Bug Description

Steps to reproduce

1. Run recent image (I'm on #178 on mako)
2. Setup pin lock in system settings
3. Enter two events for the same time, soon, in your google calendar
4. Have your phone sync your google calendar using system settings -> accounts
5. Lock screen
6. Wait for the events

What happens

* Multiple alarms go off, notification on screen. You can hear two rings at once (separate bug)
* Tap notification to make it go away
* Sound continues, but there's no notification on screen.

At this point you cannot unlock the phone. You can swipe away the welcome screen, but the display dims a bit once you do, and nothing is clickable - can't click numbers in pin unlock, can't swipe down indicators..

You have to reboot the phone to get past this.

I have further discovered that if your phone gets into this state you can tap where you think the dismiss icon is for the notification (top left of the screen) and you _can_ dismiss it, despite it not actually being visible.

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
Revision history for this message
Dave Morley (davmor2) wrote :

Although this is a rare thing for me I understand that people do have overlapping meeting and personal alarms so this could happen more often than not. Having to reboot a phone to get into it because alarm crash the login screen is not great.

Changed in indicator-datetime (Ubuntu):
importance: Undecided → High
summary: - 2nd of 2 alarms at same time is unclickable
+ PIN-locked phone becomes unresponsive after simultaneous alarms
Revision history for this message
Michał Sawicz (saviq) wrote :

Feels like unity8 is involved if the phone becomes unresponsive in this case...

tags: added: lt-blocker lt-category-visible lt-prio-high
Revision history for this message
Mirco Müller (macslow) wrote :

I tried to reproduce your step-by-step instructions on my N4 (image 187) and could not cause any entered event to trigger anything. I've even set everything to us/english, because I thought the timezone-settings might cause a problem, but even with us/english timezones nothing happened.

I've my Google-account set up to sync calendar and contacts and everything else you describe. No calendar-event triggers anything for me. I must be exposed to a different bug here, so can't help atm.

Revision history for this message
Mirco Müller (macslow) wrote :

The entered events (on the N4) also don't show up on my google-calendar on my desktop-machine. Syncing, although enabled, does not seem to work for me. Events from my normal calendar also don't get displayed in the calendar-app on the N4.

Revision history for this message
Mirco Müller (macslow) wrote :

Even the indicator-datetime does not show the test events I entered.

Revision history for this message
Gerry Boland (gerboland) wrote :

Following these steps exactly, calendar sync seemed to fail, so they didn't work for me.

But when I manually created 2 events, with names & 5 minute reminders, then I could reproduce the bug

Revision history for this message
Dave Morley (davmor2) wrote :

Mirco you can just set 2 alarms in the clock app for the same time it's quicker and easier.

I can confirm that things didn't work when popey first reported it. I'm happy to retry shortly though.

Revision history for this message
Mirco Müller (macslow) wrote :

Ok, with the two clock-alarms I am able to trigger the bug.

Revision history for this message
Mirco Müller (macslow) wrote :

The bug is actually in lp:unity-notifications. The more-than-one-notification-per-app-in-queue guard does not work and that's causing this issue. I'm currently working on fixing this in lp:unity-notifications.

Changed in unity8 (Ubuntu):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Mirco Müller (macslow)
Changed in unity-notifications (Ubuntu):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Mirco Müller (macslow)
Charles Kerr (charlesk)
Changed in indicator-datetime (Ubuntu):
status: Confirmed → Invalid
description: updated
Revision history for this message
Charles Kerr (charlesk) wrote :

Reopening for indicator-datetime:

Even if unity-notification's guard were working properly, indicator-datetime should probably do something to fold multiple alarms into a single notification / single sound.

Changed in indicator-datetime (Ubuntu):
status: Invalid → Triaged
assignee: nobody → Charles Kerr (charlesk)
Revision history for this message
Charles Kerr (charlesk) wrote :

Hm, actually I'm not sure it made sense for me to reopen this for datetime: the questions of how to make this user friendly (e.g., do we fold alarms into a single notification) need to be addressed but are not traincon0 blockers and shouldn't hold up the resolution of this ticket if MacSlow's patch does the job.

So I've opened a separate ticket (bug #1358890) for the secondary question of how two alarms at once should be displayed, and am re-closing this ticket as invalid wrt datetime.

Changed in indicator-datetime (Ubuntu):
status: Triaged → Invalid
Revision history for this message
kevin gunn (kgunn72) wrote :

Adding Mirco's python script to replicate the issue
 http://pastebin.ubuntu.com/8099238

it's not always occuring even with the script. But reliable enough.

This is a potential workaround branch, but not linking to bug as to leave this bug open for a more complete solution to be worked on
https://code.launchpad.net/~macslow/unity8/disable-opacity-animation-1354406-workaround/+merge/231588

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package unity8 - 8.00+14.10.20140820-0ubuntu1

---------------
unity8 (8.00+14.10.20140820-0ubuntu1) utopic; urgency=low

  [ CI bot ]
  * Resync trunk

  [ Nick Dedekind ]
  * Fixed CachedUnityMenuModel destruction unhinging indicators. (LP:
    #1328646)

  [ Mirco Müller ]
  * Temporarily disable any opacity-animation for notifications to
    unblock the train due to LP: 1354406. (LP: #1354406)
 -- Ubuntu daily release <email address hidden> Wed, 20 Aug 2014 20:03:55 +0000

Changed in unity8 (Ubuntu):
status: In Progress → Fix Released
Changed in unity-notifications (Ubuntu):
assignee: Mirco Müller (macslow) → nobody
status: In Progress → New
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.