** Changed in: unity-notifications (Ubuntu)
Assignee: Mirco Müller (macslow) => (unassigned)
** Changed in: unity-notifications (Ubuntu)
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
** Branch linked: lp:ubuntu/utopic-proposed/unity8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354406
Title:
PIN-locked phone becomes unresponsive after simultaneous alarms
To manage
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
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
** Changed
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
** Branch linked: lp:~macslow/unity-notifications/fix-1354406
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354406
Title:
PIN-locked phone becomes unresponsive after simultaneous alarms
To manage
** Description changed:
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
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.
--
You received this bug notification because you are a
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
Even the indicator-datetime does not show the test events I entered.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354406
Title:
PIN-locked phone becomes unresponsive after simultaneous alarms
To
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Ok, with the two clock-alarms I am able to trigger the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354406
Title:
PIN-locked phone becomes unresponsive after simultaneous alarms
To manage
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
** Changed in:
** Changed in: indicator-datetime (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354406
Title:
PIN-locked phone becomes unresponsive after simultaneous
Feels like unity8 is involved if the phone becomes unresponsive in this
case...
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: lt-blocker lt-category-visible lt-prio-high
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354406
Title:
PIN-locked phone becomes unresponsive after simultaneous alarms
To manage
** Summary changed:
- 2nd of 2 alarms at same time is unclickable
+ PIN-locked phone becomes unresponsive after simultaneous alarms
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354406
Title:
19 matches
Mail list logo
