[15:54] <oSoMoN> is it a known issue that autopilot fails to issue special key codes? I’ve upgraded my xenial+overlay laptop to zesty, and suddenly all my autopilot tests that involve keyboard fail, like this: http://pastebin.ubuntu.com/24139572/
[15:55] <oSoMoN> that’s for 'Escape', but other key combinations like 'Ctrl+plus' or 'F6' fail similarly
[16:00] <oSoMoN> jibel, ever seen↑ before?
[16:02] <oSoMoN> also interesting is that the same tests fail in a xenial+overlay virtualbox VM (pretty sure they used to pass there too), so it looks like something on the host system that’s affecting not just the host but also guests
[16:38] <oSoMoN> replacing references to 'Escape' by 'Esc' in my autopilot tests seems to fix that case, and references to function keys such as 'F11' by 'f11', but 'ctrl+something' combinations don’t work
[16:38] <oSoMoN> could this be a regression introduced by the recent new autopilot upstream release?
[17:52] <jibel> rhuddie, ^ do you know? is it the new release?
[18:34] <rhuddie> oSoMoN, we haven't seen any problems like that. the key codes themselves are coming from python3-evdev package, so it could be a difference in that package that's causing the issue. I can take a look.
[18:51] <oSoMoN> rhuddie, I talked to Santiago, he says « we've updated autopilot to assume Mir if desktop was used so _uinput would be used for keyboard events »
[18:51] <oSoMoN> so it appears to be an autopilot regression
[18:51] <oSoMoN> which I can work around to some extent in my tests
[18:52] <oSoMoN> but it looks like Santiago is on to a fix already anyway
[19:20] <rhuddie> oSoMoN, ok thanks, I'll check with santiago