Regression : Inbuilt Bluetooth devices are no longer recognised

Bug #347512 reported by Neil Broadley
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

On my both an old Dell x300 and a new Toshiba U-400 laptop, the built in bluetooth device is not recognised in Jaunty 9.04. An external dongle, however, is recognised and works correctly. I have reproduced this behaviour using both Bluez-gnome and Blueman 1.02 (from Blueman developer's PPA).

Using Intrepid 8.10, the internal bluetooth device is recognised correctly in both laptops.

The built-in in bluetooth dongle is correctly identified on my MacMini, so this issue is related only the certain bluetooth models in those affected laptops.

This bug report is possibly linked to https://bugs.launchpad.net/blueman/+bug/317566, but that bug is filed directly against blueman and I believe that this is a kernel/driver issue.

Please let me know if there is additional information I can provide to diagnose the issue.

Revision history for this message
Neil Broadley (scaine) wrote :

It turns out that this is directly related to bug : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/45021

My Toshiba U-400 needs the Omnibook module in order to use its internal Bluetooth adaptor. Full instructions are here :
http://docs.google.com/View?docid=dgd53r6d_36hqmmh4hn, which outlines how to install module-assistant from Debian, compile the omnibook-source module and add it to the modprobe. Works a charm.

Revision history for this message
Monkey (monkey-libre) wrote :

I think that this bug affect to gnome-bluetooth

affects: ubuntu → gnome-bluetooth (Ubuntu)
Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

gnome-bluetooth is only a Graphical frontend so it has nothing to do with that problem.
I reassign to ubuntu in order that someone reassign to the right component (kernel?)

affects: gnome-bluetooth (Ubuntu) → ubuntu
Revision history for this message
David Tombs (dgtombs) wrote :

Assigning to linux, they can tell us if the problem is elsewhere.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Scaine,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 347512

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Neil Broadley (scaine) wrote :

The issue still exists in Lucid (10.04) Beta 1. There is no detection of my Toshiba's bluetooth hardware without the omnibook module.

Sadly, I've already used module assistant to create a new omnibook-capable kernel on my laptop which experiences the issue, so I don't want to be running that kernel when I run the apport-collect command. I'll reboot over the next couple of days and send that information.

I've never tested an upstream kernel before either, but will follow the link and do my best to complete that work too.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
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.