Hi everyone, I have the same problem. The solution to avoid the log flooding the entire disk is to place this line in the root cron (sudo crontab -e): */1 * * * * [[ $(tail /mnt/data/system/var/log/syslog | grep -vi "cron" | grep "The offending callback was SourceFunc().") ]] && kill -HUP $(pidof gnome-shell)
This greps the last lines of the log every minute and triggers a restart of gnome-shell if the offending callback is found. None of the current applications are killed (except gnome-shell) which is convenient. If you are limited in space, I would recommend to run the command every 30s or less. Source of this is available here: https://gitlab.gnome.org/GNOME /gnome-shell/-/issues/1868#note_1050922 Hope this helps. EDIT: By the way, here are information related to my system: - Ubuntu 20.04.2 - 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:39:42 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux - GNOME Shell 3.36.7 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1908429 Title: gnome-shell fills syslog: 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. The offending callback was SourceFunc(). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
