[Desktop-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Changed in: ubuntu-ux Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity 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 Ubuntu UX: Fix Released Status in Unity: Invalid Status in unity-notifications: Confirmed Status in indicator-network package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu: Triaged 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** No longer affects: telephony-service (Ubuntu) ** Project changed: telephony-service = telephony-service (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity 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 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: Triaged 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Changed in: indicator-network (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
Reopening, because adding the x-canonical-snap-decisions-timeout hint was a bad idea. The notification spec already has a timeout parameter on org.freedesktop.Notifications.Notify(). We can just use that one for snap decisions and ignore it for all other notification types. I've attached branches for unity-notifications and indicator-network. ** Changed in: unity-notifications Status: Fix Released = Confirmed ** Changed in: indicator-network (Ubuntu) Status: Fix Released = Confirmed ** Branch linked: lp:~larsu/unity-notifications/revert-timeout ** Branch linked: lp:~larsu/indicator-network/use-standard-timeout -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
This bug was fixed in the package indicator-network - 0.5.1+14.10.20140602-0ubuntu1 --- indicator-network (0.5.1+14.10.20140602-0ubuntu1) utopic; urgency=low [ CI bot ] * Resync trunk [ Antti Kaijanmäki ] * Use x-canonical-snap-decisions-timeout on the wifi password and sim unlock dialogs to prevent them from expiring automatically. (LP: #1295762) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 02 Jun 2014 11:03:06 + ** Changed in: indicator-network (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: New 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 “indicator-network” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Confirmed 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
This bug was fixed in the package unity-notifications - 0.1.1+14.10.20140602-0ubuntu1 --- unity-notifications (0.1.1+14.10.20140602-0ubuntu1) utopic; urgency=low [ Mirco Müller ] * Added a snap-decisions-specific hint to allow control over the timeout of a notification. (LP: #1295762) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 02 Jun 2014 10:58:29 + ** Changed in: unity-notifications (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: New 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 “indicator-network” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Confirmed 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
added telephony-service to affected projects as we still need the incoming call snap decision and some of the messaging snap decisions to use this hint. ** Also affects: telephony-service Importance: Undecided Status: New ** Changed in: telephony-service Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko) ** Changed in: indicator-network Status: New = Fix Released ** Changed in: unity-notifications Status: In Progress = Fix Released ** Changed in: unity Status: Triaged = Invalid ** Changed in: unity (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity 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: Fix Released Status in “indicator-network” package in Ubuntu: Fix Released 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295762] Re: snap decision timeout needs to be determined by the requesting app
** Also affects: indicator-network Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1295762 Title: snap decision timeout needs to be determined by the requesting app Status in Network Menu: New 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/indicator-network/+bug/1295762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp