Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Keyboard layout not detected because of custom 'xmodmap' mappings. #1755

Closed
SDLBugzilla opened this issue Feb 10, 2021 · 1 comment
Closed

Keyboard layout not detected because of custom 'xmodmap' mappings. #1755

SDLBugzilla opened this issue Feb 10, 2021 · 1 comment
Labels
abandoned Bug has been abandoned for various reasons

Comments

@SDLBugzilla
Copy link
Collaborator

This bug report was migrated from our old Bugzilla tracker.

Reported in version: 2.0.2
Reported for operating system, platform: Linux, x86_64

Comments on the original bug report:

On 2015-02-02 14:03:57 +0000, wrote:

I have a slightly customized keyboard layout to make the tab key and some other weird placed keys on my laptop dead:

xmodmap -e "keycode 112 = Left"
xmodmap -e "keycode 117 = Right"

SDL2.0.2 completely fails to detect the keyboard layout and emits the following message: "Keyboard layout unknown, please send the following to the SDL mailing list"

The keyboard is fully unusable, not a single key is properly recognized.

My current workaround is to make a private build of SDL to force the generic X11 layout in X11_InitKeyboard()

On 2016-10-07 23:40:16 +0000, Sam Lantinga wrote:

Can you provide a patch that does that? That seems like reasonable default behavior if we can't detect the keyboard layout.
@SDLBugzilla SDLBugzilla added bug waiting Waiting on user response labels Feb 10, 2021
@slouken slouken removed the bug label May 11, 2022
@slouken slouken added abandoned Bug has been abandoned for various reasons and removed waiting Waiting on user response labels Nov 4, 2023
@slouken
Copy link
Collaborator

slouken commented Nov 4, 2023

SDL 2.0 is now in maintenance mode, and all inactive issues are being closed. If this issue is impacting you, please feel free to reopen it with additional information.

@slouken slouken closed this as not planned Won't fix, can't repro, duplicate, stale Nov 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
abandoned Bug has been abandoned for various reasons
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@slouken @SDLBugzilla