If you connect to a Linux device with an Android device after the update, the left ctrl key does not work properly for programs running with winehq.

Hello,

Thank you for reaching out to us regarding this,

To clarify, this was working as expected for you in RDM Android 2023.1.2.0 and you're now encountering this issue after the update?

I would also like to confirm that this is working as expected for you outside RDM?

Let me know,

Best regards,

Hello,

Thank you for bringing this issue to our attention. We have investigated and found that the issue is related to recent improvements we made to how we send keyboard inputs. Compared to before, they are now sent the way they should.

The issue with WineHQ, which is an application used to launch Windows programs, is that it intercepts the input events and translates them into Windows-compatible events. This can sometimes cause problems with certain key combinations, like Ctrl, Alt, and Shift. This used to work before because some inputs weren't sent correctly, and for some reason, WineHQ was able to translate the key correctly.

To fix this issue, we recommend modifying the WineHQ registry settings to disable input event translation. Here are the steps to follow:

1. Open the WineHQ registry editor by running the command "wine regedit" in the terminal.
2. Navigate to the following registry key: HKEY_CURRENT_USER\Software\Wine\X11 Driver.
3. Create a new string value called UseXIM and set its value to "N".
4. Create another new string value called XIMInputStyle and set its value to "None".
5. Close the WineHQ registry editor.
6. Restart the application that is using WineHQ.

If you don't have the X11 Driver key in the registry, you can create it manually using the following steps:

1. Open the WineHQ registry editor by running the command "wine regedit" in the terminal.
2. In the registry editor, navigate to the HKEY_CURRENT_USER\Software\Wine key.
3. Right-click on the Wine key and select New -> Key from the context menu.
4. Name the new key X11 Driver.
5. Select the new X11 Driver key.
6. Right-click on the right-hand pane and select New -> String Value from the context menu.
7. Name the new string value UseXIM.
8. Double-click on the UseXIM value and set its value data to "N".
9. Right-click on the right-hand pane and select New -> String Value from the context menu.
10. Name the new string value XIMInputStyle.
11. Double-click on the XIMInputStyle value and set its value data to "None".
12. Close the WineHQ registry editor.

By disabling the input event translation and setting the input style to None, WineHQ should now pass your keyboard input events directly to the application, resolving the issue with the modifier keys not working correctly.

If you have any further questions or concerns, please don't hesitate to ask.

Best regards,
Frédérick Simard

This method worked. However, I don't know if this will work as winwhq is updated later.

Glad to hear that the method worked for you!

Regarding your concern about WineHQ updates potentially affecting the registry settings, based on my understanding, it is unlikely to be impacted. WineHQ follows a careful update process where it focuses on updating the program files and libraries while preserving the user's configuration settings. This approach ensures that your customized registry settings remain intact and unaffected.

While it's important to note that there can be exceptions in the case of major version upgrades or significant changes to WineHQ, the typical update process should not interfere with the registry settings.

If you have any further questions or concerns, please feel free to let me know.

Best regards,
Frédérick Simard

Glad to hear that the method worked for you!

Regarding your concern about WineHQ updates potentially affecting the registry settings, based on my understanding, it is unlikely to be impacted. WineHQ follows a careful update process where it focuses on updating the program files and libraries while preserving the user's configuration settings. This approach ensures that your customized registry settings remain intact and unaffected.

While it's important to note that there can be exceptions in the case of major version upgrades or significant changes to WineHQ, the typical update process should not interfere with the registry settings.

If you have any further questions or concerns, please feel free to let me know.

Best regards,
Frédérick Simard

Oh, unfortunately, another problem has occurred. Setting up that registry prevents other language input by ibus on Linux. Only English is input.
Essentially, it seems that the keyboard input needs to be modified.

Hello,

Thank you for bringing this to our attention. We apologize for the inconvenience you've experienced. We understand that you encountered an issue with the WineHQ registry settings, and it seems to be impacting the functionality of other language inputs through IBus.

Our team is actively investigating the matter to identify the underlying cause and find a suitable solution. We are exploring various possibilities, including examining the interactions between WineHQ and IBus configurations.

Please bear with us as we work diligently to address this issue and provide you with a resolution that ensures both WineHQ functionality and support for multiple language inputs, while also not affecting the previous improvements related keyboard input.

If you have any additional information or insights regarding the issue, please feel free to share them with us. We will keep you updated on our progress.

Best regards,
Frédérick Simard

Hello,

We have a solution for your issue, which will be implemented in our upcoming release by the end of June.

Best regards,
Frédérick Simard

The shift key has not been sent properly since this update.

Hello,

We've tested the Shift key issue on Linux (xrdp), in and out of WineHQ, and Windows, but couldn't replicate it. Could you provide more details?
Also, the recent update should have fixed the CTRL Left key problem in WineHQ. Could you confirm if this is now resolved?

Best regards,
Frédérick Simard

Running xev and pressing the left and right shift keys and capslock will not respond to keystrokes. Ctrl and alt are fixed.

We have identified the cause of the problem. This occurs when Unicode transfer is turned on. And then there was another problem. You need to press ctrl+shift+v to copy and paste from the terminal, but these mix keys do not work properly. So I purposely assigned a shift to the left super key

Hello,
Thank you for the clarification. We are going to open a ticket for that and investigate it further.

Best regards,
Frédérick Simard

Hello,
We have found the issue regarding the Ctrl + Shift + keys. A fix should be released really soon.

Best regards,
Frédérick Simard