dhcpcd conflicts with the new network manager. Mention in the upgrade guide to remove dhcpcd when using NetworkManager in gnome 2.26. Reproducible: Always
(In reply to comment #0) > dhcpcd conflicts with the new network manager. Mention in the upgrade guide to > remove dhcpcd when using NetworkManager in gnome 2.26. > > Reproducible: Always > Actually I did a little more digging on this, it wasnt dhcpcd that was causing hte conflict nor was it dhclient that solved it. In trying different solutions to resolve the issue I must have gotten confused. I have now figured out what the conflict was though. The problem was with the net.ethX scripts. Those scripts block network manager from receiving the dhcp information. Removing net.eth0 and net.eth1 from the default runlevel was the real fix for this problem. I have been running with the net.eth scripts AND networkmanager on the default run level and never had a conflict before now. Hope this helps someone else cut to the chase. Also I think mentioning this in the migration guide would definitely be useful!
Networkmanager has nothing to do with gnome and with our upgrade guide. Your problem is specific to NM and not to gnome, please contact NM maintainers. (use epkginfo)
(In reply to comment #2) > Networkmanager has nothing to do with gnome and with our upgrade guide. > Your problem is specific to NM and not to gnome, please contact NM maintainers. > (use epkginfo) > Thanks, I guess I had a hard time finding what components were all part of gnome. Now I know networkmanager isn't one. Reformulated this problem as bug 290094 http://bugs.gentoo.org/show_bug.cgi?id=290094
(In reply to comment #3) > Thanks, I guess I had a hard time finding what components were all part of > gnome. Now I know networkmanager isn't one. > FTR: metadata.xml is a reliable way to know the maintainers of a particular package. If you don't see 'gnome@gentoo.org' in there, it's not maintained by us.
