Bug 254140 - VNC installation fails with _X11TransSocketINETConnect() localhost:6001: Name or service not known
Summary: VNC installation fails with _X11TransSocketINETConnect() localhost:6001: Name...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 8
Hardware: ppc64
OS: Linux
low
low
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-08-24 13:12 UTC by Jochen Roth
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version: test3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-05 08:52:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jochen Roth 2007-08-24 13:12:47 UTC
Description of problem:
I tried to install f8test1 on a JS21 blade (ppc64) by using a ppc DVD and the
"vnc" parameter. 
After determining the IP-Address anaconda isn't able to create a VNC server
because of the following message. I was able to install f8test1 by using the
text mode installer.  

Version-Release number of selected component (if applicable):
f8test1

How reproducible:
always

Steps to Reproduce:
1. Burn ppc64 DVD
2. Type "linux64 vnc" at yaboot command prompt
3. wait for the following message
  
Actual results:

Running anaconda, the Fedora system installer - please wait...                 
Probing for video card:   Unable to probe
No video hardware found, assuming headless
Starting VNC...


WARNING!!! VNC server running with NO PASSWORD!
You can use the vncpassword=<password> boot option
if you would like to secure the server.


The VNC server is now running.
Please connect to <fqdn>:1 (9.x.x.x) to begin the install...
_X11TransSocketINETConnect() can't get address for localhost:6001: Name or
service not known

(mini-wm:1307): Gtk-WARNING **: cannot open display: :1

Comment 1 Chris Lumens 2007-08-24 18:11:51 UTC
Are there any error messages on tty3?

Comment 2 Jochen Roth 2007-10-05 08:52:14 UTC
I just tested it again with test3 and it works now. 


Note You need to log in before you can comment on or make changes to this bug.