-- Logs begin at Wed 2017-08-30 13:07:19 +0430, end at Wed 2017-08-30 16:13:13 +0430. --
Aug 30 16:09:30 hostname unknown[20409]: secret_item_get_schema_name: assertion 'variant != NULL' failed
Aug 30 16:09:30 hostname unknown[20409]: secret_item_get_schema_name: assertion 'variant != NULL' failed
Aug 30 16:09:30 hostname unknown[20409]: secret_item_get_schema_name: assertion 'variant != NULL' failed
Aug 30 16:09:30 hostname unknown[20409]: secret_item_get_schema_name: assertion 'variant != NULL' failed
Aug 30 16:09:30 hostname unknown[20409]: secret_item_get_schema_name: assertion 'variant != NULL' failed
Aug 30 16:09:30 hostname unknown[20409]: secret_item_get_schema_name: assertion 'variant != NULL' failed
Aug 30 16:09:30 hostname unknown[20409]: secret_item_get_schema_name: assertion 'variant != NULL' failed
Aug 30 16:09:30 hostname unknown[20409]: secret_item_get_schema_name: assertion 'variant != NULL' failed
Aug 30 16:09:30 hostname unknown[20409]: secret_item_get_schema_name: assertion 'variant != NULL' failed
Aug 30 16:09:30 hostname unknown[20409]: secret_item_get_schema_name: assertion 'variant != NULL' failed
Aug 30 16:09:30 hostname unknown[20409]: secret_item_get_schema_name: assertion 'variant != NULL' failed
Aug 30 16:09:30 hostname unknown[20409]: secret_item_get_schema_name: assertion 'variant != NULL' failed
Aug 30 16:09:30 hostname unknown[20409]: secret_item_get_schema_name: assertion 'variant != NULL' failed
Aug 30 16:09:30 hostname unknown[20409]: secret_item_get_schema_name: assertion 'variant != NULL' failed
Aug 30 16:09:30 hostname unknown[20409]: secret_item_get_schema_name: assertion 'variant != NULL' failed
Aug 30 16:09:30 hostname unknown[20409]: secret_item_get_schema_name: assertion 'variant != NULL' failed
Aug 30 16:09:30 hostname systemd[19798]: xdg-permission-store.service: Failed with result 'exit-code'.
Aug 30 16:09:30 hostname deja-dup-monito[21047]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:09:30 hostname deja-dup-monito[21047]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:09:30 hostname gsd-rfkill[20123]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput'
Aug 30 16:09:30 hostname evolution-addre[20286]: Error releasing name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx20266x2: The connection is closed
Aug 30 16:09:30 hostname deja-dup-monito[21047]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:09:30 hostname deja-dup-monito[21047]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:09:30 hostname deja-dup-monito[21047]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:09:30 hostname gsd-printer[20263]: The connection is closed
Aug 30 16:09:30 hostname zeitgeist-datah[20354]: zeitgeist-datahub.vala:227: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
Aug 30 16:09:30 hostname zeitgeist-fts[20369]: Error releasing name org.gnome.zeitgeist.SimpleIndexer: The connection is closed
Aug 30 16:09:30 hostname zeitgeist-fts[20369]: zeitgeist-fts.vala:252: The connection is closed
Aug 30 16:09:30 hostname indicator-appli[20177]: Name Lost
Aug 30 16:09:30 hostname zeitgeist-daemo[20363]: g_object_unref: assertion 'object->ref_count > 0' failed
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on ShellGenericContainer 0x7743be1f70.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on ShellGenericContainer 0x7743be1f70.
Aug 30 16:09:30 hostname gnome-shell[19953]: instance of invalid non-instantiatable type '(null)'
Aug 30 16:09:30 hostname gnome-shell[19953]: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7745c6f700.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745c6b950.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745c6b950.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7745c7ce70.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745c850d0.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745c850d0.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x774335dc60.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x77457ddc80.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x77457ddc80.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7745890e60.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x77438c2c80.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x77438c2c80.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x774568b270.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x77432f5c90.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x77432f5c90.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x774581bc80.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x774564cc90.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x774564cc90.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x77432aaf20.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x77435c4880.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x77435c4880.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7745b8fcf0.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745b83b90.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745b83b90.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7745791c30.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x774577a880.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x774577a880.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7744583460.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7744c8ba10.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7744c8ba10.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7745c94bd0.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745c92250.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745c92250.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x77457507b0.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745734bb0.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745734bb0.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x774585e460.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745883880.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745883880.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x774570a460.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x774589dd90.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x774589dd90.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x774338bc60.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x774580a480.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x774580a480.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7745ca1940.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745cdc8c0.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745cdc8c0.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7745b7dc60.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x77458d2680.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x77458d2680.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7744788450.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x774554ed80.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7745ce4b40.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7745caaa40.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7745c9b120.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7745c8dff0.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7745d19970.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745d15800.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745d15800.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7745cf0fe0.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7745d10160.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745d179b0.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StButton 0x7745d179b0.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was actor-removed on ShellGenericContainer 0x7745cf0fe0.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7743bb7980.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7743bba470.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7744129270.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7746d32460.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7744c42bd0.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x774694ffd0.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7746b5a610.
Aug 30 16:09:30 hostname gnome-shell[19953]: 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.
Aug 30 16:09:30 hostname gnome-shell[19953]: The offending signal was destroy on StBin 0x7746864430.
Aug 30 16:09:30 hostname pulseaudio[21221]: [pulseaudio] core-util.c: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 1000), but by uid 0! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
Aug 30 16:09:30 hostname org.gnome.Shell.desktop[19953]: (EE)
Aug 30 16:09:30 hostname org.gnome.Shell.desktop[19953]: Fatal server error:
Aug 30 16:09:30 hostname org.gnome.Shell.desktop[19953]: (EE) failed to read Wayland events: Connection reset by peer
Aug 30 16:09:30 hostname org.gnome.Shell.desktop[19953]: (EE)
Aug 30 16:09:31 hostname systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 30 16:09:31 hostname lightdm[21269]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 30 16:09:31 hostname lightdm[21269]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 30 16:09:31 hostname org.gnome.ScreenSaver[21306]: Unable to init server: Could not connect: Connection refused
Aug 30 16:09:31 hostname gnome-screensav[21426]: Cannot open display: 
Aug 30 16:09:31 hostname gnome-session-binary[21295]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
Aug 30 16:09:31 hostname gnome-session-binary[21295]: WARNING: Could not parse desktop file blueman.desktop or it references a not found TryExec binary
Aug 30 16:09:31 hostname gnome-session-binary[21295]: WARNING: Could not parse desktop file vino-server.desktop or it references a not found TryExec binary
Aug 30 16:09:31 hostname gnome-session-binary[21295]: WARNING: Could not parse desktop file xembedsniproxy.desktop or it references a not found TryExec binary
Aug 30 16:09:31 hostname gnome-session-binary[21295]: WARNING: Could not parse desktop file plasmashell.desktop or it references a not found TryExec binary
Aug 30 16:09:31 hostname gnome-session-binary[21295]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary
Aug 30 16:09:31 hostname gnome-session-binary[21295]: WARNING: Could not parse desktop file xscreensaver.desktop or it references a not found TryExec binary
Aug 30 16:09:31 hostname gnome-session-binary[21295]: WARNING: Could not parse desktop file klipper.desktop or it references a not found TryExec binary
Aug 30 16:09:31 hostname gnome-session-binary[21295]: WARNING: Could not parse desktop file pam_kwallet_init.desktop or it references a not found TryExec binary
Aug 30 16:09:31 hostname gnome-session-binary[21295]: WARNING: Could not parse desktop file xfsettingsd.desktop or it references a not found TryExec binary
Aug 30 16:09:31 hostname gnome-session-binary[21295]: WARNING: Could not parse desktop file blueman.desktop or it references a not found TryExec binary
Aug 30 16:09:31 hostname gnome-session-binary[21295]: WARNING: Could not parse desktop file baloo_file.desktop or it references a not found TryExec binary
Aug 30 16:09:31 hostname gnome-session-binary[21295]: WARNING: Could not parse desktop file tracker-miner-user-guides.desktop or it references a not found TryExec binary
Aug 30 16:09:31 hostname gnome-session-binary[21295]: WARNING: Could not parse desktop file krunner.desktop or it references a not found TryExec binary
Aug 30 16:09:31 hostname org.a11y.Bus[21442]: Activating service name='org.a11y.atspi.Registry'
Aug 30 16:09:31 hostname org.a11y.Bus[21442]: Successfully activated service 'org.a11y.atspi.Registry'
Aug 30 16:09:32 hostname gnome-shell[21441]: Failed to apply DRM plane transform 0: Invalid argument
Aug 30 16:09:32 hostname org.gnome.Shell.desktop[21441]: glamor: EGL version 1.4 (DRI2):
Aug 30 16:09:35 hostname gnome-shell[21441]: Some code accessed the property 'LIBMUTTER_API_VERSION' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:35 hostname gnome-shell[21441]: Some code accessed the property 'KEYBOARD_ANIMATION_TIME' on the module 'layout'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:35 hostname gnome-shell[21441]: Some code accessed the property 'ANIMATION_TIME_OUT' on the module 'iconGrid'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:35 hostname gnome-shell[21441]: Some code accessed the property 'ANIMATION_MAX_DELAY_OUT_FOR_ITEM' on the module 'iconGrid'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'Urgency' on the module 'messageTray'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'PACKAGE_VERSION' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'HAVE_NETWORKMANAGER' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'SlideDirection' on the module 'overviewControls'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'SortGroup' on the module 'ctrlAltTab'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'Ornament' on the module 'popupMenu'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'HAVE_BLUETOOTH' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'Keyboard' on the module 'keyboard'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'Component' on the module 'networkAgent'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'SYSCONFDIR' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'Component' on the module 'polkitAgent'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'Component' on the module 'telepathyClient'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'Component' on the module 'keyring'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'Component' on the module 'autorunManager'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'Component' on the module 'automountManager'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'AnimationDirection' on the module 'iconGrid'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'HorizontalSeparator' on the module 'separator'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'extensions' on the module 'extensionUtils'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gnome-shell[21441]: Some code accessed the property 'ApplicationsButton' on the module 'menu'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:36 hostname gsd-wacom[21570]: gsd_device_mapper_get: assertion 'screen != NULL' failed
Aug 30 16:09:36 hostname gsd-wacom[21570]: gsd_device_manager_get: assertion 'screen != NULL' failed
Aug 30 16:09:36 hostname gsd-wacom[21570]: invalid (NULL) pointer instance
Aug 30 16:09:36 hostname gsd-wacom[21570]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Aug 30 16:09:36 hostname gsd-wacom[21570]: invalid (NULL) pointer instance
Aug 30 16:09:36 hostname gsd-wacom[21570]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Aug 30 16:09:36 hostname gsd-wacom[21570]: gsd_device_manager_list_devices: assertion 'GSD_IS_DEVICE_MANAGER (manager)' failed
Aug 30 16:09:36 hostname gsd-xsettings[21572]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'GetCurrentState'
Aug 30 16:09:36 hostname gsd-sharing[21628]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Aug 30 16:09:36 hostname gsd-sharing[21628]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service not loaded.
Aug 30 16:09:37 hostname gsd-rfkill[21623]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput'
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'MenuSettingsController' on the module 'controller'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'HotCornerManager' on the module 'helper'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'MenuHotKeybinder' on the module 'helper'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'KeybindingManager' on the module 'helper'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'HOT_KEY' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'EMPTY_STRING' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'MENU_APPEARANCE' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'MENU_BUTTON_TEXT' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'MENU_BUTTON_ICON' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'MENU_ICON_PATH' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'MENU_POSITION' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'DBusMenu' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'WORKAROUND_RELOAD_TYPE_REGISTER' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'StatusNotifierWatcher' on the module 'statusNotifierWatcher'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'StatusNotifierWatcher' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'DASH_ITEM_LABEL_SHOW_TIME' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'DASH_ANIMATION_TIME' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'DASH_ITEM_LABEL_HIDE_TIME' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'DASH_ITEM_HOVER_TIMEOUT' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'LOCALEDIR' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'DockManager' on the module 'docking'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'GlobalSignalsHandler' on the module 'utils'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'Intellihide' on the module 'intellihide'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'MyDash' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'InjectionsHandler' on the module 'utils'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'ThemeManager' on the module 'theming'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'connect' on the module 'extensionSystem'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname nautilus-autostart.desktop[21666]: sys:1: PyGIWarning: Nautilus was imported without specifying a version first. Use gi.require_version('Nautilus', '3.0') before import to ensure that the right version gets loaded.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'Logger' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'PresenceStatus' on the module 'gnomeSession'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'State' on the module 'modalDialog'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'PopupAnimation' on the module 'boxpointer'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:37 hostname gnome-shell[21441]: Some code accessed the property 'MyAppIcon' on the module 'appIcons'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:38 hostname org.gnome.Shell.desktop[21441]: Window manager warning: "XF86RFKill" is not a valid accelerator
Aug 30 16:09:38 hostname org.freedesktop.FileManager1[21306]: sys:1: PyGIWarning: Nautilus was imported without specifying a version first. Use gi.require_version('Nautilus', '3.0') before import to ensure that the right version gets loaded.
Aug 30 16:09:38 hostname gnome-software[21680]: application has no ID set
Aug 30 16:09:38 hostname nautilus-deskto[21666]: Can not calculate _NET_NUMBER_OF_DESKTOPS
Aug 30 16:09:38 hostname nautilus-deskto[21666]: Can not calculate _NET_NUMBER_OF_DESKTOPS
Aug 30 16:09:38 hostname nautilus-deskto[21666]: Can not get _NET_WORKAREA
Aug 30 16:09:38 hostname nautilus-deskto[21666]: Can not determine workarea, guessing at layout
Aug 30 16:09:39 hostname nautilus-deskto[21666]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:09:39 hostname nautilus-deskto[21666]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:09:39 hostname nautilus-deskto[21666]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:09:39 hostname nautilus-deskto[21666]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:09:39 hostname gnome-software[21680]: com.github.cybre.budgie-haste-applet was of type addon but had no extends
Aug 30 16:09:39 hostname gnome-software[21680]: com.github.cybre.budgie-screenshot-applet was of type addon but had no extends
Aug 30 16:09:39 hostname gnome-software[21680]: plugin appstream took 1.1 seconds to do setup
Aug 30 16:09:39 hostname nautilus-deskto[21666]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:09:39 hostname nautilus-deskto[21666]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:09:39 hostname gnome-software[21680]: failed to call gs_plugin_add_updates_historical on packagekit-offline: The transaction did not complete
Aug 30 16:09:45 hostname gsd-print-notif[21622]: Source ID 5 was not found when attempting to remove it
Aug 30 16:09:45 hostname systemd[21284]: Failed to subscribe to NameOwnerChanged signal for 'org.gnome.user-share.webdav': Connection reset by peer
Aug 30 16:09:45 hostname systemd[21284]: gnome-user-share-webdav.service: Cannot watch bus name org.gnome.user-share.webdav: Connection reset by peer
Aug 30 16:09:45 hostname systemd[21284]: xdg-permission-store.service: Failed with result 'exit-code'.
Aug 30 16:09:45 hostname tracker-miner-f[21681]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:09:45 hostname tracker-miner-f[21681]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:09:45 hostname tracker-miner-f[21681]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:09:45 hostname tracker-miner-f[21681]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:09:45 hostname tracker-miner-f[21681]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:09:45 hostname gsd-sharing[21628]: Error releasing name org.gnome.SettingsDaemon.Sharing: The connection is closed
Aug 30 16:09:45 hostname gsd-screensaver[21627]: Error releasing name org.freedesktop.ScreenSaver: The connection is closed
Aug 30 16:09:45 hostname gnome-software[21680]: lost session service
Aug 30 16:09:45 hostname indicator-appli[21673]: Name Lost
Aug 30 16:09:45 hostname evolution-calen[21748]: Error releasing name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx21737x2: The connection is closed
Aug 30 16:09:45 hostname gnome-session-binary[21295]: GLib-GIO-WARNING: Error releasing name org.gnome.SessionManager: The connection is closed
Aug 30 16:09:45 hostname gsd-power[21619]: Error releasing name org.gnome.SettingsDaemon.Power: The connection is closed
Aug 30 16:09:45 hostname tracker-miner-f[21681]: Error while sending AddMatch() message: The connection is closed
Aug 30 16:09:45 hostname tracker-miner-f[21681]: Error while sending AddMatch() message: The connection is closed
Aug 30 16:09:45 hostname tracker-miner-f[21681]: Error while sending AddMatch() message: The connection is closed
Aug 30 16:09:45 hostname gnome-shell[21441]: 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.
Aug 30 16:09:45 hostname gnome-shell[21441]: The offending signal was destroy on ShellGenericContainer 0xd7f06e86e0.
Aug 30 16:09:45 hostname gnome-shell[21441]: 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.
Aug 30 16:09:45 hostname gnome-shell[21441]: The offending signal was destroy on ShellGenericContainer 0xd7f06e86e0.
Aug 30 16:09:45 hostname gnome-shell[21441]: instance of invalid non-instantiatable type '(null)'
Aug 30 16:09:45 hostname gnome-shell[21441]: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Aug 30 16:09:45 hostname org.gnome.Shell.desktop[21441]: (EE)
Aug 30 16:09:45 hostname org.gnome.Shell.desktop[21441]: Fatal server error:
Aug 30 16:09:45 hostname org.gnome.Shell.desktop[21441]: (EE) failed to read Wayland events: Connection reset by peer
Aug 30 16:09:45 hostname org.gnome.Shell.desktop[21441]: (EE)
Aug 30 16:09:45 hostname systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 30 16:09:45 hostname lightdm[21879]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 30 16:09:45 hostname lightdm[21879]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 30 16:09:46 hostname org.gnome.ScreenSaver[21907]: Unable to init server: Could not connect: Connection refused
Aug 30 16:09:46 hostname gnome-screensav[22028]: Cannot open display: 
Aug 30 16:09:46 hostname gnome-session-binary[21896]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
Aug 30 16:09:46 hostname gnome-session-binary[21896]: WARNING: Could not parse desktop file blueman.desktop or it references a not found TryExec binary
Aug 30 16:09:46 hostname gnome-session-binary[21896]: WARNING: Could not parse desktop file vino-server.desktop or it references a not found TryExec binary
Aug 30 16:09:46 hostname gnome-session-binary[21896]: WARNING: Could not parse desktop file xembedsniproxy.desktop or it references a not found TryExec binary
Aug 30 16:09:46 hostname gnome-session-binary[21896]: WARNING: Could not parse desktop file plasmashell.desktop or it references a not found TryExec binary
Aug 30 16:09:46 hostname gnome-session-binary[21896]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary
Aug 30 16:09:46 hostname gnome-session-binary[21896]: WARNING: Could not parse desktop file xscreensaver.desktop or it references a not found TryExec binary
Aug 30 16:09:46 hostname gnome-session-binary[21896]: WARNING: Could not parse desktop file klipper.desktop or it references a not found TryExec binary
Aug 30 16:09:46 hostname gnome-session-binary[21896]: WARNING: Could not parse desktop file pam_kwallet_init.desktop or it references a not found TryExec binary
Aug 30 16:09:46 hostname gnome-session-binary[21896]: WARNING: Could not parse desktop file xfsettingsd.desktop or it references a not found TryExec binary
Aug 30 16:09:46 hostname gnome-session-binary[21896]: WARNING: Could not parse desktop file blueman.desktop or it references a not found TryExec binary
Aug 30 16:09:46 hostname gnome-session-binary[21896]: WARNING: Could not parse desktop file baloo_file.desktop or it references a not found TryExec binary
Aug 30 16:09:46 hostname gnome-session-binary[21896]: WARNING: Could not parse desktop file tracker-miner-user-guides.desktop or it references a not found TryExec binary
Aug 30 16:09:46 hostname gnome-session-binary[21896]: WARNING: Could not parse desktop file krunner.desktop or it references a not found TryExec binary
Aug 30 16:09:46 hostname gnome-shell[22040]: Failed to apply DRM plane transform 0: Invalid argument
Aug 30 16:09:46 hostname org.gnome.Shell.desktop[22040]: glamor: EGL version 1.4 (DRI2):
Aug 30 16:09:50 hostname gnome-shell[22040]: Some code accessed the property 'LIBMUTTER_API_VERSION' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'KEYBOARD_ANIMATION_TIME' on the module 'layout'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'ANIMATION_TIME_OUT' on the module 'iconGrid'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'ANIMATION_MAX_DELAY_OUT_FOR_ITEM' on the module 'iconGrid'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'Urgency' on the module 'messageTray'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'PACKAGE_VERSION' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'HAVE_NETWORKMANAGER' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'SlideDirection' on the module 'overviewControls'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'SortGroup' on the module 'ctrlAltTab'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'Ornament' on the module 'popupMenu'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'HAVE_BLUETOOTH' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'Keyboard' on the module 'keyboard'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'Component' on the module 'networkAgent'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'SYSCONFDIR' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'Component' on the module 'polkitAgent'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'Component' on the module 'telepathyClient'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'Component' on the module 'keyring'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'Component' on the module 'autorunManager'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'Component' on the module 'automountManager'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'AnimationDirection' on the module 'iconGrid'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'HorizontalSeparator' on the module 'separator'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'extensions' on the module 'extensionUtils'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:51 hostname gnome-shell[22040]: Some code accessed the property 'ApplicationsButton' on the module 'menu'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gsd-wacom[22159]: gsd_device_mapper_get: assertion 'screen != NULL' failed
Aug 30 16:09:52 hostname gsd-wacom[22159]: gsd_device_manager_get: assertion 'screen != NULL' failed
Aug 30 16:09:52 hostname gsd-wacom[22159]: invalid (NULL) pointer instance
Aug 30 16:09:52 hostname gsd-wacom[22159]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Aug 30 16:09:52 hostname gsd-wacom[22159]: invalid (NULL) pointer instance
Aug 30 16:09:52 hostname gsd-wacom[22159]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Aug 30 16:09:52 hostname gsd-wacom[22159]: gsd_device_manager_list_devices: assertion 'GSD_IS_DEVICE_MANAGER (manager)' failed
Aug 30 16:09:52 hostname gsd-rfkill[22211]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput'
Aug 30 16:09:52 hostname gsd-xsettings[22160]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'GetCurrentState'
Aug 30 16:09:52 hostname gsd-sharing[22217]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Aug 30 16:09:52 hostname gsd-sharing[22217]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service not loaded.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'MenuSettingsController' on the module 'controller'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'HotCornerManager' on the module 'helper'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'MenuHotKeybinder' on the module 'helper'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'KeybindingManager' on the module 'helper'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'HOT_KEY' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'EMPTY_STRING' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'MENU_APPEARANCE' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'MENU_BUTTON_TEXT' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'MENU_BUTTON_ICON' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'MENU_ICON_PATH' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'MENU_POSITION' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'DBusMenu' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'WORKAROUND_RELOAD_TYPE_REGISTER' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'StatusNotifierWatcher' on the module 'statusNotifierWatcher'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'StatusNotifierWatcher' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname nautilus-autostart.desktop[22262]: sys:1: PyGIWarning: Nautilus was imported without specifying a version first. Use gi.require_version('Nautilus', '3.0') before import to ensure that the right version gets loaded.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'DASH_ITEM_LABEL_SHOW_TIME' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'DASH_ANIMATION_TIME' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'DASH_ITEM_LABEL_HIDE_TIME' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'DASH_ITEM_HOVER_TIMEOUT' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'LOCALEDIR' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'DockManager' on the module 'docking'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'GlobalSignalsHandler' on the module 'utils'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'Intellihide' on the module 'intellihide'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'MyDash' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'InjectionsHandler' on the module 'utils'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'ThemeManager' on the module 'theming'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'connect' on the module 'extensionSystem'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'Logger' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'PresenceStatus' on the module 'gnomeSession'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:52 hostname gnome-shell[22040]: Some code accessed the property 'State' on the module 'modalDialog'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:53 hostname gnome-shell[22040]: Some code accessed the property 'PopupAnimation' on the module 'boxpointer'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:53 hostname org.gnome.Shell.desktop[22040]: Window manager warning: "XF86RFKill" is not a valid accelerator
Aug 30 16:09:53 hostname gnome-shell[22040]: Some code accessed the property 'MyAppIcon' on the module 'appIcons'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:09:53 hostname org.freedesktop.FileManager1[21907]: sys:1: PyGIWarning: Nautilus was imported without specifying a version first. Use gi.require_version('Nautilus', '3.0') before import to ensure that the right version gets loaded.
Aug 30 16:09:53 hostname gnome-software[22276]: application has no ID set
Aug 30 16:09:53 hostname nautilus-deskto[22262]: Can not calculate _NET_NUMBER_OF_DESKTOPS
Aug 30 16:09:53 hostname nautilus-deskto[22262]: Can not calculate _NET_NUMBER_OF_DESKTOPS
Aug 30 16:09:53 hostname nautilus-deskto[22262]: Can not get _NET_WORKAREA
Aug 30 16:09:53 hostname nautilus-deskto[22262]: Can not determine workarea, guessing at layout
Aug 30 16:09:54 hostname nautilus-deskto[22262]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:09:54 hostname nautilus-deskto[22262]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:09:54 hostname nautilus-deskto[22262]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:09:54 hostname nautilus-deskto[22262]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:09:54 hostname nautilus-deskto[22262]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:09:54 hostname gnome-software[22276]: com.github.cybre.budgie-haste-applet was of type addon but had no extends
Aug 30 16:09:54 hostname gnome-software[22276]: com.github.cybre.budgie-screenshot-applet was of type addon but had no extends
Aug 30 16:09:54 hostname gnome-software[22276]: plugin appstream took 1.0 seconds to do setup
Aug 30 16:09:54 hostname gnome-software[22276]: failed to call gs_plugin_add_updates_historical on packagekit-offline: The transaction did not complete
Aug 30 16:09:54 hostname nautilus-deskto[22262]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:10:00 hostname pulseaudio[22068]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out
Aug 30 16:10:04 hostname systemd[21890]: xdg-permission-store.service: Failed with result 'exit-code'.
Aug 30 16:10:04 hostname tracker-miner-f[22280]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:10:04 hostname gsd-power[22205]: Error releasing name org.gnome.SettingsDaemon.Power: The connection is closed
Aug 30 16:10:04 hostname nautilus-deskto[22262]: Failed to unregister client: The connection is closed
Aug 30 16:10:04 hostname gnome-software[22276]: lost session service
Aug 30 16:10:04 hostname gnome-shell[22040]: 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.
Aug 30 16:10:04 hostname gnome-shell[22040]: The offending signal was destroy on ShellGenericContainer 0x40979b8660.
Aug 30 16:10:04 hostname gnome-shell[22040]: 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.
Aug 30 16:10:04 hostname gnome-shell[22040]: The offending signal was destroy on ShellGenericContainer 0x40979b8660.
Aug 30 16:10:04 hostname gnome-shell[22040]: instance of invalid non-instantiatable type '(null)'
Aug 30 16:10:04 hostname gnome-shell[22040]: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Aug 30 16:10:04 hostname indicator-appli[22269]: Name Lost
Aug 30 16:10:04 hostname evolution-addre[22366]: Error releasing name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx22348x2: The connection is closed
Aug 30 16:10:04 hostname ibus-daemon[22112]: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). Most likely the process is ignoring SIGCHLD, or some other thread is invoking waitpid() with a nonpositive first argument; either behavior can break applications that use g_child_watch_add()/g_spawn_sync() either directly or indirectly.
Aug 30 16:10:04 hostname tracker-miner-f[22280]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:10:04 hostname tracker-miner-f[22280]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:10:04 hostname tracker-miner-f[22280]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:10:04 hostname tracker-miner-f[22280]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:10:04 hostname tracker-miner-f[22280]: Error while sending AddMatch() message: The connection is closed
Aug 30 16:10:04 hostname tracker-miner-f[22280]: Error while sending AddMatch() message: The connection is closed
Aug 30 16:10:04 hostname tracker-miner-f[22280]: Error while sending AddMatch() message: The connection is closed
Aug 30 16:10:04 hostname org.gnome.Shell.desktop[22040]: (EE)
Aug 30 16:10:04 hostname org.gnome.Shell.desktop[22040]: Fatal server error:
Aug 30 16:10:04 hostname org.gnome.Shell.desktop[22040]: (EE) failed to read Wayland events: Connection reset by peer
Aug 30 16:10:04 hostname org.gnome.Shell.desktop[22040]: (EE)
Aug 30 16:10:05 hostname systemd[1]: lightdm.service: Failed with result 'exit-code'.
Aug 30 16:10:05 hostname lightdm[22468]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 30 16:10:05 hostname lightdm[22468]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 30 16:10:05 hostname org.gnome.ScreenSaver[22495]: Unable to init server: Could not connect: Connection refused
Aug 30 16:10:05 hostname gnome-screensav[22615]: Cannot open display: 
Aug 30 16:10:05 hostname gnome-session-binary[22484]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
Aug 30 16:10:05 hostname gnome-session-binary[22484]: WARNING: Could not parse desktop file blueman.desktop or it references a not found TryExec binary
Aug 30 16:10:05 hostname gnome-session-binary[22484]: WARNING: Could not parse desktop file vino-server.desktop or it references a not found TryExec binary
Aug 30 16:10:05 hostname gnome-session-binary[22484]: WARNING: Could not parse desktop file xembedsniproxy.desktop or it references a not found TryExec binary
Aug 30 16:10:05 hostname gnome-session-binary[22484]: WARNING: Could not parse desktop file plasmashell.desktop or it references a not found TryExec binary
Aug 30 16:10:05 hostname gnome-session-binary[22484]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary
Aug 30 16:10:05 hostname gnome-session-binary[22484]: WARNING: Could not parse desktop file xscreensaver.desktop or it references a not found TryExec binary
Aug 30 16:10:05 hostname gnome-session-binary[22484]: WARNING: Could not parse desktop file klipper.desktop or it references a not found TryExec binary
Aug 30 16:10:05 hostname gnome-session-binary[22484]: WARNING: Could not parse desktop file pam_kwallet_init.desktop or it references a not found TryExec binary
Aug 30 16:10:05 hostname gnome-session-binary[22484]: WARNING: Could not parse desktop file xfsettingsd.desktop or it references a not found TryExec binary
Aug 30 16:10:05 hostname gnome-session-binary[22484]: WARNING: Could not parse desktop file blueman.desktop or it references a not found TryExec binary
Aug 30 16:10:05 hostname gnome-session-binary[22484]: WARNING: Could not parse desktop file baloo_file.desktop or it references a not found TryExec binary
Aug 30 16:10:05 hostname gnome-session-binary[22484]: WARNING: Could not parse desktop file tracker-miner-user-guides.desktop or it references a not found TryExec binary
Aug 30 16:10:05 hostname gnome-session-binary[22484]: WARNING: Could not parse desktop file krunner.desktop or it references a not found TryExec binary
Aug 30 16:10:05 hostname gnome-shell[22627]: Failed to apply DRM plane transform 0: Invalid argument
Aug 30 16:10:05 hostname org.gnome.Shell.desktop[22627]: glamor: EGL version 1.4 (DRI2):
Aug 30 16:10:10 hostname gnome-shell[22627]: Some code accessed the property 'LIBMUTTER_API_VERSION' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:10 hostname gnome-shell[22627]: Some code accessed the property 'KEYBOARD_ANIMATION_TIME' on the module 'layout'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:10 hostname gnome-shell[22627]: Some code accessed the property 'ANIMATION_TIME_OUT' on the module 'iconGrid'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:10 hostname gnome-shell[22627]: Some code accessed the property 'ANIMATION_MAX_DELAY_OUT_FOR_ITEM' on the module 'iconGrid'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:10 hostname gnome-shell[22627]: Some code accessed the property 'Urgency' on the module 'messageTray'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:10 hostname gnome-shell[22627]: Some code accessed the property 'PACKAGE_VERSION' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:10 hostname gnome-shell[22627]: Some code accessed the property 'HAVE_NETWORKMANAGER' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:10 hostname gnome-shell[22627]: Some code accessed the property 'SlideDirection' on the module 'overviewControls'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:10 hostname gnome-shell[22627]: Some code accessed the property 'SortGroup' on the module 'ctrlAltTab'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'Ornament' on the module 'popupMenu'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'HAVE_BLUETOOTH' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'Keyboard' on the module 'keyboard'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'Component' on the module 'networkAgent'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'SYSCONFDIR' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'Component' on the module 'polkitAgent'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'Component' on the module 'telepathyClient'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'Component' on the module 'keyring'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'Component' on the module 'autorunManager'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'Component' on the module 'automountManager'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'AnimationDirection' on the module 'iconGrid'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'HorizontalSeparator' on the module 'separator'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'extensions' on the module 'extensionUtils'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'ApplicationsButton' on the module 'menu'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gsd-wacom[22745]: gsd_device_mapper_get: assertion 'screen != NULL' failed
Aug 30 16:10:11 hostname gsd-wacom[22745]: gsd_device_manager_get: assertion 'screen != NULL' failed
Aug 30 16:10:11 hostname gsd-wacom[22745]: invalid (NULL) pointer instance
Aug 30 16:10:11 hostname gsd-wacom[22745]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Aug 30 16:10:11 hostname gsd-wacom[22745]: invalid (NULL) pointer instance
Aug 30 16:10:11 hostname gsd-wacom[22745]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Aug 30 16:10:11 hostname gsd-wacom[22745]: gsd_device_manager_list_devices: assertion 'GSD_IS_DEVICE_MANAGER (manager)' failed
Aug 30 16:10:11 hostname gsd-xsettings[22746]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'GetCurrentState'
Aug 30 16:10:11 hostname gsd-rfkill[22797]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput'
Aug 30 16:10:11 hostname gsd-sharing[22801]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Aug 30 16:10:11 hostname gsd-sharing[22801]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service not loaded.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'MenuSettingsController' on the module 'controller'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'HotCornerManager' on the module 'helper'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'MenuHotKeybinder' on the module 'helper'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'KeybindingManager' on the module 'helper'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'HOT_KEY' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'EMPTY_STRING' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'MENU_APPEARANCE' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'MENU_BUTTON_TEXT' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'MENU_BUTTON_ICON' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'MENU_ICON_PATH' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'MENU_POSITION' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'DBusMenu' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'WORKAROUND_RELOAD_TYPE_REGISTER' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'StatusNotifierWatcher' on the module 'statusNotifierWatcher'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'StatusNotifierWatcher' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'DASH_ITEM_LABEL_SHOW_TIME' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'DASH_ANIMATION_TIME' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'DASH_ITEM_LABEL_HIDE_TIME' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'DASH_ITEM_HOVER_TIMEOUT' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'LOCALEDIR' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'DockManager' on the module 'docking'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'GlobalSignalsHandler' on the module 'utils'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'Intellihide' on the module 'intellihide'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:11 hostname gnome-shell[22627]: Some code accessed the property 'MyDash' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:12 hostname gnome-shell[22627]: Some code accessed the property 'InjectionsHandler' on the module 'utils'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:12 hostname gnome-shell[22627]: Some code accessed the property 'ThemeManager' on the module 'theming'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:12 hostname gnome-shell[22627]: Some code accessed the property 'connect' on the module 'extensionSystem'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:12 hostname nautilus-autostart.desktop[22846]: sys:1: PyGIWarning: Nautilus was imported without specifying a version first. Use gi.require_version('Nautilus', '3.0') before import to ensure that the right version gets loaded.
Aug 30 16:10:12 hostname gnome-shell[22627]: Some code accessed the property 'Logger' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:12 hostname gnome-shell[22627]: Some code accessed the property 'PresenceStatus' on the module 'gnomeSession'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:12 hostname gnome-shell[22627]: Some code accessed the property 'State' on the module 'modalDialog'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:12 hostname gnome-shell[22627]: Some code accessed the property 'PopupAnimation' on the module 'boxpointer'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:12 hostname gnome-shell[22627]: Some code accessed the property 'MyAppIcon' on the module 'appIcons'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:12 hostname org.freedesktop.FileManager1[22495]: sys:1: PyGIWarning: Nautilus was imported without specifying a version first. Use gi.require_version('Nautilus', '3.0') before import to ensure that the right version gets loaded.
Aug 30 16:10:13 hostname gnome-software[22859]: application has no ID set
Aug 30 16:10:13 hostname org.gnome.Shell.desktop[22627]: Window manager warning: "XF86RFKill" is not a valid accelerator
Aug 30 16:10:13 hostname nautilus-deskto[22846]: Can not calculate _NET_NUMBER_OF_DESKTOPS
Aug 30 16:10:13 hostname nautilus-deskto[22846]: Can not calculate _NET_NUMBER_OF_DESKTOPS
Aug 30 16:10:13 hostname nautilus-deskto[22846]: Can not get _NET_WORKAREA
Aug 30 16:10:13 hostname nautilus-deskto[22846]: Can not determine workarea, guessing at layout
Aug 30 16:10:13 hostname nautilus-deskto[22846]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:10:13 hostname nautilus-deskto[22846]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:10:13 hostname nautilus-deskto[22846]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:10:13 hostname nautilus-deskto[22846]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:10:13 hostname gnome-software[22859]: com.github.cybre.budgie-haste-applet was of type addon but had no extends
Aug 30 16:10:13 hostname gnome-software[22859]: com.github.cybre.budgie-screenshot-applet was of type addon but had no extends
Aug 30 16:10:13 hostname gnome-software[22859]: plugin appstream took 1.0 seconds to do setup
Aug 30 16:10:13 hostname nautilus-deskto[22846]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:10:13 hostname gnome-software[22859]: failed to call gs_plugin_add_updates_historical on packagekit-offline: The transaction did not complete
Aug 30 16:10:17 hostname gnome-control-c[23023]: Ignoring launcher deja-dup-preferences (missing desktop file)
Aug 30 16:10:17 hostname gnome-control-c[23023]: Ignoring launcher landscape-client-settings (missing desktop file)
Aug 30 16:10:17 hostname gnome-control-c[23023]: Ignoring launcher ubuntuone-installer (missing desktop file)
Aug 30 16:10:18 hostname gnome-shell[22627]: setup_framebuffers: assertion 'width > 0' failed
Aug 30 16:10:27 hostname tracker-miner-f[22862]: Could not open directory 'file:///home/modir/Desktop/noks/gogs/data/sessions': Error opening directory '/home/modir/Desktop/noks/gogs/data/sessions': Permission denied
Aug 30 16:10:27 hostname tracker-miner-f[22862]: Could not enumerate container / directory 'file:///home/modir/Desktop/noks/gogs/data/sessions', Error opening directory '/home/modir/Desktop/noks/gogs/data/sessions': Permission denied
Aug 30 16:10:28 hostname gnome-shell[22627]: Some code accessed the property 'ViewPage' on the module 'viewSelector'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:28 hostname gnome-shell[22627]: Some code accessed the property 'SIDE_CONTROLS_ANIMATION_TIME' on the module 'overviewControls'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:28 hostname gnome-shell[22627]: Some code accessed the property 'VIGNETTE_BRIGHTNESS' on the module 'lightbox'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:28 hostname gnome-shell[22627]: Some code accessed the property 'VIGNETTE_SHARPNESS' on the module 'lightbox'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:28 hostname gnome-shell[22627]: Some code accessed the property 'ANIMATION_TIME' on the module 'overview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:10:31 hostname org.gnome.Nautilus[22495]: sys:1: PyGIWarning: Nautilus was imported without specifying a version first. Use gi.require_version('Nautilus', '3.0') before import to ensure that the right version gets loaded.
Aug 30 16:10:32 hostname zeitgeist-datah[23213]: zeitgeist-datahub.vala:227: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
Aug 30 16:10:35 hostname pulseaudio[22655]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Aug 30 16:10:38 hostname gsd-sharing[22801]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Aug 30 16:10:38 hostname gsd-sharing[22801]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service not loaded.
Aug 30 16:10:39 hostname systemd-sleep[23322]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255.
Aug 30 16:10:49 hostname kernel: Suspending console(s) (use no_console_suspend to debug)
Aug 30 16:10:49 hostname kernel:  cache: parent cpu1 should not be sleeping
Aug 30 16:10:49 hostname kernel:  cache: parent cpu2 should not be sleeping
Aug 30 16:10:49 hostname kernel:  cache: parent cpu3 should not be sleeping
Aug 30 16:10:49 hostname kernel: usb usb3: root hub lost power or was reset
Aug 30 16:10:49 hostname kernel: usb usb4: root hub lost power or was reset
Aug 30 16:10:50 hostname kernel: ata2.01: failed to resume link (SControl 0)
Aug 30 16:10:50 hostname kernel: ata1.01: failed to resume link (SControl 0)
Aug 30 16:10:55 hostname kernel: ata1.00: link is slow to respond, please be patient (ready=0)
Aug 30 16:10:59 hostname kernel: ata1.00: SRST failed (errno=-16)
Aug 30 16:11:00 hostname kernel: ata1.01: failed to resume link (SControl 0)
Aug 30 16:11:01 hostname systemd-sleep[23399]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255.
Aug 30 16:11:01 hostname systemd[1]: Dependency failed for Suspend.
Aug 30 16:11:04 hostname kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.3 DST=224.0.0.252 LEN=52 TOS=0x00 PREC=0x00 TTL=255 ID=56475 PROTO=UDP SPT=5355 DPT=5355 LEN=32 
Aug 30 16:11:04 hostname gsd-sharing[22801]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Aug 30 16:11:04 hostname gsd-sharing[22801]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service not loaded.
Aug 30 16:11:04 hostname kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.3 DST=224.0.0.252 LEN=52 TOS=0x00 PREC=0x00 TTL=255 ID=56476 PROTO=UDP SPT=5355 DPT=5355 LEN=32 
Aug 30 16:11:04 hostname kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=192.168.1.3 DST=224.0.0.252 LEN=52 TOS=0x00 PREC=0x00 TTL=255 ID=56480 PROTO=UDP SPT=5355 DPT=5355 LEN=32 
Aug 30 16:11:05 hostname kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:abc3:f75e:0ce2:9bcc DST=ff02:0000:0000:0000:0000:0000:0001:0003 LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=256643 PROTO=UDP SPT=5355 DPT=5355 LEN=32 
Aug 30 16:11:05 hostname kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:abc3:f75e:0ce2:9bcc DST=ff02:0000:0000:0000:0000:0000:0001:0003 LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=256643 PROTO=UDP SPT=5355 DPT=5355 LEN=32 
Aug 30 16:11:05 hostname kernel: [UFW BLOCK] IN=enp4s0 OUT= MAC= SRC=fe80:0000:0000:0000:abc3:f75e:0ce2:9bcc DST=ff02:0000:0000:0000:0000:0000:0001:0003 LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=256643 PROTO=UDP SPT=5355 DPT=5355 LEN=32 
Aug 30 16:11:23 hostname gnome-control-c[23654]: Ignoring launcher deja-dup-preferences (missing desktop file)
Aug 30 16:11:23 hostname gnome-control-c[23654]: Ignoring launcher landscape-client-settings (missing desktop file)
Aug 30 16:11:23 hostname gnome-control-c[23654]: Ignoring launcher ubuntuone-installer (missing desktop file)
Aug 30 16:11:24 hostname gnome-shell[22627]: Some code accessed the property 'WINDOW_DND_SIZE' on the module 'workspace'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:24 hostname gnome-shell[22627]: Some code accessed the property 'DRAGGING_WINDOW_OPACITY' on the module 'workspace'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:36 hostname gsd-print-notif[22795]: Source ID 14 was not found when attempting to remove it
Aug 30 16:11:36 hostname org.gnome.Shell.desktop[22627]: Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Aug 30 16:11:36 hostname systemd[22478]: xdg-permission-store.service: Failed with result 'exit-code'.
Aug 30 16:11:36 hostname gsd-media-keys[22779]: Error releasing name org.gnome.SettingsDaemon: The connection is closed
Aug 30 16:11:36 hostname indicator-appli[22852]: Name Lost
Aug 30 16:11:36 hostname evolution-calen[22938]: Error releasing name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx22910x3: The connection is closed
Aug 30 16:11:36 hostname evolution-calen[22938]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: The connection is closed (g-io-error-quark, 18)
Aug 30 16:11:36 hostname evolution-calen[22938]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: The connection is closed (g-io-error-quark, 18)
Aug 30 16:11:36 hostname evolution-calen[22938]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: The connection is closed (g-io-error-quark, 18)
Aug 30 16:11:36 hostname gnome-software[22859]: lost session service
Aug 30 16:11:36 hostname evolution-addre[22954]: Error releasing name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx22936x2: The connection is closed
Aug 30 16:11:36 hostname tracker-miner-f[22862]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:11:36 hostname tracker-miner-f[22862]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:11:36 hostname tracker-miner-f[22862]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:11:36 hostname tracker-miner-f[22862]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:11:36 hostname tracker-miner-f[22862]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Aug 30 16:11:36 hostname tracker-miner-f[22862]:   (Sparql buffer) Error in array-update: The connection is closed
Aug 30 16:11:36 hostname tracker-miner-f[22862]: Could not execute sparql: The connection is closed
Aug 30 16:11:36 hostname tracker-miner-f[22862]: Could not execute sparql: The connection is closed
Aug 30 16:11:36 hostname tracker-miner-f[22862]: Could not end data provider for container / directory 'file:///home/modir/Desktop/Makey/www/django/finished/004shop/venv/lib/python3.5/site-packages/pytz/zoneinfo/America', File enumerator has outstanding operation
Aug 30 16:11:36 hostname tracker-miner-f[22862]: Error while sending AddMatch() message: The connection is closed
Aug 30 16:11:36 hostname tracker-miner-f[22862]: Error while sending AddMatch() message: The connection is closed
Aug 30 16:11:36 hostname tracker-miner-f[22862]: Error while sending AddMatch() message: The connection is closed
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x815d18be0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x816ff8c60.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on ShellGenericContainer 0x815230620.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on ShellGenericContainer 0x815230620.
Aug 30 16:11:36 hostname gnome-shell[22627]: instance with invalid (NULL) class pointer
Aug 30 16:11:36 hostname gnome-shell[22627]: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x816da80a0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x816deac90.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x8170b04a0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x81628ffe0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x817084a20.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x815048a20.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x815cc7060.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x814f07060.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x8166c8860.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x816ca6460.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x816b424d0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x814959c60.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x814d6fc60.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x8177a7210.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8177a34d0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8177a34d0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x817792c20.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8177eb560.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8177eb560.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x8175bfc20.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8175bbed0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8175bbed0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x817582c70.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x81757f950.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x81757f950.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x817565f30.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x817562990.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x817562990.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x81758b0b0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x817588130.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x817588130.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x817577e70.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x817575c50.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x817575c50.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x817592ef0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x81759a620.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x81759a620.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x8175dd6a0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8175da5d0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8175da5d0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x817571290.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x81756dcc0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x81756dcc0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x81779e300.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x81779b960.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x81779b960.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x8175cb0c0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8175c8290.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8175c8290.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x8175a76b0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8175a4780.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8175a4780.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x8175a0520.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x81759c5b0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x81759c5b0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x8175b01c0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8175b7790.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8175b7790.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x8177b6db0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8177b42f0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8177b42f0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x8175ba050.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8175c1bc0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x8175c1bc0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x81755b380.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x817789490.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x8177810a0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x8177ea2b0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x8177aff60.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x8177bec70.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x81781df70.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x817819ee0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x817819ee0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x817807940.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StBin 0x817814dd0.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x817812a20.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was destroy on StButton 0x817812a20.
Aug 30 16:11:36 hostname gnome-shell[22627]: 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.
Aug 30 16:11:36 hostname gnome-shell[22627]: The offending signal was actor-removed on ShellGenericContainer 0x817807940.
Aug 30 16:11:36 hostname org.gnome.Shell.desktop[22627]: (EE)
Aug 30 16:11:36 hostname org.gnome.Shell.desktop[22627]: Fatal server error:
Aug 30 16:11:36 hostname org.gnome.Shell.desktop[22627]: (EE) failed to read Wayland events: Connection reset by peer
Aug 30 16:11:36 hostname org.gnome.Shell.desktop[22627]: (EE)
Aug 30 16:11:36 hostname zeitgeist-datah[23193]: zeitgeist-datahub.vala:227: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
Aug 30 16:11:36 hostname zeitgeist-daemo[23203]: Error releasing name org.gnome.zeitgeist.Engine: The connection is closed
Aug 30 16:11:36 hostname zeitgeist-fts[23209]: Error releasing name org.gnome.zeitgeist.SimpleIndexer: The connection is closed
Aug 30 16:11:36 hostname zeitgeist-fts[23209]: zeitgeist-fts.vala:252: The connection is closed
Aug 30 16:11:37 hostname lightdm[22468]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 30 16:11:37 hostname lightdm[23720]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Aug 30 16:11:37 hostname lightdm[23720]: PAM adding faulty module: pam_kwallet.so
Aug 30 16:11:37 hostname lightdm[23720]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Aug 30 16:11:37 hostname lightdm[23720]: PAM adding faulty module: pam_kwallet5.so
Aug 30 16:11:38 hostname indicator-sound[23779]: volume-control-pulse.vala:735: unable to get pulse unix socket: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 was not provided by any .service files
Aug 30 16:11:38 hostname indicator-keybo[23777]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Aug 30 16:11:39 hostname lightdm[23835]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Aug 30 16:11:39 hostname lightdm[23835]: PAM adding faulty module: pam_kwallet.so
Aug 30 16:11:39 hostname lightdm[23835]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Aug 30 16:11:39 hostname lightdm[23835]: PAM adding faulty module: pam_kwallet5.so
Aug 30 16:11:43 hostname pulseaudio[23844]: [pulseaudio] pid.c: Daemon already running.
Aug 30 16:11:51 hostname lightdm[22468]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 30 16:11:52 hostname gnome-session-c[23971]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-7t5g7Jzyee: Connection refused
Aug 30 16:11:52 hostname gnome-screensav[23998]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-7t5g7Jzyee: Connection refused
Aug 30 16:11:52 hostname gnome-screensav[23998]: Couldn't get presence status: The name org.gnome.SessionManager was not provided by any .service files
Aug 30 16:11:52 hostname gnome-session-binary[23863]: WARNING: Could not parse desktop file blueman.desktop or it references a not found TryExec binary
Aug 30 16:11:52 hostname gnome-session-binary[23863]: WARNING: Could not parse desktop file vino-server.desktop or it references a not found TryExec binary
Aug 30 16:11:52 hostname gnome-session-binary[23863]: WARNING: Could not parse desktop file xembedsniproxy.desktop or it references a not found TryExec binary
Aug 30 16:11:52 hostname gnome-session-binary[23863]: WARNING: Could not parse desktop file plasmashell.desktop or it references a not found TryExec binary
Aug 30 16:11:52 hostname gnome-session-binary[23863]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary
Aug 30 16:11:52 hostname gnome-session-binary[23863]: WARNING: Could not parse desktop file xscreensaver.desktop or it references a not found TryExec binary
Aug 30 16:11:52 hostname gnome-session-binary[23863]: WARNING: Could not parse desktop file klipper.desktop or it references a not found TryExec binary
Aug 30 16:11:52 hostname gnome-session-binary[23863]: WARNING: Could not parse desktop file pam_kwallet_init.desktop or it references a not found TryExec binary
Aug 30 16:11:52 hostname gnome-session-binary[23863]: WARNING: Could not parse desktop file xfsettingsd.desktop or it references a not found TryExec binary
Aug 30 16:11:52 hostname gnome-session-binary[23863]: WARNING: Could not parse desktop file blueman.desktop or it references a not found TryExec binary
Aug 30 16:11:52 hostname gnome-session-binary[23863]: WARNING: Could not parse desktop file baloo_file.desktop or it references a not found TryExec binary
Aug 30 16:11:52 hostname gnome-session-binary[23863]: WARNING: Could not parse desktop file tracker-miner-user-guides.desktop or it references a not found TryExec binary
Aug 30 16:11:52 hostname gnome-session-binary[23863]: WARNING: Could not parse desktop file krunner.desktop or it references a not found TryExec binary
Aug 30 16:11:53 hostname gnome-shell[24009]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-7t5g7Jzyee: Connection refused
Aug 30 16:11:56 hostname gnome-shell[24009]: Some code accessed the property 'LIBMUTTER_API_VERSION' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:56 hostname gnome-shell[24009]: Some code accessed the property 'KEYBOARD_ANIMATION_TIME' on the module 'layout'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:56 hostname gnome-shell[24009]: Some code accessed the property 'ANIMATION_TIME_OUT' on the module 'iconGrid'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:56 hostname gnome-shell[24009]: Some code accessed the property 'ANIMATION_MAX_DELAY_OUT_FOR_ITEM' on the module 'iconGrid'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:57 hostname gnome-shell[24009]: Some code accessed the property 'Urgency' on the module 'messageTray'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:57 hostname gnome-shell[24009]: Some code accessed the property 'PACKAGE_VERSION' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:57 hostname gnome-shell[24009]: Some code accessed the property 'HAVE_NETWORKMANAGER' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:57 hostname gnome-shell[24009]: Some code accessed the property 'SlideDirection' on the module 'overviewControls'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:57 hostname gnome-shell[24009]: Some code accessed the property 'SortGroup' on the module 'ctrlAltTab'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:57 hostname org.gnome.Shell.desktop[24009]: current session already has an ibus-daemon.
Aug 30 16:11:57 hostname gnome-shell[24009]: Some code accessed the property 'Ornament' on the module 'popupMenu'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:57 hostname gnome-shell[24009]: Some code accessed the property 'HAVE_BLUETOOTH' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:57 hostname gnome-shell[24009]: Some code accessed the property 'Keyboard' on the module 'keyboard'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:57 hostname gnome-shell[24009]: Some code accessed the property 'Component' on the module 'networkAgent'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:57 hostname gnome-shell[24009]: Some code accessed the property 'SYSCONFDIR' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:57 hostname gnome-shell[24009]: Some code accessed the property 'Component' on the module 'polkitAgent'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:57 hostname gnome-shell[24009]: Some code accessed the property 'Component' on the module 'telepathyClient'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:57 hostname gnome-shell[24009]: Some code accessed the property 'Component' on the module 'keyring'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:57 hostname gnome-shell[24009]: Some code accessed the property 'Component' on the module 'autorunManager'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:58 hostname gnome-shell[24009]: Some code accessed the property 'Component' on the module 'automountManager'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:58 hostname gnome-shell[24009]: Some code accessed the property 'AnimationDirection' on the module 'iconGrid'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:58 hostname gnome-shell[24009]: Some code accessed the property 'HorizontalSeparator' on the module 'separator'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:58 hostname gnome-shell[24009]: Some code accessed the property 'extensions' on the module 'extensionUtils'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:58 hostname gnome-shell[24009]: Some code accessed the property 'ApplicationsButton' on the module 'menu'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:58 hostname at-spi-dbus-bus.desktop[24102]: Activating service name='org.a11y.atspi.Registry'
Aug 30 16:11:58 hostname at-spi-dbus-bus.desktop[24102]: Successfully activated service 'org.a11y.atspi.Registry'
Aug 30 16:11:58 hostname gsd-wacom[24096]: gsd_device_mapper_get: assertion 'screen != NULL' failed
Aug 30 16:11:58 hostname gsd-wacom[24096]: gsd_device_manager_get: assertion 'screen != NULL' failed
Aug 30 16:11:58 hostname gsd-wacom[24096]: invalid (NULL) pointer instance
Aug 30 16:11:58 hostname gsd-wacom[24096]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Aug 30 16:11:58 hostname gsd-wacom[24096]: invalid (NULL) pointer instance
Aug 30 16:11:58 hostname gsd-wacom[24096]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Aug 30 16:11:58 hostname gsd-wacom[24096]: gsd_device_manager_list_devices: assertion 'GSD_IS_DEVICE_MANAGER (manager)' failed
Aug 30 16:11:58 hostname gsd-xsettings[24099]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist
Aug 30 16:11:58 hostname at-spi2-registr[24115]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Aug 30 16:11:58 hostname at-spi2-registr[24115]: Unable to register client with session manager
Aug 30 16:11:58 hostname gsd-sharing[24166]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Aug 30 16:11:58 hostname gsd-rfkill[24158]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput'
Aug 30 16:11:58 hostname gsd-sharing[24166]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service not loaded.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'MenuSettingsController' on the module 'controller'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'HotCornerManager' on the module 'helper'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'MenuHotKeybinder' on the module 'helper'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'KeybindingManager' on the module 'helper'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'HOT_KEY' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'EMPTY_STRING' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'MENU_APPEARANCE' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'MENU_BUTTON_TEXT' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'MENU_BUTTON_ICON' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'MENU_ICON_PATH' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'MENU_POSITION' on the module 'constants'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'DBusMenu' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'WORKAROUND_RELOAD_TYPE_REGISTER' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'StatusNotifierWatcher' on the module 'statusNotifierWatcher'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'StatusNotifierWatcher' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'DASH_ITEM_LABEL_SHOW_TIME' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'DASH_ANIMATION_TIME' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'DASH_ITEM_LABEL_HIDE_TIME' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'DASH_ITEM_HOVER_TIMEOUT' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname nautilus-autostart.desktop[24204]: sys:1: PyGIWarning: Nautilus was imported without specifying a version first. Use gi.require_version('Nautilus', '3.0') before import to ensure that the right version gets loaded.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'LOCALEDIR' on the module 'config'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'DockManager' on the module 'docking'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'GlobalSignalsHandler' on the module 'utils'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'Intellihide' on the module 'intellihide'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'MyDash' on the module 'dash'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'InjectionsHandler' on the module 'utils'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'ThemeManager' on the module 'theming'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'connect' on the module 'extensionSystem'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname gnome-software[24217]: application has no ID set
Aug 30 16:11:59 hostname gnome-shell[24009]: Some code accessed the property 'MyAppIcon' on the module 'appIcons'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:11:59 hostname org.freedesktop.FileManager1[23877]: sys:1: PyGIWarning: Nautilus was imported without specifying a version first. Use gi.require_version('Nautilus', '3.0') before import to ensure that the right version gets loaded.
Aug 30 16:12:00 hostname gnome-shell[24009]: Some code accessed the property 'Logger' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:12:00 hostname gnome-shell[24009]: Some code accessed the property 'PresenceStatus' on the module 'gnomeSession'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:12:00 hostname gnome-shell[24009]: Some code accessed the property 'PopupAnimation' on the module 'boxpointer'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:12:00 hostname gnome-shell[24009]: Some code accessed the property 'State' on the module 'modalDialog'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:12:00 hostname nautilus-deskto[24204]: Can not calculate _NET_NUMBER_OF_DESKTOPS
Aug 30 16:12:00 hostname nautilus-deskto[24204]: Can not calculate _NET_NUMBER_OF_DESKTOPS
Aug 30 16:12:00 hostname nautilus-deskto[24204]: Can not get _NET_WORKAREA
Aug 30 16:12:00 hostname nautilus-deskto[24204]: Can not determine workarea, guessing at layout
Aug 30 16:12:00 hostname nautilus-deskto[24204]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:12:00 hostname nautilus-deskto[24204]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:12:00 hostname org.gnome.Shell.desktop[24009]: Window manager warning: "XF86RFKill" is not a valid accelerator
Aug 30 16:12:00 hostname nautilus-deskto[24204]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:12:00 hostname gnome-software[24217]: com.github.cybre.budgie-haste-applet was of type addon but had no extends
Aug 30 16:12:00 hostname gnome-software[24217]: com.github.cybre.budgie-screenshot-applet was of type addon but had no extends
Aug 30 16:12:00 hostname gnome-software[24217]: plugin appstream took 1.3 seconds to do setup
Aug 30 16:12:00 hostname gnome-software[24217]: failed to call gs_plugin_add_updates_historical on packagekit-offline: The transaction did not complete
Aug 30 16:12:00 hostname nautilus-deskto[24204]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:12:00 hostname nautilus-deskto[24204]: Can not calculate _NET_NUMBER_OF_DESKTOPS
Aug 30 16:12:00 hostname nautilus-deskto[24204]: Can not calculate _NET_NUMBER_OF_DESKTOPS
Aug 30 16:12:00 hostname nautilus-deskto[24204]: Can not get _NET_WORKAREA
Aug 30 16:12:00 hostname nautilus-deskto[24204]: Can not determine workarea, guessing at layout
Aug 30 16:12:00 hostname nautilus-deskto[24204]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:12:00 hostname nautilus-deskto[24204]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:12:01 hostname nautilus-deskto[24204]: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
Aug 30 16:12:08 hostname pulseaudio[24019]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out
Aug 30 16:12:08 hostname gnome-shell[24009]: Some code accessed the property 'ViewPage' on the module 'viewSelector'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:12:08 hostname gnome-shell[24009]: Some code accessed the property 'SIDE_CONTROLS_ANIMATION_TIME' on the module 'overviewControls'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:12:08 hostname gnome-shell[24009]: Some code accessed the property 'VIGNETTE_BRIGHTNESS' on the module 'lightbox'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:12:08 hostname gnome-shell[24009]: Some code accessed the property 'VIGNETTE_SHARPNESS' on the module 'lightbox'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:12:08 hostname gnome-shell[24009]: Some code accessed the property 'ANIMATION_TIME' on the module 'overview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Aug 30 16:12:11 hostname org.gnome.Nautilus[23877]: sys:1: PyGIWarning: Nautilus was imported without specifying a version first. Use gi.require_version('Nautilus', '3.0') before import to ensure that the right version gets loaded.
Aug 30 16:12:15 hostname tracker-miner-f[24222]: Could not open directory 'file:///home/modir/Desktop/noks/gogs/data/sessions': Error opening directory '/home/modir/Desktop/noks/gogs/data/sessions': Permission denied
Aug 30 16:12:15 hostname tracker-miner-f[24222]: Could not enumerate container / directory 'file:///home/modir/Desktop/noks/gogs/data/sessions', Error opening directory '/home/modir/Desktop/noks/gogs/data/sessions': Permission denied
Aug 30 16:12:19 hostname zeitgeist-datah[24599]: zeitgeist-datahub.vala:227: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
Aug 30 16:12:28 hostname org.gnome.Nautilus[23877]: sys:1: PyGIWarning: Nautilus was imported without specifying a version first. Use gi.require_version('Nautilus', '3.0') before import to ensure that the right version gets loaded.
Aug 30 16:12:41 hostname systemd[23850]: tracker-store.service: Main process exited, code=killed, status=9/KILL
Aug 30 16:12:41 hostname systemd[23850]: tracker-store.service: Failed with result 'signal'.
Aug 30 16:13:13 hostname gnome-shell[24009]: Some code accessed the property 'NotificationDestroyedReason' on the module 'messageTray'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.