I installed debug symbols for libinput and had a look at the core file, and it looks very much like this:
https://bugs.freedesktop.org/show_bug.cgi?id=103298 I am missing the top frame in that stack trace, but I am guessing that is just chance based on when I took the trace. The description of how to trigger it looks like it could apply too. In any case, here is my trace: (gdb) bt #0 0x00007f6b37a2ccc7 in post_device_event (device=device@entry=0x56373d197e80, time=time@entry=1377003141, type=type@entry= LIBINPUT_EVENT_KEYBOARD_KEY, event=0x56373e972770) at libinput.c:2312 #1 0x00007f6b37a2df5f in keyboard_notify_key (device=device@entry=0x56373d197e80, time=time@entry=1377003141, key=<optimized out>, state=<optimized out>) at libinput.c:2412 #2 0x00007f6b37a30ab7 in fallback_keyboard_notify_key (device=device@entry=0x56373d197e80, time=time@entry=1377003141, key=<optimized out>, state=<optimized out>, dispatch=<optimized out>) at evdev.c:173 #3 0x00007f6b37a339b3 in fallback_process_key (e=0x7ffe3b444aa0, e=0x7ffe3b444aa0, time=1377003141, device=0x56373d197e80, dispatch=<optimized out>) at evdev.c:969 #4 0x00007f6b37a339b3 in fallback_process (evdev_dispatch=<optimized out>, device=0x56373d197e80, event=0x7ffe3b444aa0, time=1377003141) at evdev.c:1301 #5 0x00007f6b37a31159 in evdev_process_event (e=0x7ffe3b444aa0, device=0x56373d197e80) at evdev.c:2052 #6 0x00007f6b37a31159 in evdev_device_dispatch_one (ev=0x7ffe3b444aa0, device=0x56373d197e80) at evdev.c:2060 #7 0x00007f6b37a31159 in evdev_device_dispatch (data=0x56373d197e80) at evdev.c:2119 #8 0x00007f6b37a2cdaf in libinput_dispatch (libinput=0x56373d123d60) at libinput.c:2196 #9 0x00007f6b4113be9c in () ---Type <return> to continue, or q <return> to quit--- at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-1.so #10 0x00007f6b424c2fb7 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x00007f6b424c31f0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x00007f6b424c3502 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x00007f6b409f868c in meta_run () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 #14 0x000056373c9ec2e7 in () #15 0x00007f6b4038a1c1 in __libc_start_main (main= 0x56373c9ebef0, argc=1, argv=0x7ffe3b444f78, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe3b444f68) at ../csu/libc-start.c:308 #16 0x000056373c9ec3fa in () I will not fiddle around trying to properly upload the apport report just now, but I will keep it around locally. ** Bug watch added: freedesktop.org Bugzilla #103298 https://bugs.freedesktop.org/show_bug.cgi?id=103298 -- 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/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have been having regular system freezes after switching from using my laptop stand-alone to waking it up on a docking station with an external monitor. I have seen this using two identical docking station plus monitor combinations. I am still trying to find a pattern. I was able to ssh in and use apport to save this bug information. The gnome-shell process was hung at 100% CPU utilisation. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 15:56:34 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-terminal']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+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
