UI does not react correctly to mouse input on FreeBSD

[trueFireblade]

Describe the bug
I recently upgraded from 5.1 to 6.1 on FreeBSD and the UI itself (so selection of remote host/settings/etc) no longer react correctly to mouse input. The click animation on buttons plays, but they do not perform their action.

Steps to reproduce
Install latest port version on FreeBSD under X11

Client PC details (please complete the following information)

• OS: FreeBSD 14.1
• Moonlight Version: 6.1
• GPU: I5-8265U
• package type (if applicable): FreeBSD quaterly repos

Server PC details (please complete the following information)

• OS: [e.g. Windows 10 1809]
• Sunshine or GeForce Experience version: [e.g. Sunshine v0.21.0]
• GPU: [e.g. AMD Radeon RX 7900 XT]
• GPU driver: [e.g. 24.1.1]

Moonlight Logs (please attach)
Input redirection (moonlight-qt > moonlight.logs) does not work and it still prints to the console instead and the console does not keep enough history to be able to get full logs from there. If logs are needed please provide instructions on how to log to a file.

[quendae]

+1, I'm on the PopOS and wanted to try some games from Steam (Next Fest), and while left click seems to be working as OP described (animation is there, but click is not happening).

Client:

• Pop!_OS 22.04 LTS x86_64
• HP T640 Thin Client
• Kernel: 6.9.3-76060903-generic
• Moonlight 6.1.0

Host:

• Windows 10 22H2
• Sunshine v0.23.1
• AMD Radeon 6950XT
• 24.9.1 (latest)

Tried new Commandos: Origins (can't move character despite arrows shows on the ground), Industry Giant 4.0 (can't place building in tutorial)

[trueFireblade]

@quendae To me it sounds like you have a different issue, considering the fact you name games. I don't even get to connect to the remote host, the clicks with animation playing but nothing happening is in the moonlight-qt ui itself

[cgutman]

Since Moonlight logs to stderr, you will need to redirect both stdout and stderr using a command like: moonlight-qt &> moonlight.log

I'm curious if any QML or OpenGL errors are present in the logs. Typically, you will see some sort of warning from Qt when the UI breaks like that.