-- Logs begin at Mon 2017-06-26 15:16:44 AWST, end at Mon 2017-06-26 17:23:02 AWST. --
Jun 26 15:16:44 hostname kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jun 26 15:16:44 hostname kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jun 26 15:16:44 hostname kernel: PCCT header not found.
Jun 26 15:16:44 hostname kernel: pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
Jun 26 15:16:44 hostname kernel: (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
Jun 26 15:16:44 hostname kernel: tpm tpm0: A TPM error (6) occurred attempting to read a pcr value
Jun 26 15:16:44 hostname kernel: tpm tpm0: A TPM error (6) occurred attempting to read a pcr value
Jun 26 15:16:45 hostname kernel: ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20160930/utaddress-247)
Jun 26 15:16:45 hostname kernel: ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20160930/utaddress-247)
Jun 26 15:16:45 hostname kernel: ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRE) (20160930/utaddress-247)
Jun 26 15:16:45 hostname kernel: ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20160930/utaddress-247)
Jun 26 15:16:45 hostname kernel: ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20160930/utaddress-247)
Jun 26 15:16:45 hostname kernel: ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRE) (20160930/utaddress-247)
Jun 26 15:16:45 hostname kernel: ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C1F (\GPBL) (20160930/utaddress-247)
Jun 26 15:16:45 hostname kernel: ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20160930/utaddress-247)
Jun 26 15:16:45 hostname kernel: ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20160930/utaddress-247)
Jun 26 15:16:45 hostname kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Jun 26 15:16:45 hostname systemd-udevd[372]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90010, key code 190): Invalid argument
Jun 26 15:16:45 hostname systemd-udevd[372]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90011, key code 148): Invalid argument
Jun 26 15:16:45 hostname systemd-udevd[372]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90012, key code 152): Invalid argument
Jun 26 15:16:45 hostname systemd-udevd[372]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90013, key code 236): Invalid argument
Jun 26 15:16:45 hostname systemd-udevd[372]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90014, key code 238): Invalid argument
Jun 26 15:16:45 hostname systemd-udevd[372]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90015, key code 212): Invalid argument
Jun 26 15:16:45 hostname systemd-udevd[372]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90016, key code 227): Invalid argument
Jun 26 15:16:45 hostname systemd-udevd[372]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90017, key code 191): Invalid argument
Jun 26 15:16:45 hostname systemd-udevd[372]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90019, key code 205): Invalid argument
Jun 26 15:16:45 hostname systemd-udevd[372]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001a, key code 225): Invalid argument
Jun 26 15:16:45 hostname systemd-udevd[372]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001b, key code 224): Invalid argument
Jun 26 15:16:45 hostname systemd-udevd[372]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001d, key code 372): Invalid argument
Jun 26 15:16:45 hostname systemd-tmpfiles[649]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Jun 26 15:16:45 hostname systemd[1]: Failed to start AppArmor initialization.
Jun 26 15:16:45 hostname systemd[1]: apparmor.service: Failed with result 'exit-code'.
Jun 26 15:16:45 hostname NetworkManager[872]: ((devices/nm-device.c:970)): assertion '<dropped>' failed
Jun 26 15:16:46 hostname lightdm[1031]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 15:16:46 hostname lightdm[1085]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jun 26 15:16:46 hostname lightdm[1085]: PAM adding faulty module: pam_kwallet.so
Jun 26 15:16:46 hostname lightdm[1085]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jun 26 15:16:46 hostname lightdm[1085]: PAM adding faulty module: pam_kwallet5.so
Jun 26 15:16:46 hostname indicator-sound[1150]: 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
Jun 26 15:16:46 hostname indicator-keybo[1143]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Jun 26 15:16:46 hostname lightdm[1232]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jun 26 15:16:46 hostname lightdm[1232]: PAM adding faulty module: pam_kwallet.so
Jun 26 15:16:46 hostname lightdm[1232]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jun 26 15:16:46 hostname lightdm[1232]: PAM adding faulty module: pam_kwallet5.so
Jun 26 15:16:46 hostname indicator-sound[1150]: media-player-list-greeter.vala:51: Unable to get active entry: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.UnityGreeter was not provided by any .service files
Jun 26 15:16:51 hostname org.freedesktop.Notifications[1106]: Unable to init server: Could not connect: Connection refused
Jun 26 15:16:51 hostname notify-osd[1275]: cannot open display: 
Jun 26 15:16:51 hostname org.freedesktop.Notifications[1106]: Unable to init server: Could not connect: Connection refused
Jun 26 15:16:51 hostname notify-osd[1293]: cannot open display: 
Jun 26 15:17:06 hostname ModemManager[834]: <warn>  Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type'
Jun 26 15:17:06 hostname ModemManager[834]: <warn>  Couldn't create modem for device at '/sys/devices/pci0000:00/0000:00:16.3': Failed to find primary AT port
Jun 26 15:17:11 hostname pulseaudio[1195]: [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.
Jun 26 15:17:36 hostname lightdm[1031]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 15:17:36 hostname lightdm[1031]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 15:17:36 hostname org.gnome.ScreenSaver[1386]: Unable to init server: Could not connect: Connection refused
Jun 26 15:17:36 hostname gnome-screensav[1502]: Unable to initialize GTK+
Jun 26 15:17:36 hostname gnome-session-binary[1373]: 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
Jun 26 15:17:36 hostname gnome-session-binary[1373]: WARNING: Could not parse desktop file gnome-initial-setup-copy-worker.desktop or it references a not found TryExec binary
Jun 26 15:17:36 hostname gnome-session-binary[1373]: WARNING: Could not parse desktop file gnome-welcome-tour.desktop or it references a not found TryExec binary
Jun 26 15:17:36 hostname gnome-session-binary[1373]: WARNING: Could not parse desktop file spice-vdagent.desktop or it references a not found TryExec binary
Jun 26 15:17:36 hostname gnome-session-binary[1373]: WARNING: Could not parse desktop file gnome-initial-setup-first-login.desktop or it references a not found TryExec binary
Jun 26 15:17:36 hostname indicator-sound[1150]: g_object_ref: assertion 'object->ref_count > 0' failed
Jun 26 15:17:36 hostname org.gnome.Shell.desktop[1521]: glamor: EGL version 1.4 (DRI2):
Jun 26 15:17:37 hostname org.gnome.Shell.desktop[1521]: current session already has an ibus-daemon.
Jun 26 15:17:37 hostname gsd-sharing[1651]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Jun 26 15:17:37 hostname gsd-color[1682]: Failed to connect to GeoClue2 service: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Geolocation disabled for UID 1000
Jun 26 15:17:37 hostname gsd-power[1640]: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed
Jun 26 15:17:38 hostname nautilus-deskto[1780]: Can not calculate _NET_NUMBER_OF_DESKTOPS
Jun 26 15:17:38 hostname nautilus-deskto[1780]: Can not calculate _NET_NUMBER_OF_DESKTOPS
Jun 26 15:17:38 hostname nautilus-deskto[1780]: Can not get _NET_WORKAREA
Jun 26 15:17:38 hostname nautilus-deskto[1780]: Can not determine workarea, guessing at layout
Jun 26 15:17:39 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[1687]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
Jun 26 15:17:39 hostname fwupd[1899]: ignoring add-delay as device usb:00:02 already pending
Jun 26 15:17:39 hostname fwupd[1899]: ignoring add-delay as device usb:00:01 already pending
Jun 26 15:17:50 hostname gnome-shell[1521]: Could not import pending buffer: Unsupported buffer format 12760
Jun 26 15:17:57 hostname zeitgeist-datah[1969]: zeitgeist-datahub.vala:227: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
Jun 26 15:18:01 hostname pulseaudio[1552]: [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.
Jun 26 15:18:37 hostname kernel: show_signal_msg: 35 callbacks suppressed
Jun 26 15:18:51 hostname gnome-shell[1521]: Could not import pending buffer: Unsupported buffer format 12760
Jun 26 15:19:21 hostname gnome-shell[1521]: Could not import pending buffer: Unsupported buffer format 12760
Jun 26 15:20:47 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[1687]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
Jun 26 15:22:12 hostname gnome-shell[1521]: Could not import pending buffer: Unsupported buffer format 12760
Jun 26 15:32:20 hostname org.gnome.ScreenSaver[1386]: [xcb] Extra reply data still left in queue
Jun 26 15:32:20 hostname org.gnome.ScreenSaver[1386]: [xcb] This is most likely caused by a broken X extension library
Jun 26 15:32:20 hostname org.gnome.ScreenSaver[1386]: [xcb] Aborting, sorry about that.
Jun 26 15:32:20 hostname org.gnome.ScreenSaver[1386]: gnome-screensaver: ../../src/xcb_io.c:568: _XReply: Assertion `!xcb_xlib_extra_reply_data_left' failed.
Jun 26 15:32:20 hostname systemd-tmpfiles[2448]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Jun 26 16:17:37 hostname evolution-sourc[1578]: secret_service_search_sync: must specify at least one attribute to match
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:01 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname org.gnome.Shell.desktop[1521]: Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Jun 26 17:22:03 hostname gsd-print-notif[1645]: Source ID 8 was not found when attempting to remove it
Jun 26 17:22:03 hostname gnome-shell-cal[1574]: The calendar backend for 'Birthdays & Anniversaries' has crashed.
Jun 26 17:22:03 hostname tracker-miner-f[1821]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Jun 26 17:22:03 hostname gnome-session-binary[1373]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:03 hostname tracker-miner-f[1821]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Jun 26 17:22:03 hostname gnome-shell[1521]: instance of invalid non-instantiatable type '(null)'
Jun 26 17:22:03 hostname gnome-shell[1521]: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a38a1e4d00.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38a1e2c80.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38a1e2c80.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was actor-removed on ShellGenericContainer 0x55a389ed3850.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a389ea4660.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a3880fbe80.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a3880fbe80.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was actor-removed on ShellGenericContainer 0x55a389ed3850.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a38a05b240.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38a057800.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38a057800.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was actor-removed on ShellGenericContainer 0x55a389ed3850.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a389eb3260.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38810e280.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38810e280.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was actor-removed on ShellGenericContainer 0x55a389ed3850.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a389e44d50.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a389e40510.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a389e40510.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was actor-removed on ShellGenericContainer 0x55a389ed3850.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a389e67940.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a389e632c0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a389e632c0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was actor-removed on ShellGenericContainer 0x55a389ed3850.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a389e3bc30.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a389e2e790.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a389e2e790.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was actor-removed on ShellGenericContainer 0x55a389ed3850.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a38a0781c0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38a0737a0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38a0737a0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was actor-removed on ShellGenericContainer 0x55a389ed3850.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a388111540.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a389eb8aa0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a389eb8aa0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was actor-removed on ShellGenericContainer 0x55a389ed3850.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a38a06aa40.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38a06ecd0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38a06ecd0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was actor-removed on ShellGenericContainer 0x55a389ed3850.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a389e1c750.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a389de6fb0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a389de6fb0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was actor-removed on ShellGenericContainer 0x55a389ed3850.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a389ede060.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a389e236c0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a389e236c0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was actor-removed on ShellGenericContainer 0x55a389ed3850.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a38a043aa0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38a040110.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38a040110.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was actor-removed on ShellGenericContainer 0x55a389ed3850.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a38a050030.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38a053150.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38a053150.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was actor-removed on ShellGenericContainer 0x55a389ed3850.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a38a1edc60.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a38a1f83a0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a38a202450.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a38a20c7c0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a38a2562a0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38a254070.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38a254070.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was actor-removed on ShellGenericContainer 0x55a38a22e5f0.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StBin 0x55a38a24a570.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38a245340.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was destroy on StButton 0x55a38a245340.
Jun 26 17:22:03 hostname gnome-shell[1521]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Jun 26 17:22:03 hostname gnome-shell[1521]: The offending signal was actor-removed on ShellGenericContainer 0x55a38a22e5f0.
Jun 26 17:22:03 hostname pulseaudio[2560]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /run/user/1000/bus: Connection refused
Jun 26 17:22:03 hostname pulseaudio[2560]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /run/user/1000/bus: Connection refused
Jun 26 17:22:03 hostname org.gnome.Shell.desktop[1521]: (EE)
Jun 26 17:22:03 hostname org.gnome.Shell.desktop[1521]: Fatal server error:
Jun 26 17:22:03 hostname org.gnome.Shell.desktop[1521]: (EE) failed to read Wayland events: Connection reset by peer
Jun 26 17:22:03 hostname org.gnome.Shell.desktop[1521]: (EE)
Jun 26 17:22:03 hostname systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jun 26 17:22:04 hostname org.a11y.Bus[2649]: Activating service name='org.a11y.atspi.Registry'
Jun 26 17:22:04 hostname org.a11y.Bus[2649]: Successfully activated service 'org.a11y.atspi.Registry'
Jun 26 17:22:04 hostname lightdm[2619]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:04 hostname lightdm[2665]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jun 26 17:22:04 hostname lightdm[2665]: PAM adding faulty module: pam_kwallet.so
Jun 26 17:22:04 hostname lightdm[2665]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jun 26 17:22:04 hostname lightdm[2665]: PAM adding faulty module: pam_kwallet5.so
Jun 26 17:22:05 hostname indicator-keybo[2723]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Jun 26 17:22:05 hostname indicator-sound[2732]: 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
Jun 26 17:22:05 hostname lightdm[2782]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jun 26 17:22:05 hostname lightdm[2782]: PAM adding faulty module: pam_kwallet.so
Jun 26 17:22:05 hostname lightdm[2782]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jun 26 17:22:05 hostname lightdm[2782]: PAM adding faulty module: pam_kwallet5.so
Jun 26 17:22:25 hostname lightdm[2619]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:25 hostname indicator-sound[2732]: Name lost or unable to acquire bus: com.canonical.indicator.sound
Jun 26 17:22:25 hostname gnome-session-c[2906]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-Cw1gKpG2nW: Connection refused
Jun 26 17:22:25 hostname gnome-session-binary[2806]: WARNING: Could not make bus activated clients aware of QT_IM_MODULE=ibus environment variable: Could not connect: Connection refused
Jun 26 17:22:25 hostname gnome-session-binary[2806]: WARNING: Could not make bus activated clients aware of XMODIFIERS=@im=ibus environment variable: Could not connect: Connection refused
Jun 26 17:22:25 hostname gnome-session-binary[2806]: WARNING: Could not make bus activated clients aware of GNOME_DESKTOP_SESSION_ID=this-is-deprecated environment variable: Could not connect: Connection refused
Jun 26 17:22:25 hostname gnome-session-binary[2806]: WARNING: Could not make bus activated clients aware of XDG_MENU_PREFIX=gnome- environment variable: Could not connect: Connection refused
Jun 26 17:22:25 hostname gnome-session-binary[2806]: WARNING: Lost name on bus: org.gnome.SessionManager
Jun 26 17:22:25 hostname gnome-session-binary[2806]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Jun 26 17:22:26 hostname lightdm[2619]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:26 hostname lightdm[2922]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jun 26 17:22:26 hostname lightdm[2922]: PAM adding faulty module: pam_kwallet.so
Jun 26 17:22:26 hostname lightdm[2922]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jun 26 17:22:26 hostname lightdm[2922]: PAM adding faulty module: pam_kwallet5.so
Jun 26 17:22:26 hostname indicator-sound[2986]: 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
Jun 26 17:22:26 hostname indicator-keybo[2980]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Jun 26 17:22:26 hostname lightdm[3041]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jun 26 17:22:26 hostname lightdm[3041]: PAM adding faulty module: pam_kwallet.so
Jun 26 17:22:26 hostname lightdm[3041]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jun 26 17:22:26 hostname lightdm[3041]: PAM adding faulty module: pam_kwallet5.so
Jun 26 17:22:28 hostname pulseaudio[2560]: [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.
Jun 26 17:22:28 hostname pulseaudio[3022]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out
Jun 26 17:22:34 hostname lightdm[2619]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:34 hostname lightdm[2619]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:34 hostname gnome-session-binary[3062]: WARNING: Could not make bus activated clients aware of QT_IM_MODULE=ibus environment variable: Could not connect: Connection refused
Jun 26 17:22:34 hostname gnome-session-binary[3062]: WARNING: Could not make bus activated clients aware of XMODIFIERS=@im=ibus environment variable: Could not connect: Connection refused
Jun 26 17:22:34 hostname gnome-session-binary[3062]: WARNING: Could not make bus activated clients aware of GNOME_DESKTOP_SESSION_ID=this-is-deprecated environment variable: Could not connect: Connection refused
Jun 26 17:22:34 hostname gnome-session-binary[3062]: WARNING: Could not make bus activated clients aware of XDG_MENU_PREFIX=gnome- environment variable: Could not connect: Connection refused
Jun 26 17:22:34 hostname gnome-session-binary[3062]: WARNING: Could not make bus activated clients aware of SSH_AUTH_SOCK=/run/user/1000/keyring/ssh environment variable: Could not connect: Connection refused
Jun 26 17:22:34 hostname gnome-session-binary[3062]: WARNING: Lost name on bus: org.gnome.SessionManager
Jun 26 17:22:34 hostname gnome-session-binary[3062]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Jun 26 17:22:34 hostname lightdm[2619]: Error activating login1 session: GDBus.Error:org.freedesktop.login1.NoSuchSession: No session 'c6' known
Jun 26 17:22:34 hostname lightdm[2619]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 26 17:22:34 hostname lightdm[3182]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jun 26 17:22:34 hostname lightdm[3182]: PAM adding faulty module: pam_kwallet.so
Jun 26 17:22:34 hostname lightdm[3182]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jun 26 17:22:34 hostname lightdm[3182]: PAM adding faulty module: pam_kwallet5.so
Jun 26 17:22:37 hostname indicator-sound[3250]: 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
Jun 26 17:22:37 hostname indicator-keybo[3248]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Jun 26 17:22:37 hostname lightdm[3302]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Jun 26 17:22:37 hostname lightdm[3302]: PAM adding faulty module: pam_kwallet.so
Jun 26 17:22:37 hostname lightdm[3302]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Jun 26 17:22:37 hostname lightdm[3302]: PAM adding faulty module: pam_kwallet5.so
Jun 26 17:23:02 hostname pulseaudio[3283]: [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.