Arch Linux

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#25069 - [netcfg] netcfg 2.6.2 fails to connect to WPA2 wifi network

Attached to Project: Arch Linux
Opened by Anonymous Submitter - Friday, 08 July 2011, 15:39 GMT
Last edited by Ionut Biru (wonder) - Saturday, 09 July 2011, 06:16 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
  • Anonymous Submitter (2011-07-08)
Private No

Details

Description:

Netcfg 2.6.2 fails to connect to WPA2-PSK wifi network with the following error message :-

chown[ctrl_interface]: Too many levels of symbolic links
Failed to initialize control interface '/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.

Output at http://pastebin.com/zseWCjXG . Netcfg 2.6.1 worked fine. I am using testing repo.

I am able to connect to the wifi using wicd-curses if I manually delete both /run/wpa_supplicant and /var/run/wpa_supplicant . The netcfg config file used is http://pastebin.com/pnrkhN07 .

Additional info:

keshav_pr@my-comp ~ % file /run/wpa_supplicant
/run/wpa_supplicant: symbolic link in a loop
keshav_pr@my-comp ~ % file /var/run/wpa_supplicant
/var/run/wpa_supplicant: symbolic link in a loop

Packages:

netcfg 2.6.2-1
wpa_supplicant 0.7.3-3
iproute2 2.6.38-4

Steps to reproduce:
This task depends upon

Closed by  Ionut Biru (wonder)
Saturday, 09 July 2011, 06:16 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#25077 
Comment by Damir Jelić (poljar) - Friday, 08 July 2011, 18:56 GMT
Same thing happens to me. Downgrading to 2.6.1 solved the issue.

Loading...