Daniel Johnson

There's a possibility that the fix in commit cc509641f06d755c27ee32e9e0dd89ff14f07e17 will help with this problem. Could you give the latest master a try? No need to install; download it and run...

That is hilarious! But I do not understand how you create a game like this. What's the reproduction?

I don't think Lutris does adjust the config; it gives DOSBOX a configuration file if directed to do so, but it doesn't seem to mess with what's in the file....

Does your Bluetooth keyboard ALT work for anything else? Maybe a WINE game or a native one? If so, that would suggest to me that it's DOSBOX or its configuration.

I do not understand this stuff about 'moving up and down'; sounds like some kind of priority order of runtimes, but what would use that? It seems to me that...

It seems to me that if you are still seeing that on a new OS install, it must be a setting kept on EA's servers that is doing this.

Have you tried ordinary wine-ge-8-26?

Well, I notice the changelog says "Using Proton in Lutris without umu is no longer possible"; that may be your issue. But I am pretty unsure what the difference is...

I'm not sure how you know you have *this* issue. But the thing to do is post the Lutris debug log. Run this at a terminal: ```bash lutris -d ```...

This seems quite strange. Perhaps you could give us a debug log? To do so, run Lutris from the terminal: ``` lutris -d ``` And run the game, then give...