Bug 403354 - vnc installation fails if vinagre is used as client
Summary: vnc installation fails if vinagre is used as client
Status: RESOLVED DUPLICATE of bug 389386
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-24 17:22 UTC by Tejun Heo
Modified: 2008-09-15 09:10 UTC (History)
1 user (show)

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

Attachments
y2logs.tar.gz (8.87 KB, application/x-gzip)
2008-06-24 17:23 UTC, Tejun Heo 		Details
boot.msg just in case (18.20 KB, text/plain)
2008-06-24 17:24 UTC, Tejun Heo 		Details
lspci just in case (1.58 KB, text/plain)
2008-06-24 17:24 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-06-24 17:22:41 UTC 
vnc installation fails and yast dies from exception if vinagre is used as client.  Using tightvnc vncviewer works fine.  Will attach logs.
Comment 1 Tejun Heo 2008-06-24 17:23:53 UTC 
Created attachment 224076 [details]
y2logs.tar.gz
Comment 2 Tejun Heo 2008-06-24 17:24:08 UTC 
Created attachment 224077 [details]
boot.msg just in case
Comment 3 Tejun Heo 2008-06-24 17:24:22 UTC 
Created attachment 224078 [details]
lspci just in case
Comment 4 Tejun Heo 2008-06-24 18:35:29 UTC 
Further problem: After the initial boot into the installed system, firewall is activated w/ vnc ports blocked.
Comment 5 Michal Zugec 2008-07-04 07:41:22 UTC 
Kurt, could you please look at VNC problem
Tejun: write new bugreport for that please
Comment 6 Kurt Garloff 2008-09-15 07:35:55 UTC 
To me it looks like the VNC problem is somewhere between Xvnc and vinagre.
Comment 7 Stefan Dirsch 2008-09-15 09:10:17 UTC 
Known issue and has been fixed by the Driver update feature, i.e. press F6 at the beginning of installation.

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