Ubuntu
knetworkmanager package

KNetworkManager inactive after login

Bug #94831 reported by Ondřej Michálek
14
Affects Status Importance Assigned to Milestone
knetworkmanager (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Kubuntu Feisty Herd 5 on ThinkPad Z60t

In about half of the cases after I log in, the KnetworkManager does not connect to a network as it is supposed to. I ask for Kwallet password and it sits in the taskbar, however it does not have any icon and clicking it does not do anything. Killing the process knetworkmanager and starting it again solves the problem.

part of 'sudo lshw':

        *-pci:3
             description: PCI bridge
             product: 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 4
             vendor: Intel Corporation
             physical id: 1c.3
             bus info: pci@00:1c.3
             version: 03
             width: 32 bits
             clock: 33MHz
             capabilities: pci normal_decode bus_master cap_list
             configuration: driver=pcieport-driver
           *-network
                description: Wireless interface
                product: AR5212 802.11abg NIC
                vendor: Atheros Communications, Inc.
                physical id: 0
                bus info: pci@13:00.0
                logical name: wifi0
                version: 01
                serial: 00:14:a4:58:46:74
                width: 64 bits
                clock: 33MHz
                capabilities: bus_master cap_list logical ethernet physical wireless
                configuration: broadcast=yes driver=ath_pci driverversion=0.9.4.5 (0.9.3) ip=192.168.1.214 latency=0 multicast=yes wireless=IEEE 802.11g
                resources: iomemory:a7f00000-a7f0ffff irq:23

Revision history for this message
Rich Johnson (nixternal) wrote :

I can somewhat confirm this. In order for me to use KNetworkManager after login, I have to perform the following:

1) Prior to logging in, I disable WiFi by pressing the Wireless button on my laptop.
2) Once I login, and KDM displays its loading splash, I re-enable the WiFi with the button again.

This will connect everytime for me. Kind of annoying at first, but after doing it for a month or so, I have gotten used to it.

Changed in knetworkmanager:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Albert Cardona (cardona) wrote :

Same here. For feisty dist-upgraded to yersterday (April 10, 2007), knetworkmanager fails to list the wireless networks. Three days ago, though, knetworkmanager was listing the wireless networks just fine.

I have no problem in connecting manually with sudo ifup ath0 and a proper /etc/network/interfaces, so the wireless card is fine.

One note: the enable/disable wireless switch in my thinkpad t60p was always ignored by edgy; is feisty trying to acknowledge it? The second comment above suggests so.

I have the same card as the first poster:

$ lspci
...
03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

Revision history for this message
solax (solax76) wrote :

I have the same problem with a Kubuntu dapper 6.10 on a Sony Vaio, with a USB WIFI (Bus 001 Device 002: ID 0ace:1211 ZyDAS 802.11b/g USB2 WiFi).

I have configured the KNetworkManager to start with the kde session, and normally it works, asking me the kwallet password to retrive the wpa password. But sometimes it is the DCOPServer that asks me the kwallet password, not knetworkmanager!

When it happens, KNetworkManager seems to freeze and an invisible icon is present on the taskbar. Then if i open a Konsole using the button on the taskbar, 2 konsoles are opened without any reason. I think it is linked to this bug because it doesn't happen in any other case.
Once i kill the knetworkmanager process and start it again, it always correctly starts without asking for a password, because the KWallet is already open.

ciao

Revision history for this message
Divan (divan-santana) wrote :

Same for me! Hang to login type in wallet password, kill knetworkmanager and open again and then connect to wireless network :(

Will a fix be released for Feisty?

Revision history for this message
ThomasGillespie (tomjamesgillespie) wrote :

Can confirm on feisty final with Intel PRO/Wireless 3945ABG

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.