failure to get a position after allowing the page to access the location service

Bug #1381760 reported by Leo Arias on 2014-10-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

I found this while testing silo #4 with krillin image #106 of 14.09-proposed. It requires to also follow

To reproduce:
Open the webbrowser app.
Go to
Click on the arrow to find the current location.
Select allow on the dialog.
(Here a new dialog should appear. It doesn't)
After a while, the error dialog will appear saying Geolocation error: permission denied

Leo Arias (elopio) wrote :
Loïc Minier (lool) wrote :

Interestingly, while webapps and webbrowser dont work with silo 4 for me, only webapps work without and I do get the permission error you got but only without the silo!

Loïc Minier (lool) wrote :

the difference in webapps was due to trust-store in my case; I've got things to work on krillin+rtm w/o silo; most things do work on mako+utopic, but not too reliably.

Olivier Tilloy (osomon) wrote :

Just tested on krillin+rtm image #109 freshly upgraded, without silo everything works (both browser and webapps). With packages from silo 4, neither browser nor webapps work.

Marking location-service affected, as the regression is most likely introduced by it.

summary: - geolocation permission denied after allowing the page to access the
+ failure to get a position after allowing the page to access the location
Olivier Tilloy (osomon) wrote :

I also updated the title to reflect what really happens: the permission is not denied, what happens is that the location service fails to return a position.

Leo Arias (elopio) wrote :

Olivier, if the error on the dialog is not accurate, is it possible to also improve the message about what's really happening?

Olivier Tilloy (osomon) wrote :

The message is a javascript modal popup (created with window.alert()), the page itself controls its contents, so no, we can’t improve the message (and javascript alerts are a nasty thing from the past anyway, they’re bad UX practice).

Olivier Tilloy (osomon) wrote :

Closing now, as this issue was resolved a long time ago.

Changed in webbrowser-app:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers