[Dx-packages] [Bug 694224] Re: Synchronous notifications briefly steal focus
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). icon-value.py is triggering the
exact same type of notification that a regular volume-up/down would be
made of.
What's actually stealing the focus is the process handling the
multimedia-keys input. That's the media-keys-manager part (libmedia-
keys.so) of lp:gnome-settings-daemon iirc.
--
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/694224
Title:
Synchronous notifications briefly steal focus
Status in Canonical System Image:
Confirmed
Status in notify-osd package in Ubuntu:
Confirmed
Bug description:
It appears synchronous notifications (at least those for volume and
brightness) briefly steal focus when they appear. This is quite
problematic for games and some other applications that pause as soon
as they lose focus. The focus stealing does not happen with normal,
asynchronous notifications.
Here's a quick Python program to reproduce this:
#!/usr/bin/python
import gtk
import time
def cb (wid, ev):
evtime = time.strftime ("%H:%M:%S", time.localtime())
print ("%s: Lost focus!" % evtime)
win = gtk.Window()
win.connect ("focus-out-event", cb)
win.show_all()
gtk.main()
You could also just start playing Quadrapassel, then adjust your volume :)
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/694224/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1008182] Re: Provide a link to close notifications
** 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 close notifications Status in notify-osd package in Ubuntu: Won't Fix Bug description: Currently when I reconnect to the internet it is displayed a notification on top right corner of the screen. When I put the mouse over the ballon, it gets semi-transparent but there is no way to close it completely not to reduce the amount of time the message is displayed. Please provide at least a close link [x] on these ballons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1008182/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1008182] Re: Provide a link to close notifications
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 way (they are click-through and defocus if you hover the mouse-pointer over them) to not break any workflow and interrupt your current actions (e.d. clicking button, reading text) with any UI-element, which might be below the notification-bubbles. That's why it's marked as Won't Fix. For reference, please read https://wiki.ubuntu.com/NotifyOSD#Rationale The new notification-system (for unity8) revisits notifications and their interaction-design. Currently unity8 is only used on devices such as phones and tablets, but will make its way to the desktop too (keyword: convergence). As a glimpse of how it's going to look, you can watch... http://www.youtube.com/playlist?list=PLXvTBWcnTI1M1n66KdFJRyakGlANTTbfQ -- 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 close notifications Status in notify-osd package in Ubuntu: Won't Fix Bug description: Currently when I reconnect to the internet it is displayed a notification on top right corner of the screen. When I put the mouse over the ballon, it gets semi-transparent but there is no way to close it completely not to reduce the amount of time the message is displayed. Please provide at least a close link [x] on these ballons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1008182/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1378618] Re: volume notification looks bad when an indicator is open
** 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 notification looks bad when an indicator is open Status in Ubuntu UX bugs: Confirmed Status in “indicator-sound” package in Ubuntu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: I found this while testing silo 11 with krilling #88. Steps to reproduce: Open an indicator. Press a volume button. (see the attached screenshot) You will see that the notification appears, but it's the same color as the header. It has no borders, so you can't tell it's a popup. It looks like the header changed to something that's no properly aligned. phablet@ubuntu-phablet:~$ apt-cache policy indicator-sound indicator-sound: Instalados: 12.10.2+14.10.20141007-0ubuntu1 Candidato: 12.10.2+14.10.20141007-0ubuntu1 Tabla de versión: *** 12.10.2+14.10.20141007-0ubuntu1 0 500 http://ppa.launchpad.net/ci-train-ppa-service/landing-011/ubuntu-rtm/ 14.09/main armhf Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1378618/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1373404] Re: [notification] No warning of high volume level
** 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. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1373404 Title: [notification] No warning of high volume level Status in Ubuntu UX bugs: Fix Committed Status in “indicator-sound” package in Ubuntu: Fix Released Status in “pulseaudio” package in Ubuntu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: In Progress Status in “unity-notifications” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu RTM: Fix Released Status in “unity-notifications” package in Ubuntu RTM: Fix Released Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: The EU has a legal requirement for personal music players to prevent hearing damage. http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490rid=1 Desired resolution: - For RTM the design spec'ed in the following section of the Sound wiki page should be implemented https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1373404/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1373404] Re: No warning of high volume level
** 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 Title: No warning of high volume level Status in Sound Menu: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “indicator-sound” package in Ubuntu: In Progress Status in “pulseaudio” package in Ubuntu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Status in “unity-notifications” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: The EU has a legal requirement for personal music players to prevent hearing damage. http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490rid=1 Desired resolution: - For RTM the design spec'ed in the following section of the Sound wiki page should be implemented https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1373404/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1373404] Re: No warning of high volume level
** 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: dx-packages https://bugs.launchpad.net/bugs/1373404 Title: No warning of high volume level Status in Sound Menu: New Status in Ubuntu UX bugs: Fix Committed Status in “indicator-sound” package in Ubuntu: New Status in “pulseaudio” package in Ubuntu: Triaged Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu: In Progress Bug description: The EU has a legal requirement for personal music players to prevent hearing damage. http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490rid=1 Desired resolution: - For RTM the design spec'ed in the following section of the Sound wiki page should be implemented https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1373404/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1373404] Re: No warning of high volume level
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 DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1373404 Title: No warning of high volume level Status in Sound Menu: New Status in Ubuntu UX bugs: Fix Committed Status in “indicator-sound” package in Ubuntu: New Status in “pulseaudio” package in Ubuntu: Triaged Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu: In Progress Bug description: The EU has a legal requirement for personal music players to prevent hearing damage. http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490rid=1 For the purpose of this Decision, a ‘personal music player’ means a portable device, that is not covered by Directive 1999/5/EC or Directive 2006/95/EC, with headphones or earphones, used to listen to recorded, generated or broadcasted sound. 1. For the purpose of Article 4(1)(a) of Directive 2001/95/EC, the safety requirement for personal music players shall be the following: Personal music players shall be designed and manufactured in a manner that ensures that, under reasonably foreseeable conditions of use, they are inherently safe and do not cause hearing damage. 2. The requirement set out in paragraph 1 shall include in particular the following: (1) Exposure to sound levels shall be time limited to avoid hearing damage. At 80 dB(A) exposure time shall be limited to 40 hours/week, whereas at 89 dB(A) exposure time shall be limited to 5 hours/week. For other exposure levels a linear intra- and extrapolation applies. Account shall be taken of the dynamic range of sound and the reasonably foreseeable use of the products. (2) Personal music players shall provide adequate warnings on the risks involved in using the device and to the ways of avoiding them and information to users in cases where exposure poses a risk of hearing damage. Related documents: http://ec.europa.eu/health/opinions/en/hearing-loss-personal-music-player-mp3/ http://europa.eu/rapid/press-release_IP-08-1492_en.htm http://ec.europa.eu/news/environment/090928_en.htm http://europa.eu/rapid/press-release_IP-09-1364_en.htm Design: https://wiki.ubuntu.com/Sound#limits: Whenever you are using headphones, Ubuntu should frequently measure the volume of sound output. Whenever it is over 47 dB(A), your quota should be reduced accordingly... [Originally reported in private bug 1370591.] To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1373404/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1373404] Re: No warning of high volume level
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: No warning of high volume level Status in Sound Menu: New Status in Ubuntu UX bugs: Fix Committed Status in “indicator-sound” package in Ubuntu: New Status in “pulseaudio” package in Ubuntu: Triaged Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu: In Progress Bug description: The EU has a legal requirement for personal music players to prevent hearing damage. http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490rid=1 Desired resolution: - For RTM the design spec'ed in the following section of the Sound wiki page should be implemented https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1373404/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1374301] Re: osd notifications blurry
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 https://bugs.launchpad.net/bugs/1374301 Title: osd notifications blurry Status in “notify-osd” package in Ubuntu: New Bug description: Recently clean installed Ubuntu 14.04.1 Trusty Tahr. With hidpi scale set to 2, and text scale set to .75, all on screen notifications have been blurry to the point of being unreadable. Any ideas on what could cause this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1374301/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1354406] Re: PIN-locked phone becomes unresponsive after simultaneous alarms
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 Google-account set up to sync calendar and contacts and everything else you describe. No calendar-event triggers anything for me. I must be exposed to a different bug here, so can't help atm. -- 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 becomes unresponsive after simultaneous alarms Status in “indicator-datetime” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: New Bug description: 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 screen 6. Wait for the events What happens * Multiple alarms go off, notification on screen. You can hear two rings at once (separate bug) * Tap notification to make it go away * Sound continues, but there's no notification on screen. At this point you cannot unlock the phone. You can swipe away the welcome screen, but the display dims a bit once you do, and nothing is clickable - can't click numbers in pin unlock, can't swipe down indicators.. You have to reboot the phone to get past this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1354406/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1354406] Re: PIN-locked phone becomes unresponsive after simultaneous alarms
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: PIN-locked phone becomes unresponsive after simultaneous alarms Status in “indicator-datetime” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: New Bug description: 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 screen 6. Wait for the events What happens * Multiple alarms go off, notification on screen. You can hear two rings at once (separate bug) * Tap notification to make it go away * Sound continues, but there's no notification on screen. At this point you cannot unlock the phone. You can swipe away the welcome screen, but the display dims a bit once you do, and nothing is clickable - can't click numbers in pin unlock, can't swipe down indicators.. You have to reboot the phone to get past this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1354406/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1354406] Re: PIN-locked phone becomes unresponsive after simultaneous alarms
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 becomes unresponsive after simultaneous alarms Status in “indicator-datetime” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: New Bug description: 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 screen 6. Wait for the events What happens * Multiple alarms go off, notification on screen. You can hear two rings at once (separate bug) * Tap notification to make it go away * Sound continues, but there's no notification on screen. At this point you cannot unlock the phone. You can swipe away the welcome screen, but the display dims a bit once you do, and nothing is clickable - can't click numbers in pin unlock, can't swipe down indicators.. You have to reboot the phone to get past this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1354406/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1354406] Re: PIN-locked phone becomes unresponsive after simultaneous alarms
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: 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: unity-notifications (Ubuntu) Importance: Undecided = High ** Changed in: unity-notifications (Ubuntu) Assignee: (unassigned) = Mirco Müller (macslow) -- 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 becomes unresponsive after simultaneous alarms Status in “indicator-datetime” package in Ubuntu: Confirmed Status in “unity-notifications” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Bug description: 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 screen 6. Wait for the events What happens * Multiple alarms go off, notification on screen. You can hear two rings at once (separate bug) * Tap notification to make it go away * Sound continues, but there's no notification on screen. At this point you cannot unlock the phone. You can swipe away the welcome screen, but the display dims a bit once you do, and nothing is clickable - can't click numbers in pin unlock, can't swipe down indicators.. You have to reboot the phone to get past this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1354406/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
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 reason I thought introducing hints for snap decision actions was unnecessary. The hint x-canonical-snap-decisions is an indicating hint, e.g. like the standard body hint, and used to point out that there are certain rules enforced upon the use of actions, put forth by UX-design, which deviate from the FDO-standard. Therefore I do not regard x-canonical-snap-decisions as being unnecessary. Furthermore hints are the designated means to introduce new features (or different behaviour). It's unlikely that developers have a problem understanding that the timeout only applies to a specific kind of notification. Being explicit rather than implicit avoids misunderstanding and possible false-positive bug-reports due to that. Adding additional hints only increases the complexity of the API and makes it harder to switch between different kinds of notifications. By design every introduced notification-type serves a very specific purpose, that differs in behaviour, visuals and interaction. Thus switching between different notification-types is not a common thing to do for a developer, unless UX-requirements change later on. -- 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 timeout needs to be determined by the requesting app Status in Network Menu: Fix Released Status in Telephony Service: New Status in Ubuntu UX bugs: Fix Committed Status in Unity: Invalid Status in Server and client library for desktop notifications in Unity: Confirmed Status in “indicator-network” package in Ubuntu: Fix Released Status in “telephony-service” package in Ubuntu: New Status in “unity” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: Fix Released Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1295762/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
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 notifications - would be misleading, because the intention of that timeout parameter is to be affecting all kinds of notifications. -- 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 timeout needs to be determined by the requesting app Status in Network Menu: Fix Released Status in Telephony Service: New Status in Ubuntu UX bugs: Fix Committed Status in Unity: Invalid Status in Server and client library for desktop notifications in Unity: Confirmed Status in “indicator-network” package in Ubuntu: Confirmed Status in “telephony-service” package in Ubuntu: New Status in “unity” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: Fix Released Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1295762/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** 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 timeout needs to be determined by the requesting app Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Status in “unity-notifications” package in Ubuntu: Confirmed Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1295762/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1308667] Re: indicator incoming can be taken out of action from the welcome screen
** 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 Title: indicator incoming can be taken out of action from the welcome screen Status in “indicator-messages” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: PREREQUISITE: 2 phones STEPS: 1. On the Ubuntu Touch Phone (Phone A) add the other phone (Phone B) as a contact 2. Put Phone A to sleep 3. Send an sms from Phone B to Phone A 4. Notice that it very briefly displays SMS from +0123445678999 instead of the contact deatials. 5. Hit the notification for the Incoming SMS 6. Send another message now and you get no Blue icon, No notification, No Ping 2 things might be happening here from what I can tell so far: 1. The indicator dies and is in the midst of a restart when the second text comes through (no crash log for indicators just one of the only things I can think of) 2. Something is broken in the interaction of the sms system (Possibly relating to The QT bug) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity8 7.85+14.04.20140415.2-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.1-0ubuntu3 Architecture: armhf Date: Wed Apr 16 18:06:06 2014 InstallationDate: Installed on 2014-04-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS - armhf (20140416.1) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1308667/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1275524] Re: notify-osd crashed with signal 5 in _XReply()
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: notify-osd crashed with signal 5 in _XReply() Status in “notify-osd” package in Ubuntu: Confirmed Bug description: This occurred while I was away from the pc no other info. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.04.20140117.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sun Feb 2 11:24:12 2014 DesktopSession: 'ubuntu' ExecutablePath: /usr/lib/x86_64-linux-gnu/notify-osd GtkTheme: 'Ambiance' IconTheme: 'buuf3.10' InstallationDate: Installed on 2014-01-08 (24 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140108) MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7529 ProcCmdline: /usr/lib/x86_64-linux-gnu/notify-osd ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/sda5 ro quiet splash RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.0~git20140131.1d53603f-0ubuntu0sarvatt libdrm2 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt xserver-xorg-video-intel 2:2.99.907+git20140131.f934ee78-0ubuntu0sarvatt xserver-xorg-video-ati 1:7.3.0-1ubuntu1 Signal: 5 SourcePackage: notify-osd StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetGeometry () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_window_get_geometry () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: notify-osd crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 03/11/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.8 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G31M3-L V2(MS-7529) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd03/11/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7529:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnG31M3-LV2(MS-7529):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7529 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1275524/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** 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 subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: Triaged Status in “unity” package in Ubuntu: New Status in “unity-notifications” package in Ubuntu: New Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1295762/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
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 the the regular notify_notification_set_timeout() instead of a dedicated hint. -- 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 timeout needs to be determined by the requesting app Status in Ubuntu UX bugs: Fix Committed Status in Unity: Triaged Status in Server and client library for desktop notifications in Unity: Triaged Status in “unity” package in Ubuntu: New Status in “unity-notifications” package in Ubuntu: New Bug description: Problem: If user receives an SMS/call, snap decision for incoming SMS/call stays on screen for always only 60sec. and then disappears from screen (by default). There was no interaction from user. Possible solution: The snap decision should stay on screen for the amount of time the app asks it to, being always app dependant. A 60sec. time-out is too short due to use cases where an action from user is mandatory. Use case example: A class 1/2 SMS arrives after user triggered a USSD command from dialer. These type of SMS always requires a response from user (CANCEL or a further COMMAND). Thus a timeout of only 60 sec is too short because it can be missed and these type of SMS is NOT saved into the usual messages thread. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1295762/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1092905] Re: incorrect placement on multimonitor systems with focus-follow on
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 notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1092905 Title: incorrect placement on multimonitor systems with focus-follow on Status in One Hundred Papercuts: New Status in Unity: New Status in “notify-osd” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: New Bug description: When changing the volume via the mouse scroll wheel over the volume indicator, the libnotify pop-up displaying the current volume is placed a little too high, obscuring all the indicators. The volume bubble should be placed lower. Screenshot will be attached. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,resize,move,gnomecompat,snap,mousepoll,wall,imgpng,regex,place,commands,grid,session,unitymtgrabhandles,animation,fade,workarounds,expo,scale,ezoom,unityshell] Date: Fri Dec 21 14:46:22 2012 InstallationDate: Installed on 2012-05-10 (225 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2012-10-19 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1092905/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1257717] Re: Invalid g_source_remove use
** 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 g_source_remove use Status in “notify-osd” package in Ubuntu: Fix Committed Bug description: Tested on trusty, running notify-osd from a command line, Source ID ... was not found when attempting to remove it errors are displayed when notification bubbles are dismissed The new glib raises those errors, see https://bugzilla.gnome.org/show_bug.cgi?id=710724, they can lead to leaks and other issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1257717/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1253591] Re: Display switch and Radio enable/disable hotkey icons
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 https://bugs.launchpad.net/bugs/1253591 Title: Display switch and Radio enable/disable hotkey icons Status in OEM Priority Project: New Status in “notify-osd-icons” package in Ubuntu: New Status in “notify-osd-icons” source package in Precise: New Bug description: 1) Radio enable/disable, for example Fn-F2 on a Dell XPS13. 2) Display switch, for example Fn-F1 on a Dell XPS13 attached are icons from John Lea To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1253591/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1257717] Re: Invalid g_source_remove use
** 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: Invalid g_source_remove use Status in “notify-osd” package in Ubuntu: Confirmed Bug description: Tested on trusty, running notify-osd from a command line, Source ID ... was not found when attempting to remove it errors are displayed when notification bubbles are dismissed The new glib raises those errors, see https://bugzilla.gnome.org/show_bug.cgi?id=710724, they can lead to leaks and other issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1257717/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1257717] Re: Invalid g_source_remove use
** 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 g_source_remove use Status in “notify-osd” package in Ubuntu: In Progress Bug description: Tested on trusty, running notify-osd from a command line, Source ID ... was not found when attempting to remove it errors are displayed when notification bubbles are dismissed The new glib raises those errors, see https://bugzilla.gnome.org/show_bug.cgi?id=710724, they can lead to leaks and other issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1257717/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1218289] Re: [dialer app] Incoming call (snap decision) not to spec
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: notify-osd (Ubuntu) ** No longer affects: notify-osd ** No longer affects: notify-osd (Ubuntu Saucy) ** Changed in: unity8 (Ubuntu) Assignee: Nick Dedekind (nick-dedekind) = Mirco Müller (macslow) ** Changed in: unity8 Status: Triaged = Confirmed -- 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/1218289 Title: [dialer app] Incoming call (snap decision) not to spec Status in Dialer app for Ubuntu Touch: Triaged Status in Ubuntu UX bugs: Fix Committed Status in The Unity 8 shell: Confirmed Status in “dialer-app” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu: Confirmed Status in “dialer-app” source package in Saucy: Triaged Status in “unity8” source package in Saucy: Confirmed Bug description: Current situation: Incoming call appears in snap decision format, but missing: - Decision buttons not the right visual colours and assets (missing colour and combo button) - background is currently transparent, so can see content below. Desired solution: - As per spec, when receiving an incoming call the snap decision should be solid background. And the notification buttons and style should be as per design. - See Notification and Snap Decision spec for full details of the final signed off design, https://docs.google.com/a/canonical.com/document/d/1puQ9Z0yKqzsQ1VQ1OOBkxgp78iWGnAhAkFXWJFTWIrE/edit To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1218289/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 404658] Re: notification summary doesn't change for synchronous messages
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 for a dedicated symbolic bluetooth- and wifi-icon that's within the style of notify-osd-icons for enabled and disabled states * add these icons to lp:ubuntu/notify-osd-icons * see the sync-icon-only or icon-value examples of notify-osd trunk 2.) If it needs to have summary- and body-text: * use the icon-summary variant * to make it skip ahead in the queue set the urgency to critical * see the icon-smmary example of notify-osd trunk I can provide screencasts of both alternatives later today. -- 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/404658 Title: notification summary doesn't change for synchronous messages Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in “notify-osd” package in Ubuntu: Confirmed Status in “notify-osd” source package in Precise: New Bug description: Precise SRU info: [Impact] * The patch provide a fix to provide the x-canonical-private- synchronous to work with notifications different with LAYOUT_ICON_INDICATOR layout. Currently the x-canonical-private- synchronous interface only provide this layout to support brightness and volume control. [Test Case] * This patch make following command behave correctly. #notify-send -h string:x-canonical-private-synchronous:1 wireless disable -i notification-network-wireless-none ; sleep 1 ; notify- send -h string:x-canonical-private-synchronous:1 bluetooth enable -i bluetooth In current implementation, both Summary and Body text didn't get updated. [Regression Potential] * The risk should be minimal, the patch should only affect x -canonical-private-synchronous interface. This interface is only used in brightness and volume hotkey, and layout is different. * The patch is already tested in OEM projects. [Other Info] *** Original bug description: When you send a notification in Synchronous with another, the both Summary and Body text doesn't get updated. As an example: while true; do notify-send first title first subtitle -i dialog-info -h string:x-canonical-private-synchronous:test sleep 1 notify-send second title second subtitle -i dialog-error -h string:x-canonical-private-synchronous:test sleep 1 done If you run the above, what you should see is the Icon changing, but the summary/body text staying the same. Is this expected behaviour from the libnotify library? Or is this an overlooked feature? Regards Iain DISTRIB_ID=Ubuntu DISTRIB_RELEASE=9.04 DISTRIB_CODENAME=jaunty DISTRIB_DESCRIPTION=Ubuntu 9.04 Package: libnotify-bin Priority: optional Section: universe/utils Installed-Size: 72 Maintainer: Ubuntu Core Developers ubuntu-devel-disc...@lists.ubuntu.com Original-Maintainer: Andre Filipe de Assuncao e Brito de...@noisemakers.org Architecture: amd64 Source: libnotify Version: 0.4.5-0ubuntu1 Depends: libc6 (= 2.3.4), libglib2.0-0 (= 2.12.0), libnotify1 (= 0.4.4), libnotify1-gtk2.10 Filename: pool/universe/libn/libnotify/libnotify-bin_0.4.5-0ubuntu1_amd64.deb Size: 7248 MD5sum: 332bacf4fad51bb2a32d17ed08ae66bc SHA1: ecbcfde7197c8934b7883a8d561ba02ba502adf2 SHA256: 15e1b7d9858a1c89f7bd826b10b16e2c0ee305e4268bd9bd0b1be3469eb9aaf9 Description: sends desktop notifications to a notification daemon A library that sends desktop notifications to a notification daemon, as defined in the Desktop Notifications spec. These notifications can be used to inform the user about an event or display some form of information without getting in the user's way. . This package contains the binary which sends the notification. Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Task: xubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/404658/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 404658] Re: notification summary doesn't change for synchronous messages
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 notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/404658 Title: notification summary doesn't change for synchronous messages Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in “notify-osd” package in Ubuntu: Confirmed Status in “notify-osd” source package in Precise: New Bug description: Precise SRU info: [Impact] * The patch provide a fix to provide the x-canonical-private- synchronous to work with notifications different with LAYOUT_ICON_INDICATOR layout. Currently the x-canonical-private- synchronous interface only provide this layout to support brightness and volume control. [Test Case] * This patch make following command behave correctly. #notify-send -h string:x-canonical-private-synchronous:1 wireless disable -i notification-network-wireless-none ; sleep 1 ; notify- send -h string:x-canonical-private-synchronous:1 bluetooth enable -i bluetooth In current implementation, both Summary and Body text didn't get updated. [Regression Potential] * The risk should be minimal, the patch should only affect x -canonical-private-synchronous interface. This interface is only used in brightness and volume hotkey, and layout is different. * The patch is already tested in OEM projects. [Other Info] *** Original bug description: When you send a notification in Synchronous with another, the both Summary and Body text doesn't get updated. As an example: while true; do notify-send first title first subtitle -i dialog-info -h string:x-canonical-private-synchronous:test sleep 1 notify-send second title second subtitle -i dialog-error -h string:x-canonical-private-synchronous:test sleep 1 done If you run the above, what you should see is the Icon changing, but the summary/body text staying the same. Is this expected behaviour from the libnotify library? Or is this an overlooked feature? Regards Iain DISTRIB_ID=Ubuntu DISTRIB_RELEASE=9.04 DISTRIB_CODENAME=jaunty DISTRIB_DESCRIPTION=Ubuntu 9.04 Package: libnotify-bin Priority: optional Section: universe/utils Installed-Size: 72 Maintainer: Ubuntu Core Developers ubuntu-devel-disc...@lists.ubuntu.com Original-Maintainer: Andre Filipe de Assuncao e Brito de...@noisemakers.org Architecture: amd64 Source: libnotify Version: 0.4.5-0ubuntu1 Depends: libc6 (= 2.3.4), libglib2.0-0 (= 2.12.0), libnotify1 (= 0.4.4), libnotify1-gtk2.10 Filename: pool/universe/libn/libnotify/libnotify-bin_0.4.5-0ubuntu1_amd64.deb Size: 7248 MD5sum: 332bacf4fad51bb2a32d17ed08ae66bc SHA1: ecbcfde7197c8934b7883a8d561ba02ba502adf2 SHA256: 15e1b7d9858a1c89f7bd826b10b16e2c0ee305e4268bd9bd0b1be3469eb9aaf9 Description: sends desktop notifications to a notification daemon A library that sends desktop notifications to a notification daemon, as defined in the Desktop Notifications spec. These notifications can be used to inform the user about an event or display some form of information without getting in the user's way. . This package contains the binary which sends the notification. Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Task: xubuntu-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/404658/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1007784] Re: The brightness bubble overlaps with the network bubble
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 https://bugs.launchpad.net/bugs/1007784 Title: The brightness bubble overlaps with the network bubble Status in Notify OSD: New Status in “notify-osd” package in Ubuntu: New Bug description: How to reproduce : 1- Start ubuntu 2- Unplug the network cable or shutdown the wifi 3- The network bubble will be displayed 4- Start reducing the brightness while the the network bubble is displayed In my opinion this happen because the first time the network bubble were displayed the calculation of the top margin where made while there was no panel because ubuntu was just starting, and the brightness bubble were displayed after the panel were displayed and top margin has changed. To manage notifications about this bug go to: https://bugs.launchpad.net/notify-osd/+bug/1007784/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1236292] Re: Using volume buttons on phone triggers spurious popup
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 think of is to make lp:unity-notifications (the new notification- backend) silently swallow such notifications without adding them to the queue, thus not making them display at all under unity8. Thoughts? -- 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/1236292 Title: Using volume buttons on phone triggers spurious popup Status in Sound Menu: In Progress Status in The Unity 8 shell: Invalid Status in “indicator-sound” package in Ubuntu: In Progress Bug description: Flashed mako with image #82. Press volume rocker, get a popup with no image and just the text 'indicator-sound'. See screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1236292/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1227718] Re: No way to click on the sms notification and get to the messaging app
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 Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1227718 Title: No way to click on the sms notification and get to the messaging app Status in Messaging App: New Status in Notify OSD: New Status in Ubuntu UX bugs: Fix Committed Status in The Unity 8 shell: New Status in “notify-osd” package in Ubuntu: New Status in “telephony-service” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: When an sms is received , I cannot click on the notification to go to the message thread. See spec: https://docs.google.com/a/canonical.com/document/d/1BRy9 -DEXr3A1D7PHkJaXmjbe7xbRmxKkzANXuu-F6lc/edit#heading=h.k0ou6qh6t2wc ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: messaging-app 0.1+13.10.20130917-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.2-0ubuntu1 Architecture: armhf Date: Thu Sep 19 14:24:48 2013 InstallationDate: Installed on 2013-09-18 (0 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20130918.1) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: messaging-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/messaging-app/+bug/1227718/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1227718] Re: No way to click on the sms notification and get to the messaging app
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 other program to the front, start some program or whatever. The action is executed as soon as the user taps anywhere on the interactive notification. -- 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/1227718 Title: No way to click on the sms notification and get to the messaging app Status in Messaging App: New Status in Notify OSD: New Status in Ubuntu UX bugs: Fix Committed Status in The Unity 8 shell: New Status in “notify-osd” package in Ubuntu: New Status in “telephony-service” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: When an sms is received , I cannot click on the notification to go to the message thread. See spec: https://docs.google.com/a/canonical.com/document/d/1BRy9 -DEXr3A1D7PHkJaXmjbe7xbRmxKkzANXuu-F6lc/edit#heading=h.k0ou6qh6t2wc ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: messaging-app 0.1+13.10.20130917-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.2-0ubuntu1 Architecture: armhf Date: Thu Sep 19 14:24:48 2013 InstallationDate: Installed on 2013-09-18 (0 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20130918.1) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: messaging-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/messaging-app/+bug/1227718/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
