Hi, Currently there is an issue in connman when Connect is issued for a failed service.
1. In connect service the incoming DBusMessage is assigned to service->pending. 2. __connman_service_connect is called which will call __connman_service_clear_error. state_ipv4 and state_ipv6 is set to unknown. In the following call to service_inidicate_state, its found that we transition to idle from failure, resulting in a call to __connman_service_disconnect. 3. In disconnect reply_pending is called which will take the DBusMessage and reply with an error. This is new behaviour since the commit: 127d216001076d2b73a352a019f00d49bae30835 I'm not 100% sure what issue the commit fixed. I guess we could go back and let service_indicate_state only call disconnect in idle if previous state wasnt disconnected OR failure. But that might roll back the fix of the commit. We could also avoid to attach the message (step 1.) but a lot of other error checks would than fail... Happy for any input :-) --Richard _______________________________________________ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
