kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

Sassan, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** Tags added: needs-kernel-logs needs-upstream-testing

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

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

Title:
  No Bluetooth Device Detected in hcitool dev

Status in The Linux Kernel:
  New
Status in “bluez-utils” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My TOSHIBA Satellite A100 has a built-in Bluetooth device (so I
  suppose this must be a PCI hw), and the wireless adapter has an
  external switch for turning on/off. The problem is that no device is
  found in "hcitool dev". I dont find anything related to Bluetooth in
  lspci. It sometimes works fine when I restart the system for ten
  times, but other times I can't get it to work, no matter how many
  times I restart the Bluetooth daemon or turn it off and on again. It
  works absolutely fine in Win XP. I also get no results from hciconfig,
  however the following lines are present in dmesg when the system
  starts up

  [   21.100000] Failure registering capabilities with primary security module.
  [   21.280000] Bluetooth: Core ver 2.11
  [   21.280000] NET: Registered protocol family 31
  [   21.280000] Bluetooth: HCI device and connection manager initialized
  [   21.280000] Bluetooth: HCI socket layer initialized
  [   21.292000] Bluetooth: L2CAP ver 2.8
  [   21.292000] Bluetooth: L2CAP socket layer initialized
  [   21.340000] Bluetooth: RFCOMM socket layer initialized
  [   21.340000] Bluetooth: RFCOMM TTY layer initialized
  [   21.340000] Bluetooth: RFCOMM ver 1.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/180659/+subscriptions