Bug 1227612 - keyboard layout wrong for various applications
Summary: keyboard layout wrong for various applications
Status: RESOLVED DUPLICATE of bug 1219505
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Leap 15.6
Hardware: Other Other
: P3 - Medium : Normal (vote)
Target Milestone: ---
Assignee: Gfx Bugs
QA Contact: Gfx Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-10 09:10 UTC by Harald Mueller-Ney
Modified: 2024-07-10 09:51 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Log of text session using xterm as example not working (912 bytes, text/plain)
2024-07-10 09:10 UTC, Harald Mueller-Ney
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Mueller-Ney 2024-07-10 09:10:42 UTC
Created attachment 875987 [details]
Log of text session using  xterm as example not working

Fresh install of openSUSE Leap 15.6 - Gnome, Wayland

System is set to German  and German keyboard layout.
Gnome/GTK application seem to use correctly German keyboard layout. Other applications like e.g. Chrome, Thunderbird using  US keyboard layout.

Using Yast -> Hardware -> Keyboard (or in German Tastatur) the keyboard setting is German.  

Using the textbox, it is using US (QWERTY) not German (QWERTZ) layout. Switching back and forth via any other layout the textbox is using German layout (QWERTZ). 

Using now already running Chrome, it is using now German Layout. No restart needed, which hints for an issue in Wayland/X. Unfortunately the setting is not surviving a reboot nor an logout/login.

xterm as well suffers from the issue. I will attach a log of my changes. 

It seems we do not set the correct keymap for X/Wayland but just for GTK.

The issue seems to be present for more users and seem to hit as well upgrades - See:
https://forums.opensuse.org/t/wrong-keyboard-layout-on-most-applications-after-fresh-install/175773
Comment 1 Stefan Dirsch 2024-07-10 09:51:15 UTC
Another dup

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