-- Logs begin at Thu 2019-05-02 13:12:22 AWST, end at Tue 2019-07-16 14:39:57 AWST. --
[    5.089082] kab gnome-shell[944]: g_dir_open_with_errno: assertion 'path != NULL' failed
[    5.089983] kab gnome-shell[944]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
[    5.090929] kab gnome-shell[944]: g_dir_open_with_errno: assertion 'path != NULL' failed
[    5.091056] kab gnome-shell[944]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
[    5.325786] kab gnome-shell[944]: Getting invalid resource scale property
[    5.366343] kab gnome-shell[944]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
[    5.395957] kab gnome-shell[944]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1644]: reference to undefined property "MetaWindowXwayland"
[ 9099.018071] kab gnome-shell[944]: Connection to xwayland lost
[11770.300673] kab gnome-shell[20492]: g_dir_open_with_errno: assertion 'path != NULL' failed
[11770.300984] kab gnome-shell[20492]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
[11770.301033] kab gnome-shell[20492]: g_dir_open_with_errno: assertion 'path != NULL' failed
[11770.301080] kab gnome-shell[20492]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
[11770.503648] kab gnome-shell[20492]: Getting invalid resource scale property
[11770.546708] kab gnome-shell[20492]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
[11770.569516] kab gnome-shell[20492]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1644]: reference to undefined property "MetaWindowXwayland"
[11780.286251] kab gnome-shell[20695]: Failed to find schema: org.gnome.settings-daemon.plugins.xsettings
[11780.921503] kab gnome-shell[20695]: g_dir_open_with_errno: assertion 'path != NULL' failed
[11780.921685] kab gnome-shell[20695]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
[11780.923302] kab gnome-shell[20695]: g_dir_open_with_errno: assertion 'path != NULL' failed
[11780.923369] kab gnome-shell[20695]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
[11780.951008] kab gnome-shell[20695]: Telepathy is not available, chat integration will be disabled.
[11781.069599] kab gnome-shell[20695]: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/appIcons.js 1054]: unreachable code after return statement
[11781.272861] kab gnome-shell[20695]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
[11781.852342] kab org.gnome.Shell.desktop[20695]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[11781.852610] kab org.gnome.Shell.desktop[20695]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[11781.852610] kab org.gnome.Shell.desktop[20695]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[11781.852610] kab org.gnome.Shell.desktop[20695]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[11781.852610] kab org.gnome.Shell.desktop[20695]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[11781.852610] kab org.gnome.Shell.desktop[20695]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[11781.852610] kab org.gnome.Shell.desktop[20695]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[11781.852821] kab org.gnome.Shell.desktop[20695]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[11781.852821] kab org.gnome.Shell.desktop[20695]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[11782.374589] kab gnome-shell[20695]: GNOME Shell started at Tue Jul 16 2019 14:33:39 GMT+0800 (AWST)
[11786.285475] kab org.gnome.Shell.desktop[20695]: libinput error: client bug: timer event4 debounce: offset negative (-138ms)
[11786.285475] kab org.gnome.Shell.desktop[20695]: libinput error: client bug: timer event4 debounce short: offset negative (-151ms)
[11790.011803] kab gnome-shell[20492]: Connection to xwayland lost
[11797.486312] kab gnome-shell[20695]: Received error from DBus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application
[11797.486641] kab gnome-shell[20695]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0
[11843.830193] kab gnome-shell[20695]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.201/org/ayatana/NotificationItem/software_update_available
[11843.838722] kab gnome-shell[20695]: [AppIndicatorSupport-FATAL] unable to update overlay icon
[11843.839734] kab gnome-shell[20695]: [AppIndicatorSupport-FATAL] unable to update overlay icon
[12088.915651] kab org.gnome.Shell.desktop[20695]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
[12088.915651] kab org.gnome.Shell.desktop[20695]: == Stack trace for context 0x556609d3a2e0 ==
[12088.915651] kab org.gnome.Shell.desktop[20695]: #0   7ffdc21534b0 b   resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (7f1caffb90d0 @ 25)
[12088.915651] kab org.gnome.Shell.desktop[20695]: #1   55660bc03068 i   /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:190 (7f1cad06c0d0 @ 75)
[12088.915651] kab org.gnome.Shell.desktop[20695]: #2   55660bc02ff0 i   /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:111 (7f1cad067ca0 @ 12)
[12088.915651] kab org.gnome.Shell.desktop[20695]: == Stack trace for context 0x556609d3a2e0 ==
[12088.923005] kab org.gnome.Shell.desktop[20695]: == Stack trace for context 0x556609d3a2e0 ==
[12088.932082] kab gnome-shell[20695]: Object Meta.BackgroundActor (0x55660af11230), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[12088.934747] kab gnome-shell[20695]: 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.
[12088.934909] kab gnome-shell[20695]: The offending signal was destroy on Gjs_BaseIcon 0x55660e6d5480.
[12088.935055] kab gnome-shell[20695]: 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.
[12088.935194] kab gnome-shell[20695]: The offending signal was destroy on Gjs_BaseIcon 0x55660e451c80.
[12088.935335] kab gnome-shell[20695]: 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.
[12088.935472] kab gnome-shell[20695]: The offending signal was destroy on Gjs_BaseIcon 0x55660a51c750.
[12088.935642] kab gnome-shell[20695]: 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.
[12088.935781] kab gnome-shell[20695]: The offending signal was destroy on Gjs_BaseIcon 0x55660a3d5e80.
[12088.935922] kab gnome-shell[20695]: 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.
[12088.936061] kab gnome-shell[20695]: The offending signal was destroy on Gjs_BaseIcon 0x55660c80c480.
[12088.936209] kab gnome-shell[20695]: 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.
[12088.936355] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660e2b3740.
[12088.936922] kab gnome-shell[20695]: 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.
[12088.937127] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660e2b3740.
[12088.937283] kab gnome-shell[20695]: 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.
[12088.937420] kab gnome-shell[20695]: The offending signal was destroy on Gjs_BaseIcon 0x55660ee6f990.
[12088.937562] kab gnome-shell[20695]: 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.
[12088.937706] kab gnome-shell[20695]: The offending signal was actor-removed on Gjs_IconGrid 0x55660c3e7ec0.
[12088.937846] kab gnome-shell[20695]: 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.
[12088.937995] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660e4ec0a0.
[12088.938146] kab gnome-shell[20695]: 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.
[12088.938282] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660e4ec0a0.
[12088.938416] kab gnome-shell[20695]: 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.
[12088.938573] kab gnome-shell[20695]: The offending signal was destroy on Gjs_BaseIcon 0x55660e4efb60.
[12088.938723] kab gnome-shell[20695]: 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.
[12088.938860] kab gnome-shell[20695]: The offending signal was actor-removed on Gjs_IconGrid 0x55660c3e7ec0.
[12088.939003] kab gnome-shell[20695]: 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.
[12088.939146] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660a506b10.
[12088.939287] kab gnome-shell[20695]: 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.
[12088.939438] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660a506b10.
[12088.939578] kab gnome-shell[20695]: 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.
[12088.939714] kab gnome-shell[20695]: The offending signal was destroy on Gjs_BaseIcon 0x55660a50d680.
[12088.939865] kab gnome-shell[20695]: 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.
[12088.940007] kab gnome-shell[20695]: The offending signal was actor-removed on Gjs_IconGrid 0x55660c3e7ec0.
[12088.940134] kab gnome-shell[20695]: 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.
[12088.940257] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660b8640a0.
[12088.940389] kab gnome-shell[20695]: 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.
[12088.940523] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660b8640a0.
[12088.940915] kab gnome-shell[20695]: 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.
[12088.941082] kab gnome-shell[20695]: The offending signal was destroy on Gjs_BaseIcon 0x55660c1bc4c0.
[12088.941195] kab gnome-shell[20695]: 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.
[12088.941298] kab gnome-shell[20695]: The offending signal was actor-removed on Gjs_IconGrid 0x55660c3e7ec0.
[12088.941398] kab gnome-shell[20695]: 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.
[12088.941511] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660bc2c5d0.
[12088.941617] kab gnome-shell[20695]: 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.
[12088.941716] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660bc2c5d0.
[12088.941815] kab gnome-shell[20695]: 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.
[12088.941914] kab gnome-shell[20695]: The offending signal was destroy on Gjs_BaseIcon 0x55660e4c2a90.
[12088.942013] kab gnome-shell[20695]: 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.
[12088.942118] kab gnome-shell[20695]: The offending signal was actor-removed on Gjs_IconGrid 0x55660c3e7ec0.
[12088.942218] kab gnome-shell[20695]: 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.
[12088.942317] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660c5646a0.
[12088.942419] kab gnome-shell[20695]: 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.
[12088.942523] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660c5646a0.
[12088.942621] kab gnome-shell[20695]: 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.
[12088.942714] kab gnome-shell[20695]: The offending signal was destroy on Gjs_BaseIcon 0x55660b8d9880.
[12088.942820] kab gnome-shell[20695]: 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.
[12088.942920] kab gnome-shell[20695]: The offending signal was actor-removed on Gjs_IconGrid 0x55660c3e7ec0.
[12088.943022] kab gnome-shell[20695]: 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.
[12088.943122] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660c838ca0.
[12088.943230] kab gnome-shell[20695]: 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.
[12088.943330] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660c838ca0.
[12088.943437] kab gnome-shell[20695]: 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.
[12088.943538] kab gnome-shell[20695]: The offending signal was destroy on Gjs_BaseIcon 0x55660c821c80.
[12088.943638] kab gnome-shell[20695]: 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.
[12088.943750] kab gnome-shell[20695]: The offending signal was actor-removed on Gjs_IconGrid 0x55660c3e7ec0.
[12088.943865] kab gnome-shell[20695]: 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.
[12088.943958] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660c5a3eb0.
[12088.944059] kab gnome-shell[20695]: 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.
[12088.944163] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660c5a3eb0.
[12088.944256] kab gnome-shell[20695]: 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.
[12088.944347] kab gnome-shell[20695]: The offending signal was destroy on Gjs_BaseIcon 0x55660ed79530.
[12088.944446] kab gnome-shell[20695]: 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.
[12088.944545] kab gnome-shell[20695]: The offending signal was actor-removed on Gjs_IconGrid 0x55660c3e7ec0.
[12088.944668] kab gnome-shell[20695]: 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.
[12088.944774] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660e4daaa0.
[12088.944883] kab gnome-shell[20695]: 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.
[12088.944983] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660e4daaa0.
[12088.945076] kab gnome-shell[20695]: 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.
[12088.945173] kab gnome-shell[20695]: The offending signal was destroy on Gjs_BaseIcon 0x55660e4e1080.
[12088.945272] kab gnome-shell[20695]: 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.
[12088.945374] kab gnome-shell[20695]: The offending signal was actor-removed on Gjs_IconGrid 0x55660c3e7ec0.
[12088.945475] kab gnome-shell[20695]: 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.
[12088.945584] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660c75cca0.
[12088.945684] kab gnome-shell[20695]: 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.
[12088.945783] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660c75cca0.
[12088.945882] kab gnome-shell[20695]: 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.
[12088.945985] kab gnome-shell[20695]: The offending signal was destroy on Gjs_BaseIcon 0x55660c754c80.
[12088.946085] kab gnome-shell[20695]: 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.
[12088.946190] kab gnome-shell[20695]: The offending signal was actor-removed on Gjs_IconGrid 0x55660c3e7ec0.
[12088.946289] kab gnome-shell[20695]: 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.
[12088.946387] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660c3e90a0.
[12088.946486] kab gnome-shell[20695]: 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.
[12088.946584] kab gnome-shell[20695]: The offending signal was destroy on StButton 0x55660c3e90a0.
[12088.946693] kab gnome-shell[20695]: 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.
[12088.946793] kab gnome-shell[20695]: The offending signal was destroy on Gjs_BaseIcon 0x55660a970080.
[12088.946900] kab gnome-shell[20695]: 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.
[12088.947494] kab gnome-shell[20695]: The offending signal was actor-removed on Gjs_IconGrid 0x55660c3e7ec0.
[12090.281461] kab gnome-shell[22027]: g_dir_open_with_errno: assertion 'path != NULL' failed
[12090.281744] kab gnome-shell[22027]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
[12090.282067] kab gnome-shell[22027]: g_dir_open_with_errno: assertion 'path != NULL' failed
[12090.282154] kab gnome-shell[22027]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
[12090.480129] kab gnome-shell[22027]: Getting invalid resource scale property
[12090.520914] kab gnome-shell[22027]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
[12090.557238] kab gnome-shell[22027]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1644]: reference to undefined property "MetaWindowXwayland"
[12113.222750] kab gnome-shell[22309]: g_dir_open_with_errno: assertion 'path != NULL' failed
[12113.223077] kab gnome-shell[22309]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
[12113.223204] kab gnome-shell[22309]: g_dir_open_with_errno: assertion 'path != NULL' failed
[12113.223270] kab gnome-shell[22309]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
[12113.254118] kab gnome-shell[22309]: Telepathy is not available, chat integration will be disabled.
[12113.398833] kab gnome-shell[22309]: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/appIcons.js 1054]: unreachable code after return statement
[12113.762903] kab gnome-shell[22309]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
[12114.136113] kab org.gnome.Shell.desktop[22309]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[12114.136293] kab org.gnome.Shell.desktop[22309]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[12114.136293] kab org.gnome.Shell.desktop[22309]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[12114.136347] kab org.gnome.Shell.desktop[22309]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[12114.136347] kab org.gnome.Shell.desktop[22309]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[12114.136347] kab org.gnome.Shell.desktop[22309]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[12114.136451] kab org.gnome.Shell.desktop[22309]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[12114.136451] kab org.gnome.Shell.desktop[22309]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[12114.136451] kab org.gnome.Shell.desktop[22309]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[12114.747681] kab gnome-shell[22309]: GNOME Shell started at Tue Jul 16 2019 14:39:11 GMT+0800 (AWST)
[12115.004327] kab gnome-shell[22309]: Error connecting to Nautilus
[12122.016728] kab gnome-shell[22027]: Connection to xwayland lost
[12128.933647] kab gnome-shell[22763]: g_dir_open_with_errno: assertion 'path != NULL' failed
[12128.934000] kab gnome-shell[22763]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
[12128.934074] kab gnome-shell[22763]: g_dir_open_with_errno: assertion 'path != NULL' failed
[12128.934135] kab gnome-shell[22763]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
[12129.125391] kab gnome-shell[22763]: Getting invalid resource scale property
[12129.165805] kab gnome-shell[22763]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
[12129.210458] kab gnome-shell[22763]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1644]: reference to undefined property "MetaWindowXwayland"
[12136.665643] kab gnome-shell[22961]: Failed to find schema: org.gnome.settings-daemon.plugins.xsettings
[12137.516683] kab gnome-shell[22961]: g_dir_open_with_errno: assertion 'path != NULL' failed
[12137.516803] kab gnome-shell[22961]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
[12137.517137] kab gnome-shell[22961]: g_dir_open_with_errno: assertion 'path != NULL' failed
[12137.517205] kab gnome-shell[22961]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
[12137.552468] kab gnome-shell[22961]: Telepathy is not available, chat integration will be disabled.
[12137.705412] kab gnome-shell[22961]: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/appIcons.js 1054]: unreachable code after return statement
[12137.918093] kab gnome-shell[22961]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
[12138.399134] kab org.gnome.Shell.desktop[22961]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[12138.399134] kab org.gnome.Shell.desktop[22961]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[12138.399134] kab org.gnome.Shell.desktop[22961]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[12138.399354] kab org.gnome.Shell.desktop[22961]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[12138.399354] kab org.gnome.Shell.desktop[22961]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[12138.399354] kab org.gnome.Shell.desktop[22961]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[12138.399354] kab org.gnome.Shell.desktop[22961]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[12138.399354] kab org.gnome.Shell.desktop[22961]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[12138.399354] kab org.gnome.Shell.desktop[22961]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[12138.925431] kab gnome-shell[22961]: GNOME Shell started at Tue Jul 16 2019 14:39:35 GMT+0800 (AWST)
[12139.153934] kab gnome-shell[22961]: Error connecting to Nautilus
[12147.021204] kab gnome-shell[22763]: Connection to xwayland lost
[12151.886140] kab gnome-shell[22961]: Object Meta.BackgroundActor (0x55a1f510d3c0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[12151.886441] kab org.gnome.Shell.desktop[22961]: == Stack trace for context 0x55a1f3f322e0 ==
[12151.886441] kab org.gnome.Shell.desktop[22961]: #0   7ffd4a5abb70 b   resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (7fc7867b90d0 @ 25)
[12151.886441] kab org.gnome.Shell.desktop[22961]: #1   55a1f4190a18 i   /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:190 (7fc75be6c0d0 @ 75)
[12151.886441] kab org.gnome.Shell.desktop[22961]: #2   55a1f41909a0 i   /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:111 (7fc75be67ca0 @ 12)
[12153.423563] kab gnome-shell[23447]: g_dir_open_with_errno: assertion 'path != NULL' failed
[12153.423855] kab gnome-shell[23447]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
[12153.424102] kab gnome-shell[23447]: g_dir_open_with_errno: assertion 'path != NULL' failed
[12153.424160] kab gnome-shell[23447]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
[12153.598913] kab gnome-shell[23447]: Getting invalid resource scale property
[12153.639260] kab gnome-shell[23447]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
[12153.670344] kab gnome-shell[23447]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1644]: reference to undefined property "MetaWindowXwayland"