gnome-shell-extension-gsconnect
gnome-shell-extension-gsconnect copied to clipboard
GSConnect
Error filling up my syslog rapidly
Hello! this error has been popping up and filing up my system log file
Nov 8 09:20:27 hostname org.gnome.Shell.Extensions.GSConnect[4088]: #0 55e8d503dbf0 i /home/username/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:729 (2025ff98d178 @ 963)
Nov 8 09:20:27 hostname org.gnome.Shell.Extensions.GSConnect[4088]: == Stack trace for context 0x55e8d4f8d1a0 ==
Nov 8 09:20:27 hostname gjs[4088]: The offending callback was SourceFunc().
Nov 8 09:20:27 hostname org.gnome.Shell.Extensions.GSConnect[4088]: #0 55e8d503dbf0 i /home/username/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:729 (2025ff98d178 @ 963)
Nov 8 09:20:27 hostname org.gnome.Shell.Extensions.GSConnect[4088]: == Stack trace for context 0x55e8d4f8d1a0 ==
Nov 8 09:20:27 hostname gjs[4088]: 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.
I have to delete syslog.1 every so often because it gets so large that it'll eat up all my space.
i am running on: Distributor ID: Ubuntu Description: Ubuntu 20.04.5 LTS Release: 20.04 Codename: focal
I converted this system over from an ubuntu installation initially.
Anyone have a solution? i know i saw a closed issue with this from 2020 but i did not see a resolution there.
I have had that happen to me just once and I couldn't catch why it happened that time. It's really hard to fix when I don't know exactly what causes it. It's still an issue and will probably be very easily fixed once the fault is located (which is quite hard).
I have had that happen to me just once and I couldn't catch why it happened that time. It's really hard to fix when I don't know exactly what causes it. It's still an issue and will probably be very easily fixed once the fault is located (which is quite hard).
I am going to keep tailing my syslog while interacting with it and see if i can pin it down. will post here again when i have some more information.
