We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 3216 - Custom key bindings completely disables keyboard input
Summary: Custom key bindings completely disables keyboard input
Status: RESOLVED FIXED
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: 2.0.3
Hardware: x86_64 Linux
: P2 critical
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-28 13:53 UTC by Alister Sanders
Modified: 2015-12-29 07:21 UTC (History)
1 user (show)

See Also:

Attachments
Full error log (12.05 KB, text/plain)
2015-12-28 13:53 UTC, Alister Sanders 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alister Sanders 2015-12-28 13:53:20 UTC 
Created attachment 2349 [details]
Full error log

When running an SDL2-based application whilst having custom keyboard bindings through xmodmap, this causes all of the keys on the keyboard to become unrecognized by SDL. Basically, if a program using SDL2 is run through a terminal, it spurts out one of these messages for each key on the keyboard:

    code = 1, sym = 0xFF1b, (Escape), scancode = 41 (Escape)

And makes keyboard input for that program impossible.

Attached is the full error log
Comment 1 Alister Sanders 2015-12-29 07:21:30 UTC 
This problem has been resolved with the new 2.0.4 release