tp_g_set_error_unsupported_handle_type has this in its documentation: * FIXME: Shouldn't the error be NotImplemented? The spec doesn't always * allow us to return that, though. The distinction between tp_g_set_error_unsupported_handle_type and tp_g_set_error_invalid_handle_type is that the former is used for handle types which are defined by the spec, but for which the CM doesn't have a handle repository, while the latter is used for handle types which (at the time the CM was compiled) weren't mentioned by the spec. Perhaps this is too subtle and we should just pick one.
(In reply to comment #0) > Perhaps this is too subtle and we should just pick one. The distinction will be lost in case the client library implements a later spec where new handle types are defined, and the CM is built to an older version. I vote for "unsupported" to be future-proof.
Fixed soon in 0.7.23
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.