|
Bugzilla – Full Text Bug Listing |
| Summary: | factory build: vnc-based installation gives error on SuSEfirewall2_init | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | eric m <ericm24x7> |
| Component: | Installation | Assignee: | E-mail List <bnc-team-screening> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
please attach /var/log/YaST/* The latest factory build dated on 1.29.06 fixed the above problem. |
VNC-based installation has error message on "Nework Configuration" stage. Under the "Firewall" subset heading: Remote Administration (VNC) ports are [blocked] Pressing the highlighted [blocked] does NOT switch the option to [open] as expected. So pressing the [next] button to continue on with the installation will display the error message on "SuSEfirewall2_init". NOTE: using factory distribution build dated 1.27.06