gpsd starts to early for bluetooth gps mice

Bug #359352 reported by Andreas Gölzer
2
Affects Status Importance Assigned to Milestone
gpsd (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

In current jaunty, during bootup gpsd starts before the bluetooth services.

I have set up, following guidelines, my bluetooth gps mouse as /dev/rfcomm1.
If I start up jaunty, gpsd does not talk with the gpsmouse, even if the mouse is activated only after bootup.
This seems to be a problem not unique to ubuntu as described on the gpsd bluetooth page, http://gpsd.berlios.de/bt.html .
As a workaround, I used:
rc-update.d -f gpsd remove
rc-update.d gpsd defaults 80
(bluetooth starts at 74)
With that, after bootup, gpsd is in a usable state.

Distribution: Ubuntu jaunty (development branch) Release: 9.04
Package: gpsd: Installed: 2.38-1ubuntu3

Related branches

Revision history for this message
Bernd Zeimetz (bzed) wrote :

Looking at the current bluez source:
DEB_UPDATE_RCD_PARAMS = "start 25 2 3 4 5 . stop 74 0 1 6 ."

which is the same as in Debian.
I'll change the default start to 26 and stop to 73 to start it before libvirt and stop it after libvirt.

Revision history for this message
Bernd Zeimetz (bzed) wrote :

Fixed in 2.39-2, which should be synced soon.

Changed in gpsd (Ubuntu):
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gpsd - 2.39-2

---------------
gpsd (2.39-2) unstable; urgency=low

  * [765fde7b] Calculate soname and library version properly.
  * [1da6bffd] Support the "status" action in the init.d script.
    (Closes: #528688) - thanks to Peter Eisentraut
  * [634d40b0] Make gpsd.hotplug.wrapper work with Ubuntu. (LP: #367197)
  * [1a66eb21] Start gpsd after bluetooth. (LP: #359352)
  * [1e5ffb92] Adding patch to fix a crash in libgpsmm.
  * [ba4e66a1] Updating symbols file after fixing libgpsmm.

 -- Luca Falavigna <email address hidden> Mon, 22 Jun 2009 15:53:32 +0100

Changed in gpsd (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.