https://bugs.kde.org/show_bug.cgi?id=514241
Bug ID: 514241
Summary: pipe(|) char can not be input by jp keyboard, because
the key between hat(^) and BS does not work.
Classification: Applications
Product: krdc
Version First 25.12.0
Reported In:
Platform: Neon
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: RDP
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
When jp keyboard is used, the key between hat(^) and BS is not work
The key is the only key that can input the pipe character.
(On jp keyboard, to input pipe(|) char, press the key with the Shift key.)
STEPS TO REPRODUCE
1. Set keyboard layout to "Japanese (ja)" in KRDC Host Setting - General tab
2. Connect to Windows 11 using RDP
OBSERVED RESULT
The key between hat(^) and BS does not work.
As a result, pipe characters (typed using the Shift key combination) cannot be
input.
Of course, backslash char (which is assigned as the yen symbol in Japan) cannot
be entered, but there is an alternative key to input the backslash between
slash(/) and right shift.
EXPECTED RESULT
The signal from the key between hat(^) and BS is correctly sent to the host.
SOFTWARE/OS VERSIONS
KRDC: 25.12.0
KDE Frameworks: 6.21.0
Qt: 6.10.1
KDE neon User Edition (Wayland)
Build ABI: x86_64-little_endian-lp64
Kernel: linux 6.14.0-37-generic
RDP Host : Windows 11 Pro
ADDITIONAL INFORMATION
The Japanese keyboard layout is described in detail on the English Wikipedia.
https://en.wikipedia.org/wiki/Keyboard_layout#Japanese
The keycode of the not working key between hat(^) and BS is 220 (0xDC) on
Javascript "onkeydown" event.
The keycode of the working key between slash(/) and right shift is 226 (0xE2)
on Javascript "onkeydown" event.
The key between hat(^) and BS does not work in Remmina 1.4.41 (git 3792a0bed)
(on neon From Flathub).
The key between hat(^) and BS worked correctly in Remmina 1.4.39 (git n/a) (on
Kubuntu 25.04).
The key between hat(^) and BS does not work in KRDC 25.03.90 (on Kubuntu
25.04).
--
You are receiving this mail because:
You are watching all bug changes.
