[Bug 727876] New: bluez is missing /etc/bluetooth/serial.conf from distributed rpm/package
https://bugzilla.novell.com/show_bug.cgi?id=727876 https://bugzilla.novell.com/show_bug.cgi?id=727876#c0 Summary: bluez is missing /etc/bluetooth/serial.conf from distributed rpm/package Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: All OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: howard.bryan.webb@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 In /var/log/messages, I see the message, when I plug in a serial bluetooth device: Nov 2 11:27:55 t4 bluetoothd[29000]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory Investigating... ls -l /etc/bluetooth -rw-r--r-- 1 root root 2422 Sep 19 12:12 main.conf -rw-r--r-- 1 root root 297 Sep 19 12:12 rfcomm.conf yast -> software management -> search -> bluez -> Technical Data reports: bluez - Bluetooth Stack for Linux Version: 4.96-5.1 Source Package: bluez-4.96-5.1 yast -> software management -> search -> bluez -> File List reports: /etc/bluetooth /etc/bluetooth/main.conf <---------- /etc/bluetooth/rfcomm.conf <---------- /etc/dbus-1/system.d/bluetooth.conf <<snip>> Conclusion: /etc/bluetooth/serial.conf should be supplied as part of the bluez package Reproducible: Always Steps to Reproduce: 1. Install openSuse 12.1 RC1, including kde's bluedevil and bluez 2. Verify that there is no file /etc/bluetooth/serial.conf installed additionally, you can 3. With system running, tail -f /var/log/messages 4. Plug in a bluetooth serial device 5, Observe bluetoothd file-not-found msg in /var/log/messages Actual Results: Exactly as described above Expected Results: 1) A template file /etc/bluetooth/serial.conf showing its form so it can be modified by the system admin as appropriate 2) No failure msg in /var/log/messages There are no man pages or other documentation describing the files in /etc/bluetooth, so having a completely specified template file, just like /etc/bluetooth/main.conf is important. -- 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#c Andreas Jaeger <aj@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seife@novell.slipkontur.de AssignedTo|bnc-team-screening@forge.pr |vbotka@suse.com |ovo.novell.com | -- 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#c1 --- Comment #1 from Bryan Webb <howard.bryan.webb@gmail.com> 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#c2 Stefan Seyfried <seife@novell.slipkontur.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-11-03 07:55:27 CET --- can you elaborate on "bluetooth serial device"? I have never seen one, so I don't know what that is. Those messages are only informational, the files are not needed (only if you want to change defaults system wide, they are useful), so I'd suggest to just ignore the message ;-) -- 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 <howard.bryan.webb@gmail.com> 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#c4 --- Comment #4 from Bryan Webb <howard.bryan.webb@gmail.com> 2011-11-03 19:29:20 UTC --- "Those messages are only informational, the files are not needed (only if you want to change defaults system wide, they are useful), so I'd suggest to just ignore the message" Keep in mind there is no other documentation (that I know of) from which I can generate the proper .conf files. I am just the type to want to change my system defaults, so including these in the next bluez release would be fine. I am in no hurry this moment. -- 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 <seife@novell.slipkontur.de> 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.
participants (1)
-
bugzilla_noreply＠novell.com