Bug 327552 - kvkbd only works as an English-layout keyboard
Summary: kvkbd only works as an English-layout keyboard
Status: RESOLVED DUPLICATE of bug 174110
Alias: None
Product: kvkbd
Classification: Miscellaneous
Component: general (show other bugs)
Version: 0.6
Platform: Kubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Guillaume Martres
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-13 11:06 UTC by thisguy642
Modified: 2013-11-20 14:01 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description thisguy642 2013-11-13 11:06:51 UTC
kvkbd's virtual keys enter characters that match an English keyboard layout, disregarding the setting for the physical keyboard layout. System language also doesn't make a difference. Even more oddly, the layout is visually correct at the first run, but changes to an English layout after pressing a virtual key for the first time, regardless of whether the key press had any effect.

Reproducible: Always

Steps to Reproduce:
1. Set keyboard layout to something other than English.
2. Open kvkbd (make sure it's not running first).
3. Press any virtual key that's not a control key.
Actual Results:  
The kvkbd layout will visually change to English, and the virtual key press and all further virtual key presses will have the same effect they would on a keyboard with an English layout.

Expected Results:  
kvkbd should always behave like a keyboard with the layout the user has selected for use with the physical keyboard, so the user can easily enter special characters for the selected language.

German keyboard layout, system language usually US English, temporarily changed to German and then back for testing purposes. Kubuntu 13.10 with KDE 4.11.2.
Comment 1 Christoph Feck 2013-11-14 03:16:02 UTC
See also bug 174110, which might be a duplicate.
Comment 2 thisguy642 2013-11-20 14:01:04 UTC
Mostly yes - the setxkbmap workaround does it for me.
Comment 3 thisguy642 2013-11-20 14:01:26 UTC

*** This bug has been marked as a duplicate of bug 174110 ***