[Bug 332124] [NEW] [jaunty] knetworkmanager does not connect to wireless network

[Thomas Dreibholz]

Public bug reported:

knetworkmanager under Jaunty (updated to latest version, tested on February 20, 2009) does not connect to wireless network on Thinkpad W500. This computer has an Intel wireless card integrated:
$ lspci |grep Wireless
03:00.0 Network controller: Intel Corporation Wireless WiFi Link 5300

The wireless LED is on, knetworkmanager sees the WLAN, it is using WEP
and the key entered in knetworkmanager is correct. But selecting the
WLAN menu item to connect to my network fails. Using nm-applet,
connecting to the network works without any problems.

Output of knetworkmanager:
Activate Connection /org/freedesktop/NetworkManagerSettings/Connection/0 on
Device /org/freedesktop/Hal/devices/net_00_21_6a_0b_26_74
Connection::GetSecretsAsync for setting 802-11-wireless-security, id 0
Connection::slotSecretsNeeded 802-11-wireless-security, new: no
WirelessSecurity::toSecretsMap
insert wep key0: XXXXXXXXXXXXX
SendGetSecretsReply1 id 0
SendGetSecretsReply2
  Processing Setting 'connection'
ConnectionSetting::toSecretsMap
  Setting 'connection' is empty, discarding
  Processing Setting 'ipv4'
ConnectionSetting::toSecretsMap
  Setting 'ipv4' is empty, discarding
  Processing Setting '802-11-wireless'
ConnectionSetting::toSecretsMap
  Setting '802-11-wireless' is empty, discarding
  Processing Setting '802-11-wireless-security'
WirelessSecurity::toSecretsMap
insert wep key0: XXXXXXXXXXXXX
  Attach setting '802-11-wireless-security'
    group: <list>  <string>tkip</string>  <string>ccmp</string> </list>
    key-mgmt: <string>none</string>
    pairwise: <list>  <string>tkip</string>  <string>ccmp</string> </list>
    wep-key0: <string>XXXXXXXXXXXXX</string>
    wep-tx-keyidx: <int32>0</int32>
  Processing Setting '802-1x'
IEEE8021x::toSecretsMap
  Setting '802-1x' is empty, discarding
Connection::GetSecretsAsync for setting 802-11-wireless-security, id 0
Connection::slotSecretsNeeded 802-11-wireless-security, new: yes
ConnectionStore::slotSecretsNeeded
Storage::hasSecretsStored

After that:
$ ifconfig wlan0
wlan0     Link encap:Ethernet  Hardware Adresse 00:21:6a:0b:26:74
          UP BROADCAST MULTICAST  MTU:1500  Metrik:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

$ iwconfig wlan0
wlan0     IEEE 802.11abgn  ESSID:""
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
          Tx-Power=15 dBm
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

This is definitely a problem of knetworkmanager, since nm-applet works
flawlessly. So, my work-around is to simply use nm-applet for the
moment.

** Affects: knetworkmanager (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: jaunty

** Tags added: jaunty

-- 
[jaunty] knetworkmanager does not connect to wireless network
https://bugs.launchpad.net/bugs/332124
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.