Hi. The original reporter of this bug mentioned two issues, the "invalid option passed to rfcomm" issue, and the "mising dev parameter" message from rfcomm.
The first issue has been fixed with the new release, but not the second. I'm experiencing the same bug with this new version, and because of it my bluetooth devices are not working. The issue seems to be that rfcomm can't see the bluetooth device, since rfcomm show all doesn't show anything (hcitool and hciconfig can see the device just fine). Since it was already mentioned in this bug I'm not sure if it's appropiate to continue here or if I should file a new bug about it. Either way I don't think bluez 5.x should go into testing before it's resovled. The bug is definetly in the bluez package, it'll start or stop working if I upgrade/downgrade between the version in sid and the verison in testing with no other change on my system. Please let me know about any info you need about my system to narrow down what the problem could be, and if I should file a new bug or continue here. Thanks, Andreas Eriksson
