Geoclue-2.20 not working with gnome-3.16.x

[Zeeshan Ali (Khattak)]

On Sat, Aug 1, 2015 at 4:06 PM, John Frankish <john.frankish at outlook.com> wrote:
>> > > I'd suggest you file a bug on Maps then cause the demo where-am-i connects fine so it's Maps' specific issue.
>> > >
>> > Just to be sure I've understood, if where-am-I is working, all you get is:
>> >
>> > " Client object: /org/freedesktop/GeoClue2/Client/1"
>> >
>> > ..and nothing else?
>>
>> Well you should be getting a location but of course it's not guaranteed and depends
>> on many factors but at least you are not getting any errors. If this is a desktop machine
>> without WiFi, your only bet is GeoIP and that's not a very reliable or complete method
>> (and it would require internet access). You can make the app wait a bit longer by using
>> the -t option and see what geoclue says on the console when app connects to it.
>> Debugging can be turned on by defining `G_MESSAGES_DEBUG=Geoclue`.
>>
> Progress is being made (laptop + wifi)
>
> $ sudo G_MESSAGES_DEBUG=Geoclue /usr/local/lib/geoclue-2.0/geoclue -t 60
>
> (geoclue:18146): Geoclue-DEBUG: Available accuracy level from GClueWifi: 4
> (geoclue:18146): Geoclue-DEBUG: WiFi device 'wlan0' added.
> (geoclue:18146): Geoclue-DEBUG: Available accuracy level from GClueWifi: 6
> (geoclue:18146): Geoclue-DEBUG: New agent for user ID '1001'
> (geoclue:18146): Geoclue-DEBUG: Number of connected clients: 1
> (geoclue:18146): Geoclue-DEBUG: 'org.gnome.Maps' not in configuration
>
> ..so, adding the following to geoclue.conf - odd that it's not there in the first place :P

Because it should not be there. That is not a whitelist of ONLY
clients we give location to but rather apps that bypass the agent
authorization, either cause they are system components or have their
own means/UI to authorize apps.

Having said that you are not the first one to report this strange
issue that I fail to reproduce:

https://bugzilla.redhat.com/show_bug.cgi?id=1214978

But I'll have another look into this issue next week. Please comment
on that bug and CC yourself.

> $ sudo G_MESSAGES_DEBUG=Geoclue /usr/local/lib/geoclue-2.0/geoclue -t 60
> (geoclue:18455): Geoclue-DEBUG: Available accuracy level from GClueWifi: 4
> (geoclue:18455): Geoclue-DEBUG: WiFi device 'wlan0' added.
> (geoclue:18455): Geoclue-DEBUG: Available accuracy level from GClueWifi: 6
> (geoclue:18455): Geoclue-DEBUG: New agent for user ID '1001'
> (geoclue:18455): Geoclue-DEBUG: Number of connected clients: 1
> (geoclue:18455): Geoclue-DEBUG: Service now in use
> (geoclue:18455): Geoclue-DEBUG: GClueLocator now active
> (geoclue:18455): Geoclue-DEBUG: GClueWifi now active
> (geoclue:18455): Geoclue-DEBUG: Not starting GClue3G (accuracy level: 0). Requested accuracy level: 8.
> (geoclue:18455): Geoclue-DEBUG: Not starting GClueCDMA (accuracy level: 0). Requested accuracy level: 8.
> (geoclue:18455): Geoclue-DEBUG: Not starting GClueModemGPS (accuracy level: 0). Requested accuracy level: 8.
> (geoclue:18455): Geoclue-DEBUG: 'org.gnome.Maps' started.
> (geoclue:18455): Geoclue-DEBUG: WiFi AP 'Livebox-1250' added.
> (geoclue:18455): Geoclue-DEBUG: WiFi AP 'Livebox-1250' added.
> (geoclue:18455): Geoclue-DEBUG: Refreshing location..
> (geoclue:18455): Geoclue-DEBUG: Network available
> (geoclue:18455): Geoclue-DEBUG: Sending following request to 'https://location.services.mozilla.com/v1/geolocate?key=geoclue':
> {"wifiAccessPoints":[{"macAddress":"00:19:70:af:ae:26","signalStrength":-84}]}
>
>
> (geoclue:18455): GLib-Net-WARNING **: The anchor file name for used with a GTlsFileDatabase must be an absolute path, and not relative: path=/usr/local/etc/ssl/certs/ca-certificates.crt
>
> (geoclue:18455): Geoclue-WARNING **: Failed to query location: Unacceptable TLS certificate
>
> ..but:
>
> $ ls -l /usr/local/etc/ssl/certs/ca-certificates.crt
> -rw-r--r--    1 root     root        245341 Feb  9  2013 /usr/local/etc/ssl/certs/ca-certificates.crt

Those errors are from glib, geoclue just use plain old libsoup and
glib API to access the network. Pretty sure libsoup on your system is
broken for HTTPS or your cert file is too old. I'd advice to file a
bug against libsoup for this.

-- 
Regards,

Zeeshan Ali (Khattak)
________________________________________
Befriend GNOME: http://www.gnome.org/friends/