On Wed 15 Jun 2022 at 13:38:06 +0200, Vincent Lefevre wrote: > On 2022-06-15 12:14:19 +0100, Brian wrote: > > On Wed 15 Jun 2022 at 12:45:23 +0200, Vincent Lefevre wrote: > > > > > On 2022-06-15 10:32:58 +0100, Brian wrote: > > > > On Wed 15 Jun 2022 at 11:16:40 +0200, Vincent Lefevre wrote: > > > > > The OP wanted an X11 app, while iwlist and nmcli are just command-line > > > > > utilities (though one may want to write a script to show information > > > > > in an X11 app, a text terminal or something else?). But my remark was > > > > > mainly: the iwlist and nmcli utilities can get the information as a > > > > > normal user, so there is a major limitation in wpa_gui and wpa_cli. > > > > > > > > This limitation does not exist. wpa_gui and wpa_cli are both capable > > > > of being run as a mormal user. > > > > > > So, why do I get a "Could not connect to wpa_supplicant" error > > > with the default configuration? > > > > Because wpa_supplicant is not aware of GROUP=netdev. See my other > > post in this thread. > > So, that's a limitation. There is no such limitation with other tools > (iwconfig, nmcli, and in the past, wicd), which work as a normal user > without needing anything special.
So, we will have it as a limitation. However, it is long-standing and wpa_gui has efficiently managed connections here for a non-root user for some time, which is all I ask of it. I can live with it. Maybe wpa_cli and wpa_gui will eventually become dbus-aware. -- Brian.
