300608 – YaST does not save network settings

Bug 300608 - YaST does not save network settings

Summary: YaST does not save network settings

Status:	RESOLVED DUPLICATE of bug 299033

Alias:	None

Product:	openSUSE 10.3
Classification:	openSUSE
Component:	YaST2 (show other bugs)
Version:	Beta 1
Hardware:	x86 Other

Priority:	P5 - None Severity: Major (vote)
Target Milestone:	---
Assignee:	Michal Zugec
QA Contact:	Jiri Srain

URL:	http://www.viruzz.is.dreaming.org
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2007-08-15 12:40 UTC by Henning Schleef
Modified:	2007-08-16 14:40 UTC (History)
CC List:	0 users

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

Attachments
yast log (859.85 KB, application/x-tgz) 2007-08-15 21:40 UTC, Trango Towers	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Henning Schleef 2007-08-15 12:40:58 UTC

When I use YaST to configure my network devices (IP-Address, W-LAN, DNS/Routing, etc. pp.), YaST does not keep the settings after saving. By starting YaST again, it says that my network devices was not configured yet (even though I had configured it several minutes before).
Mabye I should mention that my network device is an Intel PRO/Wireless i3945ABG whose drivers were already included in openSUSE 10.2 and that the 'database is locked' bug occurs before (http://bugzilla.novell.com/show_bug.cgi?id=297627).

Comment 1 Cyril Hrubis 2007-08-15 16:34:26 UTC

Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST

Thanks!

Comment 2 Trango Towers 2007-08-15 21:40:35 UTC

Created attachment 157785 [details]
yast log

The same bug applies to me. Here is the y2log

Comment 3 Michal Zugec 2007-08-16 14:40:09 UTC

duplicate (already fixed)
as workaround be sure in all configured devices that "Enable Device Control for Non-root User via KInternet" is not checked (Device->Configure, tab General)

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