Bug 530319
| Summary: | NetworkManager Fails to Start on Fedora 12 Beta | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Daniel Qarras <dqarras> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | dcbw, fedoraproject |
| 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: | 2009-10-22 20:55:21 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
Daniel Qarras
2009-10-22 10:34:34 UTC
I've got the same problem. I came across an old blog post (18 months) that had this workaround: $ gtk-update-icon-cache $ nm-applet & then networkmanager starts. Unfortunately this must be done again when the computer is rebooted. *** This bug has been marked as a duplicate of bug 530253 *** |