20 Jun
2017
20 Jun
'17
3:35 a.m.
Hi!
Might not solve your problem, but I had to install and use wicd + wicd-gtk to get WPA2
working with a decent GUI.
Nik
Am Dienstag, 20. Juni 2017 schrieb Uwe Brauer:
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
>>
"deloptes" == deloptes <deloptes(a)gmail.com> writes:
Uwe Brauer wrote:
> Potential causes:
> * Insufficient permissions
> * NetworkManager not running
> * DBUS failure
>
Have you eliminated those three issues?
You mean running it as root? Why the hack should I do this if it is not
necessary for WPA2 personal.
How shall I address the other 2 problems and again why does WPA2
Personal work?
If so file a bug report with some information on
how to reproduce it.
I can do that the problem is I encounter the problem for eduroam which
supports only WPA2 Enterprise, I don't know whether the problem occurs
for other WPA2 nets and I am not sure how many users have access to
eduroam.
But I will do
Uwe Brauer
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting