Comment 3 for bug 909865

I installed the latest kernel 3.3rc2. It didn't fixed it.
I then tried to reinstall bluez 4.98 from source, it didn't fixed.
I did try service restart in between steps.

Then i installed Blueman, started it but it shows bluez error that bluez daemon was not running

I tried rfcomm command to connect with my mobile... it did asked the passkey on my mobile... no passkey matched.

Then, i tried to run bluez-simple-agent in terminal believing it was a pairing agent .
it threw some python traceback errors:

Traceback (most recent call last):
  File "/usr/bin/bluez-simple-agent", line 88, in <module>
    manager = dbus.Interface(bus.get_object("org.bluez", "/"),
  File "/usr/lib/pymodules/python2.7/dbus/bus.py", line 244, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/pymodules/python2.7/dbus/proxies.py", line 241, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/pymodules/python2.7/dbus/bus.py", line 183, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib/pymodules/python2.7/dbus/bus.py", line 281, in start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib/pymodules/python2.7/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files

Currently, I have uninstalled bluez(and with it i think gnome-bluetooth), then installed blueman (and it reinstalled bluez4.91).
Blueman is showing same errors as above even now.