Bug 194128

Same problem on my network.
An excerpt of my wpa_supplicant.log:
  Trying to associate with 00:19:cb:4e:b9:42 (SSID='MySSID' freq=2412 MHz)
  Association request to the driver failed                                       
  Associated with 00:19:cb:4e:b9:42
  CTRL-EVENT-SCAN-RESULTS

On Novell bugyills this bug is known as #508561:
  https://bugzilla.novell.com:443/show_bug.cgi?id=508561
The reporter also did some informative investigations of the wpa_supplicant.

I have this problem as well using KDE 4.3 beta 2 on Karmic alpha 2. I'm unable to associate with my wpa protected wifi network. Using the network manager applet from gnome (nm-applet) works fine.

Here is the output I get in dmesg:

[  566.147841] wlan0: authenticate with AP 00:04:e2:fd:8a:8a
[  566.149373] wlan0: authenticated
[  566.149380] wlan0: associate with AP 00:04:e2:fd:8a:8a
[  566.151488] wlan0: RX AssocResp from 00:04:e2:fd:8a:8a (capab=0x431 status=0 aid=2)
[  566.151495] wlan0: associated
[  576.567116] wlan0: disassociating by local choice (reason=3)

This problem is still present with KDE 4.3 RC1.

*** This bug has been confirmed by popular vote. ***

What versions of NetworkManager are you using? 0.7.0 or 0.7.1?

Please give the exact version of your NM packages.

Not sure after several days of trying with Karmic Alpha 2, I went back to
9.04 and installed Wicd network manager.  Could not get Wicd to work in
Karmic at all.  Figured I would wait a while to see if this gets fixed in
later Karmic releases. I have never had any luck with Network Manager in any
version of Kubuntu.  I always give it a try and sometimes I can get it to
connect to my home network but if I go to a hot spot somewhere it will take
a hr. to get it on line so I just install Wicd, it almost always connects
instantly, just would not run in Karmic Alpha 2.

John


On Thu, Jul 16, 2009 at 4:59 AM, Will Stephenson <wstephenson@kde.org>wrote:

> https://bugs.kde.org/show_bug.cgi?id=194128
>
>
>
>
>
> --- Comment #6 from Will Stephenson <wstephenson kde org>  2009-07-16
> 11:59:32 ---
> What versions of NetworkManager are you using? 0.7.0 or 0.7.1?
>
> Please give the exact version of your NM packages.
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are a voter for the bug.
>

I am using 0.7.1. However, it does not appear to be networkmanager, but, rather, the KDE Plasmoid as utilizing the Gnome nm-applet allows me to connect just fine.

Robert: can you post full logs of the KNM and nm-applet connection attempts?

The most useful logs include where NM starts up and sees the client's connections as well as the connection attempt.  To get this and only this, kill NetworkManager and restart it in a root shell with NetworkManager --no-daemon, then connect.  The client being tested should be running the whole time. 

Thanks

Probably the same as 195824

Will: I am just heading into work, so I will do this at my first opportunity.

** ADVERTISEMENT **
Sunday morning is a great time for getting NM logs, find out how at http://userbase.kde.org/NetworkManagement!

Created attachment 35672 [details]
Networkmanager Output when trying to connect to a WPA WLAN using the NM-Plasmoid

Here is the output of NetworkManager when I try to connect to my home WPA-network "btux".

Created attachment 35673 [details]
NetworkManager Output when successfully connecting to WPA WLAN

This is the log of NetworkManager when I connect to the same WLAN using nm-applet. It works!

I also have this problem. The affected computer is an ASUS X50GL laptop. GNOME network manager works flawlessly, as does WICD (as of Kubuntu 9.04).

I committed some changes that may have fixed this bug today.   If you can test latest SVN, please do and report back with logs if it still fails.

Same problem on HP 6530b laptop. Network manager works with wireless when I boot into Ubuntu+GNOME. However, with Kubuntu, I can see the plasmoid in the system tray, and when I click on it, I can see the list of wireless networks available. However, I cannot click on any network to connect to it.

LAN/eth0 connects fine, though.

Exactly which SVN revision of Network Management/knetworkmanager is the package you are using based on?

@Will: I cannot tell. I do 'apt-get upgrade' every 24 hours on the Kubuntu Karmic packages. Is there a command I can run to check the SVN revision from installed packages?

@Kanwar: This is the command and it's output:
stas@citry:~$ apt-cache policy plasma-widget-networkmanagement
plasma-widget-networkmanagement:
  Geïnstalleerd: 0.1~svn1002781-0ubuntu3
  Kandidaat: 0.1~svn1002781-0ubuntu3
  Versietabel:
 *** 0.1~svn1002781-0ubuntu3 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

Regards,

Stas Verberkt

1002781 is outdated now.   And you should be using 'knetworkmanager' not the Network Management plasmoid.  If you have a 101xxxx versioned knetworkmanager and kdebase4-workspace including fixes from 4.3 branch from this week, WPA should work.

Ok, I will ask the Ubuntu people to update. The knetworkmanager is also in the package plasma-widget-networkmanagement. The package knetworkmanager itself contains an ancient version:

stas@citry:~$ apt-cache policy knetworkmanager
knetworkmanager:
  Geïnstalleerd: (geen)
  Kandidaat: 1:0.7svn864988-0ubuntu8
  Versietabel:
     1:0.7svn864988-0ubuntu8 0
        500 http://archive.ubuntu.com karmic/main Packages

@Will: Here's the output:

kanwar@******:~$ apt-cache policy plasma-widget-networkmanagement
plasma-widget-networkmanagement:
  Installed: 0.1~svn1002781-0ubuntu2
  Candidate: 0.1~svn1002781-0ubuntu2
  Version table:
 *** 0.1~svn1002781-0ubuntu2 0
        500 http://au.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

Ubuntu just updated to 1011298. After upgrading I'm able to connect to my network.

Excellent.  I'll leave this open until I get a couple more confirmations though.

There are also some confirmations on Launchpad:
https://bugs.launchpad.net/bugs/392593

The equivalent openSUSE report also indicates it's fixed  http://bugzilla.novell.com/show_bug.cgi?id=525980