Bug 768531

Summary: With the NetworkManager.conf dns=dnsmasq setting NetworkManager crashes after activating a OpenVPN tunnel
Product: [Fedora] Fedora Reporter: Jonathan Briggs <zlynx>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: dcbw, iny, jklimes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-20 15:28:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
gdb backtrace none

Description Jonathan Briggs 2011-12-16 22:28:29 UTC
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.

Comment 1 Jirka Klimes 2012-09-06 09:50:14 UTC
Hmm, it looks like a crash because no nameservers are present in IP configuration.

Fixed in upstream git master:
585564b9f5bdc85739e8c2115c29d15fb58477a6

Comment 2 Fedora Update System 2012-10-04 14:28:08 UTC
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

Comment 3 Fedora Update System 2012-10-05 18:24:17 UTC
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

Comment 4 Fedora Update System 2012-10-06 05:28:02 UTC
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).

Comment 5 Fedora Update System 2012-10-06 20:10:56 UTC
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

Comment 6 Fedora Update System 2012-12-20 15:28:44 UTC
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.

Comment 7 Jonathan Briggs 2012-12-20 18:27:04 UTC
This bug report is for Fedora 16. How does a Fedora 18 update address the problem?