Sunshine
Sunshine copied to clipboard
LizardByte
No mouse on Bazzite and Sunshine v2025.107.25026
Is there an existing issue for this?
- [x] I have searched the existing issues
Is your issue described in the documentation?
- [x] I have read the documentation
Is your issue present in the latest beta/pre-release?
None
Describe the Bug
Try to move away from Win11 for gaming. Try to find a Linux distro where Sunshine is actually working. Tried some distros (openSuse, Ubuntu 24.04/24.10, Xubuntu 24.04/24.10, Fedora 41, Mint, Gentoo, Manjaro, Arch, CachyOS, ..., and Bazzite). Bazzite seems to be the only distro where Sunshine detects my video card (Nvidia 4060) so I am quite happy. At least this is the status "out of the box" with Bazzite.
Yet, Moonlight does not show mouse when connected. The log says
Warning: No KMS cursor plane found. Cursor may not be displayed while streaming
I tried to do
setcap cap_sys_admin+p $(readlink -f $(which sunshine))
but since Bazzite is read-only system, it complains that I cannot do this command and would rather need to bundle it in a RPM (which I have not clue how to do).
Also, following other "tricks" like running screen recorder, accessibility tools, setting KWIN-...flags, etc. all did not work. Interestingly, when running a screen recorder and connecting via Moonlight I can see the mouse "inside" the screen recorder video, but not on the screen itself. So at least Moonlight provides info on mouse movement, but Sunshine simply does not seem able to render it to Moonlight?
Also found a ticket where a migration "away from kmsgrab" is discussed. May this be related?
Expected Behavior
Would love to see the mouse pointer :)
Additional Context
No response
Host Operating System
Linux
Operating System Version
Bazzite "downloaded on Jan 17th 2025"
Architecture
amd64/x86_64
Sunshine commit or version
v2025.107.25026
Package
other (not listed)
GPU Type
NVIDIA
GPU Model
4060
GPU Driver/Mesa Version
565.77
Capture Method
KMS (Linux)
Config
Apps
Relevant log output
Warning: No KMS cursor plane found. Cursor may not be displayed while streaming
https://docs.lizardbyte.dev/projects/sunshine/master/md_docs_2troubleshooting.html#unusual-mouse-behavior
In particular, this is likely due to missing the modeset=1 parameter for the nvidia kernel module.
Thank for the quick reply. modeset was / is set:
bash-5.2# rpm-ostree kargs rhgb quiet root=UUID=bdb23ce2-80b0-4a8a-a307-52d2256b1bc14 rootflags=subvol=root rw ostree=ostree/boot.0/default/ea967519f4b11d0b812f95d00995f4d7de6464fe8be98e477f0b7ff79ca4fe6f/0 bluetooth.disable_ertm=1 preemnt=full rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1
How to check "setcap". Found this PR which I assume may have done it already for Bazzite, but not sure: https://github.com/LizardByte/Sunshine/pull/3050
setcap is set automatically in the rpm spec file when using our Fedora copr build.
Ok, then it seems that things do not work properly even setcap and modeset are applied. Today, got notification about new build of sunshine (version 118) but still try to figure out how to install this in bazzite.
It seems this issue hasn't had any activity in the past 90 days. If it's still something you'd like addressed, please let us know by leaving a comment. Otherwise, to help keep our backlog tidy, we'll be closing this issue in 10 days. Thanks!
It seems this issue hasn't had any activity in the past 90 days. If it's still something you'd like addressed, please let us know by leaving a comment. Otherwise, to help keep our backlog tidy, we'll be closing this issue in 10 days. Thanks!
I can confirm this is still an issue.
I am suspecting this bug is related to this one: https://github.com/LizardByte/Sunshine/issues/3860
I'm also having this issue on CachyOS with a 9700XT. I have tried multiple client devices and on all of them no mouse input is shown on the host. I can get cursor movement and hover working if I enable "remote desktop mode" in moonlight, but clicks are not detected.
It seems this issue hasn't had any activity in the past 90 days. If it's still something you'd like addressed, please let us know by leaving a comment. Otherwise, to help keep our backlog tidy, we'll be closing this issue in 10 days. Thanks!
This issue was closed because it has been stalled for 10 days with no activity.