Comment 22 for bug 284211

Revision history for this message
aptgetmoo (dezull) wrote : Re: [Bug 284211] Re: [intrepid] network-manager-gnome 0.7 missing PEAP-GTC option

These are the steps for Jaunty.

First go to packages.ubuntu.com,search and download these packages(make sure
you download the hardy ones)
network-manager hold
network-manager-gnome
dhcdbd
gnome-system-tools
libnm-glib0
libnm-util0
Put these files in a folder. Make sure no other *.deb file in this folder

Then kill related processes:
killall nm-applet -9
sudo killall NetworkManager -9
sudo killall NetworkManagerDispatcher -9

then remove some packages:
sudo apt-get remove network-manager network-manager-gnome libnm-glib0
libnm-util1

then go the folder directory where you put all the downloaded packages, run:
sudo dpkg -i *.deb
echo "network-manager hold" | sudo dpkg --set-selections
echo "network-manager-gnome hold" | sudo dpkg --set-selections
echo "dhcdbd hold"| sudo dpkg --set-selections
echo "gnome-system-tools hold"| sudo dpkg --set-selections
echo "libnm-glib0 hold"| sudo dpkg --set-selections
echo "libnm-util0 hold" | sudo dpkg --set-selections
sudo NetworkManager&
nm-applet&

Then you networkmanager should work again with GTC.
If not try restarting your machine. This may not be the best way. In fact,
I tried several times before getting the right packages to remove and
install. There are another application, WICD I think, that can replace
networkmanager. But I'm not sure it will work with GTC.
On Wed, May 6, 2009 at 1:15 AM, Jeff Rash <email address hidden> wrote:

> > aptgetmoo wrote on 2009-04-21: (permalink)
> >
> >There is a temporary workaround. You can install the one from Hardy. I
> tried
> >and it worked. But the 3G-broadband setup will become harder, since you
> will
> >have to do it manually. But if you are just going to use the wifi
> >connection, there shouldn't be any problem.
>
> Can you explain how to do this?
>
> --
> [intrepid] network-manager-gnome 0.7 missing PEAP-GTC option
> https://bugs.launchpad.net/bugs/284211
> You received this bug notification because you are a direct subscriber
> of the bug.
>