Location trust service is not started on image 203

Bug #1359866 reported by Dave Morley
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
location-service (Ubuntu)
Fix Released
Critical
Thomas Voß

Bug Description

On 201 I got popups for location service on 203 I don't. So somewhere between 201 and 203 something landed that killed the location service.

STEP:
1. Open camera app click on location
2. Install here maps open it
3. Open maps.google.com in the browser

EXPECTED:
A popup from location service asking for permission for that app to access location

ACTUAL:
No popup ever appears meaning that location is never triggered.

tags: added: lt-blocker lt-category-visible lt-prio-high
Thomas Strehl (strehl-t)
Changed in location-service (Ubuntu):
assignee: nobody → Thomas Voß (thomas-voss)
Revision history for this message
David Barth (dbarth) wrote :

For reference, and testers in particular, you can start the service manually with:

/usr/bin/trust-stored-skeleton \
    --remote-agent DBusRemoteAgent --bus=system \
    --local-agent MirAgent \
    --trusted-mir-socket=/var/run/user/$(id -u)/mir_socket_trusted \
    --for-service UbuntuLocationService \
    --store-bus session

(from /usr/share/upstart/sessions/ubuntu-location-service-trust-stored.conf)

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

I see the trust-stored-skeleton crash when an app (Here, Gmaps) makes a request for location data
Subsequently other apps do not see a prompt to allow or deny access, and no location responses are provided.

I do see location updates in/var/log/upstart/ubuntu-espoo-service.log

Changed in location-service (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.