Just an update - the problem got progressively more severe over days. So
I ordered a new keyboard and replaced it. The issue has now gone. So it
looks like this was a hardware issue. I have marked this bug report as
invalid.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
I re-installed Wayland and logged in with the Ubuntu on Wayland option
but it didn't fix the issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1922766
Title:
UP and DOWN
You do "have Wayland installed" already. It's an option hiding on the
login screen behind the button in the bottom-right corner of the screen.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
The only other devices I use with my laptop wireless with usb
transceiver or bluetooth and none have keys. Unfortunately I don't have
Wayland installed but I will go through the above bug to see what I can
infer (and probably install Wayland to test), but in the mean time I
have progressed a bit.
The Xorg logs seem to suggest several non-keyboard devices are being
treated as keyboards (because they have buttons maybe?). That might not
be a bug in itself but it might mean you will suffer from the same delay
as bug 108.
Please try logging into 'Ubuntu on Wayland' instead and see if that
There isn't anything in top that looks like an issue, gnome-shell was at
the top with a about 9% CPU.
Disabling all extensions does not fix the issue.
I did see some errors in the systemd journal related to PCI, these
appeared a few seconds after trying to use the up and down keys.
Errors in
Thanks for the bug report. I can't seem to reproduce the problem in
20.04 here...
Please open two Terminal windows and in one run 'top' and in the other
run 'journalctl -f'. Then reproduce the bug again. While the bug is
happening, do you see high CPU usage in 'top' or any messages flooding
the
