Bug 545978 - NetworkManager writes empty resolv.conf
Summary: NetworkManager writes empty resolv.conf
Status: RESOLVED DUPLICATE of bug 544195
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: Network (show other bugs)
Version: Factory
Hardware: All SUSE Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-10 10:01 UTC by Jeremy Bicha
Modified: 2009-10-10 11:10 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeremy Bicha 2009-10-10 10:01:50 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-2.1 Firefox/3.5.3

.

Reproducible: Always

Steps to Reproduce:
1. Upgrade to latest Factory (I installed from M8)
2. Reboot
3. Connect to your Network with NetworkManager (either KDE or GNOME, wired or wireless)
Actual Results:  
NetworkManager appears to write an empty resolv.conf.
I can access my router or websites via their IP address, but DNS is broken.
Deleting resolv.conf allowed the file to be recreated correctly

Expected Results:  
.

I had not touched my /etc/resolv.conf file before.
Comment 1 Forgotten User Xh41Ao4q6j 2009-10-10 10:59:09 UTC
I haven't touched /etc/resolv.conf by hand too, but there is one resolv.conf.netconfig. Although, I switched few times between ifup that worked with wired connection, trying to see is NetworkManager picking up wireless, so that can be a reason for resolv.conf.netconfig. 

Besides on boot, before KNetworkManager was manually started, the resolv.conf was missing nameserver line. There was only # Generated by NetworkManager .
Comment 2 Forgotten User Xh41Ao4q6j 2009-10-10 11:07:41 UTC
This bug is duplicate of bug #544195
Comment 3 Forgotten User Xh41Ao4q6j 2009-10-10 11:10:07 UTC
This bug is duplicate of bug #544195

(double comment to satisfy bugzilla)

*** This bug has been marked as a duplicate of bug 544195 ***