On 2018-12-25 20:57:44 +0100, Vincent Lefevre wrote:
> I still get the error message in bad format, but the error message
> now appears only in the system logs (journalctl).
Note that this bug is about the bad format of this error message.
> For the connection failure itself, I don't know yet.
On 2018-12-24 09:52:58 +0100, Andrej Shadura wrote:
> On Sun, 23 Dec 2018 at 23:54, Vincent Lefevre wrote:
> > I got the following error (via wicd logs):
> >
> > 2018/12/23 22:11:27 :: wpa_cli -i wlp61s0 terminate
> > Failed to connect to non-global ctrl_ifname: wlp61s0 error: No such file
> >
On Sun, 23 Dec 2018 at 23:54, Vincent Lefevre wrote:
> I got the following error (via wicd logs):
>
> 2018/12/23 22:11:27 :: wpa_cli -i wlp61s0 terminate
> Failed to connect to non-global ctrl_ifname: wlp61s0 error: No such file or
> directory
>
> This should have been:
>
> Failed to connect to
On 2018-12-23 23:51:41 +0100, Vincent Lefevre wrote:
> I got the following error (via wicd logs):
>
> 2018/12/23 22:11:27 :: wpa_cli -i wlp61s0 terminate
> Failed to connect to non-global ctrl_ifname: wlp61s0 error: No such file or
> directory
>
> This should have been:
>
> Failed to connect
Package: wpasupplicant
Version: 2:2.6-21
Severity: minor
I got the following error (via wicd logs):
2018/12/23 22:11:27 :: wpa_cli -i wlp61s0 terminate
Failed to connect to non-global ctrl_ifname: wlp61s0 error: No such file or
directory
This should have been:
Failed to connect to non-global
5 matches
Mail list logo
