| Summary: | Autoreconnect broken after update | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Milan Kerslager <milan.kerslager> | ||||
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 14 | CC: | dcbw, jklimes | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-08-16 17:58:40 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Milan Kerslager
2011-01-18 06:23:35 UTC
What version did work for you? Do you see problems in wired or WiFi reconnecting? What drivers do you use (find out by e.g. nm-tool)? Could you also paste /var/log/messages in? Created attachment 474457 [details]
nm-tool output (proprietary kmod-wl driver from rpmfussion for BCM4313)
I'm using proprietary driver for BCM4313 WiFi card (kmod-wl from rpmfussion).
It seems like in the past after resume from hibernation-to-disc I saw list of wireless networks from the previous location. Now after resume there is empty list of available networks. So this may be problem as NM sees no networks after resume in the time NM should restore previous state (ie "connected").
The list appears a minute after resume, but NM stays unconnected.
NetworkManager-0.8.1-10.git20100831.fc14.x86_64
kmod-wl-2.6.35.10-74.fc14.x86_64-5.60.48.36-2.fc14.7.x86_64
Latest NM update was Dec 2, so it appears like this issue is caused by some side effect NM could not overcome.
It would be helpful to see logs. Could you follow the steps in "Debugging WiFi Connections" section on http://live.gnome.org/NetworkManager/Debugging, do suspend/resume and paste the logs in? I watched the logs. NM wake ups and because there were no available network (as reported by non-yet-really-ready wifi card), NM did not reconnect and give up and did not tried once more after a while. Maybe there should be three or five try-to-restore-previous-state before NM decided to not trying any more. I'll post logs here later. This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |