-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
policykit issue for Geoclue and ModemManager #118
Comments
The rule in here seemed to fix it https://githubmemory.com/repo/dreemurrs-embedded/Pine64-Arch/issues/212
There seemed a concern about it being a good rule though. |
Is that not something that gets resolved after this: https://gitlab.freedesktop.org/geoclue/geoclue/-/commit/a9aea6a4948e2ff9ec5ff066cf20dac069c0d3a0 ? |
No, that's to do with phosh acting as an agent for applications wanting to access geoclue. Not geoclue accessing location sources, such as the EG25. |
Marius found a better rule polkit.addRule(function(action, subject) {
if ((action.id == "org.freedesktop.ModemManager1.Device.Control" ||
action.id == "org.freedesktop.ModemManager1.Location") &&
subject.user == "geoclue") {
return polkit.Result.YES;
}
}); |
geoclue maintainer has been contacted to add it to geoclue2 package. |
Contributed to that part: https://gitlab.freedesktop.org/geoclue/geoclue/-/merge_requests/102 So it's going to be included in next geoclue2 release. |
Looking at the output of
journalctl -flu geoclue
restarting geoclue and then starting Gnome Maps shows thisLooks like geoclue can't access the modem location stuff because of a policykit issue.
The text was updated successfully, but these errors were encountered: