I also have this issue. Another work around is to use the Gnome Vino Server. I have also downgraded to version: tigervnc-server-1.0.0-1.fc12.x86_64 and seems to work on F12.

I'm not able to reproduce this issue. Would it be possible to attach full .vnc/hostname:1.log, please? Thank you in advance.

Adam:

Xvnc:
=====

/usr/bin/Xvnc :6 -geometry 1280x1024 -depth 24 -dpi 96 -httpd /usr/share/vnc/classes -auth /root/.Xauthority -rfbauth /root/.vnc/passwd -log *:stderr:30 -ClientWaitTimeMillis 20000 -IdleTimeout 0 -rfbport 5906 -desktop=root@vortex


Since my "/root/.vnc/vortex:6.log" file is short I will just paste it in:

----------------------------------------------------------
Xvnc TigerVNC 1.0.90 - built Jun 24 2010 10:00:40
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 10800000, The X.Org Foundation


Thu Jul  8 20:52:40 2010
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on all interface(s), port 5906
 vncext:      Listening for HTTP connections on all interface(s), port 5806
 vncext:      created VNC server for screen 0

Thu Jul  8 20:53:03 2010
 Connections: accepted: 10.222.222.18::61504
 SConnection: Client needs protocol version 3.8
 SConnection: Client requests security type VncAuth(2)
 SConnection: AuthFailureException: Authentication failure
 Connections: closed: 10.222.222.18::61504 (Authentication failure)

Thu Jul  8 20:53:12 2010
 Connections: accepted: 10.222.222.18::61505
 SConnection: Client needs protocol version 3.8
 SConnection: Client requests security type VncAuth(2)
 VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
 VNCSConnST:  Client pixel format depth 24 (32bpp) little-endian rgb888

Thu Jul  8 20:53:56 2010
 Input:       generate_modkeymap failed
 Input:       generate_modkeymap failed

Thu Jul  8 20:54:24 2010
 Input:       generate_modkeymap failed
 Input:       generate_modkeymap failed
 Input:       generate_modkeymap failed
 Input:       generate_modkeymap failed

Thu Jul  8 23:03:06 2010
 Input:       generate_modkeymap failed
 Input:       generate_modkeymap failed
 Input:       generate_modkeymap failed
 Input:       generate_modkeymap failed
 Input:       generate_modkeymap failed

Thu Jul  8 23:03:07 2010
 Input:       generate_modkeymap failed

Fri Jul  9 11:59:03 2010
 Input:       generate_modkeymap failed

Fri Jul  9 11:59:04 2010
 Input:       generate_modkeymap failed

Thanks for your logs. However I'm still not able to reproduce this issue even when I start Xvnc with same parameters.

Would it be possible tell me how exactly do you start your desktop in the virtual machine? Do you start Xvnc via /usr/bin/vncserver command? If yes, please attach your .vnc/xstartup. Also please tell me which window manager do you use. Thank you in advance.

This error only occurs with the VMWare WorkStation application. If I run another X-application (e.g., firefox) within the VNC session, keyboard input/output behaves normally and no "generate_modkeymap failed" messages occur.

I can also control the VMware workstation manager and setting with no keyboard input/output issues. This problem only occurs with typing within a guest virtual machine (examples terminal, login dialog, etc...).

This xstartup is run to start the GNOME desktop. This for the vnc session. The VMware WorkStation is run within this VNC session. No Xvnc sessions are run within the virtual machines themselves.

So I believe there is an interaction between the tigervnc server v1.0.1 and VM WorkStation 7 Guest VMs. Remember if I revert back to tigervnc server 1.0.0 keyboard I/O behaves normally which is the current workaround.

xstartup:
=========
#!/bin/bash
# Copyright (C) 1999 - 2004 Red Hat, Inc. All rights reserved. This
# copyrighted material is made available to anyone wishing to use, modify,
# copy, or redistribute it subject to the terms and conditions of the
# GNU General Public License version 2.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.

#
# Redirect errors to a file in user's home directory if we can...
if [ -z "$GDMSESSION" ]; then
  #
  # Non-GDM redirect output:
  errfile="$HOME/.xsession-errors${DISPLAY}.log";
  if /bin/cp /dev/null "$errfile" 2> /dev/null ; then
    /bin/chmod 600 "$errfile";
    exec > "$errfile" 2>&1;
  else
    errfile=$(/bin/mktemp -q /tmp/xses-$USER.XXXXXX;)
    if [ $? -eq 0 ]; then
      exec > "$errfile" 2>&1;
    fi
  fi
fi

#
# NST Default X start init script (attempts to launch the
# X Window Desktop Manager below from ssh-agent parent process)
SSH_LAUNCH="";
if [ \( -z "${SSH_AGENT_PID}" \) -a      \( -x "/usr/bin/ssh-agent" \) ]; then
  SSH_LAUNCH="/usr/bin/ssh-agent";
fi

#
# Source in Startup X Window Applications:
if [ -f "${HOME}/.vnc/xstartupapps" ]; then
 source "${HOME}/.vnc/xstartupapps";
fi

#
# Startup the currently configured X Window Desktop Manager:
exec gnome-session;

(In reply to comment #5)

Thanks for your information, I will try to reproduce this issue with the VM Workstation.

> So I believe there is an interaction between the tigervnc server v1.0.1 and VM
> WorkStation 7 Guest VMs. Remember if I revert back to tigervnc server 1.0.0
> keyboard I/O behaves normally which is the current workaround.

Although this is usually useful information, there is a huge difference between 1.0.0 and 1.0.1 server in keyboard handling in Fedora because those servers are built against different major versions of X.Org.

Thanks rwhalb for log and xstartup.

The issue i have encountered is the same as rwhalb. Only in VMware Guest OS.

The following is .vnc/xstartup.
$cat ~/.vnc/xstartup

#!/bin/sh

#vncconfig -iconic &
# Uncomment the following two lines for normal desktop:
 unset SESSION_MANAGER
 exec /etc/X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &


I start Xvnc via "service vncserver start"(Automatic when boot).

The following is /etc/sysconfig/vncservers ( +extension XKEYBOARD doesn't matter, I have tried with/without this option)

#/etc/sysconfig/vncservers
 VNCSERVERS="1:shr"
 VNCSERVERARGS[1]="-geometry 1200x900 -localhost -nolisten tcp +extension XKEYBOARD"

I would like to ask you to reproduce the problem with rpm on http://atkac.fedorapeople.org/tigervnc/tigervnc-server-1.0.90-0.12.20100420svn4030.fc13.1.x86_64.rpm, please. Although this rpm won't solve this issue, it will write more details which will help in further debugging. Make sure you pass "-log *:stderr:100" parameter to Xvnc and attach vncserver log here, please. Thank you in advance.

Created attachment 438725 [details]
Error output for debug tigervnc-server RPM

I have attached an Xvnc log file above using RPM:

tigervnc-server-.0.90-0.12.20100420svn4030.fc13.1.x86_64.rpm

- Most of the error info is at the bottom.

I ran Xvnc using the following:

/usr/bin/Xvnc :6 -geometry 1280x1024 -depth 24 -dpi 96 -httpd /usr/share/vnc/classes -auth /root/.Xauthority -rfbauth /root/.vnc/passwd -log *:stderr:100 -log *:stderr:100 -ClientWaitTimeMillis 20000 -IdleTimeout 0 -rfbport 5906 -desktop=root@vortex

---RWH

Created attachment 438910 [details]
Error log for debug tigervnc-server RPM (VMware Workstation 7.1.1)

The log I attached is very similar to rwhalb's.

Every time I press any key in VMware Workstation, it will generate the error:

 Input:       generate_modkeymap failed, detail: 11
 Input:       generate_modkeymap failed, detail: 11

I use VMware Workstation 7.1.1.

This is odd, "detail 11" indicates generate_modkeymap should have failed due lack of memory. This doesn't sound believably for me.

May I ask you test another debug tigervnc-server from https://kojiweb.fedoraproject.org/koji/taskinfo?taskID=2409072, please? (download it from bottom of the page) This build should give me enough information to figure what exactly VMware Workstation does. Then attach log file as before, please.

Adam:

Your link:

https://kojiweb.fedoraproject.org/koji/taskinfo?taskID=2409072

appears broken????

---Ron Henderson

(In reply to comment #14)
> Adam:
> 
> Your link:
> 
> https://kojiweb.fedoraproject.org/koji/taskinfo?taskID=2409072
> 
> appears broken????

Hm, the link works fine for me. However I put tigervnc-server also on http://atkac.fedorapeople.org/tigervnc/tigervnc-server-1.0.90-0.12.20100420svn4030.fc13.2.x86_64.rpm so you can try this link.

Created attachment 439665 [details]
Log File for tigervnc-server-1.0.90-0.12.20100420svn4030.fc13.2.x86_64.rpm

I have attached another Xvnc log file above using RPM:

tigervnc-server-.0.90-0.12.20100420svn4030.fc13.2.x86_64.rpm

- Most of the error info is at the bottom.

I ran Xvnc using the following:

/usr/bin/Xvnc :6 -geometry 1280x1024 -depth 24 -dpi 96 -httpd
/usr/share/vnc/classes -auth /root/.Xauthority -rfbauth /root/.vnc/passwd -log
*:stderr:100 -log *:stderr:100 -ClientWaitTimeMillis 20000 -IdleTimeout 0
-rfbport 5906 -desktop=root@vortex

---RWH

I ran into a similar problem.  It started out in Vino not transferring "(" or ")" the parentheses keys.  So I to tried tigervnc-server-1.0.90- 0.12.20100420svn4030.fc13.x86_64  This was worse as no keys were seen anywhere on the desktop or in the VMware window and once I clicked the mouse in the window it wouldn't release since keyboard presses were not recognized.  I backed off to  tigervnc-server-1.0.0-1.fc12.x86_64.rpm and all is well.  If you want additional info let me know.

Hubert

May I ask you to retest this issue with http://atkac.fedorapeople.org/tigervnc/tigervnc-server-1.0.90-0.12.20100420svn4030.fc13.4.x86_64.rpm, please? This package should finally solve this issue, I hope. In case it is still broken please attach log as before. Thank you in advance.

Adam:

Greate job! Just tried RPM:

tigervnc-server-1.0.90-0.12.20100420svn4030.fc13.4.x86_64.rpm

Now works as expected: running VMware Workstation 7.1 under tiger-vnc and typing within Linux VM guest in a terminal window. Hopefully others will concur with my results so that this fix can be released in the F13 update repo...

Thanks for your support...

Ron Henderson

Thanks Adam~~

I have tried tigervnc-server-1.0.90-0.12.20100420svn4030.fc13.4.x86_64.rpm
 and It works fine to me.

shr

tigervnc-1.0.90-0.13.20100420svn4030.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/tigervnc-1.0.90-0.13.20100420svn4030.fc13

tigervnc-1.0.90-0.13.20100420svn4030.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update tigervnc'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/tigervnc-1.0.90-0.13.20100420svn4030.fc13

tigervnc-1.0.90-0.13.20100420svn4030.fc13 solved this issue for me on Fedora 13 and RHEL 6.0 Beta Release 2
Thanks
Hubert

tigervnc-1.0.90-0.13.20100420svn4030.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.