Hi. Instead of trying to figure out why "sudo wpa_gui" works for you and
not me, I just looked to see what it would take to make wpa_gui for for
the non-root user.
You mentioned something about the netdev group, but none of the wpa
control files have this group; I don't know if this is a bug in the
wpasupplicant package. Specifically, I had
$ ls -ld /run/wpa_*
-rw-r--r-- 1 root root 6 Apr 6 15:08 /run/wpa_action.wlp3s0.pid
drwxr-x--- 2 root root 60 Apr 6 15:08 /run/wpa_supplicant
-rw-r--r-- 1 root root 6 Apr 6 15:08 /run/wpa_supplicant.wlp3s0.pid
$ ls -l /run/wpa_supplicant/wlp3s0
srwxrwx--- 1 root root 0 Apr 6 15:08 /run/wpa_supplicant/wlp3s0
Manually giving access to all users makes this work:
$ sudo chmod 777 /run/wpa_supplicant
$ sudo chmod 777 /run/wpa_supplicant/wlp3s0
After this I can run wpa_gui as a regular user, and things continue to
work. Is this closer to how wpa_gui is supposed to be used? Is there a
bug in the supplicant packaging?
If this IS closer to the intent, then wpa_gui should be shipped in
/usr/bin, not /usr/sbin.
Thanks
