Comment 27 for bug 284982

The problem everybody is having seems a software thing, a lot of people is having problems with connections.

I think I never had errors on dmesg. I removed the blueman repository and reverted to standard ubuntu config.

If I put now the usb bluetooth dongle and click setup new device->Forward the detection of the nintendo wiimote is instantaneus the problem is connecting, if I click forward:

Pairing wih Nintendo RVL-CNT-01 failed

Looking at dsmesg:

[ 121.654024] Bluetooth: L2CAP ver 2.11
[ 121.654034] Bluetooth: L2CAP socket layer initialized
[ 121.677795] Bluetooth: SCO (Voice Link) ver 0.6
[ 121.677806] Bluetooth: SCO socket layer initialized
[ 121.702842] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 121.702853] Bluetooth: BNEP filters: protocol multicast
[ 121.720389] Bluetooth: RFCOMM socket layer initialized
[ 121.720676] Bluetooth: RFCOMM TTY layer initialized
[ 121.720684] Bluetooth: RFCOMM ver 1.10
[ 121.758876] Bridge firewalling registered
[ 121.759112] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
[ 172.856849] CPU0 attaching NULL sched-domain.
[ 172.856860] CPU1 attaching NULL sched-domain.
[ 172.857834] CPU0 attaching sched-domain:
[ 172.857839] domain 0: span 0-1 level MC
[ 172.857843] groups: 0 1
[ 172.857850] CPU1 attaching sched-domain:
[ 172.857852] domain 0: span 0-1 level MC
[ 172.857855] groups: 1 0
[ 245.576132] hci_cmd_task: hci0 command tx timeout

The program lswm detects the device without problems, wmgui gives:
Socket connect error (control channel)

I have used my wiimotes with same hardware with former ubuntu versions, and it just worked. Something has been broken in the software side.