Ubuntu
network-manager package

network manager hangs after trying to connect to a non-working wap

Bug #112225 reported by Stephen Crosby
6
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: network-manager

Every day when I turn on my laptop, network-manager attempts to connect to a wap that doesn't work. I don't know much about why it doesn't work, but nobody I know can connect to it. While it tries to connect, I get no green dots in the tray icon but the animation does display. It stays like that seemingly forever. Also if I click the icon, and select a working network, it will not connect.

If on the other hand, I first select 'create new wireless network', then type a name for it and click ok, I can then select a working wap and connect to it almost instantaneously.

I am a novice user so if I can give any more information please let me know. For now, here is my ifconfig:
eth0 Link encap:Ethernet HWaddr 00:18:F3:CA:A3:83
          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)
          Interrupt:17 Base address:0xa000

eth1 Link encap:Ethernet HWaddr 00:18:DE:28:86:03
          inet addr:129.8.224.56 Bcast:129.8.227.255 Mask:255.255.252.0
          inet6 addr: fe80::218:deff:fe28:8603/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:85995 errors:3 dropped:1372 overruns:0 frame:0
          TX packets:1534 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7882938 (7.5 MiB) TX bytes:205661 (200.8 KiB)
          Interrupt:16 Base address:0xe000 Memory:fdeff000-fdefffff

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:5 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:364 (364.0 b) TX bytes:364 (364.0 b)

Here is my /etc/network/interfaces:

auto lo
iface lo inet loopback

iface eth1 inet dhcp
auto eth1

iface eth0 inet dhcp
auto eth0

See original description
Revision history for this message
Stephen Crosby (stevecrozz) wrote :

Here's the output of lspci as it relates to my wirelss card:
01:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

Here's the output of modprobe -c | grep ipw3495 which I believe is the name of the driver I use.
$ modprobe -c | grep ipw3945
install ipw3945 /sbin/modprobe --ignore-install ipw3945 ; sleep 0.5 ; /sbin/ipw3945d-$(uname -r) --quiet
remove ipw3945 /sbin/ipw3945d-$(uname -r) --kill ; /sbin/modprobe -r --ignore-remove ipw3945

Revision history for this message
Stephen Crosby (stevecrozz) wrote :

As a further note, part of my first post is innacurate. Network manager shows the animation, but not the green dot while it hangs. Also it does not ever say, unable to connect, it just hangs forever. I went ahead and cleared my log, reproduced the bug, and finally performed the fix steps as I outlined the bug by:
1. clicking create a new network, then ok
2. then selecting a working network all from within the network-manager enjoyment

I've included daemon.log which reflects this test only and you can see the working connect at the end and all the garbage infinite loop at the top.

Revision history for this message
Stephen Crosby (stevecrozz) wrote :

looking for some progress on this. now that I'm doing some more traveling I'm noticing this same problem in more places. for whatever reason, the network manager gets stuck in some kind of infinite loop and never connects to a network. Clicking on another network doesn't fix the problem. The only way I've discovered to fix this problem is to create a new network (which in itself never actually works by the way), this breaks the loop somehow and then when I click on a working wifi hotspot name, I am very quickly connected to it.

Stephen Crosby (stevecrozz)
Changed in network-manager:
status: New → Confirmed
description: updated
Revision history for this message
Alexander Sack (asac) wrote :

can you please check if you still see this particular issue in latest gutsy network-manager 0.6.5-0ubuntu15 or above?

Changed in network-manager:
status: Confirmed → Incomplete
importance: Undecided → Medium
Revision history for this message
Stephen Crosby (stevecrozz) wrote :

Thanks for the follow up, this particular issue should be closed.

Stephen Crosby (stevecrozz)
Changed in network-manager:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

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