Failed to acquire name 'org.freedesktop.GeoClue2'

[Zeeshan Ali (Khattak)]

On Thu, Nov 6, 2014 at 6:35 PM, Zeeshan Ali (Khattak)
<zeeshanak at gnome.org> wrote:
> On Thu, Nov 6, 2014 at 6:18 PM, Zeeshan Ali (Khattak)
> <zeeshanak at gnome.org> wrote:
>> On Thu, Nov 6, 2014 at 5:58 PM, Zeeshan Ali (Khattak)
>> <zeeshanak at gnome.org> wrote:
>>> On Thu, Nov 6, 2014 at 5:50 PM, Zeeshan Ali (Khattak)
>>> <zeeshanak at gnome.org> wrote:
>>>> On Thu, Nov 6, 2014 at 4:01 AM, Garvan Keeley <gkeeley at mozilla.com> wrote:
>>>>>
>>>>> On my non-VM arch linux, the latest code runs fine. I get the exact same output as above (the WARNING+CRITICAL), however, where-am-i outputs locations successfully.
>>>>
>>>> This gets weirder and weirder. :( Firstly, you should get *a* location
>>>> inside VMs too (wifi geolocation is unlikely to work unless you
>>>> somehow expose your wifi device inside the VM) and secondly, why are
>>>> you getting all these errors and warnings and not me. :(
>>>
>>> Actually its totally impossible that you get no extra output (other
>>> than what you already pasted) from geoclue with
>>> G_MESSAGES_DEBUG=Geoclue if your client is getting a location. You
>>> must be seeing messages  like:
>>>
>>> (geoclue:30295): Geoclue-DEBUG: Available accuracy level from GClueWifi: 4
>>> (geoclue:30295): Geoclue-DEBUG: Available accuracy level from GClueWifi: 6
>>>
>>>
>>> Having said that, i haven't tested under an environment w/o an agent
>>> (gnome-shell) running for a long time. Maybe that explains some of the
>>> issues here. I'll test that too..
>>
>> Ok, disabling the agent code, I'm also seeing (only) two of these
>> warnings/criticals so now I have a way to fix those at least:
>>
>> (geoclue:31278): GLib-GObject-WARNING **: invalid (NULL) pointer instance
>>
>> (geoclue:31278): GLib-GObject-CRITICAL **: g_signal_connect_data:
>> assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
>
> Waiting a few more seconds, I see other warnings/criticals too. I just
> pushed a fix so now at least the criticals/warnings issue should be
> resolved.

Everything should be fixed now in git master.

-- 
Regards,

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