keyboard not responding after suspend after some time

[Krzysztof]

I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 18.10
GsettingsChanges:
 b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2018-08-06 (165 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
NonfreeKernelModules: nvidia_modeset nvidia
Package: gnome-shell 3.30.1-2ubuntu1.18.10.2
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Tags: cosmic
Uname: Linux 4.18.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True

[Sebastien Bacher (seb128)]

the description sounds a bit similar to bug #1807056

[Daniel van Vugt (vanvugt)]

Next time the keyboard stops responding, please try the workaround suggested in bug 1807056:

1. Click on Show Applications (bottom left corner).

2. Click on Type to search...

3. Start typing.

If that doesn't work around the problem then next please provide more information about your system by running:

  apport-collect 1812014

[Krzysztof (krzysztof-oracz)]

apport information

[Krzysztof (krzysztof-oracz)]

apport information

[Krzysztof (krzysztof-oracz)]

So... it happend again. The workaround doesn't work.

[Daniel van Vugt (vanvugt)]

Thanks.

Since we need each bug to be about a single issue, let's make this one about just the keyboard not responding. If you have other performance problems then please log a new bugs for those.

[Krzysztof (krzysztof-oracz)]

Hi,
I mentioned the performance problem because as I believe it is connected with not responding keyboard. If I notice a performance problem for instance during watching yt video I know that keyboard stopped working.

[Daniel van Vugt (vanvugt)]

OK then, maybe they are related. That's quite possible since gnome-shell is basically one single threaded event loop.

[Daniel van Vugt (vanvugt)]

I will still avoid mentioning "performance" in the bug title to stop other people from jumping on board thinking this is the same as their "performance" problems.

[Daniel van Vugt (vanvugt)]

Can you please:

1. Open a Terminal and run 'top'. Leave it running.

2. Suspend, resume and reproduce the bug.

3. About 10 seconds or more later, while the keyboard is not responding, please take a photo of the Terminal window with 'top' running in it.

4. Attach the photo here.

[Krzysztof (krzysztof-oracz)]

foto 1 of the terminal with running top command

[Krzysztof (krzysztof-oracz)]

Foto 2 of the terminal with running top command

[Krzysztof (krzysztof-oracz)]

Foto 3 of terminal with running top command

[Krzysztof (krzysztof-oracz)]

Hi,
I've attached three photos with running the top command. One of them looks normal but the others are not, I guess :)
I hope it will help.
The second thought: I updated the system about a week ago and now this bug happens after a much longer time... maybe this is by chance, but anyway I wanted to share this with you.

[Daniel van Vugt (vanvugt)]

Thanks, those photos are very helpful.

One shows 'upower' using 100% CPU and another shows 'kworker/6:0-events' using 100%. I wonder if that second one is related to Nvidia (like bug 1808108)...

Can you please run:

  dmesg > dmesg.txt

and send us the resulting file 'dmesg.txt'?

[Daniel van Vugt (vanvugt)]

Please also run:

  dpkg -l > dpkgl.txt

and send us the resulting file 'dpkgl.txt'.

[Krzysztof (krzysztof-oracz)]

dmesg

[Krzysztof (krzysztof-oracz)]

dpkg -l

[Daniel van Vugt (vanvugt)]

Thanks. Please also run 'xrandr' and send us the output.

[Krzysztof (krzysztof-oracz)]

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
   1920x1080 60.02*+ 60.01 59.97 59.96 59.93
   1680x1050 59.95 59.88
   1600x1024 60.17
   1400x1050 59.98
   1600x900 59.99 59.94 59.95 59.82
   1280x1024 60.02
   1440x900 59.89
   1400x900 59.96 59.88
   1280x960 60.00
   1440x810 60.00 59.97
   1368x768 59.88 59.85
   1360x768 59.80 59.96
   1280x800 59.99 59.97 59.81 59.91
   1152x864 60.00
   1280x720 60.00 59.99 59.86 59.74
   1024x768 60.04 60.00
   960x720 60.00
   928x696 60.05
   896x672 60.01
   1024x576 59.95 59.96 59.90 59.82
   960x600 59.93 60.00
   960x540 59.96 59.99 59.63 59.82
   800x600 60.00 60.32 56.25
   840x525 60.01 59.88
   864x486 59.92 59.57
   800x512 60.17
   700x525 59.98
   800x450 59.95 59.82
   640x512 60.02
   720x450 59.89
   700x450 59.96 59.88
   640x480 60.00 59.94
   720x405 59.51 58.99
   684x384 59.88 59.85
   680x384 59.80 59.96
   640x400 59.88 59.98
   576x432 60.06
   640x360 59.86 59.83 59.84 59.32
   512x384 60.00
   512x288 60.00 59.92
   480x270 59.63 59.82
   400x300 60.32 56.34
   432x243 59.92 59.57
   320x240 60.05
   360x202 59.51 59.13
   320x180 59.84 59.32

[Daniel van Vugt (vanvugt)]

Thanks. The best guess I can make is a problem in upower or the Nvidia driver (comment #15). Those are definitely performance problems (100% CPU for no obvious reason) and could well explain why the keyboard stops responding.

Maybe next we need to look at the system log in detail... If you can recover from the problem without rebooting then please run:

  journalctl -b0 > curlog.txt

If you have to reboot to recover from the problem then please run this after rebooting:

  journalctl -b-1 > prevlog.txt

and send us the resulting log file.

[Krzysztof (krzysztof-oracz)]

journalctl -b-1 > prevlog.txt

[Daniel van Vugt (vanvugt)]

Thanks.

There are a few unusual log messages coming from your gnome-shell which suggests some unusual extensions might be installed.

Please try removing all your gnome-shell extensions, reboot, and then tell us if the problem persists.

[Krzysztof (krzysztof-oracz)]

Hi,
I have no unusual extensions installed and even though I disabled all gnom extensions the problem remained.
After checking that, I did what I should have done at the beginning - I changed display driver to X.Org X Server nouveau and since then I have got no problems with the keyboard at all. So it clearly indicates that the problem is with nvidia-driver-390. As I haven't played any video games recently it doesn't' bother me, but it would be nice to have this driver working correctly.
Regards
Krzysztof

[Daniel van Vugt (vanvugt)]

I'm not sure how the Nvidia driver could be related.

Although this looks relevant to keyboard problems. This appears a few times in your log (comment #22):

sty 27 21:03:24 br00net gnome-shell[2527]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argument callback, got undefined
    setEngine@resource:///org/gnome/shell/misc/ibusManager.js:212:9
    wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
    activateInputSource@resource:///org/gnome/shell/ui/status/keyboard.js:490:13
    wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
    _emit@resource:///org/gnome/gjs/modules/signals.js:128:27
    activate@resource:///org/gnome/shell/ui/status/keyboard.js:65:9
    wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
    _inputSourcesChanged@resource:///org/gnome/shell/ui/status/keyboard.js:620:13
    wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
    reload@resource:///org/gnome/shell/ui/status/keyboard.js:369:9
    wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
    _ibusSetContentType@resource:///org/gnome/shell/ui/status/keyboard.js:691:9
    wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
    _emit@resource:///org/gnome/gjs/modules/signals.js:128:27
    _setContentType@resource:///org/gnome/shell/misc/ibusManager.js:188:9
    wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22

[Daniel van Vugt (vanvugt)]

Although ^^^ the above error ^^^ is already covered by bug 1812593.

[Krzysztof (krzysztof-oracz)]

Hi, recently I had changed the gpu driver to the latest one from nvidia nvidia-driver-418(opensource) and I since then, I started experiencing performance problems similar to those mentioned earlier: "'upower' using 100% CPU and another shows 'kworker/6:0-events' using 100%.". The prolems starts after suspending my system and bringing it back to life like previously, but this time keyboard is working fine.

[Daniel van Vugt (vanvugt)]

Please keep this bug about the keyboard only.

Performance issues should be logged as separate bugs, although it sounds like bug 1808108 is one of the issues.

[Launchpad Janitor (janitor)]

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for nvidia-graphics-drivers-390 (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for upower (Ubuntu) because there has been no activity for 60 days.]