kernel-packages team mailing list archive

[Michael Schaller <misch@xxxxxxxxxx>]

Looks like we get the error on restart of the bluetooth service because
the dbus service reload failed beforehand. Unfortunately the reload
error of the dbus service is ignored which makes troubleshooting harder
than it would need to be. IMHO this is an error in the bluez.postinst
script.

# restart dbus
dbus start/running, process 22184
# start bluetooth
start: Job is already running: bluetooth
# dpkg --configure bluez ; echo "exit code: $?"
Setting up bluez (4.101-0ubuntu11) ...
reload: Method "Reload" with signature "" on interface "com.ubuntu.Upstart0_6.Instance" doesn't exist

invoke-rc.d: initscript dbus, action "force-reload" failed.
exit code: 0


Can we update the bluez.postinst script to not ignore errors if the dbus service reload fails?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1301962

Title:
  package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10
  (Trusty) fails

Status in “bluez” package in Ubuntu:
  New

Bug description:
  During an upgrade of a vanilla Precise install to Trusty I've
  encountered already twice this issue:

  $ sudo dpkg --configure bluez
  Setting up bluez (4.101-0ubuntu10) ...
  reload: Method "Reload" with signature "" on interface "com.ubuntu.Upstart0_6.Instance" doesn't exist

  invoke-rc.d: initscript dbus, action "force-reload" failed.
  start: Job failed to start
  invoke-rc.d: initscript bluetooth, action "start" failed.
  dpkg: error processing package bluez (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   bluez

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1301962/+subscriptions