← Back to team overview

kernel-packages team mailing list archive

[Bug 589464] Re: /usr/sbin/bluetoothd doesn't get started automatically

 

This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.

** Changed in: bluez (Ubuntu)
       Status: New => Invalid

-- 
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/589464

Title:
  /usr/sbin/bluetoothd doesn't get started automatically

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: bluez

  Lucid Lynx. When I reboot, bluetooth-applet says that Bluetooth is on,
  but the icon is greyed out and it doesn't include any of the options
  to send files, etc (attaching a screenshot of bluetooth menu).
  Toggling it on and off has no effect. I've also noticed that
  bluetoothd is not running. If I start bluetoothd manually, then
  everything works fine.

  So, for some reason bluetoothd is not getting started properly, but I
  don't know how to diagnose further.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: bluez 4.60-0ubuntu8
  ProcVersionSignature: Ubuntu 2.6.32-22.35-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  Architecture: i386
  Date: Thu Jun  3 20:36:55 2010
  ExecutablePath: /usr/sbin/bluetoothd
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
  MachineType: ASUSTeK Computer INC. 1000
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=bd33138b-199c-4b7b-a000-d26406f80f15 ro quiet splash
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: bluez
  dmi.bios.date: 07/14/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1000
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x00000000
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd07/14/2008:svnASUSTeKComputerINC.:pn1000:pvrx.x:rvnASUSTeKComputerINC.:rn1000:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1000
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.
  hciconfig:
   hci0:	Type: USB
   	BD Address: 00:15:AF:FA:0E:DF ACL MTU: 1021:8 SCO MTU: 64:1
   	UP RUNNING PSCAN ISCAN 
   	RX bytes:1025 acl:0 sco:0 events:36 errors:0
   	TX bytes:1597 acl:0 sco:0 commands:36 errors:0

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