gnome shell freezes while notification is disappearing
Affected version
I'm using Wayland on Fedora 32
$ uname -a
Linux faultier 5.6.8-300.fc32.x86_64 #1 SMP Wed Apr 29 19:01:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/os-release
NAME=Fedora
VERSION="32 (Workstation Edition)"
ID=fedora
VERSION_ID=32
VERSION_CODENAME=""
PLATFORM_ID="platform:f32"
PRETTY_NAME="Fedora 32 (Workstation Edition)"
ANSI_COLOR="0;34"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:32"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f32/system-administrators-guide/"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=32
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=32
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Workstation Edition"
VARIANT_ID=workstation
$ gnome-shell --version
GNOME Shell 3.36.2
Bug summary
When notification preview is closing / disappearing gnome-shell freezes for more than half a minute, even <ctrl>+<alt>+F1 etc. not working happened with notifications from GSConnect, Firefox and Evolution so far
Steps to reproduce
- receive notification
- let notification go away
- notification gets stuck half way gone, so is everything else
- after a while (30 - 40 secs) gnome-shell starts to respond again
What happened
gnome-shell freezes for 30-40 secs, not responding at all, even <ctrl>+<alt>+F1 etc. not working
What did you expect to happen
not getting stuck
Relevant logs, screenshots, screencasts etc.
$ journalctl -xe # immediately after unfreez
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 13:55:40 faultier gnome-shell[3145]: libinput error: client bug: timer event7 tap: scheduled expiry is in the past (-450ms), your system is too slow
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending callback was allocate(), a vfunc.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on StWidget 0x562400a3d470.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending callback was update_allocation(), a vfunc.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending callback was allocate(), a vfunc.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on StWidget 0x562400a3d470.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on Gjs_ui_messageTray_MessageTray 0x562400a38100.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending callback was update_allocation(), a vfunc.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending callback was allocate(), a vfunc.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on StWidget 0x562400a3d470.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on Gjs_ui_messageTray_MessageTray 0x562400a38100.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending callback was update_allocation(), a vfunc.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 13:55:40 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 13:55:40 faultier gnome-shell[3145]: The offending signal was notify on GnomeWallClock 0x562400b1b080.
.
.
.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending callback was allocate(), a vfunc.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on StWidget 0x562400a3d470.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending callback was update_allocation(), a vfunc.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending callback was allocate(), a vfunc.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on StWidget 0x562400a3d470.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on Gjs_ui_messageTray_MessageTray 0x562400a38100.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending callback was update_allocation(), a vfunc.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending callback was allocate(), a vfunc.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on StWidget 0x562400a3d470.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on Gjs_ui_messageTray_MessageTray 0x562400a38100.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending callback was update_allocation(), a vfunc.
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was handle-method-call on GjsDBusImplementation 0x562400b14100.
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 14:03:17 faultier gnome-shell[3145]: == Stack trace for context 0x5623ff489170 ==
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 14:03:17 faultier gnome-shell[3145]: libinput error: client bug: timer event7 tap: scheduled expiry is in the past (-271ms), your system is too slow
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on NMAccessPoint 0x5624047f08c0.
Mai 06 14:03:17 faultier gnome-shell[3145]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mai 06 14:03:17 faultier gnome-shell[3145]: The offending signal was notify on GnomeWallClock 0x562400b1b080.