ihse (the submitter) wrote: > As for the second issue however, about the valid interface > (a wifi card) not showing, it still seems a valid problem. > Some more digging around turned up that by using nm-tool, > I could still see the wlan0 card. So this is either a problem > solely in nm-applet, or in the combination of > NetworkManager and nm-applet.
Is this still a problem in Precise? Mathieu wrote: > Marking as High Importance is still Undecided. ** Summary changed: - Network connection fails on fresh install + NetworkManager fails to configure wlan0 when /e/n/i contains "iface eth0 inet manual" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/678450 Title: NetworkManager fails to configure wlan0 when /e/n/i contains "iface eth0 inet manual" Status in “network-manager” package in Ubuntu: New Bug description: Binary package hint: network-manager I install Maverick (10.10) on a new computer. I boot it, and I don't get any network connectivity on the very first start. That is no good way of starting a new installation... What seems to have happend is this: In /etc/network/interfaces, apart from the loopback stanza, the following is added: auto eth0 iface eth0 inet manual Combined with /etc/NetworkManager/nm-system-settings.conf containing: [ifupdown] managed=false this effectively means that NetworkManager does not "see" eth0. For some reason, this seems to prevent the GNOME Network Manager applet to appear, even though I have a wireless card as well (which shows up in the NM applet after I fixed the eth0 problem). This has happened on at least four computers, one desktop and one laptop, and also a co-worker on his laptop, and finally on a virtual installation in VirtualBox (to test this behaviour again). The co- worker found out one workaround, by changing the NM config file to "managed=true". I tried to remove the eth0 part of /etc/network/interfaces, which worked as well. Comparing with older versions of Ubuntu, which has managed=false but no eth0 information in interfaces, this seems like the preferrable fix. There seems to be several issues at work here. First of all, why did I get the eth0 stuff in my interfaces file during installation? (The major problem) Second, why did this stop Network Manager from managing my wifi card? I am happy to provide whatever extra information is needed to solve the bug. All of these computers were connected on a company network which requires a proxy to connect to the outside world. I don't know if it is relevant, but it might be. Also, several people here (including me) have been using Ubuntu for a long time on this network, and this has never happened before, on anything between Jaunty and Lucid. And yes, we do have a DHCP server on the network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/678450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
