Merged and released (e.g. rc-proposed). Also see
https://www.youtube.com/watch?v=5AS_r85m0Qs
** Changed in: unity-system-compositor
Assignee: (unassigned) = Mirco Müller (macslow)
** Changed in: unity-system-compositor (Ubuntu)
Assignee: (unassigned) = Mirco Müller (macslow
Greetings Petar!
I'm not sure I fully understand the state your phone is in, when this
happens to you. From my understanding it appears you might not be aware
of the collapse/expand feature of snap-decision notifications of unity8.
This happens when there is more than one snap-decision
** Changed in: unity8 (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1476664
Title:
not possible to answer call when low
I'll look into it before the weekend.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1476664
Title:
not possible to answer call when low battery indicator is shown
** Branch linked: lp:~macslow/qtmir/fix-1475678
** Branch linked: lp:~macslow/qtubuntu/fix-1475678
** Branch linked: lp:~macslow/unity8/fix-1475678
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
** Changed in: qtmir
Importance: Undecided = High
** Changed in: qtubuntu
Importance: Undecided = High
** Changed in: unity8 (Ubuntu)
Importance: Undecided = High
** Changed in: qtmir
Status: New = In Progress
** Changed in: qtubuntu
Status: New = In Progress
** Changed
** Changed in: qtmir
Assignee: (unassigned) = Mirco Müller (macslow)
** Changed in: qtubuntu
Assignee: (unassigned) = Mirco Müller (macslow)
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) = Mirco Müller (macslow)
--
You received this bug notification because you
** Changed in: unity-notifications (Ubuntu)
Status: In Progress = Triaged
** Changed in: unity-notifications (Ubuntu)
Importance: High = Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
** Changed in: unity8 (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1422711
Title:
SIM pin notification breaks
I was able to reproduce this issue and am looking into it now.
** Changed in: unity8 (Ubuntu)
Status: New = Confirmed
** Changed in: unity8 (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
The proposed fix in the MP works. Now I need to see with mzanetti (or
any other reviewer), if we're all happy with the proposed solution.
The visual glitch, when the SIM pin-entry fullscreen notification,
opens, is due to the way the custom UI is injected into the
notification. The interpretation
** Changed in: unity8 (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1378618
Title:
volume notification looks
** Changed in: unity8 (Ubuntu)
Status: In Progress = Fix Released
** Changed in: unity-notifications (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound
** Changed in: unity8 (Ubuntu RTM)
Status: New = In Progress
** No longer affects: unity-notifications (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
Ubuntu.
** Changed in: unity8 (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1378417
Title:
Icon clipping in notification-renderer
Yes.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
Ubuntu.
https://bugs.launchpad.net/bugs/1384730
Title:
[notifications] remove combo button from incoming call snap
Status in Ubuntu UX bugs:
** No longer affects: unity-notifications (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
Ubuntu.
https://bugs.launchpad.net/bugs/1384730
Title:
[notifications] remove combo button from
** Branch linked: lp:~macslow/unity8/replace-combo-button-fix-1384730
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
Ubuntu.
https://bugs.launchpad.net/bugs/1384730
Title:
[notifications] remove
The related branches in action on the mako (against image 105)
https://www.youtube.com/watch?v=bLNWI4GvplQ
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
Ubuntu.
https://bugs.launchpad.net/bugs/1358343
** Changed in: unity8 (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
Ubuntu.
https://bugs.launchpad.net/bugs/1384730
Title:
[notifications] remove
** Changed in: unity8 (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1378827
Title:
[notification] incoming call snap decision
Is this bug really meant for RTM? It was initially marked as Critical
- and I've taken over this for the change in affected package - and
would thus also imply it being targetted for RTM. Can some of the
stakeholders please comment.
--
You received this bug notification because you are a member
-case.
I'll update the bug to affect the correct packages.
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) = Mirco Müller (macslow)
** Also affects: telephony-service (Ubuntu)
Importance: Undecided
For sake of completeness/correctness... the snap-decision notification
triggered by telephony-service does not use more than two actions...
accept and reject. Thus it does not make use of the additional
ComboButton-feature of the notification-system.
What Olga is refering to, are the synthetic
: Undecided = Critical
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) = Mirco Müller (macslow)
** No longer affects: unity-notifications (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
Ubuntu
Why is lp:dialer-app linked to this bug and not lp:telephony-service?
The latter is the one which creates and triggers the incoming-call snap-
decision notification.
With the upcoming support for the SwipeToAct widget in notifications,
which is specifically designed to solve this very UX-bug, all
** Branch linked: lp:~macslow/unity-notifications/swipe-to-act-
fix-1358343
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1358343
Title:
[notifications] too easy to
)
Assignee: (unassigned) = Mirco Müller (macslow)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
Ubuntu.
https://bugs.launchpad.net/bugs/1358343
Title:
[notifications] too easy to answer a call
Selene, you a right about the issue with the volume-notification.
Matthew mentioned this too in comment #3. But I suggest opening a new
bug for the sync. volume notification over sound-indicator as the
initial background-color contrast of this bug is fixed.
Let's not have bug-entries organically
*** This bug is a duplicate of bug 1378417 ***
https://bugs.launchpad.net/bugs/1378417
** This bug has been marked a duplicate of bug 1378417
Icon clipping in notification-renderer
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Branch linked: lp:~macslow/unity-settings-daemon/max-volume-
notification-warning
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1373404
Title:
No warning of
** Branch linked: lp:~macslow/unity8/synchronous-notification
** Branch linked: lp:~macslow/unity-notifications/synchronous-
notification
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
You are all not fully correct.
Current notifications in unity8 trunk have snap-decisions using dark on
bright. All other notification-types use bright on dark. These color-
schemes are static currently.
The unity8 branch (lp:~macslow/unity8/synchronous-notification) up for
review - introducing
** Changed in: unity8 (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1378618
Title:
volume notification looks bad when an
*** This bug is a duplicate of bug 1378618 ***
https://bugs.launchpad.net/bugs/1378618
Although this was filed earlier I marked this as duplicate of LP:
#1378618 as more discussion has happend on LP: #1378618 already and a
fixing branch is attached too already.
** This bug has been marked a
Just had the meeting with Olga and James to answer the above mentioned
questions. Results from the meeting are...
- sizes, margins and colors of the current implementation-state are
accoding to design
- transition animations are provided now
- used icons in design-mockup are wrong,
I agree with Charles. As all-embracing as mpt's solution for the
convoluted EU-regulations is, that will not be doable in the RTM-
timeframe.
Still for the warning-at-75% stop-gap suggestion, I need a design-
sanctioned mockup.
--
You received this bug notification because you are a member of
This also solves any potential synchronization issues between sound-
playback and notification display.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1378920
Title:
I think that notifications should play such sounds, since we now have
the sound-hint support. Thus I agree with saviq, that incoming
call/message jingles should be offloaded to notifications to be
played.
Playback in snap-decision type notifications would loop sound-playback
until said
** Changed in: unity-notifications (Ubuntu)
Assignee: (unassigned) = Mirco Müller (macslow)
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) = Mirco Müller (macslow)
** Changed in: telephony-service (Ubuntu)
Assignee: (unassigned) = Mirco Müller (macslow)
--
You received
Current implementation in action...
https://www.youtube.com/watch?v=J_tvCQ5hHxI
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1373404
Title:
No warning of high
The needed change needs to happen in the frontend of notifications
(unity8). The backend, unity-notifications, is not to be touched.
** Project changed: unity-notifications = unity8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Branch linked: lp:~macslow/unity8/swipe-to-act-fix-1358343
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1358343
Title:
[notifications] [design] too easy to answer
Extracting the whole snap-decision functionality into a separate dialog
service, which would be easier to isolate, feels like a too large effort
for rtm, considering the other fires we've to put out still.
Admittedly I've not done a thorough analysis of the expected effort yet.
But it will
Ah, thanks for the clarification mpt! I was a bit surprised by John's
initial question regarding this, as I don't recall having heard from
Design that notification (-bubbles) were meant to be suppressed in any
way.
--
You received this bug notification because you are a member of Ubuntu
Touch
Whatever the solution is going to be, please remember, that the
notification-daemon does not have any domain- or context-knowledge about
the notification (and its contents) it receives. So any suppress-
filtering will have to be based solely on the notification-type: snap-
decision, ephemeral,
** Branch linked: lp:~macslow/unity8/synchronous-notification
** Branch linked: lp:~macslow/unity-notifications/synchronous-
notification
** Branch linked: lp:~macslow/indicator-sound/synchronous-notification
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
That's the current state of the attached branches in action...
https://www.youtube.com/watch?v=mi-Z2Rn7Fxo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1232633
Title:
The design for the phone is different from the old NotifyOSD design
referenced in the mentioned wiki-page in the bug-description.
Furthermore the sound to play back on the phone has not been stated nor
provided anywhere.
--
You received this bug notification because you are a member of Ubuntu
of my prepaid SIM-card due
to this bug.
** Affects: unity8 (Ubuntu)
Importance: High
Assignee: Mirco Müller (macslow)
Status: In Progress
** Tags: rtm14 touch-2014-09-25
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) = Mirco Müller (macslow)
** Changed in: unity8
The DBus-APIs used for exporting these via QMenuModel (Qt/QML-binding
for GMenuModel) are:
* org.gtk.Actions
* org.gtk.Menus
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
So there are no ephemeral notifications anymore?! I do not see them
being refered to in any way in the design-document. See...
www.youtube.com/watch?v=KI-uBmr_TNQt=1m30s
... for an example.
Ephemeral notifications are just that. Not interactive in any way and
just used to display not too
** Changed in: content-hub
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1350281
Title:
Download Complete snap-decision -
** Changed in: unity8 (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1365987
Title:
Clicking on 'Show
** Changed in: telephony-service
Status: In Progress = Fix Released
** Changed in: unity-notifications
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
Ubuntu.
Only snap-decisions are meant to be dismissable via swipe. Who connected
this bug to branch lp:~macslow/unity8/swipe-dismiss-snap-decisions ?
I do not agree with the current state of solution. The design-document
explicitly states only snap-decision notifications to be dismissable
(via swipe).
I don't seem to be running into any crash. Also I can't make out any
dbus timeouts in the *.log-files on the devices I tested this on. The
stutter is more striking, when a sound is attached to the notification.
Just from looking at the back- and frontend of the notification-system,
I don't know
** Changed in: unity8 (Ubuntu)
Status: New = Confirmed
** Changed in: unity8 (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) = Mirco Müller (macslow)
** Changed in: unity8 (Ubuntu)
Importance: Undecided = High
** Changed in: unity8 (Ubuntu)
Status: Confirmed = In Progress
** Branch linked: lp:~macslow/unity8/swipe-dismiss-snap-decisions
--
You
** Changed in: unity8 (Ubuntu)
Status: New = Confirmed
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) = Mirco Müller (macslow)
** Branch linked: lp:~macslow/unity8/fix-1348092
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Here's the link to the very commit fixing this issue for reference...
http://bazaar.launchpad.net/~macslow/unity8/fix-1348092/revision/1089
** Changed in: unity8 (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I marked the link to unity-notifications as invalid, since it's only
within the scope of the notification-triggering application to pass the
correct icon to the notification-backend.
** Changed in: unity-notifications (Ubuntu)
Status: New = Invalid
--
You received this bug notification
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
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
Even the indicator-datetime does not show the test events I entered.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1354406
Title:
PIN-locked phone becomes
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
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1354406
Title:
PIN-locked phone becomes unresponsive
** Changed in: indicator-network
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1346904
Title:
wifi-password snap
As of UbuntuTouch image r138 the ComboButton-support is available. For
reference see http://www.youtube.com/watch?v=EUCJ7XaPxjk
** Changed in: unity8
Status: Confirmed = Fix Released
** Changed in: unity8 (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug
** Branch linked: lp:~macslow/unity-notifications/fix-1335787
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1335787
Title:
Notifications should force plain text
Status
69 matches
Mail list logo
