Red Hat Bugzilla – Bug 171516
Delayed scan after resume
Last modified: 2008-08-02 19:40:33 EDT
Description of problem:
After resuming from suspend to RAM, NM takes about 20 seconds to start scanning.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. With NM running...
2. Suspend to RAM (with dbus signals to NM).
nm-applet shows no connection for 20-30 seconds before starting to scan.
NM should commence scanning on resume.
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
There's still some flakey behaviors in NM, but this doesn't seem to be so much
of an issue now.