This bug was fixed in the package gpsd - 3.20-8ubuntu0.1
---
gpsd (3.20-8ubuntu0.1) focal; urgency=medium
* d/usr.sbin.gpsd: improve apparmor rules for PPS usage
(LP: #1872175 LP: #1872178)
-- Christian Ehrhardt Thu, 30 Apr
2020 12:40:23 +0200
** Changed in: gpsd (Ubuntu Fo
As expected before the fix I wasn't able to use any PPS.
Upgrading to gpsd 3.20-8ubuntu0.1 worked without any further breakage.
We see on upgrade that the apparmor profile is replaced:
[12408.110277] audit: type=1400 audit(1589444818.093:34): apparmor="STATUS"
operation="profile_replace" profile
FYI - I'll verify this tomorrow morning once I've freed up another system.
For the sake of completeness I want to check this on another arch than where I
wrote the fixes. TO ensure this really helps in a generic way.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hello Mark, or anyone else affected,
Accepted gpsd into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gpsd/3.20-8ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubun
Waiting in Focal-unapproved since yesterday - FYI autopkgtest sniff
tests are good as well in
https://bileto.ubuntu.com/excuses/4047/focal.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872178
Ti
The auto-sync in groovy also included 3.20-8/3.20-9 which covers this
issue here:
gpsd (3.20-10) unstable; urgency=medium
[ Christian Ehrhardt ]
* [7670b61e] exchange gpsd-client/tools content
* [fb81a96a] examples also need to be in -clients instead of -tools then
* [7f8d06a8] d/control[
This bug was fixed in the package gpsd - 3.20-11
---
gpsd (3.20-11) unstable; urgency=medium
[ Christian Ehrhardt ]
* [232c8d73] d/rules: fix ubxtool to use python3 in the gpsd package (LP:
#1878158)
Signed-off-by: Christian Ehrhardt
-- Bernd Zeimetz Tue, 12 May 2020 13:
** Also affects: gpsd (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872178
Title:
GPSD unable to use Kernel PPS
To manage notifications a
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/gpsd/+git/gpsd/+merge/383405
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872178
Title:
GPSD unable to use Kernel P
** Description changed:
- I am working with gpsd and a pulse-per-second (PPS) signal on a serial
- port.
+ [Impact]
+
+ * Current GPSD apparmor isolation is too strict to use PPS devices
+properly.
+
+ * backport changes we added to 20.10 to fix this
+
+
+ [Test Case]
+
+ * Set up a P
FYI - fix submitted as part of PR https://salsa.debian.org/debian-gps-
team/pkg-gpsd/-/merge_requests/5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872178
Title:
GPSD unable to use Kernel PPS
To
See https://bugs.launchpad.net/ubuntu/+source/gpsd/+bug/1872175/comments/7
This makes it work for me, but needs security sign off and a few more tests.
TL;DR: some extra apparmor rules for PPS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I'm seeing gpsd to set up the PPS sources (and yield it on stop):
[ 801.277262] pps pps1: new PPS source usbserial0
[ 801.277308] pps pps1: source "/dev/ttyUSB0" added
...
[ 1706.141555] pps pps1: removed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Changed in: gpsd (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872178
Title:
GPSD unable to use Kernel PPS
To manage notif
I'm slowly but surely ramping up my test bed.
On a broken PPS device you'd get:
ubuntu gpsd[2585]: gpsd:ERROR: KPPS:/dev/pps0 time_pps_setparams(mode=0x1001)
failed: unknown error
That happens if e.g. a device announced PPS but since it didn't
initialize the kernel driver (by not soldering the
FYI I usually used a usb GPS to check gpsd's function e.g. on a merge of a new
version.
But that one had no PPS capability.
I now ordered one that should have it (via some tweaks on the USB port).
With the current times a delivery from Asia might take a few extra day.
I'll debug this further once
Hi Mark,
Disclaimer: my gps device has no PPS so I'm stabbing a bit in the dark here. I
beg your pardon for that in advance.
By default devices are hot-added as they are detected e.g. via udev.
But for PPS there is a permission issue if you have it set up like it.
>From [1]: "In order to present
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872178
Title:
GPSD unable to use Kernel PPS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
** Also affects: gpsd (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: chrony (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872178
Title:
GPSD unable to use Kern
19 matches
Mail list logo
