This lost-focus is not caused by notify-osd itself.
You can verify this by running Dylan's provided python-script and
triggering lp:notify-osd/examples/icon-value.py in another terminal
(with a "sleep 10" before that, so you've enough time to focus Dylan's
running python-script and its output).
** Changed in: notify-osd (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1008182
Title:
Provide a link to
The interaction-design (or rather non-interaction design) of desktop-
notifications wrt to NotifyOSD (used in conjuction with unity7 on the
current desktop) does explicitly not provide any means to allow/force
the user to act on them (e.g. close them).
The notification-bubbles do not get in your
** Changed in: unity8 (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1378618
Title:
volume
** 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 DX
Packages, which is subscribed to indicator-sound in Ubuntu.
** Branch linked: lp:~macslow/unity-settings-daemon/max-volume-
notification-warning
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1373404
** 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 DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions:
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
Current implementation in action...
https://www.youtube.com/watch?v=J_tvCQ5hHxI
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1373404
Title:
Can you provide a screenshot of the encountered issue, Andrew?
Futhermore what type of session (desktop-environment) are you running?
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
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 DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1354406
Title:
Ok, with the two clock-alarms I am able to trigger the bug.
--
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
https://bugs.launchpad.net/bugs/1354406
Title:
PIN-locked phone
in: unity8 (Ubuntu)
Importance: Undecided = High
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) = Mirco Müller (macslow)
** Also affects: unity-notifications (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity-notifications (Ubuntu)
Status: New = In Progress
Am 11.06.2014 12:20, schrieb Lars Uebernickel:
I disagree. The x-canonical-snap-decisions-timeout is intentionally used in
favour of the Freedesktop timeout feature, to indicate very clearly, that is
is only applicable to snap-decisions notifications.
I think that's unnecessary for the same
I disagree. The x-canonical-snap-decisions-timeout is intentionally
used in favour of the Freedesktop timeout feature, to indicate very
clearly, that is is only applicable to snap-decisions notifications.
Using the regular parameter of the Notify() method - and only applying
it snap-decisioin
** Changed in: unity-notifications
Status: Triaged = In Progress
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1295762
Title:
snap decision
** Changed in: unity8 (Ubuntu)
Assignee: Mirco Müller (macslow) = (unassigned)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-messages in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1308667
What multihead-mode have you set for notify-osd... focus-follow or
dont-focus-follow?
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1275524
Title:
** Changed in: unity-notifications
Assignee: (unassigned) = Mirco Müller (macslow)
** Changed in: unity
Assignee: (unassigned) = Mirco Müller (macslow)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching
As discussed with Olga last week, a possible solution would be the
introduction of a new integer hint (e.g. x-canonical-private-timeout),
which would allow a snap-decision to divert from the regular timeout-
behaviour that's usually the case with snap-decisions.
On could argue if we start using
If I recall correctly this is due to the fact that the desktop's strut
is taken from the wrong screen (or the fact that all attached screens
are treated as one big desktop). This needs a per-screen strut
calculation before each notification is placed visibly on screen.
--
You received this bug
** Changed in: notify-osd (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1257717
Title:
Invalid
I've uploaded the new icons to lp:~ubuntu-art-pkg/notify-osd/notify-osd-
icons-ubuntu and now do the SRU-ing for precise.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd-icons in Ubuntu.
Matching subscriptions: dx-packages
** Changed in: notify-osd (Ubuntu)
Assignee: (unassigned) = Mirco Müller (macslow)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1257717
Title
** Changed in: notify-osd (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1257717
Title:
Invalid
The visual part for this is purely a unity8/shell (thus notification-
frontend) issue. It's on the my workitem-list already for this cycle.
notify-osd is not related to this at all.
** Changed in: unity8
Assignee: Nick Dedekind (nick-dedekind) = Mirco Müller (macslow)
** No longer affects
I commented on larsu's patch.
The correct way to address this - staying within notify-osd's design-
guidelines - splits up in two alternatives...
1.) If it needs to be a synchonous notification:
* use either the sync-icon-only or icon-value variant of a synchonous
notification
* ask Design
Here's the promised screencast...
** Attachment added: screencast
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/404658/+attachment/3903371/+files/alternative-solution.mp4
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to
Yes, the the strut-dimension being updated (once the panel shows up) is
the most likely cause for this placement-calculation glitch.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
There is no visual/UX-design for confirmation (aka sychnonous)
notifications on UbuntuTouch... and I don't know if they are meant to be
added in the future.
As of rev385 of lp:indicator-sound the triggering of a confirmation
notification was added. The lowest impact work-around I can currently
Have a look at lp:unity-notifications in the examples directory. There
is a Python-example (interactive-notification.py), demonstrating how to
setup such a clickable notification.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in
The program triggering the sms-notification needs to make sure it's
using an interactive notification. Such an interactive notification
allows to define an action (just like with snap-decision notifications),
which can then be used by the triggering program as it sees fit... e.g.
to bring some
33 matches
Mail list logo
