Package: gpsd
Version: 3.10+dev3~d6b65b48-1
Severity: grave
Justification: renders package unusable
Since the switch to systemd, gpsd's support for hotplug of USB devices is
broken using the default configuration. This means that for most users, just
installing gpsd and plugging in a GPS does not work, and it breaks working
installations upon upgrade.
The problem is that the udev hotplug script and gpsd have diverging views of
what the control socket path is.
When gpsd is installed on jessie, it is launched by systemd as follows:
gpsd -N
=> it uses gpsd's default control socket path: /var/run/gpsd.sock
This is confirmed by running lsof -p `pidof gpsd`
gpsd 5271 gpsd 3u unix 0xffff8800a10127c0 0t0 71137
/var/run/gpsd.sock
The udev hotplug script on the other hand reads /etc/default/gpsd to determine
the path of the control socket, and the default value is:
# gpsd control socket location.
GPSD_SOCKET="/run/gpsd/gpsd.sock"
As a result of this, when the GPS is plugged in, the hotplug script thinks gpsd
is not running, and launches a new instance of gpsd. This new instance of gpsd
does not work as the port on which gpsd listens is already taken by the first
process.
Please either change the default value of GPSD_SOCKET in /etc/default/gpsd or
change the systemd launch script so that it respects GPSD_SOCKET.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages gpsd depends on:
ii adduser 3.113+nmu3
ii init-system-helpers 1.20
ii libbluetooth3 5.21-1
ii libc6 2.19-7
ii libdbus-1-3 1.8.6-1
ii libgps21 3.10+dev3~d6b65b48-1
ii libusb-1.0-0 2:1.0.19-1
ii lsb-base 4.1+Debian13
ii netbase 5.2
ii systemd-sysv 208-6
Versions of packages gpsd recommends:
ii python 2.7.8-1
ii udev 208-6
Versions of packages gpsd suggests:
ii dbus 1.8.6-1
pn gpsd-clients <none>
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
