On Fri, 16 Apr 2010 16:14:31 -0430, Patrick O'Callaghan wrote: > On Fri, 2010-04-16 at 18:51 +0000, BeartoothHOS wrote: >> Is it just me?? [....] > Sounds like the old "interface not managed by NetworkManager" trick. > Some Gnome apps rely on NM to tell them if the machine is connected. If > the interface is not managed by NM, they don't realize the connection > works. This happens to Evolution for example. Luckily yum is not a Gnome > app and therefore is not confused. > > Solution: mark the interface as NM-managed (in system-control-network). It is certainly true that I stop and disable NM every time I catch it. It may have potential that only developers can see, but for me as for others here, it's nothing but trouble. That being so, wouldn't marking the interface as NM-managed cause it to *be* NM-managed?? That's not worth it. Even with ethernet cables, let alone wirelessly; I'd be offline -- really offline, unable to use email, Pan, or any browser -- all the time, instead of just gpk some of the time. IOW, the opposite of a solution. How about trying something like "yum remove NetworkManager"?? Would that wake those apps up?? Or even make them smell the coffee? -- Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User I have precious (very precious!) little idea where up is. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
