Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40941 - [wpa_supplicant] Various errors in initialization.

Attached to Project: Community Packages
Opened by aaaaaaaaaaaaaaaaaaaa (Pyroh) - Monday, 23 June 2014, 04:51 GMT
Last edited by Daniel Micay (thestinger) - Tuesday, 05 August 2014, 00:15 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

My journal contains multiple instances of the following errors.

Jun 22 22:29:25 orchid dhcpcd[348]: wlp3s0: failed to start wpa_supplicant
Jun 22 22:29:25 orchid dhcpcd[349]: wlp3s0: Successfully initialized wpa_supplicant
Line 1062: unknown EAP method 'SIM'
You may need to add support for this EAP method during wpa_supplicant
build time configuration.
See README for more information.
Line 1062: failed to parse eap 'SIM'.
Line 1065: failed to parse network block.
Line 1072: unknown EAP method 'PSK'
You may need to add support for this EAP method during wpa_supplicant
build time configuration.
See README for more information.
Line 1072: failed to parse eap 'PSK'.
Line 1076: failed to parse network block.
Line 1108: unknown EAP method 'IKEV2'
You may need to add support for this EAP method during wpa_supplicant
build time configuration.
See README for more information.
Line 1108: failed to parse eap 'IKEV2'.
Line 1111: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant/wpa_supplicant.conf'.

wpa_supplicant and dhcpcd seem to work fine, so I assume this is just invalid config options being used.
This task depends upon

Closed by  Daniel Micay (thestinger)
Tuesday, 05 August 2014, 00:15 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed according to the reporter, and it should be filed against [core] anyway.
Comment by Doug Newgard (Scimmia) - Monday, 23 June 2014, 05:14 GMT
Is it possible you're running into  FS#37468 ?
Comment by aaaaaaaaaaaaaaaaaaaa (Pyroh) - Wednesday, 25 June 2014, 23:19 GMT
I just tried to replicate that and there doesn't seem to be an additional wpa_supplicant instance being spawned (using 'pgrep -a wpa' yields the same pid for wpa_supplicant).
Comment by aaaaaaaaaaaaaaaaaaaa (Pyroh) - Thursday, 31 July 2014, 01:04 GMT
The newer version fixes the issues. For the longest time I had just manually removed the offending sections in wpa_supplicant.conf, but it appears that it's been fixed upstream.

Loading...