Confirmed this bug is still happening. And it's not as easy as exiting if there are zero input drivers. Because the input driver loads (just does not respond to any input):
[2016-03-01 17:17:06.258314] mirserver: Selected input driver: mir:evdev-input (version: 0.20.1)
Confirmed this bug is still happening. And it's not as easy as exiting if there are zero input drivers. Because the input driver loads (just does not respond to any input):
[2016-03-01 17:17:06.258314] mirserver: Selected input driver: mir:evdev-input (version: 0.20.1)