| Summary: | nm-connection-editor does not allow editing of connections | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andrew Duggan <lists> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 14 | CC: | antonio.montagnani, dcbw, enricop, jklimes, theo148 |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-04-07 12:52:58 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
Andrew Duggan
2011-03-03 03:26:53 UTC
Downgrading to NetworkManager-0.8.1-9.git20100831.fc14.i686 "fixes", i.e., restores access to those fields in my connections with secrets and also allows the "VPN" tab do be disabled and configurable for VPN connections. Correction to that last sentence. ... Also allows the "VPN" tab to be *enabled* and configurable... I am having the same issues listed here (see Bug: https://bugzilla.redhat.com/show_bug.cgi?id=681532 ) except I initially had the Password dialogue pop-up, and straight after that received an error message "Error initializing editor 802-11 wireless", and could not edit the settings. After deleting all my entries an recreating them, or allowing the wireless section to auto detect them, I no longer receive a Password dialogue pop-up and still can't edit the settings. Even logging in as root does not enable the fields in the editor. Trying NetworkManager-0.8.3.997-1.fc14 from Koji seems to bring back the editing functions for everything, but I got the following AVCs when I did the
service NetworkManager restart
type=AVC msg=audit(1299170145.728:21039): avc: denied { signull } for pid=9899 comm="NetworkManager" scontext=unconfined_u:system_r:NetworkManager_t:s0 tcontext=unconfined_u:system_r:dhcpc_t:s0 tclass=process
type=SYSCALL msg=audit(1299170145.728:21039): arch=i386 syscall=kill success=no exit=EACCES a0=1a37 a1=0 a2=8104ad0 a3=1a37 items=0 ppid=1 pid=9899 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm=NetworkManager exe=/usr/sbin/NetworkManager subj=unconfined_u:system_r:NetworkManager_t:s0 key=(null)
*** Bug 681532 has been marked as a duplicate of this bug. *** Should be fixed by latest update. Can you confirm? As for SElinux error, I think the contexts are not correct (unconfined_u). It should be system_u. Relabelling should help: # /sbin/restorecon -R -v /sbin # /sbin/restorecon -R -v /usr/sbin or whole filesystem # touch /.autorelabel # reboot Links: - http://wiki.centos.org/HowTos/SELinux - http://docs.fedoraproject.org/en-US/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html - see also bug 681706 I did not experience the SELinux issue after installing NetworkManager-0.8.3.997-1.fc14 from Koji Also, all seems to be okay, I can edit the various fields as required. Closing per comment #7. |