[Jaunty] wireless wifi with WPA2 not working

[lophiomys]

Binary package hint: network-manager

Wireless AR5212 with WPA2 not working in Kubuntu 9.04 Jaunty Beta.
using proprietary MadWiFi driver and default installation of Network Manager.
There is no WPA2 option in Network-Manager for wireless connections.

Regression> it was working with Kubuntu 8.04 and 8.10.

Two lines from the System Log which are my favorite suspects:
<WARN> list_connections_cb(): Couldn't retrieve connections: No such method 'ListConnections' in interface 'org.freedesktop.NetworkManagerSettings' at object path '/org/freedesktop/NetworkManagerSettings' (signature '').
...
2009-04-15 16:12:39 T42pUXGA dhclient wifi0: unknown hardware address type 801

ibmuser@T42pUXGA:~$ uname -a
Linux T42pUXGA 2.6.28-11-generic #41-Ubuntu SMP Wed Apr 8 04:38:53 UTC 2009 i686 GNU/Linux

ibmuser@T42pUXGA:~$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04

ibmuser@T42pUXGA:~$ lspci
....
02:02.0 Ethernet controller: Atheros Communications Inc. AR5212 802.11abg NIC (rev 01)

[Alexander Sack (asac)]

there is something out of sync version wise you your system.

are you using plasma networkmanager applet or knetworkmanager?

post the output of

dpkg -l network-manager
dpkg -l network-manager-gnome
dpkg -l network-manager-kde

[lophiomys (lophiomys)]

I did not anything special to the Kubuntu Jaunty installation.
After the upgrade vom 8.10 to 9.04 Beta hung itself, I reformatted the boot partition and installed Kubuntu 9.04 Beta from CD. Thereafter all Updates with KPackageKit. No manual interference with any configuration at all.

Info as requested:

ibmuser@T42pUXGA:~$ dpkg -l network-manager
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-===============================-===============================-==============================================================================
ii network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2 network management framework daemon
ibmuser@T42pUXGA:~$ dpkg -l network-manager-gnome
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-===============================-===============================-==============================================================================
un network-manager-gnome <none> (no description available)
ibmuser@T42pUXGA:~$ dpkg -l network-manager-kde
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-===============================-===============================-==============================================================================
ii network-manager-kde 1:0.7svn864988-0ubuntu8 KDE systray applet for controlling NetworkManager

HTH

[Alexander Sack (asac)]

i am not sure, but shouldnt jaunty use the plasmoid network applet or something? afaik the network-manager-kde package is not kde4 and has a bunch of bugs.

Anyway, to be sure, please install the -gnome package and remove the -kde one.

then start nm-applet from the command line (as its not automatically started in kde afaik). if this is still an issue its probably a driver bug. please reproduce and attach your complete syslog as well as lspci/lsusb/lshal output.

[Alexander Sack (asac)]

if all this doesnt help, also check whether installing linux-backport-modules-jaunty packages followed by a restart helps improve your situation.

[Victor Vargas (kamus)]

Since this report have a long time without activity, please could you check (if is possible) in latest version included in Karmic if this issue is still happening? Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]