Knetworkmanager loose wireless connection, Networkmanager crashing

[Schmirrwurst]

Binary package hint: knetworkmanager

On startup, the wireless connection isn't connecting.
On clicking on knetworkmanager, to activate the wlan manually, it connects, but a few secounds after that, it disconnect again. By reconnecting manually (by clicking on the wlan connection from knetworkmanager), the second time, it usually works, but not always. Sometimes the connection process stays at 0%, and Networkmanage is taking 100% cpu.

[Devin Torres (devinus)]

I can confirm this bug. I believe it has something to do with us having Broadcom network controllers. I managed to find this on Launchpad by Googling for "knetworkmanager disconnected first time" and immediately noticed we both used Broadcom's.

0b:00.0 Network controller [0280]: Broadcom Corporation BCM94311MCG wlan mini-PCI [14e4:4311] (rev 01)
        Subsystem: Dell Unknown device [1028:0007]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 17
        Region 0: Memory at fe8fc000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>

[Devin Torres (devinus)]

I should also note this is only when I store keys unencrypted. When I use KWallet the problem seems to go away.

[burgy (keith-burgoyne)]

I can confirm that this also happens to me, using an Atheros AR2413 chipset. This did not happen in Feisty. After selecting a WEP or WPA-encrypted network, the connection is established, and then within a second, knetworkmanager disconnects. It then attempts to connect to the nearest unencrypted network. This goes away after I reconnect to the encrypted network a second or third time.

lspci:

03:00.0 Ethernet controller: Atheros Communications, Inc. AR2413 802.11bg NIC (rev 01)

/var/log/messages:

Dec 12 21:32:48 zissou kernel: [66871.240000] ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready
Dec 12 21:32:57 zissou dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.host_name
Dec 12 21:32:57 zissou dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.domain_name
Dec 12 21:32:57 zissou dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.nis_domain
Dec 12 21:32:57 zissou dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.nis_servers
Dec 12 21:33:21 zissou kernel: [66901.140000] ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready
Dec 12 21:33:23 zissou kernel: [66902.352000] ADDRCONF(NETDEV_UP): ath0: link is not ready
Dec 12 21:33:25 zissou kernel: [66904.532000] ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready
Dec 12 21:33:28 zissou kernel: [66907.168000] ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready
Dec 12 21:33:29 zissou kernel: [66908.308000] ADDRCONF(NETDEV_UP): ath0: link is not ready
Dec 12 21:33:31 zissou kernel: [66910.368000] ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready
Dec 12 21:33:33 zissou dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.host_name
Dec 12 21:33:33 zissou dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.domain_name
Dec 12 21:33:33 zissou dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.nis_domain
Dec 12 21:33:33 zissou dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.nis_servers

[lcampagn (luke-campagnola)]

Confirmed for Atheros 5212, using kubuntu/gutsy and ndiswrapper. I seem to have the same key line in my logfile as the original poster--the connection proceeds normally, stays connected a few seconds, then suddenly:
   NetworkManager: <info> SWITCH: terminating current connection 'ath0' because it's no longer valid.

The attached log shows the connection stayed about 15 seconds, then automatically dropped. I did this twice before the connection stayed on permenently.

Can anybody explain what "terminating current connection because it's no longer valid" means?

[Christian Iversen (chrivers)]

I can confirm this bug on gutsy with ipw2200.

The connection stays up for a little while, then the message:

   NetworkManager: <info> SWITCH: terminating current connection 'ath0' because it's no longer valid.

appears in the log, and the connection is dropped.

[Gertjan (gertjan-hofman)]

Confirm as well on Gutsy, wireless is
02:02.0 Ethernet controller: Atheros Communications, Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)
on a toshiba A70 laptop.

Same pattern - doesnt connect by default, then connects, disconnect within 15 sec and stay the second time. Very annoying. Anyone at Ubuntu have a comment here ?

Cheers

Gertjan

[Thomas R. N. Jansson (tjansson)]

I can confirm this bug on a updated version of Ubuntu 7.10 on Thinkpad X30.

Kind regards
Thomas Jansson

[Thomas R. N. Jansson (tjansson)]

I just tried to change from storing the keys uencrypted to using kwallet and it fixed the problem as Devin Torres also writes.

Kind regards
Thomas Jansson

[lcampagn (luke-campagnola)]

My keys are stored by kwallet and I still see the bug.

On Feb 1, 2008 11:50 AM, tjansson <email address hidden> wrote:

> I just tried to change from storing the keys uencrypted to using kwallet
> and it fixed the problem as Devin Torres also writes.
>
> Kind regards
> Thomas Jansson
>
> --
> Knetworkmanager loose wireless connection, Networkmanager crashing
> https://bugs.launchpad.net/bugs/159949
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Christian Iversen (chrivers)]

My keys are also stored in kwallet, and I also see the bug.

[djtm (djtm)]

Confirm with Gutsy, BCM4311 (b43) and 2.6.24.3, WPA

[Gertjan (gertjan-hofman)]

Seems fixed in Hardy Heron

[Luka Renko (lure)]

Thanks for report. Will close the bug as fixed. If you can still reproduce this in Hardy, please feel free to reopen or open new bug.

[lcampagn (luke-campagnola)]

Seemed like this problem was fixed for me, and now for a few days, suddenly I'm seeing it again--exact same symptoms and error messages!

[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.