> подумаешь в консоль выкинет, иксы тоже выплевывают а раз два.

Причем тут "выкинет-выплюнет", если речь шла об уведомлениях оконного менеджера и буфере обмена o_O

> а на счет микро и тому подобного о чем ты сказал, ни разу  не встречал, все нормально там

Ну раз аноним не встречал, то значит так оно и есть - а в багтрекерах просто врут и выдумывают, даже сами редхатовцы и гнум-апстрим, когда намекают на баг в дизайне протокола:
> Peter Hutterer  (Senior Software Engineer @ RedHat)
> libinput doesn't do key repeats - it filters out the kernel repeats and only passes key down/up events on to the compositor. The key repeat you're seeing is the one triggered in the compositor (or Xorg but that's where this bug doesn't trigger) and is
> simply caused by gnome-shell being busy doing something else and thus not handling events as fast as it should.

https://bugzilla.gnome.org/show_bug.cgi?id=745032
> Mouse Tracking 'Laggy' on Wayland, and mouse movements cause frame drops in other OpenGL applications

Status:     RESOLVED INCOMPLETE
Reported:     2015-02-23 16:35
Modified:     2019-11-05 20:52 UTC
> we'll probably move libinput processing to its own thread (as
> is done on recent versions of Xorg) where it can directly update the
> hardware cursor without waiting for main drawing loop. This would probably
> involve moving the libinput backend from clutter to mutter, and adding
> mutexes shared by the KMS code and libinput backend. Doing this will not
> affect latency issues related to clients receiving input events; that'll
> require much larger changes, such as splitting up the shell UI into a
> separate process.