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

[Issue]: Incorrect mouse buttons in Samsung DeX #1476

Open
knyipab opened this issue Feb 19, 2025 · 0 comments
Open

[Issue]: Incorrect mouse buttons in Samsung DeX #1476

knyipab opened this issue Feb 19, 2025 · 0 comments
Labels

Comments

@knyipab
Copy link

knyipab commented Feb 19, 2025

Describe the bug

When using hardware mouse with Samsung phone in DeX mode, the right click and middle click signals are not accurately sent (??) to sunshine. Some applications just cannot pick up user's middle click and right click. More specifically see below steps to reproduce.

This does not happen to the same phone in the normal, non-DeX mode.

Steps to reproduce

Test a Samsung phone with this website:
https://w3c.github.io/uievents/tools/mouse-event-viewer.html

This is in DeX mode (abnormal):

Image

This is in normal, non-DeX mode:

Image

This difference will causes applications below not able to respond to user mouse action correctly.

Affected games

Many applications. E.g.:

  • Chromium cannot close tab using middle click
  • FreeCAD cannot use middle click to navigate
  • Onlyoffice (flatpak) cannot use right click to show menu

Other Moonlight clients

PC

Moonlight adjusted settings

No

Moonlight adjusted settings (please complete the following information)

Nope.

Moonlight default settings

Yes

Gamepad-related connection issue

No

Gamepad-related input issue

No

Gamepad-related streaming issue

Yes

Android version

Android 14 (One UI 6.1.1)

Device model

Samsung Z Fold5

Server PC OS version

Archlinux

Server PC GeForce Experience version

Sunshine v2025.122.141614

Server PC Nvidia GPU driver version

Intel in KVM

Server PC antivirus and firewall software

Nope

Screenshots

No response

Relevant log output

Additional context

No response

@knyipab knyipab added the bug label Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant