[UDEV]Wrong keys during keyboard remapping

[ghost]

First and foremost consider this:
Only RetroArch bugs should be filed here. Not core bugs or game bugs
This is not a forum or a help section, this is strictly developer oriented
Description
Wrong keys are mapped when remapping keyboard keys using udev driver.

Expected behavior
[What you expected to happen]

Actual behavior
The actual keys should be remapped as whats being pressed

Steps to reproduce the bug
use udev driver (im assuming that current user is already a member of input group)
run retroarch
goto "input", select any of the "binds" menu
try to remap new keys from the keyboard.... most of the keys should display wrong when remapped( for example, assigned a spacebar to some key will will set K: d instead of K:space)
Bisect Results
[Try to bisect and tell us when this started happening]

Version/Commit
You can find this information under Information/System Information

RetroArch: 1.7.3
Environment information
OS: linux (arch)
Compiler: 7.x.x+

[orbea]

I'd like to see this fixed too. Its especially problematic when trying to use the keyboard + mouse in fps games.

[Raven-Singularity]

Not sure if this has anything to do with udev. I'm on Windows 10, key inputs are often messed up. Not sure how to assign any hotkeys in 2022. I press F11 repeatedly and nothing is input at all. I press F and it shows Scroll Lock. How is anyone supposed to use this emulator?

Why is this marked as "bug: minor", not being able to assign hotkeys is extremely major. Or is it supposedly just the labels that are wrong, but the hotkeys will still work normally?

Because that's not how it is for me. When I choose "F" for fullscreen (because "F11" can't be assigned), it says "Scroll Lock" instead of "F". So I go to my game and hit "F" but it doesn't do anything. I hit "Scroll Lock" and it goes into fullscreen.

This may be different than the udev bug, or the same. But this is definitely a major bug, as it prevents even basic use of RetroArch.

Edit:
I found the input driver section. It says it was using "sdl" as the input driver. I changed that to "raw" and now my keyboard input works. I can input "F11", and other keys show up correclty. So at least two input drivers are broken.

It doesn't make sense to include broken input drivers.

For other people that experience this issue:

1. Open the GUI menu, or the Desktop Menu interface
2. Go to: Settings > Drivers > Input
3. Switch to an input driver that is different than the broken one.
   The input driver "raw" works for me on Windows 10.
4. Restart RetroArch and try inputting hotkeys again.

[zoltanvb]

Udev input driver should work correctly nowadays, as I checked with the keyboard tester (#16390), however if there is a problem with Windows+SDL combination, this better remain open.

[sonninnos]

Yes indeed those Windows drivers have been fixed ages ago, so closing time.