Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 651475 - Cannot start vnc installation on s390x
Summary: Cannot start vnc installation on s390x
Keywords:
Status: CLOSED DUPLICATE of bug 653436
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 14
Hardware: s390x
OS: Linux
low
medium
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ZedoraTracker
TreeView+ depends on / blocked
 
Reported: 2010-11-09 16:46 UTC by Jan Stodola
Modified: 2010-11-18 14:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-18 14:52:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/tmp/*log (10.04 KB, application/x-gzip)
2010-11-09 16:46 UTC, Jan Stodola
no flags Details

Description Jan Stodola 2010-11-09 16:46:38 UTC
Created attachment 459183 [details]
/tmp/*log

Description of problem:
When trying to install F14 on s390x using vnc mode, installation shuts down after user selects vnc mode.

/tmp/vncserver.log contains:

Xvnc TigerVNC 1.0.90 - built Oct  7 2010 05:30:20
Copyright (C) 2002-2005 RealVNC Ltd.
Copyright (C) 2000-2006 Constantin Kaplinsky
Copyright (C) 2004-2009 Peter Astrand for Cendio AB
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 10900000, The X.Org Foundation


Tue Nov  9 16:38:50 2010
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on all interface(s), port 5901
 vncext:      created VNC server for screen 0
[dix] Could not init font path element catalogue:/etc/X11/fontpath.d, removing from list!
syntax error: line 8 of stdin
Errors encountered in stdin; not compiled.
(EE) Error compiling keymap (server-1)
(EE) XKB: Couldn't compile keymap
XKB: Failed to compile keymap
Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.

Fatal server error:
Failed to activate core devices.


Version-Release number of selected component (if applicable):
installation tree from http://secondary.fedoraproject.org/pub/alt/spins/S390/current/
anaconda 14.17.2 (kernel, initrd.img and install.img from 20-Oct-2010)

How reproducible:
always

Steps to Reproduce:
1. start installation in z/VM
2. connect using ssh to start the installation
3. select vnc mode when asked (with or without password)
  
Actual results:
vnc server doesn't start, system shuts down

Expected results:
vncserver is running

Additional info:

Comment 1 Dan Horák 2010-11-09 17:23:53 UTC
IIRC it's a know issue, assigning to Karsten who works on it.

Comment 2 Karsten Hopp 2010-11-18 14:52:26 UTC

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


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