Keyboard input lag in Ubuntu 18.04
Clash Royale CLAN TAG#URR8PPP up vote
8
down vote
favorite
I recently switched to Ubuntu 18.04 and since then I have
a lot of keyboard input lag, sometimes multiple seconds.
I can type the words but it takes some time until they show on the screen.
I previously used Ubuntu 16.04 without any issues.
This error occurs in Terminal but also in my web browser).
Any idea where I could start debugging this problem?
UPDATE:
So i tried the below suggested answers, thx for that.
But still no solution.
What I figured out is that this also may trigger by some
keys more than ohters ... for example when im typing cdcdcdcd
it appears really a lot.....
Also maybe important to know I use a different keyboard layout
which I set with
setxkbmap de neo (german neo layout) ( so cd is rl on asdf)
Altough this doesn't make a difference for the lag
UPDATE2:
Apparently this issues is only happening on the gnome/budgie desktop
keyboard 18.04
asked Apr 28 at 14:36
jrsm
14114
 |Â
show 2 more comments
up vote
8
down vote
favorite
I recently switched to Ubuntu 18.04 and since then I have
a lot of keyboard input lag, sometimes multiple seconds.
I can type the words but it takes some time until they show on the screen.
I previously used Ubuntu 16.04 without any issues.
This error occurs in Terminal but also in my web browser).
Any idea where I could start debugging this problem?
UPDATE:
So i tried the below suggested answers, thx for that.
But still no solution.
What I figured out is that this also may trigger by some
keys more than ohters ... for example when im typing cdcdcdcd
it appears really a lot.....
Also maybe important to know I use a different keyboard layout
which I set with
setxkbmap de neo (german neo layout) ( so cd is rl on asdf)
Altough this doesn't make a difference for the lag
UPDATE2:
Apparently this issues is only happening on the gnome/budgie desktop
keyboard 18.04
asked Apr 28 at 14:36
jrsm
14114
I had a similar experience with USB keyboard. Switching back to Unity helped. If that is an option, there is a guide linuxconfig.org/…
– logcat
May 14 at 19:01
I have to say im really not a big fan of unity :(
– jrsm
May 16 at 19:31
I think I have the same issue. Some observations: 1) If I drop to a non-graphical shell, there's no problem. 2) In Gnome: It's not just the keyboard input that's freezing, but most of the UI. I've enabled seconds in my clock and they also freeze for a while after multiple keypresses. But the mouse pointer is still moving around if I move the mouse. 3) This is not an issue with all keyboards. My old Logitech keyboard with the Unifying Receiver works fine. 4) The affected keyboard works fine with Windows and MacOS on other computers. 5) Nothing of significance in my syslog.
– decibyte
Jun 19 at 14:25
Okay, a few more observations: If I connect 2 Logitech keyboards and type on them at the same time, I experience the same issue. This might sound like an unusual use case, but my usual keyboard is an ergonomic R-Go Split Keyboard -- an abnormality which is technically two separate keyboards (each with only half they keys of a normal keyboard). A combination of one half and a Logitech keyboard gives the same result. Along with my above observations: Does that give anyone any idea about what's going on? Especially with that fact that it only occurs (for me) in Gnome(3).
– decibyte
Jun 19 at 14:47
I don't know if you also happen to be in a dual keyboard typing situation like me. But for the record, I've opened a bug with my own observations: bugs.launchpad.net/ubuntu/+bug/1777708
– decibyte
Jun 19 at 18:57
 |Â
show 2 more comments
up vote
8
down vote
favorite
up vote
8
down vote
favorite
I recently switched to Ubuntu 18.04 and since then I have
a lot of keyboard input lag, sometimes multiple seconds.
I can type the words but it takes some time until they show on the screen.
I previously used Ubuntu 16.04 without any issues.
This error occurs in Terminal but also in my web browser).
Any idea where I could start debugging this problem?
UPDATE:
So i tried the below suggested answers, thx for that.
But still no solution.
What I figured out is that this also may trigger by some
keys more than ohters ... for example when im typing cdcdcdcd
it appears really a lot.....
Also maybe important to know I use a different keyboard layout
which I set with
setxkbmap de neo (german neo layout) ( so cd is rl on asdf)
Altough this doesn't make a difference for the lag
UPDATE2:
Apparently this issues is only happening on the gnome/budgie desktop
keyboard 18.04
asked Apr 28 at 14:36
jrsm
14114
I recently switched to Ubuntu 18.04 and since then I have
a lot of keyboard input lag, sometimes multiple seconds.
I can type the words but it takes some time until they show on the screen.
I previously used Ubuntu 16.04 without any issues.
This error occurs in Terminal but also in my web browser).
Any idea where I could start debugging this problem?
UPDATE:
So i tried the below suggested answers, thx for that.
But still no solution.
What I figured out is that this also may trigger by some
keys more than ohters ... for example when im typing cdcdcdcd
it appears really a lot.....
Also maybe important to know I use a different keyboard layout
which I set with
setxkbmap de neo (german neo layout) ( so cd is rl on asdf)
Altough this doesn't make a difference for the lag
UPDATE2:
Apparently this issues is only happening on the gnome/budgie desktop
keyboard 18.04
asked Apr 28 at 14:36
jrsm
14114
edited May 19 at 16:41
asked Apr 28 at 14:36
jrsm
14114
asked Apr 28 at 14:36
jrsm
14114
asked Apr 28 at 14:36
jrsm
14114
14114
I had a similar experience with USB keyboard. Switching back to Unity helped. If that is an option, there is a guide linuxconfig.org/…
– logcat
May 14 at 19:01
I have to say im really not a big fan of unity :(
– jrsm
May 16 at 19:31
I think I have the same issue. Some observations: 1) If I drop to a non-graphical shell, there's no problem. 2) In Gnome: It's not just the keyboard input that's freezing, but most of the UI. I've enabled seconds in my clock and they also freeze for a while after multiple keypresses. But the mouse pointer is still moving around if I move the mouse. 3) This is not an issue with all keyboards. My old Logitech keyboard with the Unifying Receiver works fine. 4) The affected keyboard works fine with Windows and MacOS on other computers. 5) Nothing of significance in my syslog.
– decibyte
Jun 19 at 14:25
Okay, a few more observations: If I connect 2 Logitech keyboards and type on them at the same time, I experience the same issue. This might sound like an unusual use case, but my usual keyboard is an ergonomic R-Go Split Keyboard -- an abnormality which is technically two separate keyboards (each with only half they keys of a normal keyboard). A combination of one half and a Logitech keyboard gives the same result. Along with my above observations: Does that give anyone any idea about what's going on? Especially with that fact that it only occurs (for me) in Gnome(3).
– decibyte
Jun 19 at 14:47
I don't know if you also happen to be in a dual keyboard typing situation like me. But for the record, I've opened a bug with my own observations: bugs.launchpad.net/ubuntu/+bug/1777708
– decibyte
Jun 19 at 18:57
 |Â
show 2 more comments
I had a similar experience with USB keyboard. Switching back to Unity helped. If that is an option, there is a guide linuxconfig.org/…
– logcat
May 14 at 19:01
I have to say im really not a big fan of unity :(
– jrsm
May 16 at 19:31
I think I have the same issue. Some observations: 1) If I drop to a non-graphical shell, there's no problem. 2) In Gnome: It's not just the keyboard input that's freezing, but most of the UI. I've enabled seconds in my clock and they also freeze for a while after multiple keypresses. But the mouse pointer is still moving around if I move the mouse. 3) This is not an issue with all keyboards. My old Logitech keyboard with the Unifying Receiver works fine. 4) The affected keyboard works fine with Windows and MacOS on other computers. 5) Nothing of significance in my syslog.
– decibyte
Jun 19 at 14:25
Okay, a few more observations: If I connect 2 Logitech keyboards and type on them at the same time, I experience the same issue. This might sound like an unusual use case, but my usual keyboard is an ergonomic R-Go Split Keyboard -- an abnormality which is technically two separate keyboards (each with only half they keys of a normal keyboard). A combination of one half and a Logitech keyboard gives the same result. Along with my above observations: Does that give anyone any idea about what's going on? Especially with that fact that it only occurs (for me) in Gnome(3).
– decibyte
Jun 19 at 14:47
I don't know if you also happen to be in a dual keyboard typing situation like me. But for the record, I've opened a bug with my own observations: bugs.launchpad.net/ubuntu/+bug/1777708
– decibyte
Jun 19 at 18:57
I had a similar experience with USB keyboard. Switching back to Unity helped. If that is an option, there is a guide linuxconfig.org/…
– logcat
May 14 at 19:01
I had a similar experience with USB keyboard. Switching back to Unity helped. If that is an option, there is a guide linuxconfig.org/…
– logcat
May 14 at 19:01
I have to say im really not a big fan of unity :(
– jrsm
May 16 at 19:31
I have to say im really not a big fan of unity :(
– jrsm
May 16 at 19:31
I think I have the same issue. Some observations: 1) If I drop to a non-graphical shell, there's no problem. 2) In Gnome: It's not just the keyboard input that's freezing, but most of the UI. I've enabled seconds in my clock and they also freeze for a while after multiple keypresses. But the mouse pointer is still moving around if I move the mouse. 3) This is not an issue with all keyboards. My old Logitech keyboard with the Unifying Receiver works fine. 4) The affected keyboard works fine with Windows and MacOS on other computers. 5) Nothing of significance in my syslog.
– decibyte
Jun 19 at 14:25
I think I have the same issue. Some observations: 1) If I drop to a non-graphical shell, there's no problem. 2) In Gnome: It's not just the keyboard input that's freezing, but most of the UI. I've enabled seconds in my clock and they also freeze for a while after multiple keypresses. But the mouse pointer is still moving around if I move the mouse. 3) This is not an issue with all keyboards. My old Logitech keyboard with the Unifying Receiver works fine. 4) The affected keyboard works fine with Windows and MacOS on other computers. 5) Nothing of significance in my syslog.
– decibyte
Jun 19 at 14:25
Okay, a few more observations: If I connect 2 Logitech keyboards and type on them at the same time, I experience the same issue. This might sound like an unusual use case, but my usual keyboard is an ergonomic R-Go Split Keyboard -- an abnormality which is technically two separate keyboards (each with only half they keys of a normal keyboard). A combination of one half and a Logitech keyboard gives the same result. Along with my above observations: Does that give anyone any idea about what's going on? Especially with that fact that it only occurs (for me) in Gnome(3).
– decibyte
Jun 19 at 14:47
Okay, a few more observations: If I connect 2 Logitech keyboards and type on them at the same time, I experience the same issue. This might sound like an unusual use case, but my usual keyboard is an ergonomic R-Go Split Keyboard -- an abnormality which is technically two separate keyboards (each with only half they keys of a normal keyboard). A combination of one half and a Logitech keyboard gives the same result. Along with my above observations: Does that give anyone any idea about what's going on? Especially with that fact that it only occurs (for me) in Gnome(3).
– decibyte
Jun 19 at 14:47
I don't know if you also happen to be in a dual keyboard typing situation like me. But for the record, I've opened a bug with my own observations: bugs.launchpad.net/ubuntu/+bug/1777708
– decibyte
Jun 19 at 18:57
I don't know if you also happen to be in a dual keyboard typing situation like me. But for the record, I've opened a bug with my own observations: bugs.launchpad.net/ubuntu/+bug/1777708
– decibyte
Jun 19 at 18:57
 |Â
show 2 more comments
4 Answers
4
active
oldest
votes
up vote
4
down vote
Maybe you could try your system log. I have noticed the following error on my system (multiple times):
xhci_hcd 0000:3a:00.0: xHCI host controller not responding, assume dead
This seems to be a USB3 problem. My keyboard and touch-pad on my laptop do not have this problem. My USB connected mouse also lags.
When I load Ubuntu 18.04 with the previous and still available kernel on my system as used in 17.10, kernel version 4.13.0-39-generic, I do not get the XHCI errors. Also, my keyboard and mouse do not lag anymore.
I am able to select this kernel via the GRUB menu in my setup.
Remark
I have not figured it out completely yet. The older kernel appears to work better but the lag is there every now and again. I can make some remarks when using the default kernel: A continuous key press (just holding a letter or character) is doing fine. It just outputs the letter or character constantly without jitter. Also, just entering letters are fine. Where I think it is going wrong with my setup are special characters like (Commas, periods, colons, semicolons, etc.). As soon as those are introduced to the input it stars going wrong. Initially I thought this might be caused by dead keys but switching those off do not make a difference. Can you confirm this behavior? Also, slow keys do not solve it on my setup.
Update
This morning I got an update which seems to solve the keyboard problem on my site. From my update log:
Commandline: aptdaemon role='role-commit-packages' sender=':1.147'
Upgrade: intel-microcode:amd64 (3.20180312.0~ubuntu18.04.1, 3.20180425.1~ubuntu0.18.04.1)
This is the only update for 18.04 I got so far. This probably also solved the slow boot times on my Laptop. It's now seconds in stead of a minute. I will send a confirmation later this week.
answered Apr 30 at 16:37
André Klaver
413
Thank you for the reply, xhci_hcd looks good on my syslog file, however
– jrsm
May 1 at 16:22
xhci loos good on my sys log hower I get often something like 1 18:19:54 ryzen gnome-software[2177]: json_object_has_member: assertion 'member_name != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strsplit: assertion 'string != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strv_length: assertion 'str_array != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: json_object_has_member: assertion 'member_name != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strsplit: assertion 'string != NULL' failed
– jrsm
May 1 at 16:24
I have not figured it out completely yet. The older kernel appears to work better but the lag is there every now and again. I can make some remarks:
– André Klaver
May 3 at 8:47
I'd be curious to know more about this issue you had. Did you ever file a bug report? If this is a real bug, it's going to affect a lot of people, as more and more users are moving to 18.04 & also more and more machines are using USB 3.0
– Emily
May 4 at 18:02
add a comment |Â
up vote
1
down vote
This may be the slow keys feature
It is toggled on and off by holding down the shift key for 8 seconds
Press the shift key for 8 seconds and see if the problem goes away
answered May 1 at 16:30
Jim Anthony
111
1
Might be good to note that in order for this feature to be toggled on/off using the shift key, the user has to first change their system settings to enable the shortcut. See Ubuntu Help: Turn On Slow Keys
– Emily
May 1 at 16:37
Except that it appears to be enabled by default :/ I never enabled it and this solved my problem
– Jim Anthony
May 1 at 16:51
Oh weird! It wasn't enabled by default on my system, but actually I was going to phrase my comment to include for the fact that it's possible that it might be for some users, because it totally seemed possible to me. Anyway hopefully this fixes it for the question-asker!
– Emily
May 1 at 22:36
This does nothing at all.
– LuÃs de Sousa
Aug 21 at 15:25
add a comment |Â
up vote
0
down vote
I had this happen on my main laptop computer when playing Terraria, when playing on my "new desktop" with such amazing parts as ddr2 ram and a dual core e8600 and USB 2.0, I had no latency, I could not even see any input lag when comparing a low end wireless keyboard to a ps2 mechanical keyboard. A computer restart and plugging it in helped. For me I think it was because the system's battery was low and it wasn't plugged in.
answered May 1 at 17:51
Tyler Pluim
187
add a comment |Â
up vote
0
down vote
I had the same issue with my favorite keyboard. All my other keyboards where working fine.
I solved the problem by switching to wayland.
You can do this with the gear button next to the sign in button at the login screen.
answered Jul 26 at 6:11
Flom
1
add a comment |Â
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
Maybe you could try your system log. I have noticed the following error on my system (multiple times):
xhci_hcd 0000:3a:00.0: xHCI host controller not responding, assume dead
This seems to be a USB3 problem. My keyboard and touch-pad on my laptop do not have this problem. My USB connected mouse also lags.
When I load Ubuntu 18.04 with the previous and still available kernel on my system as used in 17.10, kernel version 4.13.0-39-generic, I do not get the XHCI errors. Also, my keyboard and mouse do not lag anymore.
I am able to select this kernel via the GRUB menu in my setup.
Remark
I have not figured it out completely yet. The older kernel appears to work better but the lag is there every now and again. I can make some remarks when using the default kernel: A continuous key press (just holding a letter or character) is doing fine. It just outputs the letter or character constantly without jitter. Also, just entering letters are fine. Where I think it is going wrong with my setup are special characters like (Commas, periods, colons, semicolons, etc.). As soon as those are introduced to the input it stars going wrong. Initially I thought this might be caused by dead keys but switching those off do not make a difference. Can you confirm this behavior? Also, slow keys do not solve it on my setup.
Update
This morning I got an update which seems to solve the keyboard problem on my site. From my update log:
Commandline: aptdaemon role='role-commit-packages' sender=':1.147'
Upgrade: intel-microcode:amd64 (3.20180312.0~ubuntu18.04.1, 3.20180425.1~ubuntu0.18.04.1)
This is the only update for 18.04 I got so far. This probably also solved the slow boot times on my Laptop. It's now seconds in stead of a minute. I will send a confirmation later this week.
answered Apr 30 at 16:37
André Klaver
413
Thank you for the reply, xhci_hcd looks good on my syslog file, however
– jrsm
May 1 at 16:22
xhci loos good on my sys log hower I get often something like 1 18:19:54 ryzen gnome-software[2177]: json_object_has_member: assertion 'member_name != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strsplit: assertion 'string != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strv_length: assertion 'str_array != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: json_object_has_member: assertion 'member_name != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strsplit: assertion 'string != NULL' failed
– jrsm
May 1 at 16:24
I have not figured it out completely yet. The older kernel appears to work better but the lag is there every now and again. I can make some remarks:
– André Klaver
May 3 at 8:47
I'd be curious to know more about this issue you had. Did you ever file a bug report? If this is a real bug, it's going to affect a lot of people, as more and more users are moving to 18.04 & also more and more machines are using USB 3.0
– Emily
May 4 at 18:02
add a comment |Â
up vote
4
down vote
Maybe you could try your system log. I have noticed the following error on my system (multiple times):
xhci_hcd 0000:3a:00.0: xHCI host controller not responding, assume dead
This seems to be a USB3 problem. My keyboard and touch-pad on my laptop do not have this problem. My USB connected mouse also lags.
When I load Ubuntu 18.04 with the previous and still available kernel on my system as used in 17.10, kernel version 4.13.0-39-generic, I do not get the XHCI errors. Also, my keyboard and mouse do not lag anymore.
I am able to select this kernel via the GRUB menu in my setup.
Remark
I have not figured it out completely yet. The older kernel appears to work better but the lag is there every now and again. I can make some remarks when using the default kernel: A continuous key press (just holding a letter or character) is doing fine. It just outputs the letter or character constantly without jitter. Also, just entering letters are fine. Where I think it is going wrong with my setup are special characters like (Commas, periods, colons, semicolons, etc.). As soon as those are introduced to the input it stars going wrong. Initially I thought this might be caused by dead keys but switching those off do not make a difference. Can you confirm this behavior? Also, slow keys do not solve it on my setup.
Update
This morning I got an update which seems to solve the keyboard problem on my site. From my update log:
Commandline: aptdaemon role='role-commit-packages' sender=':1.147'
Upgrade: intel-microcode:amd64 (3.20180312.0~ubuntu18.04.1, 3.20180425.1~ubuntu0.18.04.1)
This is the only update for 18.04 I got so far. This probably also solved the slow boot times on my Laptop. It's now seconds in stead of a minute. I will send a confirmation later this week.
answered Apr 30 at 16:37
André Klaver
413
Thank you for the reply, xhci_hcd looks good on my syslog file, however
– jrsm
May 1 at 16:22
xhci loos good on my sys log hower I get often something like 1 18:19:54 ryzen gnome-software[2177]: json_object_has_member: assertion 'member_name != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strsplit: assertion 'string != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strv_length: assertion 'str_array != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: json_object_has_member: assertion 'member_name != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strsplit: assertion 'string != NULL' failed
– jrsm
May 1 at 16:24
I have not figured it out completely yet. The older kernel appears to work better but the lag is there every now and again. I can make some remarks:
– André Klaver
May 3 at 8:47
I'd be curious to know more about this issue you had. Did you ever file a bug report? If this is a real bug, it's going to affect a lot of people, as more and more users are moving to 18.04 & also more and more machines are using USB 3.0
– Emily
May 4 at 18:02
add a comment |Â
up vote
4
down vote
up vote
4
down vote
Maybe you could try your system log. I have noticed the following error on my system (multiple times):
xhci_hcd 0000:3a:00.0: xHCI host controller not responding, assume dead
This seems to be a USB3 problem. My keyboard and touch-pad on my laptop do not have this problem. My USB connected mouse also lags.
When I load Ubuntu 18.04 with the previous and still available kernel on my system as used in 17.10, kernel version 4.13.0-39-generic, I do not get the XHCI errors. Also, my keyboard and mouse do not lag anymore.
I am able to select this kernel via the GRUB menu in my setup.
Remark
I have not figured it out completely yet. The older kernel appears to work better but the lag is there every now and again. I can make some remarks when using the default kernel: A continuous key press (just holding a letter or character) is doing fine. It just outputs the letter or character constantly without jitter. Also, just entering letters are fine. Where I think it is going wrong with my setup are special characters like (Commas, periods, colons, semicolons, etc.). As soon as those are introduced to the input it stars going wrong. Initially I thought this might be caused by dead keys but switching those off do not make a difference. Can you confirm this behavior? Also, slow keys do not solve it on my setup.
Update
This morning I got an update which seems to solve the keyboard problem on my site. From my update log:
Commandline: aptdaemon role='role-commit-packages' sender=':1.147'
Upgrade: intel-microcode:amd64 (3.20180312.0~ubuntu18.04.1, 3.20180425.1~ubuntu0.18.04.1)
This is the only update for 18.04 I got so far. This probably also solved the slow boot times on my Laptop. It's now seconds in stead of a minute. I will send a confirmation later this week.
answered Apr 30 at 16:37
André Klaver
413
Maybe you could try your system log. I have noticed the following error on my system (multiple times):
xhci_hcd 0000:3a:00.0: xHCI host controller not responding, assume dead
This seems to be a USB3 problem. My keyboard and touch-pad on my laptop do not have this problem. My USB connected mouse also lags.
When I load Ubuntu 18.04 with the previous and still available kernel on my system as used in 17.10, kernel version 4.13.0-39-generic, I do not get the XHCI errors. Also, my keyboard and mouse do not lag anymore.
I am able to select this kernel via the GRUB menu in my setup.
Remark
I have not figured it out completely yet. The older kernel appears to work better but the lag is there every now and again. I can make some remarks when using the default kernel: A continuous key press (just holding a letter or character) is doing fine. It just outputs the letter or character constantly without jitter. Also, just entering letters are fine. Where I think it is going wrong with my setup are special characters like (Commas, periods, colons, semicolons, etc.). As soon as those are introduced to the input it stars going wrong. Initially I thought this might be caused by dead keys but switching those off do not make a difference. Can you confirm this behavior? Also, slow keys do not solve it on my setup.
Update
This morning I got an update which seems to solve the keyboard problem on my site. From my update log:
Commandline: aptdaemon role='role-commit-packages' sender=':1.147'
Upgrade: intel-microcode:amd64 (3.20180312.0~ubuntu18.04.1, 3.20180425.1~ubuntu0.18.04.1)
This is the only update for 18.04 I got so far. This probably also solved the slow boot times on my Laptop. It's now seconds in stead of a minute. I will send a confirmation later this week.
answered Apr 30 at 16:37
André Klaver
413
edited May 8 at 4:29
answered Apr 30 at 16:37
André Klaver
413
answered Apr 30 at 16:37
André Klaver
413
answered Apr 30 at 16:37
André Klaver
413
413
Thank you for the reply, xhci_hcd looks good on my syslog file, however
– jrsm
May 1 at 16:22
xhci loos good on my sys log hower I get often something like 1 18:19:54 ryzen gnome-software[2177]: json_object_has_member: assertion 'member_name != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strsplit: assertion 'string != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strv_length: assertion 'str_array != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: json_object_has_member: assertion 'member_name != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strsplit: assertion 'string != NULL' failed
– jrsm
May 1 at 16:24
I have not figured it out completely yet. The older kernel appears to work better but the lag is there every now and again. I can make some remarks:
– André Klaver
May 3 at 8:47
I'd be curious to know more about this issue you had. Did you ever file a bug report? If this is a real bug, it's going to affect a lot of people, as more and more users are moving to 18.04 & also more and more machines are using USB 3.0
– Emily
May 4 at 18:02
add a comment |Â
Thank you for the reply, xhci_hcd looks good on my syslog file, however
– jrsm
May 1 at 16:22
xhci loos good on my sys log hower I get often something like 1 18:19:54 ryzen gnome-software[2177]: json_object_has_member: assertion 'member_name != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strsplit: assertion 'string != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strv_length: assertion 'str_array != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: json_object_has_member: assertion 'member_name != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strsplit: assertion 'string != NULL' failed
– jrsm
May 1 at 16:24
I have not figured it out completely yet. The older kernel appears to work better but the lag is there every now and again. I can make some remarks:
– André Klaver
May 3 at 8:47
I'd be curious to know more about this issue you had. Did you ever file a bug report? If this is a real bug, it's going to affect a lot of people, as more and more users are moving to 18.04 & also more and more machines are using USB 3.0
– Emily
May 4 at 18:02
Thank you for the reply, xhci_hcd looks good on my syslog file, however
– jrsm
May 1 at 16:22
Thank you for the reply, xhci_hcd looks good on my syslog file, however
– jrsm
May 1 at 16:22
xhci loos good on my sys log hower I get often something like 1 18:19:54 ryzen gnome-software[2177]: json_object_has_member: assertion 'member_name != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strsplit: assertion 'string != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strv_length: assertion 'str_array != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: json_object_has_member: assertion 'member_name != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strsplit: assertion 'string != NULL' failed
– jrsm
May 1 at 16:24
xhci loos good on my sys log hower I get often something like 1 18:19:54 ryzen gnome-software[2177]: json_object_has_member: assertion 'member_name != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strsplit: assertion 'string != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strv_length: assertion 'str_array != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: json_object_has_member: assertion 'member_name != NULL' failed May 1 18:19:54 ryzen gnome-software[2177]: g_strsplit: assertion 'string != NULL' failed
– jrsm
May 1 at 16:24
I have not figured it out completely yet. The older kernel appears to work better but the lag is there every now and again. I can make some remarks:
– André Klaver
May 3 at 8:47
I have not figured it out completely yet. The older kernel appears to work better but the lag is there every now and again. I can make some remarks:
– André Klaver
May 3 at 8:47
I'd be curious to know more about this issue you had. Did you ever file a bug report? If this is a real bug, it's going to affect a lot of people, as more and more users are moving to 18.04 & also more and more machines are using USB 3.0
– Emily
May 4 at 18:02
I'd be curious to know more about this issue you had. Did you ever file a bug report? If this is a real bug, it's going to affect a lot of people, as more and more users are moving to 18.04 & also more and more machines are using USB 3.0
– Emily
May 4 at 18:02
add a comment |Â
up vote
1
down vote
This may be the slow keys feature
It is toggled on and off by holding down the shift key for 8 seconds
Press the shift key for 8 seconds and see if the problem goes away
answered May 1 at 16:30
Jim Anthony
111
1
Might be good to note that in order for this feature to be toggled on/off using the shift key, the user has to first change their system settings to enable the shortcut. See Ubuntu Help: Turn On Slow Keys
– Emily
May 1 at 16:37
Except that it appears to be enabled by default :/ I never enabled it and this solved my problem
– Jim Anthony
May 1 at 16:51
Oh weird! It wasn't enabled by default on my system, but actually I was going to phrase my comment to include for the fact that it's possible that it might be for some users, because it totally seemed possible to me. Anyway hopefully this fixes it for the question-asker!
– Emily
May 1 at 22:36
This does nothing at all.
– LuÃs de Sousa
Aug 21 at 15:25
add a comment |Â
up vote
1
down vote
This may be the slow keys feature
It is toggled on and off by holding down the shift key for 8 seconds
Press the shift key for 8 seconds and see if the problem goes away
answered May 1 at 16:30
Jim Anthony
111
1
Might be good to note that in order for this feature to be toggled on/off using the shift key, the user has to first change their system settings to enable the shortcut. See Ubuntu Help: Turn On Slow Keys
– Emily
May 1 at 16:37
Except that it appears to be enabled by default :/ I never enabled it and this solved my problem
– Jim Anthony
May 1 at 16:51
Oh weird! It wasn't enabled by default on my system, but actually I was going to phrase my comment to include for the fact that it's possible that it might be for some users, because it totally seemed possible to me. Anyway hopefully this fixes it for the question-asker!
– Emily
May 1 at 22:36
This does nothing at all.
– LuÃs de Sousa
Aug 21 at 15:25
add a comment |Â
up vote
1
down vote
up vote
1
down vote
This may be the slow keys feature
It is toggled on and off by holding down the shift key for 8 seconds
Press the shift key for 8 seconds and see if the problem goes away
answered May 1 at 16:30
Jim Anthony
111
This may be the slow keys feature
It is toggled on and off by holding down the shift key for 8 seconds
Press the shift key for 8 seconds and see if the problem goes away
answered May 1 at 16:30
Jim Anthony
111
answered May 1 at 16:30
Jim Anthony
111
answered May 1 at 16:30
Jim Anthony
111
answered May 1 at 16:30
Jim Anthony
111
111
1
Might be good to note that in order for this feature to be toggled on/off using the shift key, the user has to first change their system settings to enable the shortcut. See Ubuntu Help: Turn On Slow Keys
– Emily
May 1 at 16:37
Except that it appears to be enabled by default :/ I never enabled it and this solved my problem
– Jim Anthony
May 1 at 16:51
Oh weird! It wasn't enabled by default on my system, but actually I was going to phrase my comment to include for the fact that it's possible that it might be for some users, because it totally seemed possible to me. Anyway hopefully this fixes it for the question-asker!
– Emily
May 1 at 22:36
This does nothing at all.
– LuÃs de Sousa
Aug 21 at 15:25
add a comment |Â
1
Might be good to note that in order for this feature to be toggled on/off using the shift key, the user has to first change their system settings to enable the shortcut. See Ubuntu Help: Turn On Slow Keys
– Emily
May 1 at 16:37
Except that it appears to be enabled by default :/ I never enabled it and this solved my problem
– Jim Anthony
May 1 at 16:51
Oh weird! It wasn't enabled by default on my system, but actually I was going to phrase my comment to include for the fact that it's possible that it might be for some users, because it totally seemed possible to me. Anyway hopefully this fixes it for the question-asker!
– Emily
May 1 at 22:36
This does nothing at all.
– LuÃs de Sousa
Aug 21 at 15:25
1
1
Might be good to note that in order for this feature to be toggled on/off using the shift key, the user has to first change their system settings to enable the shortcut. See Ubuntu Help: Turn On Slow Keys
– Emily
May 1 at 16:37
Might be good to note that in order for this feature to be toggled on/off using the shift key, the user has to first change their system settings to enable the shortcut. See Ubuntu Help: Turn On Slow Keys
– Emily
May 1 at 16:37
Except that it appears to be enabled by default :/ I never enabled it and this solved my problem
– Jim Anthony
May 1 at 16:51
Except that it appears to be enabled by default :/ I never enabled it and this solved my problem
– Jim Anthony
May 1 at 16:51
Oh weird! It wasn't enabled by default on my system, but actually I was going to phrase my comment to include for the fact that it's possible that it might be for some users, because it totally seemed possible to me. Anyway hopefully this fixes it for the question-asker!
– Emily
May 1 at 22:36
Oh weird! It wasn't enabled by default on my system, but actually I was going to phrase my comment to include for the fact that it's possible that it might be for some users, because it totally seemed possible to me. Anyway hopefully this fixes it for the question-asker!
– Emily
May 1 at 22:36
This does nothing at all.
– LuÃs de Sousa
Aug 21 at 15:25
This does nothing at all.
– LuÃs de Sousa
Aug 21 at 15:25
add a comment |Â
up vote
0
down vote
I had this happen on my main laptop computer when playing Terraria, when playing on my "new desktop" with such amazing parts as ddr2 ram and a dual core e8600 and USB 2.0, I had no latency, I could not even see any input lag when comparing a low end wireless keyboard to a ps2 mechanical keyboard. A computer restart and plugging it in helped. For me I think it was because the system's battery was low and it wasn't plugged in.
answered May 1 at 17:51
Tyler Pluim
187
add a comment |Â
up vote
0
down vote
I had this happen on my main laptop computer when playing Terraria, when playing on my "new desktop" with such amazing parts as ddr2 ram and a dual core e8600 and USB 2.0, I had no latency, I could not even see any input lag when comparing a low end wireless keyboard to a ps2 mechanical keyboard. A computer restart and plugging it in helped. For me I think it was because the system's battery was low and it wasn't plugged in.
answered May 1 at 17:51
Tyler Pluim
187
add a comment |Â
up vote
0
down vote
up vote
0
down vote
I had this happen on my main laptop computer when playing Terraria, when playing on my "new desktop" with such amazing parts as ddr2 ram and a dual core e8600 and USB 2.0, I had no latency, I could not even see any input lag when comparing a low end wireless keyboard to a ps2 mechanical keyboard. A computer restart and plugging it in helped. For me I think it was because the system's battery was low and it wasn't plugged in.
answered May 1 at 17:51
Tyler Pluim
187
I had this happen on my main laptop computer when playing Terraria, when playing on my "new desktop" with such amazing parts as ddr2 ram and a dual core e8600 and USB 2.0, I had no latency, I could not even see any input lag when comparing a low end wireless keyboard to a ps2 mechanical keyboard. A computer restart and plugging it in helped. For me I think it was because the system's battery was low and it wasn't plugged in.
answered May 1 at 17:51
Tyler Pluim
187
answered May 1 at 17:51
Tyler Pluim
187
answered May 1 at 17:51
Tyler Pluim
187
answered May 1 at 17:51
Tyler Pluim
187
187
add a comment |Â
add a comment |Â
up vote
0
down vote
I had the same issue with my favorite keyboard. All my other keyboards where working fine.
I solved the problem by switching to wayland.
You can do this with the gear button next to the sign in button at the login screen.
answered Jul 26 at 6:11
Flom
1
add a comment |Â
up vote
0
down vote
I had the same issue with my favorite keyboard. All my other keyboards where working fine.
I solved the problem by switching to wayland.
You can do this with the gear button next to the sign in button at the login screen.
answered Jul 26 at 6:11
Flom
1
add a comment |Â
up vote
0
down vote
up vote
0
down vote
I had the same issue with my favorite keyboard. All my other keyboards where working fine.
I solved the problem by switching to wayland.
You can do this with the gear button next to the sign in button at the login screen.
answered Jul 26 at 6:11
Flom
1
I had the same issue with my favorite keyboard. All my other keyboards where working fine.
I solved the problem by switching to wayland.
You can do this with the gear button next to the sign in button at the login screen.
answered Jul 26 at 6:11
Flom
1
answered Jul 26 at 6:11
Flom
1
answered Jul 26 at 6:11
Flom
1
answered Jul 26 at 6:11
Flom
1
1
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1029256%2fkeyboard-input-lag-in-ubuntu-18-04%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
I had a similar experience with USB keyboard. Switching back to Unity helped. If that is an option, there is a guide linuxconfig.org/…
– logcat
May 14 at 19:01
I have to say im really not a big fan of unity :(
– jrsm
May 16 at 19:31
I think I have the same issue. Some observations: 1) If I drop to a non-graphical shell, there's no problem. 2) In Gnome: It's not just the keyboard input that's freezing, but most of the UI. I've enabled seconds in my clock and they also freeze for a while after multiple keypresses. But the mouse pointer is still moving around if I move the mouse. 3) This is not an issue with all keyboards. My old Logitech keyboard with the Unifying Receiver works fine. 4) The affected keyboard works fine with Windows and MacOS on other computers. 5) Nothing of significance in my syslog.
– decibyte
Jun 19 at 14:25
Okay, a few more observations: If I connect 2 Logitech keyboards and type on them at the same time, I experience the same issue. This might sound like an unusual use case, but my usual keyboard is an ergonomic R-Go Split Keyboard -- an abnormality which is technically two separate keyboards (each with only half they keys of a normal keyboard). A combination of one half and a Logitech keyboard gives the same result. Along with my above observations: Does that give anyone any idea about what's going on? Especially with that fact that it only occurs (for me) in Gnome(3).
– decibyte
Jun 19 at 14:47
I don't know if you also happen to be in a dual keyboard typing situation like me. But for the record, I've opened a bug with my own observations: bugs.launchpad.net/ubuntu/+bug/1777708
– decibyte
Jun 19 at 18:57