Hi Mike, On ma, 2014-07-14 at 10:37 -0400, Mike Purvis wrote: > Example session: > > > $ sudo connmanctl scan wifi > Scan completed for wifi > $ sudo connmanctl services > *AR LV-426 wifi_c4d987b634ba_4c562d343236_managed_psk > [ others... ] > $ sudo connmanctl connect wifi_c4d987b634ba_4c562d343236_managed_psk > Error /net/connman/service/wifi_c4d987b634ba_4c562d343236_managed_psk: > Input/output error > $ sudo connmanctl connect wifi_c4d987b634ba_4c562d343236_managed_psk > Error /net/connman/service/wifi_c4d987b634ba_4c562d343236_managed_psk: > Did not receive a reply. Possible causes include: the remote > application did not send a reply, the message bus security policy > blocked the reply, the reply timeout expired, or the network > connection was broken. >
Wild guess here but is it possible that connmand crashed and could not deliver the reply? You should never need to run connmanctl as a root, it is just something that is not needed if dbus is configured correctly. Cheers, Jukka _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
