Hi,
I was tracking the upstream discussion closely and I'm glad you came here with a suggested fix.
With some minor polishing I added it to the packaging git for qemu.
I built a test version in a PPA at [1].
Never the less - probably since keycodes isn't my qemu-home-turf - I'm afraid that this change has a chance to fix an issue for some, but cause new issues for other users.
Therefore I'd want to go extra safe on this.
I'd suggest:
1. you test your case against the PPA I provided
2. I want to test on my own a matrix of qemu usages and check if/how they change due to that upgrade.
3. users in general are invited to test their case (the more languages/keyboards we have the better) I think I'm gonna send a call for testing to Ubuntu-server after we are done with our tests.
Hi,
I was tracking the upstream discussion closely and I'm glad you came here with a suggested fix.
With some minor polishing I added it to the packaging git for qemu.
I built a test version in a PPA at [1].
Never the less - probably since keycodes isn't my qemu-home-turf - I'm afraid that this change has a chance to fix an issue for some, but cause new issues for other users.
Therefore I'd want to go extra safe on this.
I'd suggest:
1. you test your case against the PPA I provided
2. I want to test on my own a matrix of qemu usages and check if/how they change due to that upgrade.
3. users in general are invited to test their case (the more languages/keyboards we have the better) I think I'm gonna send a call for testing to Ubuntu-server after we are done with our tests.
[1]: https:/ /launchpad. net/~ci- train-ppa- service/ +archive/ ubuntu/ 3380