knetworkmanager won't connect if kwalletmanager hasn't been initialized

[ANDREA]

Binary package hint: knetworkmanager

i got a wpa wireless network and when logging in knetworkmanager tries to connect but obviously fails as the password is contained in the kwallet but it apparently doesn't call kwalletmanager or anything it simply fails. you have to "insist" (click it and select network to connect to) so it connects ... this is a gutsy-related bug as back in feisty this wasn't an issue and my laptop would connect automatically.

[Luka Renko (lure)]

knetworkmanager 0.2.2 is now available in Hardy and have some fixes for handling KWallet passwords.
Can you check if you can reproduce this with up-to-date Hardy?

[ANDREA (andrea54)]

hi
first of all, thank you for getting back to me. i've tested it on my laptop (using kubuntu hardy w/ kde 3.5.9) and now knetworkmanager 0.2.2. unfortunately, knetworkmanager claims that it is connected on eth0 (wired ethernet connection active: eth0; IP: 0.0.0.0) when the cable is obviously unplugged.

I then deactivated eth0 to see if it would connect to the wireless network and it did, prompting me for the kwallet password. so i think we're really close to a solution here - thank you!

[Luka Renko (lure)]

Thanks for fast response.
Can you post your /etc/network/interfaces and output of "ifconfig" at the time knetworkmanager claims you are connected to eth0?

[ANDREA (andrea54)]

here's the output:
eth0 Link encap:Ethernet HWaddr 00:40:45:2e:af:b0
          inet6 addr: fe80::240:45ff:fe2e:afb0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:5515 (5.3 KB)
          Interrupt:21 Base address:0xe800

eth2 Link encap:UNSPEC HWaddr 00-1C-BF-26-1A-FD-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth0:avahi Link encap:Ethernet HWaddr 00:40:45:2e:af:b0
          inet addr:169.254.7.129 Bcast:169.254.255.255 Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          Interrupt:21 Base address:0xe800

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:71 errors:0 dropped:0 overruns:0 frame:0
          TX packets:71 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5688 (5.5 KB) TX bytes:5688 (5.5 KB)

wlan0 Link encap:Ethernet HWaddr 00:1c:bf:26:1a:fd
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

---------------------------------------------------------------------------------------
/etc/network/interfaces:

iface lo inet loopback

[ANDREA (andrea54)]

hi there
problem unfortunately persists and has not been resolved yet; is there anything i can do to help?

ANDREA

[Jonathan Thomas (echidnaman)]

Thank you for taking the time to report this bug and helping to make Kubuntu better. The KDE3 version of KNetworkManager has been discontinued by its original authors. This unfortunately means that there will be no more bugfix releases, and updates in general will be limited to those fixing security flaws.

While we cannot fix your bug, the good news is that the applet has been totally rewritten for KDE4 in the upcoming Kubuntu 9.10 release. There is a good chance that this bug is no longer an issue with the new applet. If you find any similar or new issues with the applet included in Kubuntu 9.10, we would politely ask you to file them as new bugs against the "plasma-widget-networkmanagement" package.

Thanks in advance for your cooperation and understanding.