Comment 6 for bug 1014992

Hello again,

I have done some tests with the latest development release of Ubuntu (trusty-desktop-i386.iso, downloaded on 13.01.2014).
The bug is still there.

Here the steps I've done to check it:
- Boot ubuntu from CD (live cd, image from 13.01.2014)
- Start the bluetooth applet
- Open a terminal and enter.
  "hcitool scan" will list my bluetooth device correctly (MAC: 00:12:6F:08:98:FF)
- Start the bluetooth applet from panel to add a new bluetooth device. In the "PIN-Option" screen
  I've checked fixed pin '1234'. On the first time a number is shown which I should enter on the bluetooth device.
  This doesn't work for me. My bluetooth device could not do this. The pairing failed after a few seconds.
  On the second try this number isn't shown and pairing is OK. (This behaviour is reproducable ;-).
- Back into the terminal I entered
  "sudo usermod -a -G dialout ubuntu"
  to add the default user ubuntu to the dialout group and than login again to activate this setting with:
  "sudo login" with user "ubuntu" and empty password.
- "rfcomm connect 1 00:12:6F:08:98:FF" fails with error "Can't open RFCOMM device: Permission denied"
- "sudo rfcomm connect 1 00:12:6F:08:98:FF" works

The tests with the latest upstream kernel available I have not done. This machine is on my work and I don't
want to replace my 12.04LTS here.
But if it's useful I can do it on my new PC at home.
Should I set the "kernel-bug-exists-upstream" flag now?