Latest today's build 20070411, CD Live:
1. During boot scripts network comes up O.K., finds gateway, finds remote DNS.
2. Still during boot scripts Network Manager disables the network. Dapper and
Edgy don't do that. They "Just Work".
3. After boot completes, Network Manager says "No connection". I click on the
NM icon, then click on wired connection, it comes up, and Network Manager
reports connected.
That means the connection works and Network Manager software is defective
in disabling the network which runs just fine if Network Manager would leave it
alone.
Then I created another account, administrator privileges, and switched
users.
4. When the new user logged on, Network Manager had "No network connection".
No business doing that, should be able to switch users without causing a
hardware disconnect.
5. Clicked on Network Manager which said the network was "Disconnected" and
still reported "No network connection".
6. Clicked on Network Manager yet again, and on wired connection, and then the
connection came up. The network wasn't disconnected, except by Network Manager.
Another way to enable the network connection is "sudo dhclient" which
works fine. That's right out of the "Official Ubuntu" book,
troubleshooting section. Network Manager doesn't know about dhclent so
still shows "No network connection" even when there is one.
Could someone explain what the purpose of Network Manager is on this
system, if the primary function is to disable the only working network
connection? Ubuntu used to come up clean with no user action, now
there's extra steps required.
Thanks, Jerry
--
[feisty fawn] NetworkManager reports incorrect online status
https://bugs.launchpad.net/bugs/82927
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
