Fix handling of DBus errors emitted by the bus itself
Current code for handling dbus errors only works for errors received from the remote application itself. We must also handle errors emitted by the bus itself, for example, when it fails to spawn the target service. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
This commit is contained in:
parent
a873b496da
commit
c64904b745
@ -1129,9 +1129,8 @@ int virDBusCallMethod(DBusConnection *conn,
|
|||||||
call,
|
call,
|
||||||
VIR_DBUS_METHOD_CALL_TIMEOUT_MILLIS,
|
VIR_DBUS_METHOD_CALL_TIMEOUT_MILLIS,
|
||||||
&error))) {
|
&error))) {
|
||||||
virReportError(VIR_ERR_INTERNAL_ERROR,
|
virReportDBusServiceError(error.message ? error.message : "unknown error",
|
||||||
_("Cannot send to %s.%s on path %s with interface %s: %s"),
|
error.name);
|
||||||
destination, member, path, interface, NULLSTR(error.message));
|
|
||||||
goto cleanup;
|
goto cleanup;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user