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#39015 - [wpa_supplicant] 2.1 fails to connect to WPA2 secured network

Attached to Project: Arch Linux
Opened by Steven Vanden Branden (stevenvandenbrandenstift) - Sunday, 23 February 2014, 19:45 GMT
Last edited by Jan de Groot (JGC) - Thursday, 27 February 2014, 11:34 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

afther updating wpa_Supplicant the networkmanager in gnome fails to connect to the network

feb 23 20:11:06 Frozen NetworkManager[203]: <warn> Activation
(wlp1s0/wireless): association took too long, failing activation.
feb 23 20:11:06 Frozen NetworkManager[203]: <info> (wlp1s0): device
state change: config -> failed (reason 'SSID not found') [50 120 53]
feb 23 20:11:06 Frozen NetworkManager[203]: <info> NetworkManager state
is now DISCONNECTED
feb 23 20:11:06 Frozen NetworkManager[203]: <warn> Activation (wlp1s0)
failed for connection 'VandenSchoor living'
feb 23 20:11:06 Frozen NetworkManager[203]: <info> (wlp1s0): supplicant
interface state: scanning -> disconnected
feb 23 20:11:06 Frozen NetworkManager[203]: <info> (wlp1s0): device
state change: failed -> disconnected (reason 'none') [120 30 0]
feb 23 20:11:06 Frozen NetworkManager[203]: <info> (wlp1s0):
deactivating device (reason 'none') [0]


Additional info:
* package version(s) wpa_supplicant-2.1-1-x86_64.pkg.tar.xz and wpa_supplicant-2.1-2-x86_64.pkg.tar.xz
* config and/or log files etc.


Steps to reproduce:

install wpa_supplicant off testing and try to connect to wifi router
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 27 February 2014, 11:34 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Issue solved by fixing config.
Comment by Thomas Bächler (brain0) - Monday, 24 February 2014, 12:51 GMT
This bug report contains no information at all. There is nothing I can do here.
Comment by Steven Vanden Branden (stevenvandenbrandenstift) - Thursday, 27 February 2014, 10:04 GMT
i removed the old config files and re-entered the connection, the problem is solved now,

next time i will supply a backtrace.

greetings

Loading...