Bug 273043 - wrong processing of uppercase key events
Summary: wrong processing of uppercase key events
Status: CONFIRMED
Alias: None
Product: krfb
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: George Goldberg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-11 16:28 UTC by Amichai Rothman
Modified: 2024-07-28 10:56 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Amichai Rothman 2011-05-11 16:28:57 UTC
Version:           unspecified (using KDE 4.6.2) 
OS:                Linux

On Kubuntu Natty (with KDE 4.6.3 - the bug report dropdown only goes as far as 4.6.2 so that's what I selected there), I send 4 low-level key events from the client VNC viewer: 'A' pressed, 'A' released, 'a' pressed, 'a' released. The KRFB host is idle with a Konsole window open, and what is written at the prompt is 'aa'. If I shut down KRFB and start x11vnc instead, and repeat the exact same sequence on the client, the host now displays 'Aa' as it should. Using TightVNC on Windows in the past this worked properly as well, so I'm pretty sure the problem is with KRFB (common sense and this experiment point to the same).

Originally I had a problem dealing with an alternate input language (where I simply couldn't get normal English characters to print), however I believe it is the same bug as the much simpler case reproduced here.

Reproducible: Always

Steps to Reproduce:
Connect to the KRDC host, put the input focus on an application that expects text input (e.g. Konsole at the prompt), and send the key sequence 'Aa' (more specifically, using RFB key events for 'A' pressed, 'A' released, 'a' pressed and 'a' released).

Actual Results:  
The host shows the key sequence 'aa'.

Expected Results:  
The host should show the key sequence 'Aa'.
Comment 1 George Kiagiadakis 2011-05-11 16:37:09 UTC
I have seen this problem as well and I am also quite convinced that it's krfb. A small correction though, it is not always reproducible (always using krfb as the server and krdc as the client).