Summary: | GeoClue is a mystery to integrate: Include rules for polkit please | ||
---|---|---|---|
Product: | GeoClue | Reporter: | Tristan Van Berkom <tristan.van.berkom> |
Component: | General | Assignee: | Geoclue Bugs <geoclue-bugs> |
Status: | RESOLVED NOTOURBUG | QA Contact: | Geoclue Bugs <geoclue-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | bigon |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Tristan Van Berkom
2015-11-12 11:25:34 UTC
(In reply to Tristan Van Berkom from comment #0) > It seems that debian is rolling it's own geoclue-2.0.rules and installing it > into /usr/share/polkit-d/rules.d > > When building a system from scratch, geoclue just has no chance of working > without this essential file being installed. It's not needed. There are no polkit checks in geoclue itself. It's a debian problem (and it would be good if there was an upstream bug with discussions about this). The polkit rule has been added in debian because modemmanager is compiled in "strict" mode and block locations request by default. As stated in the debian/changelog file: * [8d8c2fe3] Add polkit rules and pkla files to allow geoclue to query a modem location (Closes: #765184) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765184 Well, until MM devs implement this: https://bugs.freedesktop.org/show_bug.cgi?id=85036 I'm afraid you're going to have to be doing what you are currently doing in debian. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.