Like call but also takes a UnixFDList object.
The file descriptors normally correspond to g_variant_type_handle values in the body of the message.
For example, if a message contains two file descriptors, fd_list would have length 2, and `g_variant_new_handle (0)` and
`g_variant_new_handle (1)` would appear somewhere in the body of the message (not necessarily in that order!) to represent the file
descriptors at indexes 0 and 1 respectively.
When designing D-Bus APIs that are intended to be interoperable, please note that non-GDBus implementations of D-Bus can usually only access file descriptors if they are referenced in this way by a value of type g_variant_type_handle in the body of the message.
This method is only available on UNIX.
| this | |
| bus_name |
a unique or well-known bus name or null if this is not a message bus connection |
| object_path |
path of remote object |
| interface_name |
D-Bus interface to invoke method on |
| method_name |
the name of the method to invoke |
| parameters |
a Variant tuple with parameters for the method or null if not passing parameters |
| reply_type |
the expected type of the reply, or null |
| flags |
flags from the DBusCallFlags enumeration |
| timeout_msec |
the timeout in milliseconds, -1 to use the default timeout or g_maxint for no timeout |
| fd_list |
a UnixFDList or null |
| cancellable |
a Cancellable or null |
| callback |
a TaskReadyCallback to call when the request is satisfied or null if you don't * care about the result of the method invocation |
| user_data |
The data to pass to |