Bug 426177
Summary: | knetworkmanager crippled in Fedora 8 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Philippe Rigault <prigault> |
Component: | knetworkmanager | Assignee: | Dennis Gilmore <dennis> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 8 | CC: | ltinkl, mmcgrath, piskozub, rdieter, roland.wolters |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-12-19 00:59:01 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Philippe Rigault
2007-12-19 00:33:54 UTC
Yep, unfortunately, knetworkmanager doesn't yet work with NetworkManager >= 0.7 (as is included in F8, see bug #298991). The best option we came up with (to handle upgrade cases primarily), was to introduce a place-holder until when/if the situation improved. Rest assured, we wouldn't be in this situation if there were any (better) alternative. *** This bug has been marked as a duplicate of 298991 *** |