Bug 146162

Summary: Yast2 network configuration doesn't let me enter nameserver IP address
Product: [openSUSE] SUSE Linux 10.1 Reporter: Markus Koßmann <markus.kossmann>
Component: YaST2Assignee: Martin Vidner <mvidner>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Critical    
Priority: P5 - None CC: bugproxy, jphblais, suse-beta, susedev, ursula.brueckner
Version: Beta 2   
Target Milestone: ---   
Hardware: i586   
OS: Other   
See Also: http://bugworks.engr.sgi.com/query.cgi/949015
http://bugworks.engr.sgi.com/query.cgi/948852
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Output of hwinfo
logfile of yast session with the problem
screenshot of yast2 with disabled nameserver entry fields

Description Markus Koßmann 2006-01-27 14:45:25 UTC
During the installion of 10.1b2 I found that the entry fields for the name server were disabled. After finishing the installation I tried again to configure these addresses. But the problem still exists
Comment 1 Markus Koßmann 2006-01-27 14:46:43 UTC
Created attachment 65421 [details]
Output of hwinfo
Comment 2 Markus Koßmann 2006-01-27 14:49:10 UTC
Created attachment 65424 [details]
logfile of yast session with the problem
Comment 3 Markus Koßmann 2006-01-27 14:50:38 UTC
Created attachment 65425 [details]
screenshot of yast2 with disabled nameserver entry fields
Comment 4 Michael Gross 2006-01-30 15:37:36 UTC
This could be intentional when using network manager which, I suppose, you're using? Waiting for a comment from Martin.
Comment 5 Martin Vidner 2006-01-30 16:29:18 UTC
No, this is a bug that strikes when the configuration is static, as in your case. The checkbox Update nameservers and searchlist via DHCP should be disregarded then, but it isn't.
Fixed for Beta 3 in yast2-network-2.13.20.
Comment 6 Christian Boltz 2006-01-31 00:21:55 UTC
*** Bug 146712 has been marked as a duplicate of this bug. ***
Comment 7 Martin Vidner 2006-01-31 16:25:12 UTC
*** Bug 146953 has been marked as a duplicate of this bug. ***
Comment 8 Martin Vidner 2006-02-01 10:07:21 UTC
*** Bug 147071 has been marked as a duplicate of this bug. ***
Comment 9 Martin Vidner 2006-02-01 10:09:33 UTC
*** Bug 147135 has been marked as a duplicate of this bug. ***