Request to auto connect relevant slots and plugs of the locationd snap

store
1

Plugs to auto connect

  • locationd:client-control (interface: location-control)
  • locationd:client-observe (interface: location-observe)
  • locationd:network-manager (interface: network-manager)
  • locationd:wpa (interface: dbus, bus: system: name: fi.w1.wpa_supplicant1)

Snap info

name:      locationd
summary:   Location service mediates access to positioning providers.
publisher: canonical
contact:   snappy-canonical-storeaccount@canonical.com
description: |
  Location service mediates access to positioning providers.
  
  Please find the source for this snap at
  https://code.launchpad.net/location-service
snap-id: bUB8lXpOC3pItJMaJattT2jhDTyBWClE
commands:
  - locationd.list-providers
  - locationd.monitor
  - locationd.set
  - locationd.status
services:
  locationd.run: simple, enabled, active
2

It isn’t immediately apparent (to me) why locationd needs access to network-manager and wpa. Can you provide more details?

3

locationd uses network-manager and wpa-supplicant to get a list of current access points to use them as input for the Mozilla Location Service provider. The provider is deactivated by default and needs to be actively enabled by the user before it starts talking with the service.

4

Thanks. +1 for all requested auto-connections.

5

After one week, only one vote was cast. Adding an extension and pinging a subset of reviewers directly: @niemeyer, @popey, @ratliff, @nessita-- can one or more of you cast your vote?

6

I’m +1 on auto-connecting these.

7

Sounds reasonable given the details provided above for network-manager and wpa. +1 from me as well.

8

3 votes for, 0 against. Granting auto-connection. This is live now.