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

Unrecognized key (fn) #3793

Closed
SDLBugzilla opened this issue Feb 11, 2021 · 2 comments
Closed

Unrecognized key (fn) #3793

SDLBugzilla opened this issue Feb 11, 2021 · 2 comments

Comments

@SDLBugzilla
Copy link
Collaborator

This bug report was migrated from our old Bugzilla tracker.

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

Comments on the original bug report:

On 2020-08-13 00:49:34 +0000, oscar.neln@gmail.com wrote:

I (very unexpectedly) got the message
"The key you just pressed is not recognized by SDL. To help get this fixed, please report this to the SDL forums/mailing list https://discourse.libsdl.org/ X11 KeyCode 151 (143), X11 KeySym
0x1008FF2B (XF86WakeUp)."
When I pressed my FN-key on my Thinkpad T480 laptop. I was told to report it, so I did.
No crashes or odd behaviour except for the message to stdout happens.

Feel free to point me in the right direction if this is reported in the wrong place.

PS. I've switched control and FN in BIOS, but I dont think this should matter.

kind regards
@InfoTeddy
Copy link
Contributor

Duplicate of #3113.

@slouken slouken removed the bug label May 11, 2022
Daaaav added a commit to Daaaav/SDL that referenced this issue Sep 3, 2022
@Daaaav
Silence Fn/XF86WakeUp key messages on some Lenovo keyboards
314ce13 
On certain Lenovo computers, pressing the Fn key on an SDL window will
print warnings from SDL in the console about an unrecognized key (X11
KeyCode 151 (143), X11 KeySym 0x1008FF2B (XF86WakeUp)). This commit
silences this warning for this specific key symbol.

Fixes libsdl-org#3113
Fixes libsdl-org#3793
@Daaaav Daaaav mentioned this issue Sep 4, 2022
Closed
@slouken
Copy link
Collaborator

slouken commented Nov 7, 2023

This is fixed in the latest SDL release.

@slouken slouken closed this as completed Nov 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@slouken @InfoTeddy @SDLBugzilla