Package: gpsd Version: 3.10+dev1~a33bfd44-1 Severity: normal Hello,
I just wasted one hour (at least) of my life figuring out why gpsd doesn't work although the hardware looked fine. What was happening? First, your gpsd.socket file only opened the systemd socket (i.e. its activation placeholder) for IPv4. Therefore, if you start another gpsd or gpsmon in raw mode or other tools then it fails on v4 but is apparently lucky to open the v6 version and therefore does not fail. Great, now when I connect with a tool then, depending on which IP protocoll version the tool prefers, it connects to a gpsd which doesn't know about the hardware but starts fine via systemd. And my doesn't receive any data and the FAQs on the net say "have patience, it will take up to 20 minutes". Very funny. Sorry, if you add socket activation then please do it right! And also make sure that it fails to connect real hardware then it fails LOUDLY. And document the extra Debian config, we have README.Debian for that! Second, I wonder how the hardware path should be configured otherwise. There are lots of GPS mice with some USB-serial converter from the shelf which your hotplug file will NOT recognice. And therefore not registered when the device is connected. Or how is the user supposed to add a such GPS device to your gpsd configuration? Especially when the daemon is not running yet because of the socket activation? I have no clue and you don't provide the docs. I tried to figure out how this device might be stored but couldn't figure it out quickly. And following official information only leads you into a trap (see above) where you wonder what t.h. is going and no data comes from the daemon or related tools. So, feel free to tell me that I am acting like a drama queen here but I just reporting the first user experience and it's seriosly suboptimal. Regards, Eduard. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12.0+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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.18 ii libbluetooth3 4.101-4.1 ii libc6 2.18-4 ii libdbus-1-3 1.8.0-2 ii libgps21 3.10+dev1~a33bfd44-1 ii libusb-1.0-0 2:1.0.17-1+b1 ii lsb-base 4.1+Debian12 ii netbase 5.2 Versions of packages gpsd recommends: ii python 2.7.5-5 ii udev 204-7 Versions of packages gpsd suggests: ii dbus 1.8.0-2 pn gpsd-clients <none> -- debconf information: * gpsd/autodetection: false gpsd/daemon_options: gpsd/device: * gpsd/start_daemon: false gpsd/brokenconfig: gpsd/socket: /var/run/gpsd.sock -- error compiling committee.c: too many arguments to function -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
