Created attachment 357273 [details] network manager displayer Description of problem: f12 rawhide networkmanager icon does not display in LiveCD,but service NetworkManager was started. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1.boot into system from LiveCD 2.log into system,confirm that service NetWorkManager has started 3.but NetworkManager icon did not display on panel. 4.restart service NetwokrManager ,the icon will display correctly.more details,see attached picture. Actual results: Expected results: Additional info:
Which LiveCD image were you using? Shortly after seeing this test day on the mailing list, I went and grabbed the x86_64 image, dated 2009-08-10. There's a different one on the Test Day page now, dated 2009-08-11. I know there was mention of this notification-area-applet problem, with instructions to stop it and restart it, but I tried that and it didn't help. That was with the old image; I haven't tried the newer one yet.
I can confirm with yesterday's rawhide written to USB flash drive. (And it's not the recent GTK2+ bug.)
From the screenshot, it almost certainly is. Note the distinctive white boxes in the panel. Also note that the console grep command is incorrect: the applet's process name is 'nm-applet', so it would not show up if you grep for 'Network'. Please test in more detail and confirm whether the nm-applet process is running, and whether this works with gtk2-2.17.7-1.fc12 or higher. If it does, this is a dupe of 510249. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Mmm. Maybe. For me it was Rawhide day or two before that LiveCD burned to USB key and the nm-applet definitely was missing but - nowadays having updated Rawhide on the disk, it works for me.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Closing for now; if we can reproduce this issue then let's reopen the bug.