[Gutsy] Knetworkmanager fails to join wireless network

Bug #129783 reported by sk0rp10
14
Affects Status Importance Assigned to Milestone
knetworkmanager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: knetworkmanager

[Regression from Feisty Fawn ]
[Reproducibility: Always]
[Wireless adapter: Intel Pro Wireless IPW3945]

Knetworkmanager does not start in the system tray at startup, even if its process is running. Killing it and reloading will end in a Kwallet opening hang-up (it hangs on opening Kwallet, as it says in the tray icon context menu).

The only way to make it work is reloading X , but even then it fails to join the wireless network at first time, asking for key even if it has it stored in kwallet. Clicking cancel on the key dialog and requesting again the connection finally works.

Revision history for this message
Sujee Maniyam (sujee) wrote :

I have gutsy and I don't see this problem. KNetworkMgr starts up every time and connects to wireless every time (after asking KWallet password)

When right-click on knetwork manager on systray and 'quit' it will ask you 'start during startup?'. Did you see that?

Revision history for this message
Manuel Siggen (manuel-siggen) wrote :

I've upgraded to Gutsy yesterday and I can confirm the second problem : upon logging, KNetworkManager startups correctly, but is unable to connect to my wireless network. Then if I ask KNetworkManger to connect to it, the connection fails the first time (without any GUI message) but succeed the second time.

I've checked in the KNetworkManger options : my wireless network is in the trusted network list.

I'll try to gather some logging info and come back. Thanks.

Revision history for this message
Manuel Siggen (manuel-siggen) wrote :

Okay, here is my syslog file, as generated between last login and first connection to the wireless network.

The following lines may be of some use :-)

Oct 21 09:08:09 x40 NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed
Oct 21 09:08:09 x40 NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed

Let me know if I can give you more debug info. Thanks in advance !

Revision history for this message
Colin Stark (cstark) wrote :

I can confirm this bug report.
Running Kubuntu 7.10 on an IBM Thinkpad R51, which has an Intel 2200BG wireless card, which I noticed is different from the card in the initial report.
Sometimes I'll start my system, KNetworkManager will start fine, ask me for my wallet password and connect to the wireless network properly. I'd say this is more the expection than the norm though.
Usually I have to kill the process and start it up again to work, often more than once. Sometimes I need to kill the kwalletmanager process as well. I'll try to describe all of the different things that happen. I'm not sure which log files are relevant to this but I'd be happy to paste them if necessary.
Sometimes on boot, the process starts up fine but there is no tray icon. Sometimes it prompts me for my wallet password, other times it doesn't. When it prompts me for the password, it connects to the wireless network properly, but there is no tray icon. When it does not prompt, it doesn't connect, and I need to kill the process and start it again to get it do so.
Other times KNetworkManager starts up fine, but halts when prompting for the key from the wallet. Right clicking on the tray icon shows "Waiting for key from wallet". The wallet prompt never appears and I usually need to restart the X Server (ctrl alt backspace) at least once once before it prompts me properly.
Sometimes, after killing the process and starting it up again, the icon shows up as a green globe in the corner instead of the disconnected network icon. In this case, right clicking on the icon shows "no devices configured". No matter how many times I kill the process and start it up again it never starts working. Restarting the X Server doesn't even fix the problem most of the time. At this point I usually restart my computer and hope for the best on the next boot. Again, I have to hope that it works the first time around but I usually have to do a bit of messing around before it starts. Sometimes I have to restart my computer again. The most times I've rebooted in a row to try to get this work is 3 (I believe).
The last problem is that sometimes after I start it up, it's very flaky with the connection. It'll connect fine, then disconnect after a few seconds to a minute. It does this a few times before it connects and stays connected.
It's not a huge problem because once I get it working, it works fine. But since suspend and hibernate don't work properly either, I dread having to turn my computer off when I'm bringing it elsewhere because it means going through all of this.
The different problems seem completely random. There is no indication of which of the different problems is going to happen.
Hopefully this was descriptive enough

Revision history for this message
Manuel Siggen (manuel-siggen) wrote :

The problem went away when I updated the network-manager package to the version (0.6.5-0ubuntu16). I got this version using the `gutsy-proposed' repositories, as explained in bug #83623.

Revision history for this message
Benji (eilif) wrote :

I recently upgraded to gutsy from feisty ... and Knetworkmanager failed to list any wireless accesspoints or join wireless, tho iwconfig revealed the device (eth1) was working and manually using dhcpcd to setup the routing was successful (for a google test). The problem seems to have been merely one of configuration. I edited the /etc/network/interfaces, specifically, the non-working and seemingly default looked like this:

#auto eth1
iface eth1 inet dhcp

And I uncommented the auto line, and commented out the iface line, resulting in this:

auto eth1
#iface eth1 inet dhcp

Now network manager finds access points and connects automatically to my wireless network.

Revision history for this message
Andreas Moog (ampelbein) wrote : Old standing Report

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.

 status incomplete
 subscribe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkit6uMACgkQ06FgkPZwicSsAgCgkI25q3SE59BKf3jQf1mDwFDf
HHcAnA7QXkyZKXWPZM2JNL7bu9Zrincb
=LMeY
-----END PGP SIGNATURE-----

Changed in knetworkmanager:
status: New → Incomplete
Revision history for this message
Manuel Siggen (manuel-siggen) wrote :

KNetworkManager is working flawlessly for me since my last comment (https://bugs.launchpad.net/ubuntu/+source/knetworkmanager/+bug/129783/comments/5). I guess you can close this entry.

Thank you for the good work !

Revision history for this message
Andreas Moog (ampelbein) wrote : Closing the Report

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Closing the Report then. Thanks again for reporting.

 status invalid

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkixD1MACgkQ06FgkPZwicS3ugCfZu7aXSLtrclQwpNa7OQRzYZN
IQ8AnRViNX8lFDUETWELY2d/Eb/oEiRA
=MJWr
-----END PGP SIGNATURE-----

Changed in knetworkmanager:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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