This bug was fixed in the package gpsd - 3.20-6
---------------
gpsd (3.20-6) unstable; urgency=medium
[ Bernd Zeimetz ]
* [b0d9ef06] Fix autopkgtest for new systemd releases.
Thanks to Michael Biebl (Closes: #953760)
[ Christian Ehrhardt ]
* [4c4e5ea1] device-hook apparmor fixes (LP: #1868363)
The manpage defines a hook that is called by gpsd which due to current
confinement it is unable to run.
- d/usr.sbin.gpsd: allow to call the /etc/gpsd/device-hook in the
apparmor profile
- d/usr.sbin.gpsd: allow to map and execute the own binary as needed
in some containers
- d/usr.sbin.gpsd: allow to run common shell interpreters bash/dash
That hook will run within the confinement of gpsd, so if it is expected
to do anything more special a user will have to allow that in
/etc/apparmor.d/local/usr.sbin.gpsd
Signed-off-by: Christian Ehrhardt <[email protected]>
-- Bernd Zeimetz <[email protected]> Sat, 28 Mar 2020 22:16:13 +0100
** Changed in: gpsd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868363
Title:
/etc/gpsd/device-hook not actually called
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpsd/+bug/1868363/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
