-
Notifications
You must be signed in to change notification settings - Fork 2
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.
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
Is it possible to fix a vanilla bug?(linux) #4
Comments
I'd seen a similar report by an Mac user. Not very sure how I could do to fix it, but I'll keep an eye on it. |
Try this fix mod. I have no device running linux/macos, so I don't know if it works. You might test it by yourself. |
i will try |
instead of crashing i cant put some keys (like *^ù$) |
Try entering a save and reset the key. |
I can't keybind some keys like with the english layout
wdym |
What's exactly displayed when those keys were typed? Was a number displayed?
Go Singleplayer, create and enter a world, and set the keybinding in the PauseScreen's ControlsScreen. |
1 : he say : NONE 2 : And when i try in world i got NONE edit : only for unsupported key like *$^ù |
Oops, it seems I have to modify a few extra lines of code. I can't do it now, but I'll send a reply when it's done. |
So you released https://www.curseforge.com/minecraft/mc-mods/safekeystring so i will try it later |
Nothing changed on code since my last reply. Was just releasing it. I'm sorry that SafeKeyString may be not able to solve your problem currently :(( |
Have you ever tried lwjgl3ify? Since it's a problem with older lwjgl. |
LWJGL3ify is not compatible with some mods , so not tried |
description :
If i use AZERTY FRENCH keyboard on linux.
I have crash if i try to keybind $ or something to any key, and if i rego to control setting i get instant crash . So i need to delete options.txt
how to reproduce the issue :
1 : switch to linux/archlinux system
2 : switch to azerty french keyboard
3 : start the game
4 : go to control settings
4 : try to keybind some key like ù,$,*
logs :
latest.log
workaround :
Use a QWERTY ENGLISH keyboard to fix the crash
The text was updated successfully, but these errors were encountered: