Hello,
geoclue2 should be especially configured to allow applications to
request the location. Add something like that in :
[redshift]
allowed=true
system=false
users=
https://wiki.archlinux.org/index.php/Redshift#Failed_to_run_Redshift_due_to_geoclue2
I'm not 100% sure if there is an other way to do so without modifying
the config.
I would also suggest you to disable the old geoclue support, I really
would like to remove the package from the archive.
Cheers,
Laurent Bigonville
Le Mon, 25 May 2015 16:22:19 +0530,
Ritesh Raj Sarraf r...@debian.org a écrit :
Control: retitle -1 GeoClue 2 not accessible by normal user over the
bus
Okay. There's no need for any headers. Hence retitled accordingly.
But can you guys please shed some light on who is currently consuming
geoclue2 ?
From what I investigated so far, it registers on the system bus, but
no one is allowed to invoke its methods.
As my normal user creds, I tried to invoke the dbus methods and it
timed out. But as per the dbus policy for geoclue, it states that
such method invocation should be allowed.
Second, redshift for example, is using the o.f.GeoClue2.Location path,
where as Debian's geoclue2 is providing o.f.GeoClue2.Client.Location
path. Is it expected ?
On Monday 25 May 2015 03:42 PM, Debian Bug Tracking System wrote:
Thank you for filing a new Bug report with Debian.
This is an automatically generated reply to let you know your
message has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due
course.
Your message has been sent to the package maintainer(s):
Laurent Bigonville bi...@debian.org
If you wish to submit further information on this problem, please
send it to 786...@bugs.debian.org.
Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
