406438 – vnc port is blocked on first boot into the installed system after vnc installation

Bug 406438 - vnc port is blocked on first boot into the installed system after vnc installation

Summary: vnc port is blocked on first boot into the installed system after vnc install...

Status:	RESOLVED DUPLICATE of bug 398855

Alias:	None

Product:	openSUSE 11.0
Classification:	openSUSE
Component:	Installation (show other bugs)
Version:	Final
Hardware:	Other Other

Priority:	P3 - Medium Severity: Normal (vote)
Target Milestone:	---
Assignee:	Lukas Ocilka
QA Contact:	Jiri Srain

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2008-07-04 07:55 UTC by Tejun Heo
Modified:	2008-08-06 14:38 UTC (History)
CC List:	0 users

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

Attachments
y2logs (236.65 KB, application/x-tar) 2008-07-19 02:58 UTC, Tejun Heo	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 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 ***