Bug 406438

Summary: vnc port is blocked on first boot into the installed system after vnc installation
Product: [openSUSE] openSUSE 11.0 Reporter: Tejun Heo <teheo>
Component: InstallationAssignee: Lukas Ocilka <locilka>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P3 - Medium    
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2logs

Description Tejun Heo 2008-07-04 07:55:59 UTC
After the initial boot into the installed system, firewall is activated w/ vnc ports blocked even if vnc was used during installation.
Comment 1 Lukas Ocilka 2008-07-15 15:43:33 UTC
Please, attach YaST logs.
BTW: Please, next time you report a bug against YaST, do it automatically.

http://en.opensuse.org/Bugs/YaST
Comment 2 Tejun Heo 2008-07-19 02:57:48 UTC
Right, I should have remembered that.  I tried a few times to reproduce the problem but didn't succeed.  It might as well be me being confused.  I had two not-so-major problems tho.

1. With autoconf off, after the initial reboot (so the second vnc connection), it told me to connect to 127.0.0.2:1 instead of the ip assigned via dhcp.  It used the right ip for the first vnc connection.

2. In the configuration summary, it warns that vnc port is blocked and suggests that it be opened.  However, clicking the (open) link two lines below doesn't do anything.  It stays closed.  I entered the firewall configuration and add vnc service manually.  The summary still said that vnc port was closed even after that, but vnc worked fine afterwards.

I'll attach y2logs.
Comment 3 Tejun Heo 2008-07-19 02:58:42 UTC
Created attachment 228889 [details]
y2logs
Comment 4 Lukas Ocilka 2008-07-22 08:56:54 UTC
The issue #1 has been already fixed meanwhile.
I'll have to check the second one but I remember fixing something about it.
Comment 5 Lukas Ocilka 2008-08-06 14:38:03 UTC

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