Opened 7 years ago
Last modified 7 years ago
#17270 new defect
Scrolling with mouse integration
Reported by: | Yaroslav | Owned by: | |
---|---|---|---|
Component: | guest additions | Version: | VirtualBox 5.1.30 |
Keywords: | mouse, scroll, wheel | Cc: | |
Guest type: | Linux | Host type: | Windows |
Description
While using VBox 5.1.30 with Mouse Integration turned on the wheel scroll event is not passed to some windows while moving the mouse. If mouse is stationary the scroll is registered fine. It happens over Chrome, Firefox, GTK windows, but works fine for Java and urxvt windows.
I've already tried it with libinput and evdev on the guest Fedora 26 system. The behavior is the same.
Thank you.
Yaroslav
Change History (14)
follow-up: 2 comment:1 by , 7 years ago
comment:2 by , 7 years ago
Replying to michael:
Please use evtest in the guest to get a better idea of what is going on.
Using evtest: the mouse move events come from "VirtualBox mouse integration" device, while wheel scroll event is coming from "ImExPS/2 Generic Explorer Mouse".
While moving mouse over Chrome window and scrolling, the scroll event is registered in evtest, but it's not reflected in the chrome window. The same happens for other GTK windows.
comment:3 by , 7 years ago
Confirm the issue exists on VBox 5.2.0 and freshly installed Fedora 27 (using VBox provided guest additions as Fedora 27 has those by default now).
comment:4 by , 7 years ago
I suggest you take this to the Chrome and/or the GTK developers, and possibly give feedback here as to what conclusion is reached.
comment:5 by , 7 years ago
Might it be something on VBox side? Fedora 27 has guest additions on it's own and using those the scroll is working fine. The issue appears only using VBox-provided guest additions.
Thanks for any help
follow-up: 7 comment:6 by , 7 years ago
Not yet looked at Fedora 27. Do they also run the user-space tools by default?
comment:7 by , 7 years ago
Replying to michael:
Not yet looked at Fedora 27. Do they also run the user-space tools by default?
Yep, I was surprised myself when after clean install the resolution/mouse integration were working out of the box.
comment:8 by , 7 years ago
Those are all the kernel tools. The user space tools are for (among other things) the shared clipboard and drag and drop.
comment:9 by , 7 years ago
That's what I'm saying. Using Fedora 27 kernel tools the scroll works fine. If I install Vbox provided guest-additions kernel modules the scroll starts having this issue.
comment:10 by , 7 years ago
To put it differently: if you use the Fedora 27 Additions, are VBoxService and VBoxClient also running? And if not, when you use ours, does stopping VBoxClient (make sure you really stop all the processes) have any effect? If so, try again, just stopping the Drag and Drop VBoxClient processes.
comment:11 by , 7 years ago
I've removed Fedora 27 Virtual Machine.
With VBox additions installed, killing all VBoxClient processes has no effect. The scroll event still is not recorded while moving mouse.
[root@localhost ~]# ps aux | grep VBox root 466 0.0 0.0 0 0 ? S< 10:34 0:00 [iprt-VBoxWQueue] root 827 0.0 0.0 368636 3208 ? Sl 10:34 0:02 /usr/sbin/VBoxService --pidfile /var/run/vboxadd-service.sh root 8613 0.0 0.0 119468 960 pts/2 S+ 14:26 0:00 grep --color=auto VBox
comment:12 by , 7 years ago
Uninstalling VirtualBox Extension Pack resolved the issue for all windows.
comment:13 by , 7 years ago
Uninstalling the Extension Pack or the Additions? I assume the second; nonetheless I still suggest that you take this to the Chrome team, as I don't think that we will be able to look at this in the near future, and other applications work. It might help them to know that when mouse integration is enabled, button events and movement events reach the guest via different virtual devices. This is somewhat unusual, but can also happen on physical systems (e.g. a laptop with a touch pad and a touch point).
comment:14 by , 7 years ago
I thought it was Extension Pack (not the Guest Additions), however looks like removing xorg-x11-drv-libinput.x86_64 actually resolved the issue (was cleaning up some packages), not removing Extension Pack.
The issue lies somewhere between VBox Guest Additions and libinput driver for x11... Not sure where to look next.
Please use evtest in the guest to get a better idea of what is going on.