From: Etaoin Shrdlu <shrdlu@unlimitedmail.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Strange problems with keyboard over vnc
Date: Mon, 25 May 2009 16:53:14 +0200 [thread overview]
Message-ID: <200905251653.14458.shrdlu@unlimitedmail.org> (raw)
I don't even know what to google for in this case.
I have a remote box running gentoo with kde 3.5, to which I connect using
VNC (krfb on the remote box, krdc on the local one).
(the actual connection goes via a ssh tunnel, but I think that is not
relevant here)
All used to work fine, until some days ago the remote site had a power
outage and the box was turned off. So I asked someone at the remote site
to turn it on (just pressing the big red switch, basically), and I could
happily connect via VNC again. Everything seemed to work fine, except
that at some point I realized that I was not able to enter uppercase
characters. That is, pressing (for example) shift+r on the local
keyboard produces a lowercase r, regardless of which shift key I use
(left or right is the same). This happens in every program (xterm,
kmail, konsole, etc.). Caps lock works fine though.
But the weirdness does not stop here. Accidentally, I discovered that if
I press shift, and then press another key and keep it pressed to trigger
repetition, I get this:
$ sSSSSSSSSsssssssssss
or this:
$ 5%%%%%%%%55555555555
in both cases, the first character is output immediately; since the key
(s or 5) is hold pressed, after a brief interval repetition starts, with
the expected output for shift+that key, but that lasts only for 8
repetitions, and after that it reverts to the non-shift version. The
number 8 seems to be constant. All of this happens just keeping the key
pressed, without releasing it. (yes, it's difficult to explain!)
Another strange thing is that combinations that involve pressing multiple
keys, one of which is shift (like for example altgr+shift+[ to get an
open brace) seem to produce the expected result (ie, { in this example).
Out of curiosity, I tried to connect to the remote box using krdc from
another gentoo+kde box, and I got exactly the same results. To complete
the picture, when using the original local box to connect to a different
remote box with the same setup everything works fine, so it seems a
problem of that specific remote box.
I tried to rebuild krdc on the local box and krfb on the remote one, no
luck.
Nothing changed in installed software releases: xorg-x11 on the remote
box is 7.2, xorg-server is 1.5.3-r6, with a pretty basic setup (just
keyboard, mouse and graphics adapter, no hal or other fancy stuff; I can
post the config as well as any other information if needed).
As I said before, I don't know even where to start looking here.
Thanks in advance for any help.
reply other threads:[~2009-05-25 14:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200905251653.14458.shrdlu@unlimitedmail.org \
--to=shrdlu@unlimitedmail.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox