Bug 393907 - Problems with keyboard layout using wayland
Summary: Problems with keyboard layout using wayland
Status: RESOLVED DUPLICATE of bug 411729
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_keyboard_layout (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
: 427793 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-05-06 12:37 UTC by Freek de Kruijf
Modified: 2020-11-23 17:02 UTC (History)
8 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Freek de Kruijf 2018-05-06 12:37:08 UTC
I am using Wayland Plasma session, first without defining a keyboard layout, because I assumed the layout would be copied from the chosen layout during installation. That layout is: US with dead keys (US int.). However I could not enter an accent using the that key followed by pressing the space bar. Instead the popup appears to enter a command like when using <Alt>+<f2>. It is the same for other dead key characters. After that I started systemsettings5 and found that no keyboard layout was active, so I configured US+int. (US with dead keys). I had the impression - can't remember for sure - i could enter character using dead keys. However after a reboot and starting a Wayland Plasma session again, the wrong behavior was back. Using systemsettings5 to inspect the layout of the keyboard, the configuration with US with dead keys was still there. Adding a normal US keyboard and getting the ability to switch between these layouts, I found that US with dead keys did not what I expected. In the test I used konsole to enter text.
Comment 1 Alexander Mentyu 2018-07-01 05:06:26 UTC
Cannot reproduce, after reboot dead keys are entering normally in Konsole. I use Right Alt key as a modifier for dead keys input though

Plasma: 5.13.1
Apps: 18.04.2
Frameworks: 5.47.0
Qt: 5.11.1
Kernel: 4.18.0-1-MANJARO
OS: Netrunner Rolling
Video: Intel 4400
Driver: xf86-video-intel 1:2.99.917+831+ge7bfc906-1
Mesa 3D: 18.1.2
Screen: 1600x900
Xorg: 1.20
Wayland: 1.15.0-1
Wayland Protocols: 1.14-1
Comment 2 Freek de Kruijf 2020-10-14 13:41:22 UTC
Tried again with the newest version of openSUSE Tumbleweed and found the same issue. Keyboard setting is US int. with dead keys. But when I press key ' followed by a space, character ' does not appear, simply a space. It is the same when I press key ' followed by key e, character é should appear, however a simple e appears.
Comment 3 jem 2020-10-16 06:38:25 UTC
I can confirm that this is a real issue, and it is related to Wayland. Every app works normally on Plasma/X11. However, the problem seems to be limited to Plasma apps, like Konsole, Dolphin and KCharSelect. Dead keys are working in Firefox (which on my machine is a Wayland app), Chromium (XWayland), Emacs (XWayland), etc. I am not using a compose key. I have a Finnish keyboard; my only keyboard configuration is /etc/vconsole.conf which contains the setting KEYMAP=fi
Comment 4 jem 2020-10-16 11:41:09 UTC
*** Bug 427793 has been marked as a duplicate of this bug. ***
Comment 5 Roman Zimmermann 2020-10-29 12:31:44 UTC
This sounds like the same issue as #411729 which was posted later but has more information.
Comment 6 Francisco Cribari 2020-10-31 21:32:08 UTC
I am also affected by this. Arch Linux, KDE, Wayland, Brazilian keyboard.
Comment 7 Fabio Forni 2020-11-01 16:31:33 UTC
I'm affected by this too, with a UK-extended layout. The accent mark is not working.

The issue seems to only be present in Qt applications.
Comment 8 Patrick Silva 2020-11-17 11:03:22 UTC

*** This bug has been marked as a duplicate of bug 426621 ***
Comment 9 Nate Graham 2020-11-23 17:02:30 UTC

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