I just upgraded to the Gutsy and it seems to be working fine.
--
Wireless no longer works after upgrade
https://bugs.launchpad.net/bugs/96532
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
If you still see this particular issue in latest network-manager
(0.6.5-0ubuntu15 and above) please reopen.
** Changed in: network-manager (Ubuntu)
Importance: Undecided = Medium
Status: Incomplete = Fix Released
--
Wireless no longer works after upgrade
can you please see if its fixed in network-manager 0.6.5-0ubuntu14
(latest gutsy). We have some huge improvements in recent uploads which
should fix a whole class of bugs. Maybe this one as well.
Thanks,
- Alexander
** Changed in: network-manager (Ubuntu)
Status: New = Incomplete
--
** Changed in: network-manager (Ubuntu)
Sourcepackagename: linux-source-2.6.20 = network-manager
Assignee: Brian Murray = (unassigned)
Status: Needs Info = Unconfirmed
--
Wireless no longer works after upgrade
https://bugs.launchpad.net/bugs/96532
You received this bug notification
Last week, I was back at my friends place, where I happened to be when I
originally upgraded to Feisty and reported this bug. I was surprised
that Network-Manager immediately connected to the router there with no
problems (without nm-applet running). I happily used my laptop for
several days.
Let's not assume NetworkManager is the problem.
It's great you found a solution, but NM works pretty much perfectly in
Fedora Core 6. So maybe it's a problem with Ubuntu's
implementation/packaging of NM, dbus, or ?
I still have a couple of systems running FC6 on different wireless
Sorry about this. I'm assuming you rebooted and didn't just
rmmod/modprobe, I'm too new to Ubuntu to know which services should
have been restarted to be 100% certain NM should work. You're tired
of this bug, and I'm out of ideas :-(
In any event, thanks for trying to get this working in
BTW, what happens when if you disable NetworkManager and try to connect
manually by CLI?
To be clear for others reading this thread, we're really talking about 3
bad behaviours that may be 3+ bugs in different processes:
1) Ubuntu defaults to have conflicting drivers (hostap, orinoco) for prism
Hmm, not good.
I did a fresh install of Feisty Beta a week ago, and I have to say
I've seen the keyboard lockup recently (perhaps the past few days)
connecting to non-WEP networks. Actually, keyboard/mouse both lock,
even the Gnome system monitor applet meters freeze.
I've just moved over to
To help others who may have this issue, and to help developers debug
it, I strongly encourage you to post that your initial results using
my suggested fixes made at least *some* progress:
Ok. That worked, partially. The NetworkManager applet now shows my
router and several other networks.
1) Sorry for this last comment. I'm new to Ubuntu and to Launchpad, I
confused this bug with a similar one, didn't notice due to email rather
than web interface. Live and learn, and sorry for the spam.
2) Perhaps the kernel module portion of this bug is related to:
Re: keyboard lock-up using hostap_pci, this bug may be related:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/89464
It might be worthwhile trying to use the orinoco drivers instead of the
hostap ones, even though the orinoco won't support WPA in NM (if at
all). To do that,
Well, I tried the orinoco drivers. I still can't connect. At least I
am not getting a keyboard lockup. I am tired of dealing with this bug.
It seems clear to me that NetworkManager is too buggy for a stable
release. I should have stuck with Edgy where wireless networking worked
fine. I have
Ok. That worked, partially. The NetworkManager applet now shows my
router and several other networks. However, it doesn't connect. The
applet spins for a while and then the laptop hangs. The keyboard is
unresponsive. I have to remove the battery in order to reboot. This
doesn't happen with a
Odd. I can connect to networks with no encryption, WEP, and WPA.
What kind of wireless network are you trying to connect to?
Oh, yes, then there is that other thing that I forgot to mention:
The first time I connected to my WPA-protected network, although it
*was visible* to NetworkManager
I did all of those things already. to make things easier disabled encryption
on my linksys router.
However, there is not much I can do because of this keyboard lockup that
happens. It seems to be only the keyboard. I can navigate with the mouse but
am unable to do a shutdown. The keyboard
I had similar issues on my T30.
You probably want the hostap driver.
See my posting here on how I got it working:
https://bugs.launchpad.net/ubuntu/+bug/104551
--
Wireless no longer works after upgrade
https://bugs.launchpad.net/bugs/96532
You received this bug notification because you are a
I have gotten it to work. Maybe it was working all along. However, the
Network Manager applet shows no network connection. I also have Wifi-
radar installed and it shows no signal. I saw in /etc/wlan wlan-
udev.sh, so I ran it to see if it would do anything. I also ran ifup
wlan0. Network
Did you remove the whole '/etc/network/interfaces' file? That wasn't my
intent, rather just to remove the wireless-essid and wireless-key .
Network-Manager is used for desktops and laptops, systems that may move
around, while the '/etc/network/interfaces' file is used more on
servers.
--
Could you please add the full contents of '/etc/network/interfaces'?
Thanks again.
--
Wireless no longer works after upgrade
https://launchpad.net/bugs/96532
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: /etc/network/interfaces
http://librarian.launchpad.net/7036222/interfaces
--
Wireless no longer works after upgrade
https://launchpad.net/bugs/96532
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Network manager will not manage interfaces that have been configured in
'/etc/network/interfaces' as yours has. Removing the wireless ESSID and
key might be enough to get network-manager to manage your interface.
--
Wireless no longer works after upgrade
https://launchpad.net/bugs/96532
--
I removed /etc/network/interfaces and NetworkManager was able to detect
the network. However it would not connect. I had to re-enable
/etc/network/interfaces to be able to connect. Why does Ubuntu have two
different and conflicting ways of configuring a network? (I presume
that the Network
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Unfortunately we can't fix it, because your description doesn't yet
have enough information.
Please include the following additional information, if you have not already
done so (please pay attention to lspci's
24 matches
Mail list logo
