bluez init.d script lost its LSB headers in Karmic

Bug #399158 reported by Martin-Éric Racine
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: bluez

'insserv' reports that the initscript for bluez (/etc/init.d/bluetooth) misses part of its LSB header. A simple diff between the Jaunty and Karmic versions of the script confirms that the Karmic version indeed misses half of the required LSB header lines and the closing statement of the LSB comment.

ProblemType: Bug
Architecture: i386
Date: Tue Jul 14 10:22:24 2009
DistroRelease: Ubuntu 9.10
Package: bluez 4.45-0ubuntu1
ProcEnviron:
 LANGUAGE=fi_FI:fi:en_GB:en
 PATH=(custom, user)
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-10.12-generic
SourcePackage: bluez
Uname: Linux 2.6.30-10-generic i586

Related branches

Revision history for this message
Martin-Éric Racine (q-funk) wrote :
Revision history for this message
Martin-Éric Racine (q-funk) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bluez - 4.45-0ubuntu2

---------------
bluez (4.45-0ubuntu2) karmic; urgency=low

  * debian/bluez.bluetooth.init:
    - Fix an error that broke LSB compliance in last upload (LP: #399158)
    - Check for /sbin/udevadm.upgrade. If it exists, we shouldn't be running
      any triggers. (LP: #399287)

 -- Mario Limonciello <email address hidden> Tue, 14 Jul 2009 13:33:26 -0500

Changed in bluez (Ubuntu):
status: New → 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.