Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#20640 - /etc/conf.d/gpsd needs "export" keyword
Attached to Project:
Community Packages
Opened by Bryce Nordgren (bnordgren) - Friday, 27 August 2010, 20:39 GMT
Last edited by Sergej Pupykin (sergej) - Sunday, 29 August 2010, 07:19 GMT
Opened by Bryce Nordgren (bnordgren) - Friday, 27 August 2010, 20:39 GMT
Last edited by Sergej Pupykin (sergej) - Sunday, 29 August 2010, 07:19 GMT
|
DetailsDescription:
gpsd does not start correctly from the udev rules when a device is inserted. The daemon does indeed start, but ignores all options set in /etc/conf.d/gpsd. In essence: 1] the "gpsd.hotplug" python script examines environment variables to determine the options to put on the gpsd command line; 2] the "gpsd.hotplug.wrapper" sources /etc/conf.d/gpsd to get the options 3] /etc/conf.d/gpsd sets shell variables but does NOT export them to the environment, hence the python hotplug script misses them. This might be an upstream installation bug, but it can be fixed in the packaging here. Just add export in front of all the shell variable declarations in /etc/conf.d/gpsd. Additional info: * package version(s): gpsd-2.95-1 Steps to reproduce: 1] Start system (ensure gpsd NOT running). 2] Plug in gps 3] in messages.log, note the line that says "launching /usr/sbin/gpsd -F /var/run/gpsd/gpsd.sock" (the extra space before "-F" is where the GPSD_OPTIONS from /etc/conf.d/gpsd should be; but isn't). |
This task depends upon