I recently downgraded my FreeBSD host from 13-CURRENT to 12.x in order to be able to use the VirtualBox bridge mode. I plan to run CURRENT in VirtualBox.
If I install CURRENT r359106 in VirtualBox, and then install emulators/virtualbox-ose-additions and Xorg, I am able to move the mouse but not click it in the guest.
Anyone else having this issue?
I'm seeing the same with FreeBSD 12.1 guest on both FreeBSD and OS X hosts.
FYI, enabling moused in the guest is a simple workaround in my case.
I have the same issue with a FreeBSD 12.1-p8 guest running virtualbox-ose-additions 5.2.44 and xorg-server 1.20.8 in VirtualBox 6.1.12 on a Windows 10 Pro 1909 host. Can confirm that enabling moused helps.
To fix this, set the sysctl kern.evdev.rcpt_mask to 12.
This is not related to virtualbox. When xserver was updated 1.20, we changed how input devices were handled on FreeBSD 12 and later. Unfortunately, 12.1 was already released, so it was not possible to update the default value for the sysctl above. For 12.2, the sysctl above will have the value 12 by default.
I have this issue with FreeBSD 12.2 and virtualbox-ose-additions 5.2.44_2 running under Windows 10 Virtualbox 6.1.16 r140961
Under X the mouse works, focus on mouseover works, but no mouse clicks are ever registered.
Starting moused doesn't help, the console mouse works fine BTW.
kern.evdev.rcpt_mask is set to 12, still doesn't work.
If I deselect pointer integration in Virtualbox then the mouse doesn't work at all, no pointer ever moves.
This hald hack doesn't work either
(In reply to Nick from comment #5)
I had the same issue but it disappeared after updating to the latest stable/12 and ports. Maybe you need to remove leftover config in /usr/local/etc/X11 and/or /usr/local/etc/X11/xorg.conf.d. It should work ok without *any* tweaking of devices (i.e. these directories completely empty). Otherwise please check Xorg.log, it should see an input device System mouse on /dev/input/eventX through udev.
Closing. Using kern.evdev.rcpt_mask should work.