Same issue here with R-Go split
Interestingly I found one configuration that works, but horribly breaks other
things:
first, have a look with xinput
$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
...
⎜ ↳ Hantick USB Keyboard Consumer Control id=20 [slave pointer (2)]
⎜ ↳ HID 0911:2188 Consumer Control id=22 [slave pointer (2)]
⎜ ↳ HID 0911:2188 Mouse id=24 [slave pointer (2)]
⎜ ↳ Hantick USB Keyboard Mouse id=25 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
...
↳ Hantick USB Keyboard id=16 [slave keyboard (3)]
↳ HID 0911:2188 System Control id=17 [slave keyboard (3)]
↳ HID 0911:2188 id=18 [slave keyboard (3)]
↳ Hantick USB Keyboard System Control id=19 [slave keyboard (3)]
↳ Hantick USB Keyboard Consumer Control id=21 [slave keyboard (3)]
↳ HID 0911:2188 Consumer Control id=23 [slave keyboard (3)]
↳ Hantick USB Keyboard Wireless Radio Control id=26 [slave
keyboard (3)]
The Hantick devices as well as the 0911:2188 devices are the R-Go Split (why so
many?)
interestingly there is a wireless radio control???
Anyway, let's create a new group
$ xinput create-master rgosplit 0
$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
...
⎡ rgosplit pointer id=27 [master pointer (28)]
⎜ ↳ rgosplit XTEST pointer id=29 [slave pointer (27)]
⎣ rgosplit keyboard id=28 [master keyboard (27)]
↳ rgosplit XTEST keyboard id=30 [slave keyboard (28)]
and now add those 0911:2188 keyboard devices to it (note that you need
to replace the numbers in the commands)
$ xinput reattach 17 28
$ xinput reattach 18 28
$ xinput reattach 23 28
$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
...
⎜ ↳ Hantick USB Keyboard Consumer Control id=20 [slave pointer (2)]
⎜ ↳ HID 0911:2188 Consumer Control id=22 [slave pointer (2)]
⎜ ↳ HID 0911:2188 Mouse id=24 [slave pointer (2)]
⎜ ↳ Hantick USB Keyboard Mouse id=25 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
...
↳ Hantick USB Keyboard id=16 [slave keyboard (3)]
↳ Hantick USB Keyboard System Control id=19 [slave keyboard (3)]
↳ Hantick USB Keyboard Consumer Control id=21 [slave keyboard (3)]
↳ Hantick USB Keyboard Wireless Radio Control id=26 [slave
keyboard (3)]
⎡ rgosplit pointer id=27 [master pointer (28)]
⎜ ↳ rgosplit XTEST pointer id=29 [slave pointer (27)]
⎣ rgosplit keyboard id=28 [master keyboard (27)]
↳ HID 0911:2188 System Control id=17 [slave keyboard (28)]
↳ HID 0911:2188 id=18 [slave keyboard (28)]
↳ HID 0911:2188 Consumer Control id=23 [slave keyboard (28)]
↳ rgosplit XTEST keyboard id=30 [slave keyboard (28)]
Now I can type with both keyboard halfs simultaneously in a gnome-terminal!
But when I switch to other applications, e.g. firefox, only one half can type...
Maybe someone can build up on this?
--
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 typing on 2 keyboards at the
same time
Status in GNOME Shell:
Unknown
Status in gnome-shell 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
