I'm facing the same symptoms. First time I realized I have this issue
was when playing a game on Stadia through Chrome/Chromium. I am using a
special hybrid joystick (movemaster.biz) to replace my keyboard, which
consists of two parts. Both devices are connected via usb and are
recognized as usb hid keyboards. When steering with the grip of the
device and only pressing buttons on the same device everything is okay.
But as soon as I press a button on the extension there is a litte lag or
stutter/freeze.

I thought it would be an issue with the browser and blamed Chromium, as
I haven't had any issues with games played locally. But now I had the
same issue with Star Wars Battlefront (from EA) played through Steam +
Proton.

The output of journalctl showed the same overwriting existing binding of
keysym errors as described here:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857392

That report leads to this report, and from here I got to
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1858#note_818548
describing a workaround with altering libmutter.

I tried that workaround on Ubuntu 20.04.3 LTS, where I at first wasn't
able to successfully biuld mutter/libmutter, but it helped to disable
the tests by editing debian/rules and add export
DEB_BUILD_OPTIONS=nocheck.

Installing the altered lib and rebooting didn't get rid of the problem
though.

Unfortunately the blog post from Osvald doesn't seem to be reachable as
the https certificate was revoked.

As the freeze happens despite the workaround, I'm not sure if it's the
same issue though. Any help would be appreciated as this behavior
totally ruins the experience.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1777708

Title:
  Desktop briefly becomes unresponsive when receiving a keypress from a
  different device/mapping than the last keypress (in Xorg)

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates
  from the repos.

  If I connect 2 (or more) keyboards to my computer and type on both at
  the same time, the desktop briefly becomes unresponsive. More
  keypresses increase the time of unresponsiveness.

  E.g. when typing a full sentence in gedit or the terminal, only very
  few characters show up on the screen (I guess up until something is
  pressed on both keyboards at the same time), then everything freezes.
  Then after a while (some seconds), all the characters show up. And the
  desktop becomes responsive again.

  Symptoms: During the freeze, windows stop updating their content. If
  seconds are enabled on the clock at the top middle, these freeze too.
  But I'm still able to move the mouse pointer around during the freeze
  without any problems.

  The back story:

  I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and
  quickly noticed the issue. But initiallly I thought it was an issue
  with the keyboard, and the problem wasn't that bad. But as I've gotten
  more used to the keyboard since yesterday and started picking up a
  proper typing speed, things got worse.

  The keyboard is technically two separate cabled USB keyboards each
  with only about half of they keys of a normal keyboard (or at least
  that's very much my impression).

  After getting the suspicion that this was a software issue, not a
  hardware issue, I tried typing on my old Logitech keyboard (Unifying
  Receiver) along with one of the R-Go halves: Same issue. Then I tried
  each of the halves without the other (as in "single" keyboard typing):
  No issue. Then I connected another Logitech keyboard (separate UR),
  typed on both Logitechs: Same issue.

  Some further observations:

  1) Nothing of significance in my syslog.
  2) If I drop to a non-graphical shell, there's no problem. I suspect this 
issue is related to X.org or Gnome, but I'm in no position to say anything 
credible about that.
  3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS 
machine.

  Let me know if there are any logs I can provide or things I can run to
  produce useful debug output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1777708/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to