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

No mouse cursor visible on VirtualBox (or VMware) #3814

Open
theothermatt opened this issue Mar 4, 2019 · 22 comments
Open

No mouse cursor visible on VirtualBox (or VMware) #3814

theothermatt opened this issue Mar 4, 2019 · 22 comments
Labels
bug Not working as intended

Comments

@theothermatt
Copy link

As requested, I'm reporting here something I originally reported on the Alpine
Linux mailing list (https://lists.alpinelinux.org/alpine-devel/6462.html).

Upgrading to 1.0-rc4 in the Alpine testing repository
(https://pkgs.alpinelinux.org/package/edge/testing/x86_64/sway) results in
having no mouse cursor visible. The mouse still functions, but is of course
pretty unusable.

This is running on Virtualbox, which as far as I can tell only recently (v6.0
onwards) gained the ability to run Sway (and probably other Wayland stuff), via
the VMSVGA graphics controller.

Hopefully what I've provided here is helpful, but please let me know if you
need anything else.

@emersion emersion added the bug Not working as intended label Mar 4, 2019
@IComplainInComments
Copy link

Im also experiencing this issue using Vmware and Open-vm-tools. The mouse works, but no cursor wants to appear.

I've tried basic troubleshooting and nothing is working. Including possible solutions for Wayland, Xwayland, and Xorg (that have/had this issue as well).

@emersion
Copy link
Member

emersion commented Mar 4, 2019

Can you run drm_info on your host?

This is probably due to swaywm/wlroots#1526

@IComplainInComments
Copy link

IComplainInComments commented Mar 4, 2019

EDIT: Let me link it for you...
EDIT 2: @emersion https://github.com/IComplainInComments/Output

@IComplainInComments
Copy link

Looks like adding WLR_NO_HARDWARE_CURSORS=1 fixes the issue.

So it looks like this problem is being caused due to a Rendering issue with Wayland and the Driver.

@theothermatt
Copy link
Author

@theothermatt
Copy link
Author

Also, I can confirm that using WLR_NO_HARDWARE_CURSORS=1 fixes the issue, albeit with a slightly laggy mouse, which is expected I guess.

@emersion emersion changed the title Sway 1.0-rc4 - no mouse cursor visible No mouse cursor visible on VirtualBox Mar 8, 2019
@jnschulze
Copy link

There's a related discussion at https://www.virtualbox.org/ticket/18239#comment:14 . According to the latest post, vmsvga doesn't support hardware cursor planes yet.

@theothermatt
Copy link
Author

An update - Virtualbox are saying things are fixed on their end (https://www.virtualbox.org/ticket/18239#comment:17).

I'm still seeing this problem with sway 1.0 on Alpine I'm afraid. Let me know if you need any more information or if I can help in any way.

@xelra
Copy link

xelra commented May 21, 2019

I'm also seeing this issue in VirtualBox 6.0.8. They say they fixed it with 6.0.4. Did they really fix it and there's an additional issue in sway?

EDIT:
I've installed GNOME, knowing it uses Wayland, just to see whether it shows a mouse pointer. And yes, it does. I also talked to someone on Fedora who also doesn't have this issue with VirtualBox.
So I guess it's really fixed on VirtualBox' side.

I'm on Arch Linux, btw.

@JSamir
Copy link

JSamir commented May 28, 2019

I've got the same issue with Ubuntu 19.04 and VirtualBox 6.0.8, using VMSVGA as graphics controller in VirtualBox.

@riquito
Copy link

riquito commented Jun 13, 2019

Sorry for the "me too", I don't know if it's any useful to you but... vmware fusion 11.1.0, ubuntu 19.04 fresh install, sway 1.1.rc2. Gnome manages to display the cursor (both with X11 and wayland gnome), sway unfortunately does not

@rstacruz
Copy link

Very closely related to https://github.com/swaywm/sway/issues/3617.

One workaround is to add this to your ~/.profile:

export WLR_NO_HARDWARE_CURSORS=1

This was suggested here:

@RedSoxFan RedSoxFan changed the title No mouse cursor visible on VirtualBox No mouse cursor visible on VirtualBox (or VMware) Dec 16, 2019
@eoli3n
Copy link

eoli3n commented Apr 27, 2020

Same here with Qemu

@Niarch

This comment has been minimized.

@NETLIFYHOSTINGAHMD
Copy link

i am not in a VM and i dont have a cursor aswell

@ku1ik
Copy link

ku1ik commented Feb 6, 2022

I'm experiencing the same problem when running Wayland+Sway under Parallels Desktop on M1 macbook. This problem doesn't occur under any other guest OS/window manager I virtualize on Parallels. I've tested Xorg+i3 on the same VM and the cursor is visible and works perfectly fine there.

@suddenlyfleck

This comment was marked as duplicate.

@hiimnooob

This comment was marked as duplicate.

@hnorkowski
Copy link

I am using Manjaro Sway with VirtualBox 6.1.38 and disabling the hardware cursor is still the only fix I could find. But the cursor is very laggy. I want to use the VM as daily driver but that that cursor is very annoying. Is there any other fix (plannend)?

@Je55eah
Copy link

Je55eah commented May 6, 2023

I am experiencing the same issue, missing mouse pointer, manjaro sway, virtualbox, mx linux host, mid 2012 macbook pro, intel hd graphics 4000

@tim-rex
Copy link

tim-rex commented Jul 16, 2023

I can report the same running Fedora 38 under Parallels on an M2 macbook pro
Setting WLR_NO_HARDWARE_CURSORS is a workaround, but performance isn't great. As others have reported, hardware cursors on this platform seem to work just fine with other window managers (Gnome/Plasma) but unclear how much of this is driven by Parallels Tools installation

drm_info attached
drminfo.txt

@bermudi
Copy link

bermudi commented Feb 23, 2024

I can also report the same issue for a very old intel GPU.
WLR_NO_HARDWARE_CURSORS seems to work rather well with no notable lag. And just like others have mentioned mouse cursor works fine in other wayland WM like weston/wayfire/hikari/etc...

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)

drm_info https://termbin.com/52m0
log https://termbin.com/dvlh
log with software cursors https://termbin.com/mtq7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Not working as intended
Development

No branches or pull requests