Bug 308763

Summary:	YaST Network Configuration module doesn't save settings
Product:	[openSUSE] openSUSE 10.3	Reporter:	Alberto Passalacqua <alberto.passalacqua>
Component:	YaST2	Assignee:	Katarina Machalkova <kmachalkova>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Critical
Priority:	P5 - None	CC:	coolo, jdsn, jlcordeiro, lnussel, locilka, sbj
Version:	Beta 3	Flags:	coolo: SHIP_STOPPER-
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Output of save_y2logs

Description Alberto Passalacqua 2007-09-07 18:30:07 UTC

If you try to add a wireless card manually, the YaST-gtk network module doesn't save the settings properly. 

- The ESSID is not assigned (iwconfig doesn't show it).
- The kernel module name is not in the field anymore, if the module is restarted.
- The firewall zone of the card is reset to the default value (no traffic allowed).

Regards,
Alberto

Comment 1 Andreas Jaeger 2007-09-08 08:34:40 UTC

could you add the YaST log files, please? See http://en.opensuse.org/Bugs/YaST

Comment 2 Alberto Passalacqua 2007-09-08 16:33:06 UTC

Created attachment 162865 [details]
Output of save_y2logs

Comment 3 Alberto Passalacqua 2007-09-08 16:33:52 UTC

I attached the output of save_y2logs. I hope it helps.

Regards,
Alberto

Comment 4 Lukas Ocilka 2007-09-19 13:30:01 UTC

Coolo: this bugs seems to be important to fix.

Kmachalkova has a working and tested fix.
Bubli: is that true?

Comment 5 Katarina Machalkova 2007-09-19 14:27:00 UTC

Important to fix, yes - because (due to broken widget manipulation and dialog validation) it can prevent the complete netcard configuration (incl. DNS, routing and the stuff) from being saved. It affects not only adding new, but also editing existing netcard.

The fact that there aren't any duplicates of this bug only means that NetworkManager works very well ;-)

I have a fix, but did not test adding a new card yet, just editing, which seems to work. The reason of the problem however seems to be the same for both cases.

Comment 6 Katarina Machalkova 2007-09-19 14:27:24 UTC

Side note: all UIs are affected, not only gtk

Comment 7 Lukas Ocilka 2007-09-19 14:30:46 UTC

Let's make it a Critical (or even blocker?)
I'd like to see it fixed in RC2 because it cannot be fixed via online update :(
Online update is in workflow "after" the network setup.

Comment 8 Stephan Kulow 2007-09-19 15:25:17 UTC

agreed.

Comment 11 Stephan Kulow 2007-09-20 17:13:13 UTC

what is the ETA?

Comment 12 Stephan Kulow 2007-09-20 17:56:47 UTC

*** Bug 326865 has been marked as a duplicate of this bug. ***

Comment 15 Stephan Kulow 2007-09-21 05:41:21 UTC

submitted

Comment 16 Stephan Kulow 2007-09-21 05:43:51 UTC

sorry, confused two bugs

Comment 19 Katarina Machalkova 2007-09-21 10:28:51 UTC

* Manually adding devices and editing existing devices now works (yast2-network 2.15.79)
* What doesn't work, is saving network module names for newly added devices
* Saving wireless features seem to work as well, but I can't test reliably right now

Comment 20 Lukas Ocilka 2007-09-21 10:46:15 UTC

*** Bug 326369 has been marked as a duplicate of this bug. ***

Comment 23 Katarina Machalkova 2007-09-21 14:24:31 UTC

I believe we can mark this as fixed. 
Manually adding devices now correctly works (incl. device number and its module) Wireless stuff for the card is correctly written into related ifcfg-wlanX sysconfig file (if iwconfig still doesn't honor these values, it's worth a new bugreport)

(yast2-network 2.15.79-2 or newer)

Comment 24 Katarina Machalkova 2007-09-26 07:15:34 UTC

*** Bug 328044 has been marked as a duplicate of this bug. ***