Bug 603817 - Network settings does not open. No error on screen or in /var/log/messages
Summary: Network settings does not open. No error on screen or in /var/log/messages
Status: RESOLVED DUPLICATE of bug 600576
Alias: None
Product: openSUSE 11.3
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Factory
Hardware: x86-64 Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-07 16:34 UTC by Rudi Pittman
Modified: 2010-05-07 18:15 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 Rudi Pittman 2010-05-07 16:34:41 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.4) Gecko/20100417 SUSE/3.6.4-1.3 Firefox/3.6.4

I upgraded Milestone 6 to Factory last night and did a reboot so I can't confirm if the problem is in milestone 6 but it might be.   I was going into network settings to change the hostname...double click...nothing happens...tried it a few more times then went to a terminal and ran yast in text mode and tried accessing network settings...same non result....finally edited the HOSTNAME manually using pico but someone should check why it's not coming up.

I have no idea what log to include so if you need something yell and I'll upload it.

Reproducible: Always

Steps to Reproduce:
1.Go into Yast
2.Click on Network Settings
3.
Actual Results:  
Does nothing

Expected Results:  
Panel should display with option to change network settings.
Comment 1 Leonardo Chiquitto 2010-05-07 18:15:23 UTC
This problem was reported in bug #600576 and was already fixed. You can wait for the fix to reach Factory or use the packages in:

  http://download.opensuse.org/repositories/YaST:/Head/openSUSE_Factory/

Thanks for taking the time to report!

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