Hide Forgot
Created attachment 547997 [details] gdb backtrace Description of problem: With the NetworkManager.conf dns=dnsmasq setting NetworkManager crashes after activating a OpenVPN tunnel. The tunnel comes up and during the DNS configuration stage, NM seg-faults. Version-Release number of selected component (if applicable): NetworkManager-0.9.2-1.fc16.x86_64 How reproducible: Every time. Steps to Reproduce: 1. Configure a Fedora 16 system using the Network Preference GUI for an OpenVPN tunnel. 2. Edit the /etc/NetworkManager/NetworkManager.conf file and set "dns=dnsmasq" 3. Activate the OpenVPN tunnel. Actual results: After the tunnel comes up NetworkManager crashes with a seg-fault. Expected results: A working OpenVPN tunnel.
Hmm, it looks like a crash because no nameservers are present in IP configuration. Fixed in upstream git master: 585564b9f5bdc85739e8c2115c29d15fb58477a6
NetworkManager-0.9.7.0-2.git20121004.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/NetworkManager-0.9.7.0-2.git20121004.fc18
NetworkManager-0.9.7.0-3.git20121004.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/NetworkManager-0.9.7.0-3.git20121004.fc18
Package NetworkManager-0.9.7.0-3.git20121004.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing NetworkManager-0.9.7.0-3.git20121004.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-15525/NetworkManager-0.9.7.0-3.git20121004.fc18 then log in and leave karma (feedback).
NetworkManager-0.9.7.0-4.git20121004.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/NetworkManager-0.9.7.0-4.git20121004.fc18
NetworkManager-0.9.7.0-3.git20121004.fc18 has been pushed to the Fedora 18 obsolete repository. If problems still persist, please make note of it in this bug report.
This bug report is for Fedora 16. How does a Fedora 18 update address the problem?