Wiican crashes when bluetooth adapter is not plugged in

[Michael Monreal]

Wiican should cover the case when it is run when no bluetooth adapter is present:

$ ./run-uninstalled.sh
Traceback (most recent call last):
  File "./bin/wiican", line 44, in <module>
    wiimanager = wiimotemanager.WiimoteManager()
  File "/home/mimox/code/bzr/wiican/wiican/wiimotemanager.py", line 67, in __init__
    self.__bluediscover = BlueDiscover()
  File "/home/mimox/code/bzr/wiican/wiican/wiimotemanager.py", line 54, in __init__
    bluezmanager = bus.get_object(BLUEZ_URI, BLUEZ_PATH)
  File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 244, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 241, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 183, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 281, in start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib/python2.6/site-packages/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

[J. Félix Ontañón (fontanon)]

You're terrible right. I've marked it as confirmed and will be fixed in next release. Thanks Michael.

And now some background: Wiican was actually developed time ago, when bluez-gnome instead of gnome-bluetooth was the standar in Gnome desktop. In those days the org.bluez system service was always alive but it seems that now when gnome-bluetooth it only starts if a bluetooth device it's plugged.

[J. Félix Ontañón (fontanon)]

Not bad solution commited: Check and monitoring bluez daemon