I'm gonna need help with this one.
Running full KDE, updated up to today, kernel 3.2.18-pclos2.bfs
Laptop is an HP G42 with a Core i3 and Intel chipset.
Bluetooth card is a Broadcom 2070. Specifically, lsusb reports this: "Bus 001 Device 004: ID 0a5c:21b4 Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR
"
I am trying to connect a cheap bluetooth headset, specifically
this (link to Amazon)
I know, cheap and unknown, but its all I need (and can afford), and... well, keep reading.
bluedevil can't seem to be able to see the headset. But the bluetooth in general is working; I can pair 3 different cell phones and event transfer files and all.
I wanted to try blueman, see if it was able to see the headset. But running blueman gives me this error:
[user1@mike-laptop ~]$ blueman-manager
Loading configuration plugins
Using gconf config backend
_________
on_bluez_name_owner_changed (/usr/bin/blueman-manager:104)
org.bluez owner changed to :1.38
Using gconf config backend
ERROR:dbus.proxies:Introspect error on org.blueman.Applet:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 586, in msg_reply_handler
reply_handler(*message.get_args_list(**get_args_opts))
File "/usr/bin/blueman-manager", line 132, in on_bluez_name_owner_changed
if not self.Applet.GetBluetoothStatus():
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
**keywords)
File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
That happens even if I run blueman as root via "su", or even if I login as root.
I tried running bluetoothd -n to see if I get any result. This is what I got:
[user1@mike-laptop ~]$ su
Password:
[root@mike-laptop user1]# bluetoothd -n
bluetoothd[11373]: Bluetooth deamon 4.93
bluetoothd[11373]: Unable to get on D-Bus
I've been scouring the web for a solution, trying many suggestions like installing almost everything I can find in Synaptic related to bluetooth, adding the user to a "bluetooth" group (had to create the group first), changing the
/etc/dbus-1/system.d/bluetooth.conf file to read from
" <policy user="root">" to
" <policy user="mike">", but nothing works.
By the way, this same problem was reported in
this thread, but in that case KDE
was working, so the solutions posted didn't help.
Now, here are the mysteries:
This same headset was working before in this same laptop, when it was runinng [the distro which must not be named]. So, I know that the headset is compatible.
This is my son's laptop, he wanted to try [the distro who must not be named], and I encouraged him to do it. Eventually, he came back to PCLOS - but we have run into this conundrum, and it might be a deal breaker (he loves listening to his music with the bluetooth headset).
And worst:
It worked once for a while! . When I first installed PCLOS, I did it from my own customized remaster. This remaster started from MiniMe. After the installation, all the bluetooth functions
including the heaset were working, but only for one user - the first user I created when installing. But the second user - mike - did not have bluetooth at all.
So, I decided to start over, this time using the full PCLinuxOS 2012 KDE iso. Now, all the users have bluetooth, when using bluedevil, but the headset refuses to work.
I would appreciate any help.
Thanks in advance.
