Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: indicator-datetime (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscripti
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Bill Filler (bfiller)
** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-dateti
So basically a snoozed alarm should stay in the indicator and clock app
after snoozing and be able to be cancelled at any time after that. It
shouldnt' disappear from indicator until it's actually done (i.e. user
presses ok and not snooze), but currently it does disappear.
--
You received this bu
I could think of two possible solutions:
1) in the indicator-datetime for the alarm there should be an action (perhaps
via left/right swipe) to cancel the pending alarm
2) if you snooze the alarm, it should still show up as enabled in the clock app
with an indication that it's going to sound aga
** Also affects: indicator-datetime (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-clock-app
Importance: Medium => High
** Changed in: ubuntu-ux
Importance: Undecided => High
** Changed in: indicator-datetime (Ubuntu)
Importance: Undecided => High
** Changed
*** This bug is a duplicate of bug 1280300 ***
https://bugs.launchpad.net/bugs/1280300
It still happens for me too in 15.10 --whenever I close the laptop lid,
the computer hibernates (I have set it to hibernate) correctly and upon
powering the laptop again, the contents are briefly visible bef
** Branch linked: lp:~sil2100/libunity-webapps/multi-arch
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity-webapps in Ubuntu.
https://bugs.launchpad.net/bugs/1539202
Title:
please multiarchify the library packages
Status in libunit
of course the moment I've submitted this I've noticed the "Related
Branches" section above that lists this patch as "Ready for review for
merging into lp:indicator-session/14.04". Can the process of accepting
it be influenced somehow?
--
You received this bug notification because you are a member
I've backported the changes that fixed this issue in 14.10. It applied
cleanly to the indicator-session 12.10.5_14.04.20151021.1-0ubuntu1 from
the trusty-updates. Rebuilding the patched source package and installing
it in Ubuntu 14.04 solves the issue. It would be nice if this patch is
applied and
I confirm that this bug also happens in mako.
current build number: 355
device name: mako
channel: ubuntu-touch/rc-proposed/ubuntu
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity-notifications (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscript
how does that work with recurring alarms? do you have to go back and
switch it on again later so that it triggers the day after?
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
The iPhone has this one figure out. When I set an alarm, I get a page
that shows me all the alarms I have created in the past, with the option
to edit them, as well as add or delete alarms. If an alarm goes off and
tap "Snooze", the modal dialog that pops up with the alarm goes away.
When I want to
13 matches
Mail list logo
