Skip to content
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

Unable to type letters with accents in any game that runs with Proton #3791

Closed
KairanD opened this issue Apr 23, 2020 · 9 comments
Closed

Unable to type letters with accents in any game that runs with Proton #3791

KairanD opened this issue Apr 23, 2020 · 9 comments

Comments

@KairanD
Copy link

KairanD commented Apr 23, 2020

#Games affected:
Any game that runs with Proton and requires typing. For example, The Elder Scrolls Online (306130) and Super Animal Royale (843380). The problem doesn't happen in native games, like CS:GO. So, it's a Proton/Wine issue.

#Computer configuration:
Processor: Core i5 4670K @ 3.8GHz.
Motherboard: Gigabyte GA-Z87-D3HP-CF @ BIOS F6.
Memory: 16GB (4 x 4GB) Corsair Vengeance @ 1600MHz.
VGA: EVGA GeForce GTX 1070Ti 8GB SC Black Edition.
OS: Ubuntu 19.10 Eoan Ermine (x64).
VGA Driver: NVidia 440.59.
Proton Version: 5.0-6.

#Problem description:
I'm able to use accents normally in everything, including Steam chat: á, é, í, ó, ú, ã, ñ.

When I open any game that runs with Proton, accents stop working instantly in Steam chat (I can only type the letter, without accent, like a, e, n) and appear like this in any in-game chat (The Elder Scrolls Online and Super Animal Royale, for example): ´a, ´e, ~a. So, all the keys are working, but the language is not being correctly recognized.

The result: when I'm playing, I can't chat with friends in Portuguese or Spanish without absurd grammatical errors. I recently stopped using Windows 10, thanks to the wonderful work you guys have done on Proton. My games run perfectly and this is the only problem, but it's annoying. I tried a lot of solution tips found across the Internet and nothing worked. Seems like this issue has been around for a while.

My system language is Brazilian Portuguese. My keyboard has the Brazilian Portuguese ABNT2 standard QWERTY layout and is working perfectly fine.

@kisak-valve
Copy link
Member

Hello @KairanD, this sounds similar to #3641. Maybe try this workaround: #3528 (comment)

@KairanD
Copy link
Author

KairanD commented Apr 23, 2020

Hey, @kisak-valve , thank you very much for the fast response! I tried the workaround suggested, but, unfortunately, it didn't solve the problem. It had no effect. :(

Captura de tela de 2020-04-23 10-10-55

@KairanD
Copy link
Author

KairanD commented Apr 25, 2020

Just to add more information, the same problem happens with my notebook (Asus K46CB):

Processor: Core i7 3537U @ 3.1 GHz
Memory: 8GB (2 x 4GB) @ 1600MHz.
VGA: GT 740M 2GB DDR3 128 bit.
OS: Ubuntu 18.04.4 LTS (x64) and Ubuntu 19.10 Eoan Ermine (x64). I tested both.
VGA Driver: NVidia 390.129.
Proton Version: 5.0-6.

I also run softwares like AutoCAD 2008 (x86) and Microsoft Office 2013 (x86) through PlayOnLinux (and so Wine) and this problem doesn't happen.

My problem can be related to #3641 and #3528 , but I'm not using the Super or Alt keys to type, since my keyboard already has accent keys natively. It can also be related to #3783 , but all my keys are working. I can type accents in game, it just doesn't detects the language correctly: for example, if I want to type "não" using the in-game chat, then the result is "n~ao". If I type in the Steam chat when a Proton game is open, the accent doesn't even show up. The strange fact is that the specific "ç" key works in both situations, so my keyboard layout is being corretly detected.

This problem doesn't happen with Windows 10. So, since Proton runs the Windows version through Wine, the issue is definately related to a configuration in Proton.

I'm kinda new in the Linux world, so I'm learning as I use it. My knowledge in programming is also very limited. I have been studying to learn a bit how Wine works and I have been exploring the files to see if I find a solution. If I find anything, I'll post here. I found some people online with the same problem, but not solutions.

@astroty
Copy link

astroty commented Jun 20, 2020

Hello @KairanD, this sounds similar to #3641. Maybe try this workaround: #3528 (comment)

I had the same issue and doing the workaround mentioned on this reply solved my issue

@KairanD
Copy link
Author

KairanD commented Jul 17, 2020

@astroty Are you also using Ubuntu 20.04 LTS and Brazilian Portuguese language? I tried again, after reinstalling my OS, and it didn't work again. I have already accepted that I can't solve this.

@leao666
Copy link

leao666 commented Aug 8, 2020

I use Debian 11 with Cinnamon PT-BR. Steam installed from repo in Brazilian Portuguese. Proton 5.0.9

My system:
Dell Inspiron 14 7472
Core i7 8550U
Intel HD 620
NVidia MX150
16 GB Ram
ABNT2 Keyboard

I solved this problem in two games as follows:

  • in the initialization options I put PROTON_DUMP_DEBUG_COMMANDS=1 %command% (in my game PROTON_NO_ESYNC=1 PROTON_DUMP_DEBUG_COMMANDS=1 %command%)
  • run game and then close it
  • you will have a directory like /tmp/proton_usuario$
  • in this directory, run ./run regedit
  • go to [HKCU\Software\Wine]
  • create key X11 Driver
  • create this value UseXIM="y" (without "")
  • the result will be as in the image below

Captura de tela de 2020-08-07 23-16-01

  • you can remove the option PROTON_DUMP_DEBUG_COMMANDS=1 %command% from your game
  • in the next reboot of your OS, this directory will disappear

Source: #3528 (comment)

@KairanD
Copy link
Author

KairanD commented Oct 25, 2020

@leao666 Thanks for the detailed info. Unfortunately, that's what I did. It's not working in Ubuntu 20.04.1 LTS or 20.10. It's an extremely annoying problem... And I have already tried everything.

This was referenced Oct 25, 2020
@KairanD
Copy link
Author

KairanD commented Oct 27, 2020

Now I've already tried (with the solution above):
1. Different versions of Proton (4.11-13, 5.0-9 and 5.13-1);
2. Disabling all the GNOME Extensions;
3. Starting with LC_ALL=pt_BR.UTF-8 LANG=pt_BR.UTF-8 %command%;
4. A combination of everything above.

Nothing worked:
image

@KairanD
Copy link
Author

KairanD commented Oct 27, 2020

GOT IT WORKING! With a fresh install of Ubuntu 20.10. The problem was my system. Now I can confirm that the solution above works. In my case, it wasn't necessary to run with LC_ALL=pt_BR.UTF-8 LANG=pt_BR.UTF-8 %command%.

@KairanD KairanD closed this as completed Oct 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants