FS#35117 - [wpa_supplicant] (x86_64)2.0-2 to 2.0-3 introduces password falsely mismatching

Attached to Project: Arch Linux
Opened by Jasper den Ouden (Jasper1984) - Monday, 06 May 2013, 19:54 GMT
Last edited by Thomas Bächler (brain0) - Tuesday, 07 May 2013, 08:54 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Thomas Bächler (brain0)
Evangelos Foutras (foutrelis)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After upgrading from 2.0-2 to 2.0-3, to my annoyance, it would no longer connect, claiming the password is wrong. It is a WPA 1/2 passphrase in wicd.(the entry is in an attachment) Downgrading resolved the issue.(unfortunately i had deleted it from /var/cache/pacman/pkg/)

I think the wireless device in my laptop is a broadcom: lsusb |grep Broad

Bus 002 Device 003: ID 0a5c:219c Broadcom Corp.

lspci |grep Broad

02:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)

The router is a Cisko WRT160N Linksys V2
This task depends upon

Closed by  Thomas Bächler (brain0)
Tuesday, 07 May 2013, 08:54 GMT
Reason for closing:  Not a bug
Comment by Jan de Groot (JGC) - Monday, 06 May 2013, 23:01 GMT
What claims your password is wrong? wpa_supplicant, or wicd that can't start wpa_supplicant?

The only change between -2 and -3 is the rebuild against libnl, so if you didn't upgrade that too (pacman -Syu!) there's your solution.
Comment by Thomas Bächler (brain0) - Tuesday, 07 May 2013, 08:54 GMT
Incomplete system upgrades are not supported. You cannot upgrade to 2.0-3 without upgrading the rest of the system (in particular, libnl).

wicd (as all network managers) claim that the passphrase is wrong whenever a connection fails, for whatever reason.

Loading...