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).
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1476664
Title:
not possible to answer call when low battery indicator is shown
To
I'll look into it before the weekend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1476664
Title:
not possible to answer call when low battery indicator is shown
To manage notifications about
** 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
Bugs, which is subscribed to 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
Bugs, which is subscribed to Ubuntu.
I'm seeing the same mir-common error with a newer mir-build
(0.12.1+15.04.20150324) on mako when an autopilot-test assertion fails.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1424017
Title:
** Changed in: notify-osd (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008182
Title:
Provide a link to close notifications
To manage notifications about
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
I have this too and looking into it.
** Changed in: abiword (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432271
Title:
[vivid] Abiword always starts after
** Changed in: unity8 (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422711
Title:
SIM pin notification breaks notification positioning
To manage
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
Bugs, which is subscribed to
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1378618
Title:
volume notification looks bad when an indicator is open
To
** 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
Bugs, which is subscribed to Ubuntu.
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1355422
Title:
[notifications]
** Changed in: unity8 (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1378417
Title:
Icon clipping in notification-renderer
To manage notifications
Yes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384730
Title:
[notifications] remove combo button from incoming call snap
To manage notifications about this bug go to:
** No longer affects: unity-notifications (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384730
Title:
[notifications] remove combo button from incoming call snap
To manage notifications
** Branch linked: lp:~macslow/unity8/replace-combo-button-fix-1384730
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384730
Title:
[notifications] remove combo button from incoming call snap
To
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358343
Title:
[TOPBLOCKER] too easy to
** Changed in: unity8 (Ubuntu)
Importance: Undecided = High
** Changed in: unity8 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384730
Title:
** Changed in: unity8 (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384730
Title:
[notifications] remove combo button from incoming call snap
To
** Changed in: unity8 (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1378827
Title:
[notification] incoming call snap decision should prevent edge
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
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
Quick clip of the added delay for the selected/locked-in state, to
give the user another visual clue of the selection she/he made...
https://chinstrap.canonical.com/~mmueller/swipe-to-act-wip-6.mp4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Branch linked: lp:~macslow/unity-notifications/swipe-to-act-
fix-1358343
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358343
Title:
[notifications] too easy to answer a call by accident
To
)
Assignee: (unassigned) = Mirco Müller (macslow)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358343
Title:
[notifications] too easy to answer a call by accident
To manage notifications about
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
Bugs, which is subscribed to
** Branch linked: lp:~macslow/unity-settings-daemon/max-volume-
notification-warning
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373404
Title:
No warning of high volume level
To manage
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1378618
Title:
volume notification looks bad when an indicator is open
To manage
*** 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,
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373404
Title:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1378920
Title:
Synchronous sound notifications
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373404
Title:
No warning of high volume level
To manage notifications
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
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374301
Title:
** Branch linked: lp:~macslow/unity8/swipe-to-act-fix-1358343
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358343
Title:
[notifications] [design] too easy to answer a call by accident
To manage
This warning is only shown to the user (on Android) if headphones are
plugged it.
We too could display such a warning by triggering a corresponding snap-
decision from indicator-sound. With our current notification-system we
have all needed means for this in place. But what icon, summary- and
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
Bugs,
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
Bugs, which
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232633
Title:
[system] Changing volume
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1306769
Title:
pinlock
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: unity8 (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365987
Title:
Clicking on 'Show Password' closes the keyboard
To manage
** Changed in: content-hub
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350281
Title:
Download Complete snap-decision - improper use of the UbuntuShape
** Changed in: sync-monitor
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350282
Title:
Remove Account snap-decision - improper use of the UbuntuShape
To
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1346838
** Changed in: unity8 (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365987
Title:
Clicking on 'Show Password' closes the keyboard
To manage
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366752
Title:
Phone
** 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
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
Bugs, which
** 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
Bugs, which is subscribed
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
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
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
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
** Changed in: indicator-network
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1346904
Title:
wifi-password snap decision - improper use of the UbuntuShape
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335787
Title:
Notifications should force plain text
To manage notifications about this
** Changed in: unity8
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335787
Title:
Notifications should force plain text
To manage notifications about this bug
** Branch linked: lp:~larsu/qmenumodel/add-nameowner-property
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308011
Title:
SIM unlock UI shifts a half-gridunit when starting and breaks easily
To
Public bug reported:
As of today (updated to kernel 3.15.0-6-generic) my utopic based
desktop-machine keeps disk i/o busy with writing constantly at about 1
Meg/sec and also spams /var/log/kern.log with:
...
Jul 11 14:09:43 HAL9000 kernel: [ 3790.678329] rfkill: input handler enabled
Jul 11
It started...
Jul 11 00:47:14 HAL9000 kernel: [ 1315.610925] rfkill: input handler disabled
Jul 11 00:47:15 HAL9000 kernel: [ 1317.065654] rfkill: input handler enabled
Jul 11 00:47:16 HAL9000 kernel: [ 1317.175074] rfkill: input handler disabled
Jul 11 00:47:17 HAL9000 kernel: [ 1318.716811]
** Attachment added: /var/log/syslog.1
https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1340710/+attachment/4150432/+files/syslog.1.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1340710
** Attachment added: /var/log/syslog
https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1340710/+attachment/4150430/+files/syslog.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1340710
regarding 1.) The attached branch addresses the gap-issue. The
ReferenceError of LockScreen.qml no longer happens. The anchor-warning
concerning Column can't be avoided without breaking the whole layout of
notifications.
regarding 2.) This is probably due to the menu-model on DBus going
missing
I looked at the code again and also measured placement and size by hand
with ruler, pen and paper on the N4 and N10... on both devices the logo-
spinner of the boot-animation is correctly centered. The size on both
devices also looks to be physically the same... thus the GU-based
scaling does
Here is a side-by-side video showing spinner-logos being centered and of
equal size on both devices: http://www.youtube.com/watch?v=zWrRlmYYBQ0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331551
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: unity8
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308011
Title:
SIM unlock UI shifts a half-gridunit when starting and breaks easily
To manage
** Changed in: unity-notifications
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295762
Title:
snap decision timeout needs to be determined by the requesting
There's a feature-request from Design to allow apps to control the
timeout duration of a notification. See https://bugs.launchpad.net
/unity-notifications/+bug/1295762. This will facilitate addressing the
issue of this bug. So once #1295762 is fixed, timeout issues can be
addressed on a
*** This bug is a duplicate of bug 1295762 ***
https://bugs.launchpad.net/bugs/1295762
I'd opt for marking this as a duplicate of LP #1295762.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
1.) Description: Ubuntu 14.04 LTS, Release: 14.04
2.) installed: ocl-icd-libopencl1 2.1.3-4, to be installed: nvidia-
libopencl1-331 331.38-0ubuntu7
3.) The expected behaviour is a successful upgrade from ocl-icd-
libopencd1 to nvidia-libopencl1-331
4.)
** Changed in: unity8 (Ubuntu)
Assignee: Mirco Müller (macslow) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308667
Title:
indicator incoming can be taken out of action from
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) = Mirco Müller (macslow)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307489
Title:
Already-running apps are not raised if triggered
Just want to add my 2 cents of information from messing with this
subject over the weekend...
To properly use cairo.Region() in Python one needs at least pycairo
1.8.10 (1.10.0 is current) for Python 3.x. For Python 2.x pycairo does
not support/implement cairo.Region().
I've an example
1 - 100 of 1406 matches
Mail list logo
