wicd on antix 17 does not log into unsecured WiFi signal

Klaas Vaak · 05-13-2019, 12:19 PM

Wicd works fine in my home, where the signal is secured. But if I go to a public WiFi place where the signal is unsecured, Wicd cannot log in - it keeps trying to contact the router but fails.

fatmac · 05-13-2019, 02:40 PM

Unsecured - but maybe it needs a password.

rokytnji · 05-13-2019, 06:31 PM

Maybe dmesg may tell ya something?

another way is to run a terminal session of wicd after logging in .

Code:

wicd-client -t &

and see what errors come up in terminal.

Klaas Vaak · 05-13-2019, 09:55 PM

Quote:

Originally Posted by fatmac

Unsecured - but maybe it needs a password.

Yes, and I do have the password, but it fails to connect.

Klaas Vaak · 05-13-2019, 10:03 PM

Quote:

Originally Posted by rokytnji

Maybe dmesg may tell ya something?

What dmesg command do I need to do?

Quote:

another way is to run a terminal session of wicd after logging in .

Code:

wicd-client -t &

and see what errors come up in terminal.

That shows:

Code:

importing pinotify failed, notifications disabled.
Has notifications support False
Loading ...
connection to daemon ...
Connected
displaytray True
Done loading.

Nothing revealing there I guess.

rokytnji · 05-13-2019, 10:12 PM

Quote:

What dmesg command do I need to do?

Code:

dmesg | tail

This seems a google browser error message

Code:

importing pinotify failed, notifications disabled.
Has notifications support False

I think having to do with notifications turned on in google chrome. Not wicd related I would think.

rokytnji · 05-13-2019, 10:14 PM

I hope you realize you need to be by one of the routers with which you are having problems with before running those commands to get a good error reading?

Klaas Vaak · 05-13-2019, 11:46 PM

Quote:

Originally Posted by rokytnji

I hope you realize you need to be by one of the routers with which you are having problems with before running those commands to get a good error reading?

That makes sense, although I thought that if there is something wrong with wicd those commands would show it anyhow. I may well be wrong, in which case I'll get back to this next Monday when I will have been at the hotspot.