Bug 785618 - NetwokManager doesn't properly report the status of connections it doesn't manage
Summary: NetwokManager doesn't properly report the status of connections it doesn't ma...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-30 01:19 UTC by Joe Zeff
Modified: 2013-02-13 13:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 13:52:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Joe Zeff 2012-01-30 01:19:56 UTC
Description of problem:

I don't use NetworkManager for the wired connection on my desktop because it mangles resolv.conf.  (Not part of the issue here.)  When I start either Firefox or Thunderbird, they query NM and it reports that my wired connection is down, although it's not.  I've been able to work around this with FF, not TB, but I shouldn't have to.  NM should report the status correctly even if it doesn't handle the interface in question.  I'd like to point out that this didn't start until I "upgraded" from F14 to F16.

Version-Release number of selected component (if applicable):

Whatever version is current with Fedora 16.

How reproducible:

100%

Steps to Reproduce:
1. Configure a wired interface using Network.
2. Tell NM that it doesn't manage the interface.
3. Try to connect using a program that queries NM for status.
  
Actual results:

NM falsely reports that the interface is inactive.

Expected results:

NM correctly reports that the interface is active.

Additional info:

I know that NM is at fault because I use it on my laptop (Not just for wireless, either; it f"plays nicely with my DNS on my wired connection, so there's no reason not to use it.) and I never have this problem.

Comment 1 Dave Miller 2012-07-20 04:07:52 UTC
Just adding a "mee too" with a slightly different configuration.  I have F16 installed on an external hard drive that I carry between home and work.  I've been going nuts trying to figure out why Thunderbird starts offline at home but online at work.  Since I'm booting from the same F16 image at both locations all of the applicable T-Bird settings were absolutely the same.

I finally ran across a discussion thread started by the originator of this bug that led me to https://bugzilla.redhat.com/show_bug.cgi?id=790106 and how to get T-Bird to not believe the lies that NM tells it.  Also, I run a static IP address for my laptop when it's on my home network (ifcfg-eth0 - it's traditional) and I let NM manage the DHCP configured interface when I'm at work.  

Finally, I've been going nuts trying to figure this out for the past couple of weeks so it was absolutely reproducible until I tweaked the T-Bird settings mention in bug #790106.

Comment 2 Fedora End Of Life 2013-01-16 13:10:39 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is 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" 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

Comment 3 Fedora End Of Life 2013-02-13 13:52:19 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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