https://bugzilla.novell.com/show_bug.cgi?id=727876 https://bugzilla.novell.com/show_bug.cgi?id=727876#c1 --- Comment #1 from Bryan Webb 2011-11-02 23:04:59 UTC --- Oops, I forgot 2 more... Nov 2 16:03:05 t4 bluetoothd[13795]: Parsing /etc/bluetooth/input.conf failed: No such file or directory Nov 2 16:03:05 t4 bluetoothd[13795]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory So, the following 3 files should be added to the bluez release package: /etc/bluetooth/audio.conf /etc/bluetooth/input.conf /etc/bluetooth/serial.conf -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=727876 https://bugzilla.novell.com/show_bug.cgi?id=727876#c3 --- Comment #3 from Bryan Webb 2011-11-03 19:20:42 UTC --- Sorry. How about "Bluetooth dongle"? I have a few I'm experimenting with... - IOGEAR GBU221 (a class 2 device) Bluetooth dongle - IOGEAR GBU421 (a class 2 device) Bluetooth dongle - ABE UB22S Bluetooth dongle Any of these, when plugged into a USB port, are recognized by Linux/bluez, and generate the /var/log/messages entries quoted above. The immediate intent is to use SPP (serial port profile)/RFCOMM over the device^H^H^H^H^H^Hdongle. The GBU421 claims to support A2DP audio support, HID, SPP, PAN, DUN, HFP, and File Transfer -- which leads me to believe all 3 of these files are in some cases needed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=727876 https://bugzilla.novell.com/show_bug.cgi?id=727876#c5 --- Comment #5 from Stefan Seyfried 2011-11-04 06:49:00 CET --- You don't need those files. I'm getting the same messages on my adapters and ppp dialup (which uses the serial port profile), a2dp and headset audio as well as keyboard and mice work just fine. There is probably no documentation on those files because nobody should ever need to use them ;-) All usb bluetooth dongles I came across the last few years support all profiles. AFAICT it is more a property of the software stack than of the hardware - but manufacturers like to write long lists of what they support ;-) The only problem I can see here is that there is a scary-looking message when there should be none. However, that's something best solved upstream with the bluez folks. So unless you have a specific example of a featurenot working because of the "missing" serial.conf, I'm inclined to fix this bug as "worksforme" :-) Best regards -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.