| Summary: | NetwokManager doesn't properly report the status of connections it doesn't manage | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joe Zeff <joe> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | dave, dcbw, drees76 |
| 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: | 2013-02-13 13:52:17 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Joe Zeff
2012-01-30 01:19:56 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. 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 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. |