https://bugzilla.novell.com/show_bug.cgi?id=722722 https://bugzilla.novell.com/show_bug.cgi?id=722722#c5 --- Comment #5 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-10-08 16:47:42 CEST --- The bluetooth errors are most of the time more of an informational type. For example, I get the following on boot: Oct 5 19:21:29 susi bluetoothd[4892]: HCI dev 0 registered Oct 5 19:21:29 susi bluetoothd[4892]: Listening for HCI events on hci0 Oct 5 19:21:30 susi bluetoothd[4892]: HCI dev 0 up Oct 5 19:21:30 susi bluetoothd[4892]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory Oct 5 19:21:30 susi bluetoothd[4892]: input-headset driver probe failed for device 00:12:EE:23:CE:EA Oct 5 19:21:30 susi bluetoothd[4892]: input-headset driver probe failed for device 00:23:F1:B1:1B:29 Oct 5 19:21:30 susi bluetoothd[4892]: input-headset driver probe failed for device B4:EE:D4:59:7C:26 Oct 5 19:21:30 susi bluetoothd[4892]: input-headset driver probe failed for device C0:E4:22:68:82:5E Oct 5 19:21:30 susi bluetoothd[4892]: input-headset driver probe failed for device 00:24:EF:D1:B3:23 I think that's for all known (paired) devices, nothing is connected at that time. Later, when I connect my headset, I get: Oct 8 15:59:08 susi bluetoothd[4889]: Connection refused (111) And it still works fine. This is probably because my Headset has two different operation modes (Telephone and a2dp/HiFi Stereo) and only one is enabled. So it is unfortunately not that easy to find the real errors out of the huge amount of logspam the bluetooth subsystem generates :-( Note that it works pretty well for me (with bluetooth-applet from gnome3 within XFCE), so it seems there is at least some way to get it working. ISTR that after the switch to gnome3 I also had to remove and re-pair all devices in order to get them going again correctly, but I don't remember the details and back then I just credited this to the unfinished state of gnome3. -- 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.