Bug 212680
Summary: | NetworkManager resume from hibernate unable to see wifi networks | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | rizo83 |
Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | bloch, ncunning, triage |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | bzcl34nup | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-05-06 16:35:15 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
rizo83
2006-10-27 23:30:39 UTC
Clemson Linux http://www.ces.clemson.edu/linux/suspend_mem.shtml detailed a script (written under FC4) for NetworkManager to sleep during hibernate. Perhaps this should be the default action in Fedora Core? Tried that script and modified it to use pm-hibernate instead of echoing disk to /sys/power/state but same results. Have to restart NetworkManager or recheck Enable Networking in the applet. I have the same problem on my Macbook Pro 15" using Fedora Core 6. I am able to get onto the network if I restart the network service and then manually type in the name of the access point. However, that seems unreliable and I usually restart the network first and then both the network manager dispatcher and network manager daemon, and then I wait a while and it seems to work sometimes. Very unscientific, but I have had positive results. Same problem with Thinkpad T41p. As far as I recall it did work (ie would re-connect after suspend to disk) after FC6 was installed from the distribution ISOs. But after a few "updates" it stopped working. My fix is to issue "ifconfig wifi0 up" from the command line. Re-connecting works for me if I restart the NetworkManager service, on a Vaio SZ3. Same problem, Black Macbook 15". FC6. I usually get around it by removing the modules, restarting networkmanager service then restarting the applet. I've noticed that the dbus-script, mentioned in comment #0, is already present in /etc/pm/hooks/10NetworkManager, I can't tell but it looks as though its already being run with no effect. I'll do a full test with FC7T2 when it comes out. Any progress on this? I have upgraded my laptop to F7 and am unable to suspend or hibernate at the moment... Ok. Do we have another bug open for these other issues? Yes, https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236783, though I don't want to take over this particular report. Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |