If I manually select the Network Manager Icon, and the wired network, the drivers function on the internet just fine.
The obvious conclusion is disabling the connection for a "carrier detect problem" is a Network Manager code decision which is not beneficial for us users. If the drivers work, they work, and since they do, then there's no justification that us users see for the Network Manager code to disable the working connection. Ubuntu Tribe 5 came right up, connection active, no problem about "carrier detect". Xubuntu has been coming right up, connection active, until Release Candidate when it joined the other non-working as booted versions when it added the Network Manager icon. Since Ubuntu Tribe 5 works fine, connection active at boot, why did Ubuntu decide to "break" Network Manager boot code again for Release, disabling the connection so I have to manually enable it? Worst case is Kubuntu 7.10 Release Code. In sequence: 1. Boots up and Network Manager shows "no active connection". Konqueror can't get internet. 2. sudo dhclient establishes connection fine. 3. System, Network shows eth0 connected, DNS, etc. O.K. 3. Network Manager shows "no active connection", Konqueror can't get internet. 4. Add/Remove accesses internet http://... just fine and downloads Firefox O.K. 5. Network Manager still shows "no active connection", Konqueror can't get internet even though Add/Remove had no problem. 6. Start Firefox, browses internet fine. Konqueror still can't. 7. After all this, Network Manager shows "no active connection", which is obviously false. Would someone explain what use Network Manager is on Kubuntu on this computer? Thank you, Jerry 7. Jerry -- does not automatically start the wired connection due to missing link beat https://bugs.launchpad.net/bugs/83143 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
