Bug 670401 - Autoreconnect broken after update
Summary: Autoreconnect broken after update
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 14
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-18 06:23 UTC by Milan Kerslager
Modified: 2012-08-16 17:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 17:58:40 UTC
Type: ---


Attachments (Terms of Use)
nm-tool output (proprietary kmod-wl driver from rpmfussion for BCM4313) (1.37 KB, text/plain)
2011-01-20 13:04 UTC, Milan Kerslager
no flags Details

Description Milan Kerslager 2011-01-18 06:23:35 UTC
Once introduced, the auto-reconnect feature used to be worked, but is broken now (latest F14 updates - NetworkManager-0.8.1-10.git20100831.fc14.x86_64).

When the system is resumed from suspend-to-disc, it waits too long or forever.
When UTP cable is plugged into the port, N-M does not detect it (maybe because the driver is hot-plugged when cable is connected an eth0 appears only then in the list of available interfaces).

Expected behavior: NM auto-reconnect like in the previous releases.

Comment 1 Jirka Klimes 2011-01-18 13:09:27 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?

Comment 2 Milan Kerslager 2011-01-20 13:04:32 UTC
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.

Comment 3 Jirka Klimes 2011-02-02 08:58:24 UTC
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?

Comment 4 Milan Kerslager 2011-02-02 10:36:46 UTC
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.

Comment 5 Fedora End Of Life 2012-08-16 17:58:43 UTC
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


Note You need to log in before you can comment on or make changes to this bug.