Thanks for the input. The suggested workaround works fine and therefore,
I'm closing the bug report.
** Changed in: wpa (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Just as an added information, providing the switch `-s
/run/wpa_supplicant` with the network-control interface connected should
work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2074070
Title:
una
So I looked into this and the observations made in this post is correct.
It's because the default path of the wpa_cli client socket made is in
/tmp (they use AF_UNIX sockets, and UDP protocol - this means the client
socket must bind a visible place for the server)
/tmp is obviously not visible out
So I have some questions about the snap run under the wpa_client case.
Is this trace repeatable? This one is odd to me in a couple of ways like
we are getting a timeout without every doing a select/poll/... so either
it is somehow missing from the trace or its being done by interrupt.
The trace s
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: wpa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2074070
Title:
unable
