-- Logs begin at Thu 2017-10-12 23:51:41 MSK, end at Fri 2017-10-13 00:13:46 MSK. --
окт 12 23:51:41 username kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
окт 12 23:51:41 username kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
окт 12 23:51:41 username kernel:  #2
окт 12 23:51:41 username kernel:  #3
окт 12 23:51:41 username kernel: PCCT header not found.
окт 12 23:51:41 username kernel: ACPI Error: Needed type [Reference], found [Integer] ed1bbf60 (20170531/exresop-103)
окт 12 23:51:41 username kernel: ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20170531/dswexec-461)
окт 12 23:51:41 username kernel: ACPI Error: Method parse/execution failed \_PR.CPU0._PDC, AE_AML_OPERAND_TYPE (20170531/psparse-550)
окт 12 23:51:41 username kernel: pmd_set_huge: Cannot satisfy [mem 0xe0000000-0xe0200000] with a huge-page mapping due to MTRR override.
окт 12 23:51:41 username kernel: (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
окт 12 23:51:41 username kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
окт 12 23:51:41 username kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
окт 12 23:51:41 username kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
окт 12 23:51:41 username kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
окт 12 23:51:41 username kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
окт 12 23:51:41 username kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
окт 12 23:51:41 username kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
окт 12 23:51:41 username kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
окт 12 23:51:41 username kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
окт 12 23:51:41 username kernel: ata1.00: NCQ Send/Recv Log not supported
окт 12 23:51:41 username kernel: ata1.00: NCQ Send/Recv Log not supported
окт 12 23:51:41 username systemd-tmpfiles[384]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
окт 12 23:51:42 username systemd[1]: Failed to activate swap /swapfile.
окт 12 23:51:42 username systemd[1]: Dependency failed for Swap.
окт 12 23:51:42 username kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000044F (\GPIS) (20170531/utaddress-247)
окт 12 23:51:42 username kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20170531/utaddress-247)
окт 12 23:51:42 username kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\GPIO) (20170531/utaddress-247)
окт 12 23:51:42 username kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20170531/utaddress-247)
окт 12 23:51:42 username kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\GPIO) (20170531/utaddress-247)
окт 12 23:51:42 username kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20170531/utaddress-247)
окт 12 23:51:42 username kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\GPIO) (20170531/utaddress-247)
окт 12 23:51:42 username kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20170531/utaddress-247)
окт 12 23:51:42 username kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
окт 12 23:51:42 username kernel: iwlwifi 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
окт 12 23:51:43 username kernel: uvcvideo 2-1.5:1.0: Entity type for entity Extension 4 was not initialized!
окт 12 23:51:43 username kernel: uvcvideo 2-1.5:1.0: Entity type for entity Processing 2 was not initialized!
окт 12 23:51:43 username kernel: uvcvideo 2-1.5:1.0: Entity type for entity Camera 1 was not initialized!
окт 12 23:51:43 username systemd[1]: Failed to activate swap /swapfile.
окт 12 23:51:43 username systemd[1]: Dependency failed for Swap.
окт 12 23:51:47 username NetworkManager[1025]: ((src/devices/nm-device.c:1452)): assertion '<dropped>' failed
окт 12 23:51:47 username wpa_supplicant[1170]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
окт 12 23:51:47 username wpa_supplicant[1170]: dbus: Failed to construct signal
окт 12 23:51:49 username lightdm[1120]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
окт 12 23:51:49 username lightdm[1189]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
окт 12 23:51:49 username lightdm[1189]: PAM adding faulty module: pam_kwallet.so
окт 12 23:51:49 username lightdm[1189]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
окт 12 23:51:49 username lightdm[1189]: PAM adding faulty module: pam_kwallet5.so
окт 12 23:52:02 username lightdm[1313]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
окт 12 23:52:02 username lightdm[1313]: PAM adding faulty module: pam_kwallet.so
окт 12 23:52:02 username lightdm[1313]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
окт 12 23:52:02 username lightdm[1313]: PAM adding faulty module: pam_kwallet5.so
окт 12 23:52:04 username systemd-resolved[1111]: Using degraded feature set (UDP) for DNS server 192.168.3.1.
окт 12 23:52:04 username kernel: vboxdrv: loading out-of-tree module taints kernel.
окт 12 23:52:04 username kernel: VBoxNetFlt: Successfully started.
окт 12 23:52:04 username kernel: VBoxNetAdp: Successfully started.
окт 12 23:52:04 username kernel: VBoxPciLinuxInit
окт 12 23:52:06 username systemd[1]: Failed to start Postfix Mail Transport Agent (instance -).
окт 12 23:52:06 username systemd[1]: postfix@-.service: Failed with result 'exit-code'.
окт 12 23:52:40 username lightdm[1120]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
окт 12 23:52:40 username lightdm[1120]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
окт 12 23:52:40 username org.gnome.ScreenSaver[2217]: Unable to init server: Could not connect: Connection refused
окт 12 23:52:40 username gnome-screensav[2313]: Cannot open display: 
окт 12 23:52:40 username gnome-session-binary[2188]: 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
окт 12 23:52:40 username gnome-session-binary[2188]: WARNING: Could not parse desktop file gnome-welcome-tour.desktop or it references a not found TryExec binary
окт 12 23:52:40 username gnome-session-binary[2188]: WARNING: Could not parse desktop file spice-vdagent.desktop or it references a not found TryExec binary
окт 12 23:52:40 username gnome-session-binary[2188]: WARNING: Could not parse desktop file gnome-initial-setup-copy-worker.desktop or it references a not found TryExec binary
окт 12 23:52:40 username gnome-session-binary[2188]: WARNING: Could not parse desktop file gnome-initial-setup-first-login.desktop or it references a not found TryExec binary
окт 12 23:52:41 username gnome-shell[2325]: Failed to migrate monitor configuration for default:???:0x0000:0x00000000: Monitor mode invalid
окт 12 23:52:41 username org.gnome.Shell.desktop[2325]: glamor: EGL version 1.4 (DRI2):
окт 12 23:52:46 username gnome-shell[2325]: 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.
окт 12 23:52:46 username gnome-shell[2325]: 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.
окт 12 23:52:46 username gnome-shell[2325]: 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.
окт 12 23:52:46 username gnome-shell[2325]: 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.
окт 12 23:52:47 username gsd-sharing[2486]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.
окт 12 23:52:47 username gsd-rfkill[2478]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput'
окт 12 23:52:47 username org.gnome.Shell.desktop[2325]: libinput error: libinput bug: timer: offset negative (-1208819)
окт 12 23:52:47 username org.gnome.Shell.desktop[2325]: libinput error: libinput bug: timer: offset negative (-743427)
окт 12 23:52:48 username org.gnome.Shell.desktop[2325]: Window manager warning: "XF86RFKill" is not a valid accelerator
окт 12 23:52:53 username org.gnome.SettingsDaemon.MediaKeys.desktop[2457]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
окт 12 23:52:54 username gnome-shell[2325]: setup_framebuffers: assertion 'width > 0' failed
окт 12 23:52:54 username fwupd[2705]: failed to open: failed to ping USB Optical Mouse: failed to send: failed to write: wrote -1 of 7
окт 12 23:52:54 username gnome-shell[2325]: 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.
окт 12 23:52:54 username gnome-shell[2325]: Some code accessed the property 'AppIndicator' on the module 'appIndicator'. 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.
окт 12 23:52:54 username gnome-shell[2325]: Some code accessed the property 'StatusNotifierItem' 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.
окт 12 23:52:54 username gnome-shell[2325]: Some code accessed the property 'connectSmart' 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.
окт 12 23:52:54 username gnome-shell[2325]: Some code accessed the property 'IndicatorStatusIcon' on the module 'indicatorStatusIcon'. 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.
окт 12 23:52:54 username gnome-shell[2325]: Some code accessed the property 'IconActor' on the module 'appIndicator'. 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.
окт 12 23:52:54 username gnome-shell[2325]: Some code accessed the property 'IconCache' on the module 'iconCache'. 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.
окт 12 23:52:54 username gnome-shell[2325]: Some code accessed the property 'SNIStatus' on the module 'appIndicator'. 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.
окт 12 23:52:54 username gnome-shell[2325]: Some code accessed the property 'Client' on the module 'dbusMenu'. 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.
окт 12 23:52:55 username org.kde.kwalletd[2217]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
окт 12 23:52:55 username org.kde.kwalletd[2217]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
окт 12 23:52:55 username org.blueman.Mechanism[856]: Unable to init server: Could not connect: Connection refused
окт 12 23:52:55 username org.blueman.Mechanism[856]: Unable to init server: Could not connect: Connection refused
окт 12 23:52:55 username blueman-mechani[2735]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
окт 12 23:52:55 username gsd-rfkill[2478]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput'
окт 12 23:52:55 username gnome-software[2556]: plugin fwupd took 1,6 seconds to do setup
окт 12 23:52:55 username gnome-shell[2325]: drmModeSetCursor2 failed with (Permission denied), drawing cursor with OpenGL from now on
окт 12 23:52:55 username gnome-shell[2325]: WL: unknown object (8), message get_swipe_gesture(no)
окт 12 23:52:55 username gnome-shell[2325]: JS ERROR: TypeError: this._proxy is null
                                             DBusClient<._beginLayoutUpdate@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/dbusMenu.js:293:9
                                             wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                             DBusClient<._requestLayoutUpdate@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/dbusMenu.js:234:13
                                             wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                             DBusClient<._clientReady@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/dbusMenu.js:369:9
                                             wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                             _makeProxyWrapper/</<@resource:///org/gnome/gjs/modules/overrides/Gio.js:203:21
окт 12 23:52:56 username python3[2593]: backintime (username/1): ERROR: Back In Time is not configured!
окт 12 23:53:00 username gnome-software[2556]: plugin appstream took 4,5 seconds to do setup
окт 12 23:53:00 username gnome-shell[2325]: WL: unknown object (8), message get_swipe_gesture(no)
окт 12 23:53:02 username tracker-extract.desktop[2562]: VA error: wayland: failed to open /dev/dri/card0: Permission denied (errno 13)
окт 12 23:53:02 username tracker-extract.desktop[2562]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
окт 12 23:53:02 username tracker-extract.desktop[2562]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
окт 12 23:53:09 username gsd-rfkill[2478]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput'
окт 12 23:53:18 username gnome-shell[2325]: setup_framebuffers: assertion 'width > 0' failed
окт 12 23:53:18 username gnome-shell[2325]: setup_framebuffers: assertion 'width > 0' failed
окт 12 23:53:18 username gnome-shell[2325]: setup_framebuffers: assertion 'width > 0' failed
окт 12 23:53:28 username org.gnome.Shell.desktop[2325]: Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
окт 12 23:53:28 username gsd-print-notif[2476]: Source ID 2 was not found when attempting to remove it
окт 12 23:53:28 username tracker-miner-f[2563]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
окт 12 23:53:28 username tracker-extract[2562]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
окт 12 23:53:28 username tracker-extract[2562]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
окт 12 23:53:28 username tracker-miner-f[2563]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
окт 12 23:53:28 username tracker-miner-f[2563]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
окт 12 23:53:28 username tracker-miner-f[2563]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
окт 12 23:53:28 username tracker-extract[2562]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
окт 12 23:53:28 username evolution-calen[2588]: Error releasing name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2482x2: The connection is closed
окт 12 23:53:28 username evolution-calen[2609]: Error releasing name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2482x3: The connection is closed
окт 12 23:53:28 username tracker-miner-f[2563]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
окт 12 23:53:28 username tracker-extract[2562]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
окт 12 23:53:28 username tracker-extract[2562]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
окт 12 23:53:28 username systemd[1]: lightdm.service: Failed with result 'exit-code'.
окт 12 23:53:28 username evolution-addre[2642]: Error releasing name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx2628x2: The connection is closed
окт 12 23:53:28 username gsd-power[2473]: Error releasing name org.gnome.SettingsDaemon.Power: The connection is closed
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username org.gnome.Shell.desktop[2325]: == Stack trace for context 0xac8010 ==
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x29caac0.
окт 12 23:53:28 username org.gnome.Shell.desktop[2325]: == Stack trace for context 0xac8010 ==
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x282b800.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x282b800.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x26a9ba0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x2857e00.
окт 12 23:53:28 username org.gnome.Shell.desktop[2325]: == Stack trace for context 0xac8010 ==
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username org.gnome.Shell.desktop[2325]: == Stack trace for context 0xac8010 ==
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x282b490.
окт 12 23:53:28 username org.gnome.Shell.desktop[2325]: == Stack trace for context 0xac8010 ==
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x282b490.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x26a9ba0.
окт 12 23:53:28 username systemd[1513]: obex.service: Failed with result 'exit-code'.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x2836aa8.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x282a360.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x282a360.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username org.gnome.Shell.desktop[2325]: == Stack trace for context 0xac8010 ==
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x26a9ba0.
окт 12 23:53:28 username org.gnome.Shell.desktop[2325]: == Stack trace for context 0xac8010 ==
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x1abcb78.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abe360.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abe360.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x26a9ba0.
окт 12 23:53:28 username unknown[2563]: Error while sending AddMatch() message: The connection is closed
окт 12 23:53:28 username unknown[2563]: Error while sending AddMatch() message: The connection is closed
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x2818a58.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abedb0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abedb0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x26a9ba0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x1abdf88.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abea40.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abea40.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x26a9ba0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x2819460.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abf120.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abf120.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x26a9ba0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x28569f0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x282adb0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x282adb0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x26a9ba0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x1abd580.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abe6d0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abe6d0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x26a9ba0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x29cb4c8.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x282bb70.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x282bb70.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x26a9ba0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x28374b0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x282a6d0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x282a6d0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x26a9ba0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x2837eb8.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x282aa40.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x282aa40.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x26a9ba0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x2819e68.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abf490.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abf490.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x26a9ba0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x2824b28.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abf800.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abf800.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x26a9ba0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x2825530.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abfb70.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abfb70.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x26a9ba0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x2825f38.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abfee0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x1abfee0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x26a9ba0.
окт 12 23:53:28 username unknown[2563]: Error while sending AddMatch() message: The connection is closed
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x28573f8.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x29cbed0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x29e0ba0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x29e15a8.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x2a36820.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x29f38e0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x29f38e0.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x2a24e18.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StBin 0x2a25b80.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x29f3570.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was destroy on StButton 0x29f3570.
окт 12 23:53:28 username gnome-shell[2325]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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.
окт 12 23:53:28 username gnome-shell[2325]: The offending signal was actor-removed on ShellGenericContainer 0x2a24e18.
окт 12 23:53:29 username org.gnome.Shell.desktop[2325]: (EE)
окт 12 23:53:29 username org.gnome.Shell.desktop[2325]: Fatal server error:
окт 12 23:53:29 username org.gnome.Shell.desktop[2325]: (EE) failed to read Wayland events: Connection reset by peer
окт 12 23:53:29 username org.gnome.Shell.desktop[2325]: (EE)
окт 12 23:53:29 username lightdm[3356]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
окт 12 23:53:29 username lightdm[3371]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
окт 12 23:53:29 username lightdm[3371]: PAM adding faulty module: pam_kwallet.so
окт 12 23:53:29 username lightdm[3371]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
окт 12 23:53:29 username lightdm[3371]: PAM adding faulty module: pam_kwallet5.so
окт 12 23:53:30 username lightdm[3428]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
окт 12 23:53:30 username lightdm[3428]: PAM adding faulty module: pam_kwallet.so
окт 12 23:53:30 username lightdm[3428]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
окт 12 23:53:30 username lightdm[3428]: PAM adding faulty module: pam_kwallet5.so
окт 12 23:53:46 username lightdm[3356]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
окт 12 23:53:46 username mate-session[3450]: WARNING: Unable to find provider '' of required component 'dock'
окт 12 23:53:47 username wnck-applet[3592]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-1BWuKCYCP4: Connection refused
окт 12 23:53:47 username trashapplet[3639]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-1BWuKCYCP4: Connection refused
окт 12 23:53:47 username notification-ar[3641]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-1BWuKCYCP4: Connection refused
окт 12 23:53:47 username mate-session[3450]: WARNING: Could not launch application 'spice-vdagent.desktop': Unable to start application: Failed to execute child process “/usr/bin/spice-vdagent” (No such file or directory)
окт 12 23:53:48 username at-spi2-registr[3720]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
окт 12 23:53:48 username at-spi2-registr[3720]: Unable to register client with session manager
окт 12 23:53:48 username at-spi2-registr[3720]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
окт 12 23:53:48 username at-spi2-registr[3720]: Unable to register client with session manager
окт 12 23:53:48 username clock-applet[3755]: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner GtkToggleButton)
окт 12 23:53:48 username org.kde.kwalletd[3479]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
окт 12 23:53:48 username org.kde.kwalletd[3479]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
окт 12 23:53:49 username python3[3721]: backintime (username/1): ERROR: Back In Time is not configured!
окт 12 23:53:49 username org.blueman.Mechanism[856]: Unable to init server: Could not connect: Connection refused
окт 12 23:53:49 username org.blueman.Mechanism[856]: Unable to init server: Could not connect: Connection refused
окт 12 23:53:49 username blueman-mechani[3863]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
окт 13 00:00:43 username postfix/sendmail[7871]: fatal: open /etc/postfix/main.cf: No such file or directory
окт 13 00:00:43 username postfix/sendmail[7879]: fatal: open /etc/postfix/main.cf: No such file or directory
окт 13 00:06:49 username systemd-tmpfiles[9684]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
окт 13 00:07:45 username kernel: VBoxPciLinuxLinuxUnload
окт 13 00:07:45 username kernel: VBoxNetFlt: Successfully started.
окт 13 00:07:45 username kernel: VBoxNetAdp: Successfully started.
окт 13 00:07:45 username kernel: VBoxPciLinuxInit
окт 13 00:13:32 username kernel: VBoxPciLinuxLinuxUnload
окт 13 00:13:32 username kernel: VBoxNetFlt: Successfully started.
окт 13 00:13:32 username kernel: VBoxNetAdp: Successfully started.
окт 13 00:13:32 username kernel: VBoxPciLinuxInit
окт 13 00:13:46 username systemd[1]: gdm.service: Unit cannot be reloaded because it is inactive.