I can also confirm this on Kubuntu Edgy. It works in the following way for me: I have a home network with a Linux and a Windows box connecting to the internet via a router. If the network cable is plugged in to the Linux box during startup, no problem -- network will work. I can even unplug the network cable, and as soon as I plug it back, Kubuntu detects it, and the network becomes available right away.
BUT if the network cable isn't plugged in at startup, this bug appears. Even if I plug it in, Ubuntu won't detect it. Maybe after minutes pass, it will work -- I've never had the patience to test it. So I have to disable/enable it, which is a pain, as the user has to be in the sudoers group. I used Ubuntu and Xubuntu before Kubuntu (Dapper? Breezy? I don't remember), and I remember seeing this problem there as well. But as of Dapper (?), Gnome removed the need to sudo if I want to start the network manager, and I also remember as if the error disappeared in Gnome altogether; but maybe not. Anyway, this is definitely a problem, which cannot be solved without a sudo (bad if you are not in the sudoers group). I am astonished by the fact that it is still unassigned. Please note that Windows XP has no problem of reacting immediately to the plugging of the network cable; how can Linux, a much more network-oriented OS not? -- Kubuntu 6.06 final: cannot retrieve an ip via dhcp from my router https://launchpad.net/bugs/48241 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
