Bluetooth light comes on but I don't think I have blue tooth.

[encompass]

When I boot up the system for the first time ever I have seen the bluetooth light has turned on.
Now this wouldn't bother me, except I don't think I have bluetooth. :/
Interesting bug, but I think it would be important to make sure I do or don't. I would love to found out how to test something like that. ;)
I have found that the light is not on after coming from some hibernations. For example now. It also does the beep telling me the there was something wrong while I came out of hibernation.

[Laurent Bigonville (bigon)]

Hi,

try to type hciconfig in a shell. what do you get?

[encompass (encompass)]

sure, I get no result... just drops back to the console.
Twas my thought to... no bluetooth.
After looking at my model of PC and the information when I bought it. I don't have bluetooth.

[Laurent Bigonville (bigon)]

Closing as invalid

[encompass (encompass)]

Why invalid... what do you mean?

[Laurent Bigonville (bigon)]

When you talk about a "bluetooth light", is it an hardware led on computer?

[encompass (encompass)]

Yeah, I have a blue led on my laptop that lights up telling me that "bluetooth" is in use. But we all know it's just a light. This has never happened before in my versions of Linux.
Just wanted to report it so people don't get confused about it.

[Laurent Bigonville (bigon)]

could add more information on your laptop (model,...)

and attach the output of lspci and lsusb

thx

[encompass (encompass)]

jason@essence:~$ sudo lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
06:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
06:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
06:01.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
06:01.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)

[encompass (encompass)]

jason@essence:~$ lsusb
Bus 005 Device 002: ID 174f:a311
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 002: ID 05ac:0304 Apple Computer, Inc. Apple Optical USB Mouse [Mitsumi]
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
jason@essence:~$
Just to tell you the 174f device is a webcam.

[encompass (encompass)]

Is there other information that you need now?

[macssam (capp)]

even after removing ubuntu 9 and installing a new win7 system
and reseting bios to default
the bluetooth light stays on on my laptop acer ...

[Thomas Hotz (thotz-deactivatedaccount)]

encompass: Is this still an issue for you? Which Ubuntu version do you use? Thank you for telling us!

macssam: This seems more than a hardware or bios problem.

[encompass (encompass)]

The issue is still there, but minor as I know I don't have bluetooth and
simply ignore it.
This is not a bios problem as it doesn't show up until the kernel starts
to load and doesn't show up on older version of ubuntu or free dos.

On 11/22/2012 03:13 PM, Thomas Hotz wrote:
> encompass: Is this still an issue for you? Which Ubuntu version do you
> use? Thank you for telling us!
>
> macssam: This seems more than a hardware or bios problem.
>
> ** Changed in: ubuntu
> Status: Confirmed => Incomplete
>
> ** Changed in: ubuntu
> Assignee: Laurent Bigonville (bigon) => (unassigned)
>

[jhoechtl (johann-hoechtl)]

Instead of opening a new report I try to add my report here as it seems to be the closest match I can get.

After upgrading to kernel 3.5.xxx (Kubuntu 12.10), I have ... probably ... the same symptom. It's described in detail here
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1072118

but I repeat for convenience:

The described behaviour is only visible, when shutting down with bluetooth disabled.
sudo /etc/init.d/bluetooth restart get's the applet catch the right state and back working.

If I reboot the laptop of with bluetooth enabled, it will come up the next time working. Working means the status is correctly recognized by the Kubuntu applet and bluetooth is working.

If I disable Bluetooth, the hardware display on the laptop remains lit. In Kubuntu 12.04, the display went off. However, the device is properly unpowered, as it saves 4 Watts (checked with meter). After reboot, the state is correctly remembered, that means the device is unpowered (the hardware indication is still lit btw.) However, the bluetooth icon in panel will recognize the adapter as powered. Unpowering has no effect and doesn't work: If I choose unpower in the applet, simply nothing happens, it remains thinking it is still powered, while it is unpowered. In other words, there is not way to power bluetooth with the applet.

service bluetooth stop
service bluetooth start

will not bring bluetooth back ... it will remain unpowered and the applet thinking it is powered.

However, issuing

sudo hciconfig hci0 reset

WILL power bluetooth AND the applet back working, so that it can be powered / unpowered.

So I think the bluetoothd stack doesn't recognize the unpowered adapter, yet correctly remains it unpowered (state keeps preserved).

[penalvch (penalvch)]

encompass, 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.

[encompass (encompass)]

I no longer can test this bug. The computer doesn't function any more.
BR,
Jason

On Tue, Aug 13, 2013 at 1:37 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> encompass, 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 removed: bluetooth led
> ** Tags added: needs-kernel-logs needs-upstream-testing
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/182101
>
> Title:
> Bluetooth light comes on but I don't think I have blue tooth.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/182101/+subscriptions
>

[penalvch (penalvch)]

encompass, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/182101/comments/16 regarding the hardware is now broken. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.