This bug was fixed in the package geoclue-2.0 - 2.7.0-3ubuntu3
---
geoclue-2.0 (2.7.0-3ubuntu3) mantic; urgency=medium
* debian/geoclue-2.0.install, debian/local/usr.libexec.geoclue,
debian/geoclue-2.0.maintscript:
- remove the apparmor profile which was added by Debian
** Tags removed: rls-mm-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2030951
Title:
geoclue service prevented from working by apparmor profile
Status in geoclue-2.0
FWIW, I disabled the AppArmor profile and clients still don't connect or
rather geoclue times out, don't know what's going on but probably
separate bug. Even deleted my modem devices and masked modemmanger,
thinking it may be talking to that and hanging there
--
You received this bug
The attached patch is enough to get the service working but doesn't
accomodate for the GPS usecase, I expect there is more than the one
denial Julian listed.
I would suggest updating the profile as we can but not putting it in
enforce mode for mantic.
** Patch added: "geoclue.patch"
** Summary changed:
- geoclue.service fails to start
+ geoclue service prevented from working by apparmor profile
** Changed in: geoclue-2.0 (Ubuntu)
Assignee: (unassigned) => Sebastien Bacher (seb128)
--
You received this bug notification because you are a member of Desktop
Packages,
5 matches
Mail list logo