Now the question is should the patch be dropped or wait for a fix from
upstream. I'm leaning towards the first option, since artful is about to
be released.
** Package changed: wayland (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New => Triaged
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1718719
Title:
qemu can't capture keys properly under wayland
Status in QEMU:
New
Status in XServer:
Incomplete
Status in qemu package in Ubuntu:
New
Status in xorg-server package in Ubuntu:
Triaged
Bug description:
This appears to be different than the previous similar bugs; patches
do look to be applied to use libinput in the wayland case. Still:
unknown keycodes `(unnamed)', please report to qemu-de...@nongnu.org
I am using qemu-system-x86 1:2.10+dfsg-0ubuntu1
on artful.
Many key inputs work correctly, but at boot the system will not
properly catch the arrow keys, the above error shows up immediately
after hitting Esc (for instance) to get to the boot menu. Booting from
CD onto a daily Ubuntu desktop image, I can't navigate the splash
menu.
The same works correctly through virt-manager (which uses spice
AFAICT, but wayland tends to crash when running virt-manager), and
things work if I switch my session to Xorg rather than wayland.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1718719/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
