Hello @VincentProuchet, you're come across a downstream fork of wine used in the Proton project. This area of code is unchanged from upstream wine, and needs to be reported and resolved in upstream wine.
https://bugs.winehq.org/show_bug.cgi?id=48650 looks relevant.
What happens
keys like ' é ' on the ' 2 ' or ' à ' on the ' 0 ' are not recognized and not transferred to the application, rendering theses keys unusable.
the original sin
As seen there : (https://github.com/ValveSoftware/wine/blame/8b5ff79bcef26007edd5f1f517ba823f56c01bf3/dlls/user32/tests/input.c#L5089)
The unit test is skipped when keyboard is not US layout.
what could be done ?
adding test for other every existing layout should be a start.
starting to debug the driver is the step that comes next
why wasn't this done already ?
If you are on a ubuntu please go to your keyboard setting-> add a new source -> then click on the "other " option of the list until it doesn't propose it anymore.
The list you should see is how many keyboard layout that exist.
Debugging everything wasn't deemed necessary mainly because the original programmer was using a US layout keyboard and didn't have time for solving all of its unrecognized keys, he did what was within its time frame.
Should this be done for the next release
It should be done
but can't be entirely done for next release.
Solution to tackle this ?
two list should be created one for the tested layout and one for the skipped
test should be written to test every layout on the tested layout list and skip every other, just in case a feral layout appear out of nowhere.
and the list should be tackled layout by layout, this approach should give us a good reading of what already work
and what doesn't.
Why not testing all layout and just acknowledge what need fixing ?
these are unit tests.
if unit test fails, compilation isn't done.
no compilation, no release.
we will have to tackle the giant bit by bit.
longer but safer and gives room for progress without pressure.
why bother fixing it ? It worked until now
well people found work around, switching from a layout to another before launching;
re-configuring key,
A considerable quantities of people is switching to Linux this year, a lot of them came in august to test, a lots of them returned to windows after seeing THAT specific problem.
for Europeans we have 8 month, if Europeans layouts are solved, all those people that can't just have to change computer every 2 years, will stick to Linux.
Just to make sure I'm understood
the test should be written to test every layout in a list regardless of the connected keyboard layout. the tool to switch keyboard layout already exist for Linux, it already simulate the keyboard the user wants
Sorry, this is really too long.