Bug 6341 - Bluetooth adapter not detected after upgrade to MGA2
Summary: Bluetooth adapter not detected after upgrade to MGA2
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-05 15:27 CEST by Brian T
Modified: 2012-06-10 23:19 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Brian T 2012-06-05 15:27:55 CEST
Description of problem:
On my Dell E4310 laptop after upgrading to Mageia 2, it says "No Bluetooth adapters have been found" in the Bluetooth module of KDE system settings and also in BlueDevil. In the Hardware section of MCC though, the Bluetooth module is detected. The bluetooth interface also appears in rfkill:

rfkill list
0: dell-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: dell-bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
3: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
4: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

Also, here's some output from dmesg:

dmesg | grep -i blue
[    9.188299] usb 2-1.7: Product: DW375 Bluetooth Module
[   15.398597] Bluetooth: Core ver 2.16
[   15.398619] Bluetooth: HCI device and connection manager initialized
[   15.398622] Bluetooth: HCI socket layer initialized
[   15.398624] Bluetooth: L2CAP socket layer initialized
[   15.398628] Bluetooth: SCO socket layer initialized
[ 2270.697625] usb 2-1.7: Product: DW375 Bluetooth Module

Bluetooth worked fine in Mageia 1 before the upgrade.

How reproducible:
Every boot

Steps to Reproduce:
1. Boot computer
2. 
3.
Comment 1 Manuel Hiebel 2012-06-10 22:30:52 CEST
does it work with hcitool scan ?

CC: sysadmin-bugs => (none)
Component: Release (media or process) => RPM Packages

Comment 2 Brian T 2012-06-10 23:19:09 CEST
Oddly enough, a few boots later, the problem just evaporated - I hadn't changed anything. In any case though, I'm closing the bug, as it's just disappeared.
Brian T 2012-06-10 23:19:36 CEST

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.