Package: synergy
Version: 1.2.2-1
Severity: important

My config:
- host A is synergy server
- host B is synergy client and is running the VMware [1] application
  (among other applications in my GNOME desktop)

I can't get capital letters (using shift or caps lock) inside VMware.
Instead I get nothing. I can get "a" but not "A". Capitals letters works
fine in the other applications on host B.

The problem is the same if I run Linux or Windows inside VMware.

I used xev(1) in a Fedora Core 4 installed inside VMware and I have:
- shift key events are OK
- "a" key events are OK
- shift + any other letter does not work. Only the shift events are seen. 
- control key events are OK
- control + another key events are OK : the two keys are seen and 4
  events are generated (control pressed, "A" pressed, "A" released,
  control released for Ctrl-A combination)

I don't have the problem if I use x2x [2] instead of synergy.

Thanks,

[1] http://www.vmware.com/
[2] http://packages.debian.org/unstable/x11/x2x

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686-smp
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages synergy depends on:
ii  libc6                    2.3.2.ds1-22    GNU C Library: Shared libraries an
ii  libgcc1                  1:4.0.0-9       GCC support library
ii  libice6                  4.3.0.dfsg.1-14 Inter-Client Exchange library
ii  libsm6                   4.3.0.dfsg.1-14 X Window System Session Management
ii  libstdc++5               1:3.3.5-13      The GNU Standard C++ Library v3
ii  libx11-6                 4.3.0.dfsg.1-14 X Window System protocol client li
ii  libxext6                 4.3.0.dfsg.1-14 X Window System miscellaneous exte
ii  libxtst6                 4.3.0.dfsg.1-14 X Window System event recording an
ii  xlibs                    4.3.0.dfsg.1-14 X Keyboard Extension (XKB) configu

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to