Keybindings (e.g. Ctrl+A) are being mapped to the US keyboard layout even if you're using another layout

Works for me (Windows 10, idk if it matters)
Make sure the text field is actually selected.

It matters.

Just to be sure, do you rather mean CTRL+A in the title?
Otherwise I can also confirm that using CTRL+A to select text isn't working, and I have to use CTRL+Q instead.
The F3+A and F3+Q shorcuts are also affected and thefore swapped out.

It seems to be caused by the use of an azerty keyboard in my case

Using CTRL+A to select the text works for me. - Windows 10

Confirmed even more by digging a bit :
This is caused by the method glfwSetKeyCallback who returns a key code assuming a US keyboard layout.
To fix it, instead of directly testing the key code returned by glfwSetKeyCallback with the GLFW_KEY constants, it has to be converted to his printable character with the glfwGetKeyName method.

Still present in 18w01a

Still present in 18w07c

Still present in 18w10d

Confirm for 18w16a

Confirm for 18w22a

Confirm for 1.13-pre1
It's very very worrying for the French players considering the imminent arrival of the 1.13... :/

Confirmed present in 1.13-pre2

Still in 1.13-pre4

Still present in 1.13-pre5

Still in 1.13-pre6

Still in 1.13-pre7

Still in 1.13-pre9... :flag_on:

Still in 1.13-pre10 😞

Is the assigned manager really fixing the bug? Because, this is a very painful bug for anyone with an AZERTY keyboard...
Especially that the 1.13 must release tomorrow! It is crazy that nobody takes seriously this bug!

Could we just have news as for the correction of the latter please? Thanks 🙂

This also affects the port of the control settings from 1.12.2 to 1.13-pre10

Still in 1.13 Release guys ....

Broken keybindings in the official release. Ouch.

I know right, especially knowing that bug was reported early

@Bertrand @Valentin @Jonathan

In my opinion, having this bug still around is still better than fixing it BUT not fixing at the same time MC-127862. For a short explanation of the issue : "Alt Gr" can cause "Ctrl" to be virtually locked. Meaning that when it's the case, typing the letter "A" (quite common letter) would delete everything (which already happens on QWERTY / QWERTZ keyboards that also have an Alt Gr key, such as german ones).

Of course, that bug isn't problematic only with "A" key, but it would make it worse.

@Azkunki Okay, but why did it work very well before and without problems? Plus, there, we are talking about keyboard shortcuts that are often used in game!

@ZeNico

I said "having this bug still around is still better than fixing it BUT not fixing at the same time MC-127862". That means "the best would be to fix them BOTH as soon as possible", not "it's better to not fix these bugs at all".

"Plus, there, we are talking about keyboard shortcuts that are often used in game!"

Except that it does not have irreversible consequences, it's annoying at most. Whereas MC-127862 is a bug that is far worse since there you can lose everything you were writing (something you might not remember well, and the bug stays active as long as you don't happen to press "Ctrl". And in top of that, only the left one works if I'm not mistaken. So if you don't know how to stop the bug, you're in for a lot of trouble, maybe up to restarting your game. Because EVERY time you will use arrow or deletion keys, it will act for the whole word). And if you fix the bug with shortcuts combinations using A (or Q / Z / W / M), as I already said, it will just make MC-127862 much worse. Because then, every single time you will type an "A" while the bug is active will instantaneously delete everything you were writing (I mean, this time you won't even have the time to realize you should stop pressing backspace (most likely) and maybe save some text from deletion, and it will occur insanely often since the letter "A" is a pretty common one. Maybe even more (a little more) in French than in English ("on vA pAs se mentir, cette combinAison de bugs est pArticulièrement chiAnte").

In other word, to never be affected by this bug even when it's active, you would manage to always write exactly what you wanted to write (so never in need to modify anything) while doing a lipogram in "A"... Good luck :/ (a lipogram in "Q" is much, much, much easier, you can't disagree on that)

NB : A "lipogram" is a text in which you purposely omit one of several letters. Doing so with the letter "E" of course is the hardest, but it's still quite a challenge as well with the letter "A". While the letter "Q" is quite pretty easy to avoid.

Still in 18w30a

Still in 18w30b

Still in 18w31a

Still in 18w32a...**

FIX PLEASE !!!!!!!!

Still in 18w33a...

Still in 1.13.1-pre1

Still in 1.13.1 RELEASE

FIX PLEASE

Still in 1.13.2-pre1...

Fix it please ! :'(

Still in 1.13.2-pre2

Still in 18w43a 😞

Still in 18w43b

Still in18w44a :angry:

Still in 18w46a
Another developer can do it?

Still in 18w47a

Still in 18w50a

Still in 19w04a

Still in 19w05a...

Still in 19w06A

Yeah... Is the assigned manager can fix the bug please? Because, this is a very painful bug for anyone with an AZERTY keyboard...

Still in 19w07a 😞

Still in 19w08a

Still in 19w08a

Still in 19w09a

Still in 19w11a

Still in 19w11b

Still in 19w12a

Still in 19w12b

Still in 19w13a

This is the third most voted bug and has been reported over two years ago and is still not fixed. It is really annoying. It seems that voting for a bug to be fixed doesn't matter at all in prioritizing the work ?

For other players: a decent workaround is to put your cursor at the end which is the case when you rename something in the anvil. Then press Shift+Begin (the arrow above end key), it will behave as a ctrl+a for a single line of text. Still better than nothing.

@val59000mc you can also use crtl+q instead, it works exactly like crtl+a should work

@stebo02 @Steb B
You might understand his opinion as for a game that is 10y old, and own by Microsoft, a simple ctrl+a should work, as we are used to do it on our azerty keyboard, ofc he knows that he can ctrl+q as he doesn't have any other choice so far ^^'

@Stef B

Except that if you start doing that in Minecraft, you'll get used to doing that out of Minecraft as well :/ Which then makes it annoying anywhere, not only in Minecraft. And to make it even worse, Ctrl+Q is a shortcut that can sometimes act like Alt+F4 (and you won't always get a warning saying you have unsaved changes. For instance, if I do it like that, when writing in my browser, it won't always warn me about anything, depending on what site I'm writing (although it doesn't seem to work anywhere anyway right now, for me. Which is weird, especially that I'm pretty sure it should have worked on Firefox and windows explorer (also tried on Notepad++, but I may have unbound that there, which could be an explanation). Maybe I've got some bug that makes that useless yet potentially annoying shortcut not work anymore for me ?)

@val59000mc

It's not at all the third most voted bug (it's the 287th), and it has been reported around 1.5 year ago. Which doesn't change that it's surprising such a bug is still around after so long of course, it's like they don't care (which is why I'm not active anymore here, and as well why I have much higher hopes in "you-know-what-game-I'm-talking-about" (or maybe not, but I obviously can't say here clearly what I'm talking about). At least it's quite promising on every aspect so far (and with some luck, maybe it will make Mojang wake up)).

This is a bug tracker, not a forum. This bug will be fixed when it is fixed, complaining here won't change that. Please comment here only if you have something new to add to the ticket. Off-topic comments will be removed.

If you need to discuss this issue anyway, feel free to open a thread on /r/Mojira.

 Still in 19w14a

Still in 19w14a

Still in 1.14 Pre-Release 1

Can confirm in 1.14 Pre-Release 1

Still in 1.14 Pre-Release 2

Still in 1.14 Pre-Release 4.
1.14 will be released on Tuesday and this bug is still not fixed since snapshot 1.13 !
When will you solve it? It's really annoying for azerty keyboard users and even more so if we also play with versions below 1.13, we have to constantly think if we need to do Ctrl + A or Ctrl + Q

Still in 1.14 Pre-Release 5 😞

I also have this issue. It didn't exist in previous versions. I think before 1.13

Copy and Paste are the most problematic ones.

OS: Kubuntu 18.04 (64 bit)

Still in the release (1.14) WTF

Please fix this ... (still in 1.14)

Still in 1.14.1 Release

Still in 1.14.2 Pre-Release 1

Still in 1.14.2 Pre-Release 2

If you ever fix this bug, please add customization support. Actually some of these keys are bend to specific letters for their easy access in US keyboard, not for their significance. One example is F3 + N which is switching gamemode, very useful for ops or on a creative map. With this key combination, you can currently reach both keys with one hand on any keyboard layout. If this bug is fixed, I won't be able to use this key without loosing my mouse control anymore, as F3 and N are very far away from each others on my layouts and will require to use both hands.

Still in 1.14.2 Release

Still in 1.14.3 Pre-Release 1 & 1.14.3 Pre-Release 2

Still in 1.14.3 Release

Still in 1.14.4 Release

Still in snapshot 19w35a

Still in 19w36a

I can only agree with @ZeNico13 (and, I mean, it's the bug update. If it's not a priority now, when will it be ?). However, and although it does not concern me anymore thanks to my new computer (but for the sake of those that are still affected), I'd like to remind you that there's also MC-127862, which will become worse if and when MC-121278 will be fixed (if it's the only one of the pair to be fixed).

In short, it would become worse because it would mean that Ctrl+A wouldn't require to actually (physically) do Ctrl+Q on the keyboard, hence with MC-127862, when writing something, it would become far, far more common to lose everything, since "A" is obviously much more common than "Q" (MC-12762 is basically the Ctrl key being virtually locked, so keyboard shortcuts can interfere, in a variety of ways, while doing something else).

Same. It's been affecting me for so long and I still trip over it all the time. This really needs to be fixed, it's a source of chronic frustration for the entire french playerbase.

You know you can change the Minecraft controls? I set my drop key from q to ` as I kept dropping  my items when walking.

@anonymous : No. We're talking about a keyboard shortcut that can more or less work anywhere, not only on Minecraft. And for this reason, even if it was possible to change the keyboard shortcut, it would be a bad idea since you would get used to your custom shortcut on Minecraft and keep doing it outside of Minecraft as well, where it would still be Ctrl+A. If would ever get used to your custom shortcut on Minecraft (which wouldn't prevent using the wrong shortcut more or less often, even out of Minecraft, most likely).

Also, even if it was possible to change the shortcut AND that it was a thing only on Minecraft, it could still be an issue, since as you said yourself, not every key fits the way you play.

What are you doing Mojang ? It's frustrating to have some changed shortcuts (on azerty keyboard we need to use qwerty shortcut wtf ??) on a single game and this from several large versions ... Please fix this, this is really important ...

I think it's more complex than just fixing the key code. For instance, a usefull shortcut for server admins is the ability to change game mode with F3 + N. On qwerty keyboard, you can hit the 2 keys with one hand. On another keyboad (bépo), you need 2 hands. This means a simple fix could break the current accessibility being offered. So a proper fix means we would need a way of customizing those controls.

Still in 20w08a

Still in 20w18a... 

This is still a thing, over 3 years later, and apparently, has been resolved by LWJGL (cf: https://bugs.mojang.com/browse/MC-121278?focusedCommentId=706194&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-706194)

all that's needed now is for someone to notice this, change a couple lines of code, and that's it

Can some please check if this is fixed in 22w16b as this snapshot comes with the latest LWJGL version.

@@unknown I checked in 22w16b and unfortunatly, the bug is still present.

Can confirm in 1.19.3.

Can confirm in 1.19.4

Can confirm: 23w12a

Can confirm in 1.20-pre1 under Linux using a french BÉPO keyword

Can confirm in 23w44a.

Confirmed in 24w12a

Can confirm in 24w14a.

Can confirm in 1.20.5-rc2.

Can confirm in 1.20.6 and 24w20a