I installed: Trident-x64-20180831.iso as guest OS in a VBox vm.
ran: trueos-update upgrade (done on 9/4/2018)
The mouse wheel when rolling UP will act like the 'back' button in konqueror, firefox, and falkon browsers.
It is a bit inconsistent as to how far 'back' the mouse wheel-up will go.
This issue happens in both lumina and kde desktop's.
This mouse issue does not exist in an older release (TrueOS-Desktop-18.03) with the same VBox configuration.
It was discovered the Trident insaller configured /etc/X11/xorg.conf
w/o a keyboard and mouse input sections. I copied the xorg.conf from the vm trueos-Desktop-18.03
and reboot. However the mouse issue remains.
Trident (this is where the mouse was having issues) version info:
This has been noticed on TrueOS since 2017, and appears to be a bad interaction between VirtualBox (host) and the moused daemon (FreeBSD guest) which results in additional mouse button 1 (left click) and mouse button 7 (back) events getting generated while using the scroll wheel on the mouse.
This can easily be reproduced/tested by installing the "xev" utility and running it. While it is running, place the mouse over the testing window and then scroll the mouse wheel.
I am unaware of any known fixes for this on FreeBSD at the present time.
This is highly irritating and I can't believe I'm the only one with this problem. Who do we contact to fix it? is it VirtualBox or FreeBSD Who is the responsible project?
I found a work-around for this issue and committed it to 18.12-U8.
Seems that turning off the "moused" service in virtualbox guest sessions prevent that mouse-click duplication/error issue.
I installed: Trident-x64-20180831.iso as guest OS in a VBox vm.
ran: trueos-update upgrade (done on 9/4/2018)
The mouse wheel when rolling UP will act like the 'back' button in konqueror, firefox, and falkon browsers.
It is a bit inconsistent as to how far 'back' the mouse wheel-up will go.
This issue happens in both lumina and kde desktop's.
This mouse issue does not exist in an older release (TrueOS-Desktop-18.03) with the same VBox configuration.
It was discovered the Trident insaller configured /etc/X11/xorg.conf
w/o a keyboard and mouse input sections. I copied the xorg.conf from the vm trueos-Desktop-18.03
and reboot. However the mouse issue remains.
Trident (this is where the mouse was having issues) version info:
TrueOS-Desktop-18.03 (In this version the mouse is working OK) version info
Using VBox (both Trueos-Desktop and Trident use this VBox configuration):
The text was updated successfully, but these errors were encountered: