Network Manager fails to connect

Bug #339716 reported by Michael Rocco Sabino
2
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

NetworkManager fails to connect to a hidden ssid using broadcom b43 wireless in jaunty alpha 5. Upgrading alpha 5 to the current daily build causes even non-network manager-initiated connections to wireless to break.

Description: Ubuntu jaunty (development branch)
Release: 9.04

network-manager:
  Installed: 0.7.1~rc1+20090220-0ubuntu1
  Candidate: 0.7.1~rc3-0ubuntu1
  Version table:
     0.7.1~rc3-0ubuntu1 0
        500 http://us.archive.ubuntu.com jaunty/main Packages
 *** 0.7.1~rc1+20090220-0ubuntu1 0
        100 /var/lib/dpkg/status

Revision history for this message
Michael Rocco Sabino (m-sabino) wrote :

Temporary workaround (for alpha 5)

-----b43netfix.sh----
echo "Stopping Network Manager. Ctrl+C to abort. Usage: ./net <essid>."
sudo /etc/init.d/NetworkManager stop

echo "Line to fix iwconfig, since 4318 sometimes doesn't associate (on my laptop)"
sudo iwconfig wlan0 essid UNBORK
echo Sudoing iwconfig wlan0 with essid: $1
sudo iwconfig wlan0 essid $1
echo "Bringing interface up and down to associate"
sudo ifconfig wlan0 down
sudo ifconfig wlan0 up
sudo dhclient wlan0

--------------------------

Revision history for this message
Michael Rocco Sabino (m-sabino) wrote :

oops the filename should read "net" at the beginning, not b43netfix.sh.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

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? Do you get the same with Karmic? Thanks in advance.

Changed in network-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Michael Rocco Sabino (m-sabino) wrote : Re: [Bug 339716] Network Manager fails to connect

Those problems seem to be gone. I had a few year old Compaq Presario that was having some trouble which I gave away, but more recently my XPS M1530 has begun to work much better in regards to Network Manager in Ubuntu.

Michael Sabino

----- Original Message -----
From: Pedro Villavicencio <email address hidden>
Date: Thursday, September 3, 2009 10:15 am
Subject: [Bug 339716] Network Manager fails to connect
To: <email address hidden>

> 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? Do you get the same with Karmic? Thanks in advance.
>
> ** Changed in: network-manager (Ubuntu)
>        Status: New => Incomplete
>
> --
> Network Manager fails to connect
> https://bugs.launchpad.net/bugs/339716
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “network-manager” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: network-manager
>
> NetworkManager fails to connect to a hidden ssid using broadcom
> b43 wireless in jaunty alpha 5. Upgrading alpha 5 to the current
> daily build causes even non-network manager-initiated
> connections to wireless to break.
>
> Description: Ubuntu jaunty (development branch)
> Release: 9.04
>
>
> network-manager:
>   Installed: 0.7.1~rc1+20090220-0ubuntu1
>   Candidate: 0.7.1~rc3-0ubuntu1
>   Version table:
>      0.7.1~rc3-0ubuntu1 0
>         500
> http://us.archive.ubuntu.com jaunty/main Packages
>  *** 0.7.1~rc1+20090220-0ubuntu1 0
>         100 /var/lib/dpkg/status

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

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

Other bug subscribers

Remote bug watches

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