Thanks to everyone for all the info. I'm a bit confused about this issue being marked "Fix Released" though. Alexander Sack wrote (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/45696/comments/65) about seeing some improvements. I'm not clear what these improvements were. Reading the other comments above, it sounds like people keep having to use workarounds, e.g. disabling and re-enabling networking manually. Some people were even having this issue in Gutsy. That doesn't sound like the issue is really "fixed" IMHO.
I still have this problem, too, occasionally, with the same chipset, WIRED Ethernet card: Intel Corporation, Device: 82562ET/EZ/GT/GZ - PRO/100 VE (LOM). Network device: eth0, Hardware address: 00:13:20:0e:ce:fb. I use DHCP networking via my wired router. I still have the same version of Ubuntu (Feisty) as before. Update Manager has so far failed in to upgrade to Gutsy, but that's -- hopefully -- a different issue.
Getting back to network manager, should I open a new bug for the same problem? --Or is Feisty not supported anymore at all now that Gutsy is out, regardless of people who have not been able to upgrade? Thanks in advance for clarifying the process.
Thanks to everyone for all the info. I'm a bit confused about this issue being marked "Fix Released" though. Alexander Sack wrote (https:/ /bugs.launchpad .net/ubuntu/ +source/ network- manager/ +bug/45696/ comments/ 65) about seeing some improvements. I'm not clear what these improvements were. Reading the other comments above, it sounds like people keep having to use workarounds, e.g. disabling and re-enabling networking manually. Some people were even having this issue in Gutsy. That doesn't sound like the issue is really "fixed" IMHO.
I still have this problem, too, occasionally, with the same chipset, WIRED Ethernet card: Intel Corporation, Device: 82562ET/EZ/GT/GZ - PRO/100 VE (LOM). Network device: eth0, Hardware address: 00:13:20:0e:ce:fb. I use DHCP networking via my wired router. I still have the same version of Ubuntu (Feisty) as before. Update Manager has so far failed in to upgrade to Gutsy, but that's -- hopefully -- a different issue.
Getting back to network manager, should I open a new bug for the same problem? --Or is Feisty not supported anymore at all now that Gutsy is out, regardless of people who have not been able to upgrade? Thanks in advance for clarifying the process.