Hi
I can connect without problem to my private net, via WPA personal, however when I try to connect to WPA2 Enterprise I cannot save my settings, I receive
Can't save
Potential causes: * Insufficient permissions * NetworkManager not running * DBUS failure
Of course I cannot connect since the setting is not saved. What puzzles me is that WPA Personal is fine.
I consider the failure for WPA Enterprise as a serious bug and I know it did not happen for example in Ubuntu 10.04+relevant trinity version.
Any help would be strongly appreciated.
Uwe Brauer
Uwe Brauer wrote:
Potential causes:
- Insufficient permissions
- NetworkManager not running
- DBUS failure
Have you eliminated those three issues?
I consider the failure for WPA Enterprise as a serious bug and I know it did not happen for example in Ubuntu 10.04+relevant trinity version.
If so file a bug report with some information on how to reproduce it.
regards
"deloptes" == deloptes deloptes@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
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:
"deloptes" == deloptes deloptes@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@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@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
"Nikolaus" == Nikolaus Klepp office@klepp.biz writes:
Hi
Hi! Might not solve your problem, but I had to install and use wicd + wicd-gtk to get WPA2 working with a decent GUI.
I tried that but for the eduroam configuration there are some parameters needed which are not provided by the wicd-gtk interface
I finally installed nm-applet and the gnome networkmanager and that worked.
But it is a bit of a shame that the tdenetworkmanager behaves strangely. It worked well in Ubuntu 10.04+trinity.
Uwe Brauer
On Tuesday 20 June 2017 21:03:06 Uwe Brauer wrote: <snip>
But it is a bit of a shame that the tdenetworkmanager behaves strangely. It worked well in Ubuntu 10.04+trinity.
Yes, I confirm that it worked fine in Ubu 10.04+trinity. Regression error has crept in - perhaps in Ubuntu, perhaps TDE. :-(((
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
On Tuesday 20 June 2017 21:03:06 Uwe Brauer wrote:
<snip> > > But it is a bit of a shame that the tdenetworkmanager behaves > strangely. It worked well in Ubuntu 10.04+trinity. > Yes, I confirm that it worked fine in Ubu 10.04+trinity. Regression error has crept in - perhaps in Ubuntu, perhaps TDE. :-(((
IIRC network-manager was completely revamped past Ubuntu 10.04. Any NM support past that is running on a large chunk of new and complex interface code talking over D-BUS. As such, regressions would be somewhat expected.
Prior to that new code there was no way at all to make tdenetworkmanager work with the new network-manager.
"deloptes" == deloptes deloptes@gmail.com writes:
Uwe Brauer wrote:
Potential causes:
- Insufficient permissions
I just run tdenetwork as root and got the same message when trying to save the configuration.
Uwe Brauer
-
deloptes -
Dr. Nikolaus Klepp -
Glen Cunningham -
Timothy Pearson -
Uwe Brauer