Comment 0 for bug 1489522

Steps to reproduce:
 * setup kvm as in our wiki
 * launch mir_demo_server with a client
 * try to move the client windows window with the mouse

-> mir does not react to move moves or clicks..

looking at the legacy input report mir opens event3 and event1 but not event2 which is the actual mouse

[1440689971.827115] mirplatform: Found graphics driver: mesa-kms
[1440689971.827130] mirplatform: Found graphics driver: dummy
[1440689971.827530] mirserver: Starting
[1440689971.827622] mircommon: Loading modules from: /usr/lib/x86_64-linux-gnu/mir/server-platform
[1440689971.827640] mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.3
[1440689971.827650] mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-dummy.so
[1440689971.827856] mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa.so.1
[1440689971.828573] mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/input-stub.so
[1440689971.829157] mirplatform: Found graphics driver: mesa-kms
[1440689971.829166] mirplatform: Found graphics driver: dummy
[1440689971.829302] mirserver: Selected driver: mesa-kms (version 0.14.0)
[1440689971.886037] mirserver: Using hardware cursor
[1440689971.887019] mirserver: Mir version 0.14.0
[1440689971.895906] mirserver: GL vendor: VMware, Inc.
[1440689971.895910] mirserver: GL renderer: Gallium 0.4 on llvmpipe (LLVM 3.6, 128 bits)
[1440689971.895911] mirserver: GL version: OpenGL ES 3.0 Mesa 10.5.9
[1440689971.895912] mirserver: GLSL version: OpenGL ES GLSL ES 3.00
[1440689971.895915] mirserver: GL max texture size = 8192
[1440689971.895931] mirserver: GL framebuffer bits: RGBA=8880, depth=0, stencil=0
[1440689971.900445] android-input: [EventHub]New device: id=1, fd=24, path='/dev/input/event0', name='Power Button', classes=0x1, configuration='', keyLayout='Generic.kl', keyCharacterMap='Generic.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=true
[1440689971.901117] android-input: [EventHub]New device: id=2, fd=25, path='/dev/input/event1', name='AT Translated Set 2 keyboard', classes=0x3, configuration='', keyLayout='Generic.kl', keyCharacterMap='Generic.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=true
[1440689971.901215] android-input: [EventHub]New device: id=3, fd=26, path='/dev/input/event3', name='VirtualPS/2 VMware VMMouse', classes=0x8, configuration='', keyLayout='', keyCharacterMap='', builtinKeyboard=false, usingSuspendBlockIoctl=false, usingClockIoctl=true
Signal 1 received. Good night.
[1440689971.901946] android-input: [InputReader]Device added: id=-1, name='Virtual', sources=0x00000301
[1440689971.905374] android-input: [InputReader]Device added: id=3, name='VirtualPS/2 VMware VMMouse', sources=0x00002002
[1440689971.905397] android-input: [InputReader]Device added: id=2, name='AT Translated Set 2 keyboard', sources=0x00000101
[1440689971.905414] android-input: [InputReader]Device added: id=1, name='Power Button', sources=0x00000101
[1440689979.377863] mirserver: Stopping
[1440689979.378842] android-input: [EventHub]Removed device: path=/dev/input/event3 name=VirtualPS/2 VMware VMMouse id=3 fd=26 classes=0x8

[1440689979.378849] android-input: [EventHub]Removed device: path=/dev/input/event1 name=AT Translated Set 2 keyboard id=2 fd=25 classes=0x3

[1440689979.378854] android-input: [EventHub]Removed device: path=/dev/input/event0 name=Power Button id=1 fd=24 classes=0x1

[1440689979.378858] android-input: [EventHub]Removed device: path=<virtual> name=Virtual id=-1 fd=-1 classes=0x40000023

Note the same happens for mir-0.15.0