Description of problem: I can't start NetworkManagerInfo included in FC3 Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Start NetworkManager service 2. run NetworkManagerInfo 3. Actual results: Runs and ends with no warnings or errors Expected results: Have the applet working Additional info: All with standard FC3 packages
NetworkManagerInfo daemonizes itself... It will also quit when NetworkManager is not present. The applet shown in the panel will only show itself when there is more than one connection present, or when the connection is wireless. Can you verify that NetworkManagerInfo is _not_ running?
Oh, true. It is running but even when using a wireless connection, the applet is not showing. [~]$ ps x | grep Network 5414 pts/2 Sl 0:00 NetworkManagerInfo 5415 pts/2 Sl 0:00 /usr/libexec/NetworkManagerNotification 5991 pts/3 R+ 0:00 grep Network [~]$
So I have NetworkManager deamon and NetworkManagerNotification running, I'm in a wireless connection, there is another AP available, but still, the applet is not showing. What should I be checking?
Does the other AP not broadcast its ESSID, and are you using a Cisco card? The current Cisco driver doesn't show non-ESSID broadcasting access points in its scans, which isn't so great :( Otherwise, if that's not true, try waiting about 20s to see if the other access point shows up. Cards won't always list every access point every scan, but NetworkManager keeps access points around until they haven't been seen for 2 minutes, so it should show up eventually... Newer versions of NetworkManager & NetworkManager-gnome might help this out too, the most recent verison should be in FC3-updates.
Closing per lack of response to previous request for information. This bug was originally filed against a much earlier version of Fedora Core, and significant changes have taken place since the last version for which this bug is confirmed. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. Please install a still supported version and retest. If it still occurs on FC5 or FC6, please reopen and assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier.