| 2012-11-04 22:56:37 |
Charles Kerr |
bug |
|
|
added bug |
| 2012-11-04 22:58:49 |
Charles Kerr |
summary |
Don't ping geoclue server if show-auto-detected-location is false |
Don't use geoclue if show-auto-detected-location is false |
|
| 2012-11-04 22:59:00 |
Charles Kerr |
summary |
Don't use geoclue if show-auto-detected-location is false |
Don't use geoclue if "show-auto-detected-location" is set to false |
|
| 2012-11-04 22:59:11 |
Charles Kerr |
bug task added |
|
ubuntu-nexus7 |
|
| 2012-11-04 22:59:49 |
Charles Kerr |
indicator-datetime: status |
Triaged |
In Progress |
|
| 2012-11-04 23:16:33 |
Charles Kerr |
description |
This change is desirable for two reasons:
(1) In the Nov 2012 UDS session on eliminating unnecessary startup memory/performance hits, we discussed deferring indicator-datetime's invocation of geoclue until it's actually needed, such as when datetime's menu is about to show.
(2) Several users perceive datetime's use of geoclue/geoip as a breach of privacy. (See bug #944251, http://ubuntuforums.org/showthread.php?t=2000108, http://askubuntu.com/questions/106916/how-do-i-stop-geoip-from-connecting-to-the-internet-every-time-i-boot)
Inspecting the code though, it seems that the geoclue code all boils down to setting the "geo_timezone" variable for use in update_location_menu_items(). There, we build a menuitem for the geo_timezone which is only shown if com.canonical.indicator.datetime.show-auto-detected-location is true.
So, indicator-datetime could avoid unnecessary startup overhead -- and please privacy-minded users -- by deferring use of geoclue until/unless the user enables the "In the clock's menu, show time in the auto-detected location" checkbox. |
This bug is split off from an "umbrella" Bug #944251 which discusses various network connections made by various applications.
Deferring use of geoclue in indicator-datetime until "show-auto-detected-location" is set to "true" by the user is desirable for two reasons:
(1) In the Nov 2012 UDS session on eliminating unnecessary startup memory/performance hits, we discussed deferring indicator-datetime's invocation of geoclue until it's actually needed, such as when datetime's menu is about to show.
(2) Several users perceive datetime's use of geoclue/geoip as a breach of privacy. (See bug #944251, http://ubuntuforums.org/showthread.php?t=2000108, http://askubuntu.com/questions/106916/how-do-i-stop-geoip-from-connecting-to-the-internet-every-time-i-boot)
Inspecting the code though, it seems that the geoclue code all boils down to setting the "geo_timezone" variable for use in update_location_menu_items(). There, we build a menuitem for the geo_timezone which is only shown if com.canonical.indicator.datetime.show-auto-detected-location is true.
So, indicator-datetime could avoid unnecessary startup overhead -- and please privacy-minded users -- by deferring use of geoclue until/unless the user enables the "In the clock's menu, show time in the auto-detected location" checkbox. |
|
| 2012-11-04 23:18:34 |
Charles Kerr |
description |
This bug is split off from an "umbrella" Bug #944251 which discusses various network connections made by various applications.
Deferring use of geoclue in indicator-datetime until "show-auto-detected-location" is set to "true" by the user is desirable for two reasons:
(1) In the Nov 2012 UDS session on eliminating unnecessary startup memory/performance hits, we discussed deferring indicator-datetime's invocation of geoclue until it's actually needed, such as when datetime's menu is about to show.
(2) Several users perceive datetime's use of geoclue/geoip as a breach of privacy. (See bug #944251, http://ubuntuforums.org/showthread.php?t=2000108, http://askubuntu.com/questions/106916/how-do-i-stop-geoip-from-connecting-to-the-internet-every-time-i-boot)
Inspecting the code though, it seems that the geoclue code all boils down to setting the "geo_timezone" variable for use in update_location_menu_items(). There, we build a menuitem for the geo_timezone which is only shown if com.canonical.indicator.datetime.show-auto-detected-location is true.
So, indicator-datetime could avoid unnecessary startup overhead -- and please privacy-minded users -- by deferring use of geoclue until/unless the user enables the "In the clock's menu, show time in the auto-detected location" checkbox. |
This bug is split off from an "umbrella" Bug #944251 which discusses various network connections made by various applications.
Deferring use of geoclue in indicator-datetime until "show-auto-detected-location" is set to "true" by the user is desirable for two reasons:
(1) In the Nov 2012 UDS session on eliminating unnecessary startup memory/performance hits on the Nexus 7, we discussed deferring indicator-datetime's invocation of geoclue until it's actually needed, such as when datetime's menu is about to show.
(2) Several users perceive datetime's use of geoclue/geoip as a breach of privacy. (See bug #944251, http://ubuntuforums.org/showthread.php?t=2000108, http://askubuntu.com/questions/106916/how-do-i-stop-geoip-from-connecting-to-the-internet-every-time-i-boot)
Inspecting the code though, it seems that the geoclue code all boils down to setting the "geo_timezone" variable for use in update_location_menu_items(). There, we build a menuitem for the geo_timezone which is only shown if com.canonical.indicator.datetime.show-auto-detected-location is true.
So, indicator-datetime could avoid unnecessary startup overhead -- and please privacy-minded users -- by deferring use of geoclue until/unless the user enables the "In the clock's menu, show time in the auto-detected location" checkbox. |
|
| 2012-11-05 01:01:49 |
Charles Kerr |
branch linked |
|
lp:~charlesk/indicator-datetime/lp-1074999 |
|
| 2012-11-05 01:17:08 |
Charles Kerr |
description |
This bug is split off from an "umbrella" Bug #944251 which discusses various network connections made by various applications.
Deferring use of geoclue in indicator-datetime until "show-auto-detected-location" is set to "true" by the user is desirable for two reasons:
(1) In the Nov 2012 UDS session on eliminating unnecessary startup memory/performance hits on the Nexus 7, we discussed deferring indicator-datetime's invocation of geoclue until it's actually needed, such as when datetime's menu is about to show.
(2) Several users perceive datetime's use of geoclue/geoip as a breach of privacy. (See bug #944251, http://ubuntuforums.org/showthread.php?t=2000108, http://askubuntu.com/questions/106916/how-do-i-stop-geoip-from-connecting-to-the-internet-every-time-i-boot)
Inspecting the code though, it seems that the geoclue code all boils down to setting the "geo_timezone" variable for use in update_location_menu_items(). There, we build a menuitem for the geo_timezone which is only shown if com.canonical.indicator.datetime.show-auto-detected-location is true.
So, indicator-datetime could avoid unnecessary startup overhead -- and please privacy-minded users -- by deferring use of geoclue until/unless the user enables the "In the clock's menu, show time in the auto-detected location" checkbox. |
This bug is split off from an "umbrella" Bug #944251 which discusses various network connections made by various applications.
There are two reasons to not use geoclue until the user's specified it in the "show-auto-detected-location" settings:
(1) In the Nov 2012 UDS session on eliminating unnecessary startup memory/performance hits on the Nexus 7, we discussed deferring indicator-datetime's invocation of geoclue until it's actually needed, such as when datetime's menu is about to show.
(2) Several users perceive datetime's use of geoclue/geoip as a breach of privacy. (See bug #944251, http://ubuntuforums.org/showthread.php?t=2000108, http://askubuntu.com/questions/106916/how-do-i-stop-geoip-from-connecting-to-the-internet-every-time-i-boot)
Inspecting the code though, it seems that the geoclue code all boils down to setting the "geo_timezone" variable for use in update_location_menu_items(). There, we build a menuitem for the geo_timezone which is only shown if com.canonical.indicator.datetime.show-auto-detected-location is true.
So, indicator-datetime could avoid unnecessary startup overhead -- and please privacy-minded users -- by deferring use of geoclue until/unless the user enables the "In the clock's menu, show time in the auto-detected location" checkbox. |
|
| 2012-11-05 17:48:06 |
PS Jenkins bot |
indicator-datetime: status |
In Progress |
Fix Committed |
|
| 2012-11-05 18:06:47 |
Alex Chiang |
tags |
performance |
mobile performance |
|
| 2012-11-05 18:07:32 |
Alex Chiang |
tags |
mobile performance |
mobile nexus7 performance |
|
| 2012-11-05 18:07:46 |
Alex Chiang |
bug task deleted |
ubuntu-nexus7 |
|
|
| 2012-11-19 13:54:11 |
Mathieu Trudel-Lapierre |
bug task added |
|
indicator-datetime (Ubuntu) |
|
| 2012-11-19 13:54:26 |
Mathieu Trudel-Lapierre |
indicator-datetime (Ubuntu): status |
New |
Fix Committed |
|
| 2012-11-19 13:54:30 |
Mathieu Trudel-Lapierre |
indicator-datetime (Ubuntu): status |
Fix Committed |
Confirmed |
|
| 2012-11-19 13:54:32 |
Mathieu Trudel-Lapierre |
indicator-datetime (Ubuntu): importance |
Undecided |
Medium |
|
| 2012-11-19 13:55:50 |
Launchpad Janitor |
branch linked |
|
lp:~mathieu-tl/indicator-datetime/bootstrap |
|
| 2012-11-23 15:31:33 |
Launchpad Janitor |
indicator-datetime (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2013-11-06 18:11:03 |
Charles Kerr |
indicator-datetime: status |
Fix Committed |
Fix Released |
|
| 2013-11-22 15:55:35 |
LeetMiniWheat |
bug |
|
|
added subscriber LeetMiniWheat |
| 2014-01-13 11:57:10 |
oriolpont |
bug |
|
|
added subscriber oriolpont |
