bluez: Fix naked ‘raise’ statements

When raising an exception, it’s generally a good idea to actually
include the exception value — otherwise Python will re-raise the ‘last
exception which was active in the current scope’, which is not so
useful, especially when you want to print that exception.

Reviewed-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Signed-off-by: Philip Withnall <philip.withnall@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D1296

bluez/ubt

@@ -464,7 +464,7 @@ class PbapDeviceProfileTester(DeviceProfileTester):
                 path = s[0]
                 break
         if not path:
-            raise
+            raise LookupError('Device ‘%s’ not found in services' % device_name)
 
         service = dbus.Interface(bus.get_object("net.connman", path),
                                  "net.connman.Service")
@@ -517,7 +517,7 @@ class PbapDeviceProfileTester(DeviceProfileTester):
             if ret == 'y' or ret == 'Y':
                 TEST_PASSED("A2DP Source")
             else:
-                raise
+                raise RuntimeError('Invalid response: ' + ret)
 
         except Exception as error:
             TEST_FAILED("A2DP Source: " + str(error))