The only progress I've seen is backwards. On my IBM Net Vista which came up with Network Manager O.K. on Feisty, now on Gutsy daily builds up through yesterday during boot Network Manager fills /var/log/syslog with hundreds and thousands of loops of enabling and disabling either eth2 (which I don't have) or eth0 before it finally finishes boot. Syslog is as much as 5 megabytes big where it should be 35 kilobytes.
My main system still requires manual intervention since Network Manager disables my Realtek card during boot; you can see it right in /var/log/syslog. Removing the Network Manager package is useless because even though it is removed, it is still active during boot and still disables my card - which works perfectly after having to enable it either by issuing sudo dhclient or clicking the applet. If Network Manager can enable the wired network by clicking on the applet, why can't it use the same thing to enable it during boot?? We the users have no clue whether Ubuntu isn't interested, can't fix it, or maybe the Network Manager people would rather work on something else (shudder). Upshot is I can get it working sooner or later, but this doesn't seem to me to be the best way to spread Ubuntu to more users. Cheers, 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
