@Riccardo, +1. I am unable to reproduce this bug on trusty. But this was a issue when it was reported. So I am guessing this was fixed upstream and was a OSK issue.
@Riccardo, +1. I am unable to reproduce this bug on trusty. But this was a issue when it was reported. So I am guessing this was fixed upstream and was a OSK issue.