After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 354565 - NetworkManager tries to get address on wired connection without link
NetworkManager tries to get address on wired connection without link
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
: 431680 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-09-06 05:51 UTC by bjohnson
Modified: 2007-06-07 13:51 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description bjohnson 2006-09-06 05:51:02 UTC 
Please describe the problem:
NetworkManager sees a wired connection and sets it up even though is it reported as having no link and no cable is plugged in.

Steps to reproduce:
1. start NetworkManager
2. observe setup of wired connection when link is not available
3. observe teardown of wired connection, then setup of wireless connection


Actual results:


Expected results:
setup of wired connection should never be attempted when there is no link

Does this happen every time?
No, actually, it only happens roughly 90% of the time for me.

Other information:
Upstreamed from: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=194124
Comment 1 bjohnson 2006-09-06 05:58:19 UTC 
I believe the the version was cvs20060529.  Check me.

http://cvs.fedora.redhat.com/viewcvs/devel/NetworkManager/NetworkManager.spec?r1=1.120&r2=1.121
Comment 2 sardion 2007-02-06 01:05:06 UTC 
I can confirm this.  Running ubuntu feisty (network-manager version 0.6.4).

https://launchpad.net/bugs/83178
Comment 3 bjohnson 2007-05-03 03:04:01 UTC 
(In reply to comment #0) 
> Does this happen every time?
> No, actually, it only happens roughly 90% of the time for me.

At least I think I understand this part a little better now.  If I boot up and wait a few seconds before I login (long enough for the system to scan for APs), then login, it will go to the wireless network right away.  If I login before there is time to scan, it goes to the wired network.

This doesn't explain why it thinks there is a link on the wired network though.
Comment 4 Matthias Clasen 2007-05-11 18:12:08 UTC 
*** Bug 431680 has been marked as a duplicate of this bug. ***
Comment 5 Pierre Ossman 2007-05-12 10:23:03 UTC 
+1

Still present in 0.6.5.
Comment 6 Dan Williams 2007-06-07 13:51:09 UTC 
Fixed in revision 2578 on NETWORKMANAGER_0_6_0_RELEASE branch.  Not a problem on trunk because trunk isn't multi-threaded.