View Issue Details

IDProjectCategoryView StatusLast Update
0004206Kali LinuxKali Package Bugpublic2018-07-27 11:56
Reporterrussm Assigned Torhertzog  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionwon't fix 
Product Versionkali-dev 
Summary0004206: Wayland breaks trackpad scrolling in VM guests
Description

When GDM uses Wayland, trackpad scrolling doesn't work in VM guests

Steps To Reproduce
  • install virt-manager
  • create a VM that boots eg kali-linux-2017-W35-amd64.iso
  • in the VM, open Settings > Mouse & Touchpad, click "Test Your Settings"
  • try to scroll using the touchpad

using the same guest image, if the host is running a Wayland session (eg 2017-W35) then scrolling does not work. is the host is not using Wayland (eg 2017-08-29 daily) then scrolling does work.

Additional Information

this issue has been worked around by kali-root-login 2017.2.0 but will presumably return when Wayland is re-enabled. reporting this bug as a "breaks under Wayland" placeholder.

Activities

rhertzog

rhertzog

2017-08-29 12:50

administrator   ~0007168

I wonder if this is not a problem introduced by virtualization more than by Wayland itself. On my laptop with Wayland, I can use my trackpad (with two finger to control the scrolling) with wayland.

But in a qemu-kvm VM with Wayland and with Xorg, the scrolling only works with the wheel on my mouse, it does not work with the trackpad.

What input devices do you have configured in your VM? Om my side, thhere's a tablet and a regular mouse.

rhertzog

rhertzog

2017-08-29 13:18

administrator   ~0007170

FWIW, this feature loss is really not critical compared to the other regressions we had so far.

russm

russm

2017-08-29 23:44

reporter   ~0007178

I have a tablet and mouse in the VM - the default HID devices provided in a new VM.

yes, trackpad scrolling works fine in the host, it is only in VM guests that trackpad scroll events are dropped/ignored/whatever.

agree this is super-low priority, but thought it was worth noting as a regression triggered by changing to a Wayland sessions.

dookie

dookie

2017-08-30 00:13

reporter   ~0007179

This also happens for me under VMware Fusion so that's another clue that maybe virtualization is the issue here rather than Wayland.

rhertzog

rhertzog

2018-07-27 11:56

administrator   ~0009400

We don't plan on doing anything special for Kali. If the issue is still present, it should be reported to Debian. And it's minor enough to not warrant investing any of my Kali time.

Issue History

Date Modified Username Field Change
2017-08-29 05:44 russm New Issue
2017-08-29 12:50 rhertzog Note Added: 0007168
2017-08-29 13:18 rhertzog Note Added: 0007170
2017-08-29 13:18 rhertzog Assigned To => rhertzog
2017-08-29 13:18 rhertzog Status new => assigned
2017-08-29 23:44 russm Note Added: 0007178
2017-08-30 00:13 dookie Note Added: 0007179
2018-07-27 11:56 rhertzog Status assigned => closed
2018-07-27 11:56 rhertzog Resolution open => won't fix
2018-07-27 11:56 rhertzog Note Added: 0009400