update-manager unable to configure gpsd

Bug #423629 reported by Nasa
16
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gpsd (Ubuntu)
Fix Released
Undecided
Bernd Zeimetz

Bug Description

Binary package hint: update-manager

Update-manager attempts to configure gpsd, however, whatever options it tries to use gpsd complains about. A dialog box shows up commenting about using "-F" and/or adding in the appropriate com ports. This was with Alpha 4 of Karmic moving from Jaunty.

What I expected:
Given that gpsd was already configured, I expected the update-manager to use those settings and move on (ie: I didn't expect to see anything)

What happened:
At 3 different points in the upgrade sequence I got a dialog box with an error message from gpsd. The dialog box had options of back and next -- however, neither button did anything and the only way to have update continue was to hit the x button on the top right hand corner.

/var/log/dist-upgrade will be added later.

Revision history for this message
Nasa (tsx-5) wrote :
Revision history for this message
to be removed (liw) wrote :

Since update-manager just installs the updated gpsd package, this sounds like a bug in that package
(perhaps the maintainer scripts). Reassigning.

affects: update-manager (Ubuntu) → gpsd (Ubuntu)
Revision history for this message
Bernd Zeimetz (bzed) wrote : Re: [Bug 423629] Re: update-manager unable to configure gpsd

Lars Wirzenius wrote:
> Since update-manager just installs the updated gpsd package, this sounds like a bug in that package
> (perhaps the maintainer scripts). Reassigning.
>
> ** Package changed: update-manager (Ubuntu) => gpsd (Ubuntu)
>

This might be a bug in gpsd and update-manager - not sure about it.I'm not able
to reproduce it on Debian, though.
The last update brought some sanety checks for the configuration, so it might
happen that a debconf questions pops up although gpsd seemed to be configured
correctly before, while the chosen configuration was never able to work
properly. I can try to debug this if I can get the /etc/default/gpsd from before
the update and probably some more informations about which version was
installaed and so on.

--
 Bernd Zeimetz Debian GNU/Linux Developer
 http://bzed.de http://www.debian.org
 GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79
                   ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F

Revision history for this message
Nasa (tsx-5) wrote :

# Default settings for gpsd.
# Please do not edit this file directly - use `dpkg-reconfigure gpsd' to
# change the options.
START_DAEMON="true"
DAEMON_OPTS=""
DEVICES="/dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller-if00-port0"
USBAUTO="true"

Note: I did edit it by hand (as dpkg-reconfigure returns an error about package being incomplete or broken)

Version reported by gpsd is 2.39

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

Nasa wrote:
> # Default settings for gpsd.
> # Please do not edit this file directly - use `dpkg-reconfigure gpsd' to
> # change the options.
> START_DAEMON="true"
> DAEMON_OPTS=""
> DEVICES="/dev/serial/by-id/usb-Prolific_Technology_Inc._USB-Serial_Controller-if00-port0"
> USBAUTO="true"

Your problem here is that DAEMON_OPTS is empty, it needs to contain a definition
for the control socket - the new debconf questions ensure that. I'm thinking
about creating a new question for that or something like that to make it
obvious, but that won't happen before the next upload.

--
 Bernd Zeimetz Debian GNU/Linux Developer
 http://bzed.de http://www.debian.org
 GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79
                   ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F

Revision history for this message
Nasa (tsx-5) wrote :

Because I suck, and failed to add all pertinent information... The DAEMON_OPTS was always empty (from initial install of jaunty).... The only thing I edited was the DEVICES line and that was after my attempts to upgrade; ie: after upgrading to the Beta version. I don't recall what was in the DEVICES line prior to me changing it (I have two usb serial type devices and wanted to avoid gpsd finding the wrong one).

This problem doesn't seem to affect the running of gpsd itself, rather it causes more of a problem for upgrading packages which have gpsd as a requirement.

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

The whole debconf stuff was reworked in 2.39-6, which is currently sitting in Debian experimental - more changes will follow soon. This should fix such upgrade issues.

Changed in gpsd (Ubuntu):
assignee: nobody → Bernd Zeimetz (bzed)
status: New → Confirmed
status: Confirmed → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (4.0 KiB)

This bug was fixed in the package gpsd - 2.39-8ubuntu1

---------------
gpsd (2.39-8ubuntu1) lucid; urgency=low

  * Sync from Debian 2.39-8, this version is known to work. Please
    get in contact with me or Bernd before touching it again.

gpsd (2.39-8) unstable; urgency=low

  * [a9e9d167] Export needed variables for the hotplug script. (Closes:
    #556956) - thanks to Luca Niccoli
  * [254f1da4] Add a missing % which caused USB autostart to fail.
    (Closes: #556954) - thanks to Luca Niccoli
  * [2990d2cc] Updating debconf translation: pt.po (Closes: #556250) -
    thanks to "Traduz - Portuguese Translation Team"
  * [dc6305e7] Updating debconf translation: sv.po (Closes: #556580) -
    thanks to Martin Bagge
  * [6066918d] Add missing : in po files and unfuzzy them.

gpsd (2.39-7) unstable; urgency=low

  [ Bernd Zeimetz ]
  * [bda49bd9] Bumping Standards-Version to 3.8.3. No changes needed.
  * [cdf3c74c] Fix hotplug script environment patch to ensure that
    'None' is not passed as gpsd option.
  * [67cde41b] Don't check for "$START_DAEMON" = "true" in
    gpsd.hotplug.wrapper anymore.
  * [c4fb8bab] Go trough all debconf questions if the daemon is started
    at boot *or* USB autodetection is enabled.
  * [f929f33f] Add dbus to 'Suggests' of gpsd.
  * [9dd1656f] Rewriting gpsd.init completely. The new start-stop-daemon
    options should ensure that gpsd is stopped definitely, hopefully
    this fixes an upgrade problem which was reported on Launchpad. (LP:
    #468915) - thanks to Walter Wittel
  * [376285e7] Updating gpsd.templates after review. - thanks to Justin
    B Rye
  * [e5d5e1f7] Updating po files for new gpsd.templates.
  * [6e23af3e] Update po files after running debconf-updatepo.
  * [691c564c] Add missing : to the control path question.
  * [8da65d0a] Running debconf-updatepo again.

  [ Esko Arajärvi ]
  * [77a66dc2] Updating debconf translation: fi.po (Closes: #554478)

  [ Kenshi Muto ]
  * [389d8f08] Updating debconf translation: ja.po (Closes: #554576)

  [ dooteo ]
  * [400eada8] Updating debconf translation: eu.po (Closes: #554540)

  [ Ivan Masár ]
  * [67146d71] Updating debconf translation: sk.po (Closes: #554681)

  [ Luca Monducci ]
  * [c52ba7fa] Updating debconf translation: it.po (Closes: #555117)

  [ Eddy Petrișor ]
  * [afb4ef0b] Updating debconf translation: ro.po (Closes: #555464)

  [ Thomas Mueller ]
  * [9f7c21e9] Updating debconf translation: de.po (Closes: #555840)

  [ Miroslav Kure ]
  * [e4246738] Updating debconf translation: cs.po (Closes: #555894)

  [ Francisco Javier Cuadrado ]
  * [3a72944f] Updating debconf translation: es.po (Closes: #556035)

  [ Yuri Kozlov ]
  * [4beef045] Updating debconf translation: ru.po (Closes: #556193)

  [ marce ]
  * [325806a3] Updating debconf translation: gl.po (Closes: #555453)

gpsd (2.39-6) experimental; urgency=low

  [ Christian Perrier ]
  * [fe381184] Updating debconf translation: fr.po (Closes: #540502)

  [ Jordà Polo ]
  * [2c23a9a6] Updating debconf translation: ca.po (Closes: #544101)

  [ Clytie Siddall ]
  * [49af80a6] Updating debconf translation: vi.po (Closes: #548020)

  [ Bernd Zeimetz ]
  * [35fe08a1] Correct dependencies in init....

Read more...

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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