===================== = EndlessOS version = ===================== NAME="Endless" VERSION="3.3.1" ID="endless" ID_LIKE="ubuntu debian" PRETTY_NAME="Endless 3.3.1" VERSION_ID="3.3.1" HOME_URL="http://www.endlessm.com/" BUILD_ID="171025-194713" ========== = Kernel = ========== Linux endless 4.13.0-12-generic #13+dev98.98453b2beos3.3.2-Endless SMP Tue Oct 24 07:20:29 UTC 2 x86_64 GNU/Linux cmdline: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-a7d4a286f29b21cc342a066d74a68b894ded66e4fcd88e20fcd025bad1c49609/vmlinuz-4.13.0-12-generic root=UUID=a2833eed-cc31-409c-b18d-e8a3571c0c55 rw splash plymouth.ignore-serial-consoles quiet ostree=/ostree/boot.1/eos/a7d4a286f29b21cc342a066d74a68b894ded66e4fcd88e20fcd025bad1c49609/0 Module Size Used by ccm 20480 6 rfcomm 77824 0 cmac 16384 1 bnep 20480 2 joydev 20480 0 intel_rapl 20480 0 x86_pkg_temp_thermal 16384 0 intel_powerclamp 16384 0 coretemp 16384 0 pn544_mei 16384 0 mei_phy 16384 1 pn544_mei arc4 16384 2 pn544 20480 1 pn544_mei hci 49152 2 mei_phy,pn544 cmdlinepart 16384 0 nfc 114688 2 hci,pn544 snd_hda_codec_hdmi 49152 1 intel_spi_platform 16384 0 kvm_intel 204800 0 kvm 585728 1 kvm_intel snd_hda_codec_realtek 94208 1 snd_hda_codec_generic 73728 1 snd_hda_codec_realtek irqbypass 16384 1 kvm intel_spi 20480 1 intel_spi_platform crct10dif_pclmul 16384 0 spi_nor 28672 1 intel_spi crc32_pclmul 16384 0 ghash_clmulni_intel 16384 0 mtd 57344 4 spi_nor,intel_spi,cmdlinepart pcbc 16384 0 acer_wmi 20480 0 sparse_keymap 16384 1 acer_wmi wmi_bmof 16384 0 uvcvideo 90112 0 aesni_intel 188416 6 videobuf2_vmalloc 16384 1 uvcvideo aes_x86_64 20480 1 aesni_intel crypto_simd 16384 1 aesni_intel videobuf2_memops 16384 1 videobuf2_vmalloc glue_helper 16384 1 aesni_intel iwlmvm 385024 0 cryptd 24576 3 crypto_simd,ghash_clmulni_intel,aesni_intel mac80211 778240 1 iwlmvm videobuf2_v4l2 24576 1 uvcvideo videobuf2_core 40960 2 uvcvideo,videobuf2_v4l2 intel_cstate 20480 0 iwlwifi 249856 1 iwlmvm intel_rapl_perf 16384 0 videodev 176128 3 uvcvideo,videobuf2_core,videobuf2_v4l2 btusb 45056 0 btrtl 16384 1 btusb btbcm 16384 1 btusb snd_hda_intel 40960 4 btintel 16384 1 btusb media 40960 2 uvcvideo,videodev rtsx_pci_ms 20480 0 psmouse 147456 0 input_leds 16384 0 bluetooth 544768 31 btrtl,btintel,bnep,btbcm,rfcomm,btusb memstick 16384 1 rtsx_pci_ms cfg80211 610304 3 iwlmvm,iwlwifi,mac80211 e1000e 245760 0 snd_hda_codec 126976 4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek mei_me 40960 0 ecdh_generic 24576 1 bluetooth lpc_ich 24576 0 snd_hda_core 81920 5 snd_hda_intel,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek ptp 20480 1 e1000e mei 102400 4 mei_phy,mei_me,pn544_mei snd_soc_rt5640 118784 0 shpchp 36864 0 snd_soc_rl6231 16384 1 snd_soc_rt5640 pps_core 20480 1 ptp snd_soc_core 229376 1 snd_soc_rt5640 snd_hwdep 20480 1 snd_hda_codec snd_compress 20480 1 snd_soc_core ac97_bus 16384 1 snd_soc_core snd_pcm_dmaengine 16384 1 snd_soc_core snd_pcm 98304 7 snd_hda_intel,snd_hda_codec,snd_pcm_dmaengine,snd_hda_core,snd_soc_rt5640,snd_hda_codec_hdmi,snd_soc_core snd_timer 32768 1 snd_pcm snd_soc_sst_acpi 16384 0 snd 81920 18 snd_compress,snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek,snd_soc_core,snd_pcm dell_smo8800 16384 0 snd_soc_sst_match 16384 1 snd_soc_sst_acpi wmi 24576 2 wmi_bmof,acer_wmi dw_dmac 16384 0 elan_i2c 36864 0 dw_dmac_core 24576 1 dw_dmac intel_smartconnect 16384 0 soundcore 16384 1 snd spi_pxa2xx_platform 24576 0 8250_dw 16384 0 mac_hid 16384 0 ip_tables 28672 0 x_tables 40960 1 ip_tables amdgpu 2015232 0 rtsx_pci_sdmmc 24576 0 i915 1806336 4 amdkfd 188416 1 amd_iommu_v2 20480 1 amdkfd radeon 1478656 1 i2c_algo_bit 16384 3 amdgpu,radeon,i915 drm_kms_helper 167936 3 amdgpu,radeon,i915 ahci 36864 2 serio_raw 16384 0 ttm 94208 2 amdgpu,radeon libahci 32768 1 ahci syscopyarea 16384 1 drm_kms_helper sysfillrect 16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper rtsx_pci 57344 2 rtsx_pci_sdmmc,rtsx_pci_ms fb_sys_fops 16384 1 drm_kms_helper drm 360448 9 amdgpu,radeon,i915,ttm,drm_kms_helper sdhci_acpi 16384 0 video 40960 2 acer_wmi,i915 sdhci 45056 1 sdhci_acpi i2c_hid 20480 0 hid 118784 1 i2c_hid =================== = EndlessOS image = =================== eos-eos3.3-amd64-amd64.171026-021926.en ========== = Uptime = ========== 22:16:34 up 22 min, 1 user, load average: 1.04, 1.79, 1.32 ================= = OSTree status = ================= eos ed6c4ba1f16b358cddcb7cb0644f1f408bf307e1be25f7c7e5539bff1e298cdc.0 (pending) origin refspec: eos:os/eos/amd64/eos3 GPG: Signature made Tue 14 Nov 2017 07:16:43 AM PST using RSA key ID 9E08D8DABA02FC46 GPG: Good signature from "EOS OSTree Signing Key 1 " GPG: Signature made Tue 14 Nov 2017 07:21:19 AM PST using RSA key ID 9E08D8DABA02FC46 GPG: Good signature from "EOS OSTree Signing Key 1 " * eos 85fcca7d196504ab5808a0e85d0cfbd4fd0c5fcf6cad4a2e0427d22b20d783d5.0 origin refspec: eos:os/eos/amd64/eos3 GPG: Signature made Wed 25 Oct 2017 01:26:44 PM PDT using RSA key ID 9E08D8DABA02FC46 GPG: Good signature from "EOS OSTree Signing Key 1 " ========================== = Product identification = ========================== sys_vendor: Acer product_name: TMP645-MG product_uuid: 56CA48BF-3961-E311-A44F-201A06BA10B0 product_version: V2.07 board_asset_tag: Type2 - Board Asset Tag board_name: BAD40_HW board_vendor: Acer board_version: V2.07 bios_date: 01/14/2014 bios_vendor: Insyde Corp. bios_version: V2.07 chassis_asset_tag: Chassis Asset Tag chassis_type: 10 chassis_vendor: Acer chassis_version: Chassis Version ======= = CPU = ======= processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 69 model name : Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz stepping : 1 microcode : 0x17 cpu MHz : 2294.630 cache size : 3072 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts bugs : bogomips : 4589.26 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 69 model name : Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz stepping : 1 microcode : 0x17 cpu MHz : 2294.630 cache size : 3072 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts bugs : bogomips : 4589.26 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 69 model name : Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz stepping : 1 microcode : 0x17 cpu MHz : 2294.630 cache size : 3072 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts bugs : bogomips : 4589.26 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 69 model name : Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz stepping : 1 microcode : 0x17 cpu MHz : 2294.630 cache size : 3072 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts bugs : bogomips : 4589.26 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: ========== = Memory = ========== total used free shared buff/cache available Mem: 7.7G 1.2G 3.1G 249M 3.4G 6.0G Swap: 4.0G 0B 4.0G MemTotal: 8060200 kB MemFree: 3268992 kB MemAvailable: 6254744 kB Buffers: 213064 kB Cached: 3019536 kB SwapCached: 0 kB Active: 2344768 kB Inactive: 1946036 kB Active(anon): 1062124 kB Inactive(anon): 251532 kB Active(file): 1282644 kB Inactive(file): 1694504 kB Unevictable: 32 kB Mlocked: 32 kB SwapTotal: 4193600 kB SwapFree: 4193600 kB Dirty: 560 kB Writeback: 0 kB AnonPages: 1058256 kB Mapped: 444908 kB Shmem: 255456 kB Slab: 372964 kB SReclaimable: 316420 kB SUnreclaim: 56544 kB KernelStack: 10128 kB PageTables: 44168 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 8223700 kB Committed_AS: 5494704 kB VmallocTotal: 34359738367 kB VmallocUsed: 0 kB VmallocChunk: 0 kB HardwareCorrupted: 0 kB AnonHugePages: 0 kB ShmemHugePages: 0 kB ShmemPmdMapped: 0 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB DirectMap4k: 168704 kB DirectMap2M: 4964352 kB DirectMap1G: 4194304 kB ========= = Disks = ========= /org/freedesktop/UDisks2/Manager: org.freedesktop.UDisks2.Manager: Version: 2.1.8 /org/freedesktop/UDisks2/block_devices/loop0: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/loop0 DeviceNumber: 1792 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/loop0 ReadOnly: false Size: 0 Symlinks: org.freedesktop.UDisks2.Loop: Autoclear: false BackingFile: SetupByUID: 0 /org/freedesktop/UDisks2/block_devices/loop1: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/loop1 DeviceNumber: 1793 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/loop1 ReadOnly: false Size: 0 Symlinks: org.freedesktop.UDisks2.Loop: Autoclear: false BackingFile: SetupByUID: 0 /org/freedesktop/UDisks2/block_devices/loop2: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/loop2 DeviceNumber: 1794 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/loop2 ReadOnly: false Size: 0 Symlinks: org.freedesktop.UDisks2.Loop: Autoclear: false BackingFile: SetupByUID: 0 /org/freedesktop/UDisks2/block_devices/loop3: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/loop3 DeviceNumber: 1795 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/loop3 ReadOnly: false Size: 0 Symlinks: org.freedesktop.UDisks2.Loop: Autoclear: false BackingFile: SetupByUID: 0 /org/freedesktop/UDisks2/block_devices/loop4: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/loop4 DeviceNumber: 1796 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/loop4 ReadOnly: false Size: 0 Symlinks: org.freedesktop.UDisks2.Loop: Autoclear: false BackingFile: SetupByUID: 0 /org/freedesktop/UDisks2/block_devices/loop5: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/loop5 DeviceNumber: 1797 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/loop5 ReadOnly: false Size: 0 Symlinks: org.freedesktop.UDisks2.Loop: Autoclear: false BackingFile: SetupByUID: 0 /org/freedesktop/UDisks2/block_devices/loop6: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/loop6 DeviceNumber: 1798 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/loop6 ReadOnly: false Size: 0 Symlinks: org.freedesktop.UDisks2.Loop: Autoclear: false BackingFile: SetupByUID: 0 /org/freedesktop/UDisks2/block_devices/loop7: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/loop7 DeviceNumber: 1799 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/loop7 ReadOnly: false Size: 0 Symlinks: org.freedesktop.UDisks2.Loop: Autoclear: false BackingFile: SetupByUID: 0 /org/freedesktop/UDisks2/block_devices/sda: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/sda DeviceNumber: 2048 Drive: '/org/freedesktop/UDisks2/drives/TOSHIBA_THNSNH256GMCT_Z3JS1156TKBY' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-TOSHIBA_THNSNH256GMCT_Z3JS1156TKBY IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sda ReadOnly: false Size: 256060514304 Symlinks: /dev/disk/by-id/ata-TOSHIBA_THNSNH256GMCT_Z3JS1156TKBY /dev/disk/by-id/wwn-0x500080db1105e051 /dev/disk/by-path/pci-0000:00:1f.2-ata-2 org.freedesktop.UDisks2.PartitionTable: Type: gpt /org/freedesktop/UDisks2/block_devices/sda1: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/sda1 DeviceNumber: 2049 Drive: '/org/freedesktop/UDisks2/drives/TOSHIBA_THNSNH256GMCT_Z3JS1156TKBY' HintAuto: false HintIconName: HintIgnore: true HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-TOSHIBA_THNSNH256GMCT_Z3JS1156TKBY-part1 IdLabel: IdType: vfat IdUUID: 8F4A-78F7 IdUsage: filesystem IdVersion: FAT16 MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sda1 ReadOnly: false Size: 65011712 Symlinks: /dev/disk/by-id/ata-TOSHIBA_THNSNH256GMCT_Z3JS1156TKBY-part1 /dev/disk/by-id/wwn-0x500080db1105e051-part1 /dev/disk/by-partuuid/5d8cce74-ecb9-4d4a-ba86-e535d4b28e60 /dev/disk/by-path/pci-0000:00:1f.2-ata-2-part1 /dev/disk/by-uuid/8F4A-78F7 org.freedesktop.UDisks2.Filesystem: MountPoints: org.freedesktop.UDisks2.Partition: Flags: 0 IsContained: false IsContainer: false Name: Number: 1 Offset: 1048576 Size: 65011712 Table: '/org/freedesktop/UDisks2/block_devices/sda' Type: c12a7328-f81f-11d2-ba4b-00a0c93ec93b UUID: 5d8cce74-ecb9-4d4a-ba86-e535d4b28e60 /org/freedesktop/UDisks2/block_devices/sda2: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/sda2 DeviceNumber: 2050 Drive: '/org/freedesktop/UDisks2/drives/TOSHIBA_THNSNH256GMCT_Z3JS1156TKBY' HintAuto: false HintIconName: HintIgnore: true HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-TOSHIBA_THNSNH256GMCT_Z3JS1156TKBY-part2 IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sda2 ReadOnly: false Size: 1048576 Symlinks: /dev/disk/by-id/ata-TOSHIBA_THNSNH256GMCT_Z3JS1156TKBY-part2 /dev/disk/by-id/wwn-0x500080db1105e051-part2 /dev/disk/by-partuuid/572ee31d-50ac-4974-9a86-d53f8c1c78d6 /dev/disk/by-path/pci-0000:00:1f.2-ata-2-part2 org.freedesktop.UDisks2.Partition: Flags: 0 IsContained: false IsContainer: false Name: Number: 2 Offset: 66060288 Size: 1048576 Table: '/org/freedesktop/UDisks2/block_devices/sda' Type: 21686148-6449-6e6f-744e-656564454649 UUID: 572ee31d-50ac-4974-9a86-d53f8c1c78d6 /org/freedesktop/UDisks2/block_devices/sda3: org.freedesktop.UDisks2.Block: Configuration: [('fstab', {'fsname': , 'dir': , 'type': , 'opts': , 'freq': <0>, 'passno': <0>})] CryptoBackingDevice: '/' Device: /dev/sda3 DeviceNumber: 2051 Drive: '/org/freedesktop/UDisks2/drives/TOSHIBA_THNSNH256GMCT_Z3JS1156TKBY' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-TOSHIBA_THNSNH256GMCT_Z3JS1156TKBY-part3 IdLabel: ostree IdType: ext4 IdUUID: 5b6b5d07-730f-44d1-b098-6a353da01317 IdUsage: filesystem IdVersion: 1.0 MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sda3 ReadOnly: false Size: 251699134464 Symlinks: /dev/disk/by-id/ata-TOSHIBA_THNSNH256GMCT_Z3JS1156TKBY-part3 /dev/disk/by-id/wwn-0x500080db1105e051-part3 /dev/disk/by-label/ostree /dev/disk/by-partuuid/f3118f26-7b5f-454e-a10f-b3b6970012a9 /dev/disk/by-path/pci-0000:00:1f.2-ata-2-part3 /dev/disk/by-uuid/5b6b5d07-730f-44d1-b098-6a353da01317 org.freedesktop.UDisks2.Filesystem: MountPoints: / /boot /sysroot /usr /var org.freedesktop.UDisks2.Partition: Flags: 0 IsContained: false IsContainer: false Name: Number: 3 Offset: 67108864 Size: 251699134464 Table: '/org/freedesktop/UDisks2/block_devices/sda' Type: 4f68bce3-e8cd-4db1-96e7-fbcaf984b709 UUID: f3118f26-7b5f-454e-a10f-b3b6970012a9 /org/freedesktop/UDisks2/block_devices/sda4: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/sda4 DeviceNumber: 2052 Drive: '/org/freedesktop/UDisks2/drives/TOSHIBA_THNSNH256GMCT_Z3JS1156TKBY' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-TOSHIBA_THNSNH256GMCT_Z3JS1156TKBY-part4 IdLabel: eos-swap IdType: swap IdUUID: 09dd7375-61fa-45ca-802c-c5e3dcaea33a IdUsage: other IdVersion: 1 MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sda4 ReadOnly: false Size: 4294254080 Symlinks: /dev/disk/by-id/ata-TOSHIBA_THNSNH256GMCT_Z3JS1156TKBY-part4 /dev/disk/by-id/wwn-0x500080db1105e051-part4 /dev/disk/by-label/eos-swap /dev/disk/by-partuuid/8ec7d619-501b-49aa-bf7d-d25f3a44c94c /dev/disk/by-path/pci-0000:00:1f.2-ata-2-part4 /dev/disk/by-uuid/09dd7375-61fa-45ca-802c-c5e3dcaea33a org.freedesktop.UDisks2.Partition: Flags: 0 IsContained: false IsContainer: false Name: Number: 4 Offset: 251766243328 Size: 4294254080 Table: '/org/freedesktop/UDisks2/block_devices/sda' Type: 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f UUID: 8ec7d619-501b-49aa-bf7d-d25f3a44c94c org.freedesktop.UDisks2.Swapspace: Active: true /org/freedesktop/UDisks2/drives/TOSHIBA_THNSNH256GMCT_Z3JS1156TKBY: org.freedesktop.UDisks2.Drive: CanPowerOff: false Configuration: {} ConnectionBus: Ejectable: false Id: TOSHIBA-THNSNH256GMCT-Z3JS1156TKBY Media: MediaAvailable: true MediaChangeDetected: true MediaCompatibility: MediaRemovable: false Model: TOSHIBA THNSNH256GMCT Optical: false OpticalBlank: false OpticalNumAudioTracks: 0 OpticalNumDataTracks: 0 OpticalNumSessions: 0 OpticalNumTracks: 0 Removable: false Revision: HTCAN102 RotationRate: 0 Seat: seat0 Serial: Z3JS1156TKBY SiblingId: Size: 256060514304 SortKey: 00coldplug/00fixed/sd____a TimeDetected: 1510869247782227 TimeMediaDetected: 1510869247782227 Vendor: WWN: 0x500080db1105e051 org.freedesktop.UDisks2.Drive.Ata: AamEnabled: false AamSupported: false AamVendorRecommendedValue: 0 ApmEnabled: true ApmSupported: true PmEnabled: true PmSupported: true ReadLookaheadEnabled: true ReadLookaheadSupported: true SecurityEnhancedEraseUnitMinutes: 2 SecurityEraseUnitMinutes: 2 SecurityFrozen: true SmartEnabled: true SmartFailing: false SmartNumAttributesFailedInThePast: 0 SmartNumAttributesFailing: 0 SmartNumBadSectors: 0 SmartPowerOnSeconds: 316800 SmartSelftestPercentRemaining: 0 SmartSelftestStatus: success SmartSupported: true SmartTemperature: 315.15000000000003 SmartUpdated: 1510899247 WriteCacheEnabled: true WriteCacheSupported: true ========== = Mounts = ========== sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) devtmpfs on /dev type devtmpfs (rw,nosuid,size=4014448k,nr_inodes=1003612,mode=755) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) configfs on /sys/kernel/config type configfs (rw,relatime) /dev/sda3 on /sysroot type ext4 (rw,relatime,errors=remount-ro,data=ordered) /dev/sda3 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered) /dev/sda3 on /boot type ext4 (rw,relatime,errors=remount-ro,data=ordered) /dev/sda3 on /usr type ext4 (ro,relatime,errors=remount-ro,data=ordered) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=26,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=14190) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) mqueue on /dev/mqueue type mqueue (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) /dev/sda3 on /var type ext4 (rw,relatime,errors=remount-ro,data=ordered) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) tmpfs on /tmp type tmpfs (rw,nosuid,nodev) tmpfs on /run/user/110 type tmpfs (rw,nosuid,nodev,relatime,size=806020k,mode=700,uid=110,gid=65534) tmpfs on /run/user/1001 type tmpfs (rw,nosuid,nodev,relatime,size=806020k,mode=700,uid=1001,gid=1001) /dev/fuse on /run/user/1001/doc type fuse (rw,nosuid,nodev,relatime,user_id=1001,group_id=1001) Filesystem Size Used Avail Use% Mounted on devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 90M 3.8G 3% /dev/shm tmpfs 3.9G 17M 3.9G 1% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/sda3 231G 23G 209G 10% / tmpfs 3.9G 80K 3.9G 1% /tmp tmpfs 788M 12K 788M 1% /run/user/110 tmpfs 788M 80K 788M 1% /run/user/1001 ====================== = Network interfaces = ====================== enp0s25 Link encap:Ethernet HWaddr 20:1a:06:ba:10:b0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:20 Memory:c0700000-c0720000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:5740 errors:0 dropped:0 overruns:0 frame:0 TX packets:5740 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1169007 (1.1 MiB) TX bytes:1169007 (1.1 MiB) wlp1s0 Link encap:Ethernet HWaddr ac:7b:a1:5c:b2:2d inet addr:192.168.1.94 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::b993:1da6:a5a8:a63a/64 Scope:Link inet6 addr: 2600:1700:8810:3020:c6c4:4730:e679:44b5/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:420641 errors:0 dropped:0 overruns:0 frame:0 TX packets:119636 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:584993031 (557.8 MiB) TX bytes:15533354 (14.8 MiB) ================== = rfkill devices = ================== rfkill0 name: hci0 type: bluetooth hard: 0 soft: 0 persistent: 0 state: 1 driver: btusb rfkill1 name: phy0 type: wlan hard: 0 soft: 0 persistent: 0 state: 1 driver: iwlwifi rfkill2 name: acer-wireless type: wlan hard: 0 soft: 0 persistent: 0 state: 1 rfkill3 name: acer-bluetooth type: bluetooth hard: 0 soft: 0 persistent: 0 state: 1 rfkill4 name: nfc0 type: nfc hard: 0 soft: 0 persistent: 0 state: 1 ============ = Graphics = ============ Renderer: Mesa DRI Intel(R) Haswell Mobile =========== = Display = =========== Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 eDP1 connected primary 1920x1080+0+0 (0x7c) normal (normal left inverted right x axis y axis) 310mm x 170mm Identifier: 0x75 Timestamp: 113979 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 2 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: _MUTTER_PRESENTATION_OUTPUT: 0 EDID: 00ffffffffffff0006af3d1100000000 00160104951f11780287e5a456509e26 0d505400000001010101010101010101 010101010101143780b8703824401010 3e0035ad100000180000000f00000000 00000000000000000020000000fe0041 554f0a202020202020202020000000fe 004231343048414e30312e31200a00a5 BACKLIGHT: 937 range: (0, 937) Backlight: 937 range: (0, 937) underscan vborder: 0 range: (0, 128) underscan hborder: 0 range: (0, 128) underscan: off supported: off, crop scaling mode: Full aspect supported: Full, Center, Full aspect Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on link-status: Good supported: Good, Bad 1920x1080 (0x7c) 141.000MHz -HSync -VSync *current +preferred h: width 1920 start 1936 end 1952 total 2104 skew 0 clock 67.02KHz v: height 1080 start 1083 end 1097 total 1116 clock 60.05Hz 1920x1080 (0x11b) 138.500MHz +HSync -VSync h: width 1920 start 1968 end 2000 total 2080 skew 0 clock 66.59KHz v: height 1080 start 1083 end 1088 total 1111 clock 59.93Hz 1680x1050 (0x11c) 119.000MHz +HSync -VSync h: width 1680 start 1728 end 1760 total 1840 skew 0 clock 64.67KHz v: height 1050 start 1053 end 1059 total 1080 clock 59.88Hz 1600x1024 (0x11d) 103.125MHz +HSync +VSync h: width 1600 start 1600 end 1656 total 1664 skew 0 clock 61.97KHz v: height 1024 start 1024 end 1029 total 1030 clock 60.17Hz 1400x1050 (0x11e) 122.000MHz +HSync +VSync h: width 1400 start 1488 end 1640 total 1880 skew 0 clock 64.89KHz v: height 1050 start 1052 end 1064 total 1082 clock 59.98Hz 1600x900 (0x11f) 118.997MHz -HSync +VSync h: width 1600 start 1696 end 1864 total 2128 skew 0 clock 55.92KHz v: height 900 start 901 end 904 total 932 clock 60.00Hz 1280x1024 (0x120) 108.000MHz +HSync +VSync h: width 1280 start 1328 end 1440 total 1688 skew 0 clock 63.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 60.02Hz 1440x900 (0x121) 106.500MHz -HSync +VSync h: width 1440 start 1520 end 1672 total 1904 skew 0 clock 55.93KHz v: height 900 start 903 end 909 total 934 clock 59.89Hz 1280x960 (0x122) 108.000MHz +HSync +VSync h: width 1280 start 1376 end 1488 total 1800 skew 0 clock 60.00KHz v: height 960 start 961 end 964 total 1000 clock 60.00Hz 1368x768 (0x123) 85.860MHz -HSync +VSync h: width 1368 start 1440 end 1584 total 1800 skew 0 clock 47.70KHz v: height 768 start 769 end 772 total 795 clock 60.00Hz 1360x768 (0x124) 84.750MHz -HSync +VSync h: width 1360 start 1432 end 1568 total 1776 skew 0 clock 47.72KHz v: height 768 start 771 end 781 total 798 clock 59.80Hz 1360x768 (0x125) 72.000MHz +HSync -VSync h: width 1360 start 1408 end 1440 total 1520 skew 0 clock 47.37KHz v: height 768 start 771 end 781 total 790 clock 59.96Hz 1152x864 (0x126) 81.620MHz -HSync +VSync h: width 1152 start 1216 end 1336 total 1520 skew 0 clock 53.70KHz v: height 864 start 865 end 868 total 895 clock 60.00Hz 1280x720 (0x127) 74.480MHz -HSync +VSync h: width 1280 start 1336 end 1472 total 1664 skew 0 clock 44.76KHz v: height 720 start 721 end 724 total 746 clock 60.00Hz 1024x768 (0x128) 65.000MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.36KHz v: height 768 start 771 end 777 total 806 clock 60.00Hz 1024x576 (0x129) 46.995MHz -HSync +VSync h: width 1024 start 1064 end 1168 total 1312 skew 0 clock 35.82KHz v: height 576 start 577 end 580 total 597 clock 60.00Hz 960x540 (0x12a) 40.784MHz -HSync +VSync h: width 960 start 992 end 1088 total 1216 skew 0 clock 33.54KHz v: height 540 start 541 end 544 total 559 clock 60.00Hz 800x600 (0x12b) 40.000MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew 0 clock 37.88KHz v: height 600 start 601 end 605 total 628 clock 60.32Hz 800x600 (0x12c) 36.000MHz +HSync +VSync h: width 800 start 824 end 896 total 1024 skew 0 clock 35.16KHz v: height 600 start 601 end 603 total 625 clock 56.25Hz 864x486 (0x12d) 32.901MHz -HSync +VSync h: width 864 start 888 end 976 total 1088 skew 0 clock 30.24KHz v: height 486 start 487 end 490 total 504 clock 60.00Hz 640x480 (0x12e) 25.175MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew 0 clock 31.47KHz v: height 480 start 490 end 492 total 525 clock 59.94Hz 720x405 (0x12f) 22.176MHz -HSync +VSync h: width 720 start 728 end 800 total 880 skew 0 clock 25.20KHz v: height 405 start 406 end 409 total 420 clock 60.00Hz 640x360 (0x130) 17.187MHz -HSync +VSync h: width 640 start 640 end 704 total 768 skew 0 clock 22.38KHz v: height 360 start 361 end 364 total 373 clock 60.00Hz DP1 disconnected (normal left inverted right x axis y axis) Identifier: 0x76 Timestamp: 113979 Subpixel: unknown Clones: HDMI1 CRTCs: 0 1 2 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: underscan vborder: 0 range: (0, 128) underscan hborder: 0 range: (0, 128) underscan: off supported: off, crop Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on link-status: Good supported: Good, Bad DP2 disconnected (normal left inverted right x axis y axis) Identifier: 0x77 Timestamp: 113979 Subpixel: unknown Clones: HDMI2 CRTCs: 0 1 2 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: underscan vborder: 0 range: (0, 128) underscan hborder: 0 range: (0, 128) underscan: off supported: off, crop Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on link-status: Good supported: Good, Bad HDMI1 disconnected (normal left inverted right x axis y axis) Identifier: 0x78 Timestamp: 113979 Subpixel: unknown Clones: DP1 CRTCs: 0 1 2 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: underscan vborder: 0 range: (0, 128) underscan hborder: 0 range: (0, 128) underscan: off supported: off, crop aspect ratio: Automatic supported: Automatic, 4:3, 16:9 Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on link-status: Good supported: Good, Bad HDMI2 disconnected (normal left inverted right x axis y axis) Identifier: 0x79 Timestamp: 113979 Subpixel: unknown Clones: DP2 CRTCs: 0 1 2 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: underscan vborder: 0 range: (0, 128) underscan hborder: 0 range: (0, 128) underscan: off supported: off, crop aspect ratio: Automatic supported: Automatic, 4:3, 16:9 Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on link-status: Good supported: Good, Bad VIRTUAL1 disconnected (normal left inverted right x axis y axis) Identifier: 0x7a Timestamp: 113979 Subpixel: no subpixels Clones: CRTCs: 3 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: ============== = Pulseaudio = ============== Card #0 Name: alsa_card.pci-0000_00_03.0 Driver: module-alsa-card.c Owner Module: 6 Properties: alsa.card = "0" alsa.card_name = "HDA Intel HDMI" alsa.long_card_name = "HDA Intel HDMI at 0xc0730000 irq 51" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:03.0" sysfs.path = "/devices/pci0000:00/0000:00:03.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "0a0c" device.product.name = "Haswell-ULT HD Audio Controller" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (sinks: 1, sources: 0, priority: 5400, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (sinks: 1, sources: 0, priority: 300, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (sinks: 1, sources: 0, priority: 300, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (sinks: 1, sources: 0, priority: 5200, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (sinks: 1, sources: 0, priority: 100, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (sinks: 1, sources: 0, priority: 100, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (sinks: 1, sources: 0, priority: 5200, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (sinks: 1, sources: 0, priority: 100, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (sinks: 1, sources: 0, priority: 100, available: no) output:hdmi-stereo-extra3: Digital Stereo (HDMI 4) Output (sinks: 1, sources: 0, priority: 5200, available: no) output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4) Output (sinks: 1, sources: 0, priority: 100, available: no) output:hdmi-surround71-extra3: Digital Surround 7.1 (HDMI 4) Output (sinks: 1, sources: 0, priority: 100, available: no) output:hdmi-stereo-extra4: Digital Stereo (HDMI 5) Output (sinks: 1, sources: 0, priority: 5200, available: no) output:hdmi-surround-extra4: Digital Surround 5.1 (HDMI 5) Output (sinks: 1, sources: 0, priority: 100, available: no) output:hdmi-surround71-extra4: Digital Surround 7.1 (HDMI 5) Output (sinks: 1, sources: 0, priority: 100, available: no) off: Off (sinks: 0, sources: 0, priority: 0, available: yes) Active Profile: off Ports: hdmi-output-0: HDMI / DisplayPort (priority: 8900, latency offset: 0 usec, not available) Properties: device.icon_name = "video-display" Part of profile(s): output:hdmi-stereo, output:hdmi-surround, output:hdmi-surround71 hdmi-output-1: HDMI / DisplayPort 2 (priority: 8800, latency offset: 0 usec, not available) Properties: device.icon_name = "video-display" Part of profile(s): output:hdmi-stereo-extra1, output:hdmi-surround-extra1, output:hdmi-surround71-extra1 hdmi-output-2: HDMI / DisplayPort 3 (priority: 8700, latency offset: 0 usec, not available) Properties: device.icon_name = "video-display" Part of profile(s): output:hdmi-stereo-extra2, output:hdmi-surround-extra2, output:hdmi-surround71-extra2 hdmi-output-3: HDMI / DisplayPort 4 (priority: 8600, latency offset: 0 usec, not available) Properties: device.icon_name = "video-display" Part of profile(s): output:hdmi-stereo-extra3, output:hdmi-surround-extra3, output:hdmi-surround71-extra3 hdmi-output-4: HDMI / DisplayPort 5 (priority: 8500, latency offset: 0 usec, not available) Properties: device.icon_name = "video-display" Part of profile(s): output:hdmi-stereo-extra4, output:hdmi-surround-extra4, output:hdmi-surround71-extra4 Card #1 Name: alsa_card.pci-0000_00_1b.0 Driver: module-alsa-card.c Owner Module: 7 Properties: alsa.card = "1" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xc0734000 irq 50" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:1b.0" sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "9c20" device.product.name = "8 Series HD Audio Controller" device.form_factor = "internal" device.string = "1" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Profiles: input:analog-stereo: Analog Stereo Input (sinks: 0, sources: 1, priority: 60, available: yes) output:analog-stereo: Analog Stereo Output (sinks: 1, sources: 0, priority: 6000, available: yes) output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (sinks: 1, sources: 1, priority: 6060, available: yes) off: Off (sinks: 0, sources: 0, priority: 0, available: yes) Active Profile: output:analog-stereo+input:analog-stereo Ports: analog-input-internal-mic: Internal Microphone (priority: 8900, latency offset: 0 usec) Properties: device.icon_name = "audio-input-microphone" Part of profile(s): input:analog-stereo, output:analog-stereo+input:analog-stereo analog-input-mic: Microphone (priority: 8700, latency offset: 0 usec, not available) Properties: device.icon_name = "audio-input-microphone" Part of profile(s): input:analog-stereo, output:analog-stereo+input:analog-stereo analog-input-linein: Line In (priority: 8100, latency offset: 0 usec, not available) Part of profile(s): input:analog-stereo, output:analog-stereo+input:analog-stereo analog-output-lineout: Line Out (priority: 8000, latency offset: 0 usec) Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo analog-output-speaker: Speakers (priority: 7900, latency offset: 0 usec) Properties: device.icon_name = "audio-speakers" Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo analog-output-headphones: Headphones (priority: 9900, latency offset: 0 usec, not available) Properties: device.icon_name = "audio-headphones" Part of profile(s): output:analog-stereo, output:analog-stereo+input:analog-stereo Source #0 State: SUSPENDED Name: alsa_output.pci-0000_00_1b.0.analog-stereo.monitor Description: Monitor of Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: alsa_output.pci-0000_00_1b.0.analog-stereo Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Built-in Audio Analog Stereo" device.class = "monitor" alsa.card = "1" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xc0734000 irq 50" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:1b.0" sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "9c20" device.product.name = "8 Series HD Audio Controller" device.form_factor = "internal" device.string = "1" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Formats: pcm Source #1 State: SUSPENDED Name: alsa_input.pci-0000_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 8251 / 13% / -54.00 dB, front-right: 8251 / 13% / -54.00 dB balance 0.00 Base Volume: 5206 / 8% / -66.00 dB Monitor of Sink: n/a Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC282 Analog" alsa.id = "ALC282 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "1" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xc0734000 irq 50" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:1b.0" sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "9c20" device.product.name = "8 Series HD Audio Controller" device.form_factor = "internal" device.string = "front:1" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC282" alsa.components = "HDA:10ec0282,1025081e,00100003" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-input-internal-mic: Internal Microphone (priority: 8900) analog-input-mic: Microphone (priority: 8700, not available) analog-input-linein: Line In (priority: 8100, not available) Active Port: analog-input-internal-mic Formats: pcm Sink #0 State: SUSPENDED Name: alsa_output.pci-0000_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: no Volume: front-left: 25109 / 38% / -25.00 dB, front-right: 25109 / 38% / -25.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: alsa_output.pci-0000_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC282 Analog" alsa.id = "ALC282 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "1" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xc0734000 irq 50" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:1b.0" sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "9c20" device.product.name = "8 Series HD Audio Controller" device.form_factor = "internal" device.string = "front:1" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC282" alsa.components = "HDA:10ec0282,1025081e,00100003" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-lineout: Line Out (priority: 8000) analog-output-speaker: Speakers (priority: 7900) analog-output-headphones: Headphones (priority: 9900, not available) Active Port: analog-output-lineout Formats: pcm ================= = Input devices = ================= I: Bus=0019 Vendor=0000 Product=0005 Version=0000 N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor=0000 Product=0001 Version=0000 N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10000000000000 0 I: Bus=0019 Vendor=0000 Product=0003 Version=0000 N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0E:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor=0000 Product=0001 Version=0000 N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10000000000000 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=10000 c020000000000 0 0 700f02000003 3802078f870f401 febfffdfffefffff fffffffffffffffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor=0000 Product=0006 Version=0000 N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:38/LNXVIDEO:00/input/input6 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b00000000 0 0 0 I: Bus=0019 Vendor=0000 Product=0006 Version=0000 N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input7 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=3e000b00000000 0 0 0 I: Bus=0003 Vendor=1bcf Product=2c57 Version=0006 N: Name="HD WebCam: HD WebCam" P: Phys=usb-0000:00:14.0-6/button S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb2/2-6/2-6:1.0/input/input9 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=100000 0 0 0 I: Bus=0019 Vendor=0000 Product=0000 Version=0000 N: Name="Acer WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input10 U: Uniq= H: Handlers=rfkill kbd event8 B: PROP=0 B: EV=13 B: KEY=1c0000 0 0 0 0 1600800000c00 300000 0 0 B: MSC=10 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card1/input11 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=10 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card1/input12 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=10 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel PCH Line" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card1/input13 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=2000 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card1/input14 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card1/input15 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel HDMI HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input16 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel HDMI HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input17 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel HDMI HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input18 U: Uniq= H: Handlers=event16 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel HDMI HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input19 U: Uniq= H: Handlers=event17 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel HDMI HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input20 U: Uniq= H: Handlers=event18 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input8 U: Uniq= H: Handlers=mouse0 event19 B: PROP=1 B: EV=b B: KEY=e520 30000 0 0 0 0 B: ABS=660800011000003 =============== = PCI devices = =============== 00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 09) Subsystem: Acer Incorporated [ALI] Device [1025:081e] Flags: bus master, fast devsel, latency 0 Capabilities: Kernel driver in use: hsw_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:081e] Flags: bus master, fast devsel, latency 0, IRQ 45 Memory at c0000000 (64-bit, non-prefetchable) [size=4M] Memory at b0000000 (64-bit, prefetchable) [size=256M] I/O ports at 4000 [size=64] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: Kernel driver in use: i915 00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio Controller [8086:0a0c] (rev 09) Subsystem: Acer Incorporated [ALI] Device [1025:081e] Flags: bus master, fast devsel, latency 0, IRQ 51 Memory at c0730000 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel 00:14.0 USB controller [0c03]: Intel Corporation 8 Series USB xHCI HC [8086:9c31] (rev 04) (prog-if 30 [XHCI]) Subsystem: Acer Incorporated [ALI] Device [1025:081e] Flags: bus master, medium devsel, latency 0, IRQ 42 Memory at c0720000 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: xhci_hcd 00:16.0 Communication controller [0780]: Intel Corporation 8 Series HECI #0 [8086:9c3a] (rev 04) Subsystem: Acer Incorporated [ALI] Device [1025:081e] Flags: bus master, fast devsel, latency 0, IRQ 47 Memory at c0738000 (64-bit, non-prefetchable) [size=32] Capabilities: Kernel driver in use: mei_me 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I218-LM [8086:155a] (rev 04) Subsystem: Acer Incorporated [ALI] Device [1025:081e] Flags: bus master, fast devsel, latency 0, IRQ 48 Memory at c0700000 (32-bit, non-prefetchable) [size=128K] Memory at c073d000 (32-bit, non-prefetchable) [size=4K] I/O ports at 4080 [size=32] Capabilities: Kernel driver in use: e1000e 00:1b.0 Audio device [0403]: Intel Corporation 8 Series HD Audio Controller [8086:9c20] (rev 04) Subsystem: Acer Incorporated [ALI] Device [1025:081e] Flags: bus master, fast devsel, latency 0, IRQ 50 Memory at c0734000 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 4 [8086:9c16] (rev e4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: c0600000-c06fffff Capabilities: Kernel driver in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 5 [8086:9c18] (rev e4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 00003000-00003fff Memory behind bridge: c0500000-c05fffff Prefetchable memory behind bridge: 00000000a0000000-00000000afffffff Capabilities: Kernel driver in use: pcieport 00:1c.5 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 6 [8086:9c1a] (rev e4) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 Memory behind bridge: c0400000-c04fffff Capabilities: 00:1d.0 USB controller [0c03]: Intel Corporation 8 Series USB EHCI #1 [8086:9c26] (rev 04) (prog-if 20 [EHCI]) Subsystem: Acer Incorporated [ALI] Device [1025:081e] Flags: bus master, medium devsel, latency 0, IRQ 23 Memory at c073c000 (32-bit, non-prefetchable) [size=1K] Capabilities: Kernel driver in use: ehci-pci 00:1f.0 ISA bridge [0601]: Intel Corporation 8 Series LPC Controller [8086:9c43] (rev 04) Subsystem: Acer Incorporated [ALI] Device [1025:081e] Flags: bus master, medium devsel, latency 0 Capabilities: Kernel driver in use: lpc_ich 00:1f.2 SATA controller [0106]: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] [8086:9c03] (rev 04) (prog-if 01 [AHCI 1.0]) Subsystem: Acer Incorporated [ALI] Device [1025:081e] Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 44 I/O ports at 40a8 [size=8] I/O ports at 40b4 [size=4] I/O ports at 40a0 [size=8] I/O ports at 40b0 [size=4] I/O ports at 4060 [size=32] Memory at c073b000 (32-bit, non-prefetchable) [size=2K] Capabilities: Kernel driver in use: ahci 00:1f.3 SMBus [0c05]: Intel Corporation 8 Series SMBus Controller [8086:9c22] (rev 04) Subsystem: Acer Incorporated [ALI] Device [1025:081e] Flags: medium devsel, IRQ 11 Memory at c0739000 (64-bit, non-prefetchable) [size=256] I/O ports at 4040 [size=32] 01:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4060] Flags: bus master, fast devsel, latency 0, IRQ 49 Memory at c0600000 (64-bit, non-prefetchable) [size=8K] Capabilities: Kernel driver in use: iwlwifi 02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] [1002:6600] (rev ff) (prog-if ff) !!! Unknown header type 7f Kernel driver in use: radeon 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] (rev 01) Subsystem: Acer Incorporated [ALI] Device [1025:081e] Flags: bus master, fast devsel, latency 0, IRQ 43 Memory at c0400000 (32-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: rtsx_pci =============== = USB devices = =============== Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 002 Device 003: ID 8087:07dc Intel Corp. Bus 002 Device 002: ID 1bcf:2c57 Sunplus Innovation Technology Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub =============== = MMC devices = =============== mmc0 driver: rtsx_pci_sdmmc =============== = I2C devices = =============== i2c-0 name: i915 gmbus ssc driver: i915 i2c-1 name: i915 gmbus vga driver: i915 i2c-2 name: i915 gmbus panel driver: i915 i2c-3 name: i915 gmbus dpc driver: i915 i2c-4 name: i915 gmbus dpb driver: i915 i2c-5 name: i915 gmbus dpd driver: i915 i2c-6 name: Radeon i2c bit bus 0x90 driver: radeon i2c-7 name: Radeon i2c bit bus 0x91 driver: radeon i2c-8 name: Radeon i2c bit bus 0x92 driver: radeon i2c-9 name: Radeon i2c bit bus 0x93 driver: radeon i2c-10 name: Radeon i2c bit bus 0x94 driver: radeon i2c-11 name: Radeon i2c bit bus 0x95 driver: radeon i2c-12 name: Radeon i2c bit bus 0x96 driver: radeon i2c-13 name: Radeon i2c bit bus 0x97 driver: radeon i2c-14 name: DPDDC-A i2c-15 name: DPDDC-B i2c-16 name: DPDDC-C ================ = ALSA devices = ================ 0 [HDMI ]: HDA-Intel - HDA Intel HDMI HDA Intel HDMI at 0xc0730000 irq 51 1 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xc0734000 irq 50 ============= = Intel HDA = ============= card0 codec#0: Codec: Intel Haswell HDMI Address: 0 AFG Function Id: 0x1 (unsol 0) Vendor Id: 0x80862807 Subsystem Id: 0x80860101 Revision Id: 0x100000 No Modem Function Group found Default PCM: rates [0x0]: bits [0x0]: formats [0x0]: Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D3 CLKSTOP EPSS Power: setting=D0, actual=D0, Clock-stop-OK GPIO: io=0, o=0, i=0, unsolicited=0, wake=0 Node 0x02 [Audio Output] wcaps 0x6611: 8-Channels Digital Converter: stream=0, channel=0 Digital: Enabled KAE Digital category: 0x0 IEC Coding Type: 0x0 PCM: rates [0x7f0]: 32000 44100 48000 88200 96000 176400 192000 bits [0x1e]: 16 20 24 32 formats [0x5]: PCM AC3 Power states: D0 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x6611: 8-Channels Digital Converter: stream=0, channel=0 Digital: Enabled KAE Digital category: 0x0 IEC Coding Type: 0x0 PCM: rates [0x7f0]: 32000 44100 48000 88200 96000 176400 192000 bits [0x1e]: 16 20 24 32 formats [0x5]: PCM AC3 Power states: D0 D3 EPSS Power: setting=D0, actual=D0 Node 0x04 [Audio Output] wcaps 0x6611: 8-Channels Digital Converter: stream=0, channel=0 Digital: Enabled KAE Digital category: 0x0 IEC Coding Type: 0x0 PCM: rates [0x7f0]: 32000 44100 48000 88200 96000 176400 192000 bits [0x1e]: 16 20 24 32 formats [0x5]: PCM AC3 Power states: D0 D3 EPSS Power: setting=D0, actual=D0 Node 0x05 [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x0b000094: OUT Detect HBR HDMI DP Pin Default 0x18560010: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0x1, Sequence = 0x0 Pin-ctls: 0x00: Unsolicited: tag=00, enabled=0 Power states: D0 D3 EPSS Power: setting=D0, actual=D0 Devices: 0 Connection: 0 In-driver Connection: 3 0x02 0x03 0x04 Node 0x06 [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x0b000094: OUT Detect HBR HDMI DP Pin Default 0x18560010: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0x1, Sequence = 0x0 Pin-ctls: 0x00: Unsolicited: tag=00, enabled=0 Power states: D0 D3 EPSS Power: setting=D0, actual=D0 Devices: 0 Connection: 0 In-driver Connection: 3 0x02 0x03 0x04 Node 0x07 [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x0b000094: OUT Detect HBR HDMI DP Pin Default 0x18560010: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0x1, Sequence = 0x0 Pin-ctls: 0x00: Unsolicited: tag=00, enabled=0 Power states: D0 D3 EPSS Power: setting=D0, actual=D0 Devices: 0 Connection: 0 In-driver Connection: 3 0x02 0x03 0x04 Node 0x08 [Vendor Defined Widget] wcaps 0xf00000: Mono card1 codec#0: Codec: Realtek ALC282 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0282 Subsystem Id: 0x1025081e Revision Id: 0x100003 No Modem Function Group found Default PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=3, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=5, channel=0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone+LO Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC282 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0 Amp-Out vals: [0x36 0x36] Converter: stream=5, channel=0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x04 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x05 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x06 [Audio Output] wcaps 0x611: Stereo Digital Converter: stream=0, channel=0 Digital: Digital category: 0x0 IEC Coding Type: 0x0 PCM: rates [0x5e0]: 44100 48000 88200 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Node 0x07 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x08 [Audio Input] wcaps 0x10051b: Stereo Amp-In Device: name="ALC282 Analog", type="Audio", device=0 Amp-In caps: ofs=0x17, nsteps=0x3f, stepsize=0x02, mute=1 Amp-In vals: [0x27 0x27] Converter: stream=0, channel=0 SDI-Select: 0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Connection: 1 0x23 Node 0x09 [Audio Input] wcaps 0x10051b: Stereo Amp-In Amp-In caps: ofs=0x17, nsteps=0x3f, stepsize=0x02, mute=1 Amp-In vals: [0x97 0x97] Converter: stream=0, channel=0 SDI-Select: 0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Connection: 1 0x22 Node 0x0a [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x0b [Audio Mixer] wcaps 0x20010b: Stereo Amp-In Control: name="Mic Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=1, ofs=0 Control: name="Mic Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=In, idx=1, ofs=0 Control: name="Mic Playback Volume", index=1, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Control: name="Mic Playback Switch", index=1, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Control: name="Line Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=2, ofs=0 Control: name="Line Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=In, idx=2, ofs=0 Amp-In caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1 Amp-In vals: [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] Connection: 5 0x18 0x19 0x1a 0x1b 0x1d Node 0x0c [Audio Mixer] wcaps 0x20010b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] [0x80 0x80] Connection: 2 0x02 0x0b Node 0x0d [Audio Mixer] wcaps 0x20010b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] [0x80 0x80] Connection: 2 0x03 0x0b Node 0x0e [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x0f [Audio Mixer] wcaps 0x20010a: Mono Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] Connection: 1 0x0d Node 0x10 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x11 [Audio Input] wcaps 0x10051b: Stereo Amp-In Control: name="Capture Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Control: name="Capture Switch", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x17, nsteps=0x3f, stepsize=0x02, mute=1 Amp-In vals: [0x27 0x27] Converter: stream=1, channel=0 SDI-Select: 0 PCM: rates [0x560]: 44100 48000 96000 192000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 1 0x12 Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In Control: name="Internal Mic Boost Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x2f, mute=0 Amp-In vals: [0x00 0x00] Pincap 0x00000020: IN Pin Default 0x90a601b0: [Fixed] Mic at Int N/A Conn = Digital, Color = Unknown DefAssociation = 0xb, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x20: IN Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x13 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x14 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Control: name="Speaker Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x80 0x80] Pincap 0x00010014: OUT EAPD Detect EAPD 0x2: EAPD Pin Default 0x90170110: [Fixed] Speaker at Int N/A Conn = Analog, Color = Unknown DefAssociation = 0x1, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 1 0x0c Node 0x15 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x16 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x17 [Pin Complex] wcaps 0x40050c: Mono Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x80] Pincap 0x00000010: OUT Pin Default 0x40020008: [N/A] Line Out at Ext N/A Conn = 1/4, Color = Unknown DefAssociation = 0x0, Sequence = 0x8 Pin-ctls: 0x00: Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Connection: 1 0x0f Node 0x18 [Pin Complex] wcaps 0x40048b: Stereo Amp-In Control: name="Mic Boost Volume", index=1, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x2f, mute=0 Amp-In vals: [0x00 0x00] Pincap 0x00003724: IN Detect Vref caps: HIZ 50 GRD 80 100 Pin Default 0x03a19030: [Jack] Mic at Ext Left Conn = 1/8, Color = Pink DefAssociation = 0x3, Sequence = 0x0 Pin-ctls: 0x24: IN VREF_80 Unsolicited: tag=04, enabled=1 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Node 0x19 [Pin Complex] wcaps 0x40048b: Stereo Amp-In Control: name="Mic Boost Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x2f, mute=0 Amp-In vals: [0x00 0x00] Pincap 0x00003724: IN Detect Vref caps: HIZ 50 GRD 80 100 Pin Default 0x04a19031: [Jack] Mic at Ext Right Conn = 1/8, Color = Pink DefAssociation = 0x3, Sequence = 0x1 Pin-ctls: 0x24: IN VREF_80 Unsolicited: tag=03, enabled=1 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Node 0x1a [Pin Complex] wcaps 0x40048b: Stereo Amp-In Control: name="Line Boost Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x2f, mute=0 Amp-In vals: [0x00 0x00] Pincap 0x00003724: IN Detect Vref caps: HIZ 50 GRD 80 100 Pin Default 0x0481303f: [Jack] Line In at Ext Right Conn = 1/8, Color = Blue DefAssociation = 0x3, Sequence = 0xf Pin-ctls: 0x20: IN VREF_HIZ Unsolicited: tag=05, enabled=1 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Node 0x1b [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out Control: name="Line Out Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x2f, mute=0 Amp-In vals: [0x00 0x00] Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x0000373c: IN OUT HP Detect Vref caps: HIZ 50 GRD 80 100 Pin Default 0x04214020: [Jack] HP Out at Ext Right Conn = 1/8, Color = Green DefAssociation = 0x2, Sequence = 0x0 Pin-ctls: 0x40: OUT VREF_HIZ Unsolicited: tag=01, enabled=1 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Connection: 2 0x0c 0x0d* Node 0x1c [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x1d [Pin Complex] wcaps 0x400400: Mono Pincap 0x00000020: IN Pin Default 0x40e00001: [N/A] Reserved at Ext N/A Conn = Unknown, Color = Unknown DefAssociation = 0x0, Sequence = 0x1 Pin-ctls: 0x20: IN Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Node 0x1e [Pin Complex] wcaps 0x400781: Stereo Digital Pincap 0x00000014: OUT Detect Pin Default 0x411111f0: [N/A] Speaker at Ext Rear Conn = 1/8, Color = Black DefAssociation = 0xf, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Connection: 1 0x06 Node 0x1f [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x20 [Vendor Defined Widget] wcaps 0xf00040: Mono Processing caps: benign=0, ncoeff=117 Node 0x21 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Control: name="Headphone Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x80 0x80] Pincap 0x0000001c: OUT HP Detect Pin Default 0x0321401f: [Jack] HP Out at Ext Left Conn = 1/8, Color = Green DefAssociation = 0x1, Sequence = 0xf Pin-ctls: 0xc0: OUT HP Unsolicited: tag=02, enabled=1 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Connection: 2 0x0c 0x0d* Node 0x22 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] Connection: 6 0x18 0x19 0x1a 0x1b 0x1d 0x0b Node 0x23 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] Connection: 6 0x18 0x19 0x1a 0x1b 0x1d 0x0b hwC1D0: vendor: 0x10ec0282 subsystem: 0x1025081e init_pin_configs: 0x12 0x90a601b0 0x14 0x90170110 0x17 0x40020008 0x18 0x03a19030 0x19 0x04a19031 0x1a 0x0481303f 0x1b 0x04214020 0x1d 0x40e00001 0x1e 0x411111f0 0x21 0x0321401f hwC0D0: vendor: 0x80862807 subsystem: 0x80860101 init_pin_configs: 0x05 0x18560010 0x06 0x18560010 0x07 0x18560010 ============ = Printers = ============ CUPS status: ------------ scheduler is running no system default destination =============== = Temperature = =============== +44°C ==================== = Chromium plugins = ==================== Flash Version: 27.0.0.187 Widevine Version: 62.0.3202.94-1 ========== = Codecs = ========== /var/lib/codecs /var/lib/codecs/.gnupg /var/lib/codecs/.gnupg/keys.d Plugin Details: Name libav Description All libav codecs and formats (system install) Filename /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so Version 1.10.4 License LGPL Source module gst-libav Binary package libav Origin URL http://www.libav.org avdeinterlace: libav Deinterlace element avdec_vp9: libav Google VP9 decoder avdec_vp8: libav On2 VP8 decoder avdec_vp3: libav On2 VP3 decoder avdec_mp3: libav MP3 (MPEG audio layer 3) decoder 5 features: +-- 5 elements Blacklisted files: Total count: 0 blacklisted files =================== = Flatpak remotes = =================== eos-apps Endless Applications https://ostree.endlessm.com/ostree/eos-apps 1 system eos-runtimes Endless OS and Runtimes https://ostree.endlessm.com/ostree/eos-amd64 1 system eos-sdk Endless Runtime and SDK https://ostree.endlessm.com/ostree/eos-sdk 1 system flathub Flathub https://flathub.org/repo/ 1 system gnome Gnome Stable Runtimes https://sdk.gnome.org/repo/ 1 system gnome-apps Gnome Stable Applications https://sdk.gnome.org/repo-apps/ 1 system ==================== = Flatpak runtimes = ==================== com.endlessm.Platform/x86_64/eos3.1 eos-runtimes 177cdeb11386 - 2.1 GB system com.endlessm.Platform/x86_64/eos3.2 eos-runtimes 15e0e3b90dcd - 2.1 GB system com.endlessm.apps.Platform/x86_64/1 eos-sdk 6ccb8ee214e5 - 876.6 MB system org.gnome.Platform/x86_64/3.26 gnome 62e099553492 - 790.8 MB system org.gnome.Weather.Locale/x86_64/stable gnome-apps 4aaa2e562493 - 512 bytes system,partial ======================== = Flatpak applications = ======================== com.endlessm.EknServices/x86_64/eos3 eos-sdk da7df31933c8 - 1.0 MB system,current com.endlessm.animals.en/x86_64/eos3 eos-apps a211dab79cc6 - 142.1 MB system,current com.endlessm.astronomy.en/x86_64/eos3 eos-apps b93fbdee0c83 - 95.6 MB system,current com.endlessm.biology.en/x86_64/eos3 eos-apps 5a1217fb989c - 118.7 MB system,current com.endlessm.celebrities.en/x86_64/eos3 eos-apps d78843e0d0c9 - 171.8 MB system,current com.endlessm.cooking.en/x86_64/eos3 eos-apps bac342667b01 - 154.1 MB system,current com.endlessm.dinosaurs.en/x86_64/eos3 eos-apps 4049df796355 - 92.4 MB system,current com.endlessm.disabilities.en/x86_64/eos3 eos-apps 7a7be716ebf1 - 64.5 MB system,current com.endlessm.encyclopedia.en/x86_64/eos3 eos-apps 918d9937982f - 5.0 GB system,current com.endlessm.farming.en/x86_64/eos3 eos-apps 11471a2e35de - 118.1 MB system,current com.endlessm.finance/x86_64/eos3 eos-apps 8586a7cbf0fc - 5.5 MB system,current com.endlessm.geography.en/x86_64/eos3 eos-apps 1f1e09e3e9e1 - 457.1 MB system,current com.endlessm.health.en/x86_64/eos3 eos-apps 16559c1fcdb4 - 72.4 MB system,current com.endlessm.healthy_teeth.en/x86_64/eos3 eos-apps 2a27645b5a48 - 82.5 MB system,current com.endlessm.history.en/x86_64/eos3 eos-apps 7d25f406fa54 - 299.3 MB system,current com.endlessm.howto.en/x86_64/eos3 eos-apps fd18e4149496 - 174.4 MB system,current com.endlessm.maternity.en/x86_64/eos3 eos-apps daac2a5f46de - 130.0 MB system,current com.endlessm.math.en/x86_64/eos3 eos-apps fa0335f8d3bf - 45.8 MB system,current com.endlessm.myths.en/x86_64/eos3 eos-apps bfcb9104fc9f - 70.6 MB system,current com.endlessm.photos/x86_64/eos3 eos-apps 5250d277b48f - 64.0 MB system,current com.endlessm.physics.en/x86_64/eos3 eos-apps 165f12f5a421 - 46.5 MB system,current com.endlessm.programming/x86_64/eos3 eos-apps 83cda6895d6e - 14.6 MB system,current com.endlessm.programming_guide.en/x86_64/eos3 eos-apps b89863c0f888 - 74.0 MB system,current com.endlessm.resume/x86_64/eos3 eos-apps 9e824bba7477 - 12.3 MB system,current com.endlessm.soccer.en/x86_64/eos3 eos-apps 85239ebb9fe3 - 98.6 MB system,current com.endlessm.socialsciences.en/x86_64/eos3 eos-apps 18025327285d - 67.5 MB system,current com.endlessm.textbooks.en/x86_64/eos3 eos-apps ef44849537dd - 405.1 MB system,current com.endlessm.translation/x86_64/eos3 eos-apps e29ef08d8e5e - 2.1 MB system,current com.endlessm.travel.en/x86_64/eos3 eos-apps f0c78763be69 - 848.5 MB system,current com.endlessm.water_and_sanitation.en/x86_64/eos3 eos-apps 65b907d88d31 - 46.6 MB system,current com.endlessm.world_literature.en/x86_64/eos3 eos-apps 28b6d43f8fb0 - 913.9 MB system,current com.github.Slingshot/x86_64/eos3 eos-apps fd2df401bd32 - 26.6 MB system,current com.google.Chrome/x86_64/eos3 eos-apps 3c53c34fbc70 - 602.6 kB system,current com.teeworlds.Teeworlds/x86_64/eos3 eos-apps 6e25c7729d4d - 7.6 MB system,current de.billardgl.Billardgl/x86_64/eos3 eos-apps 51a7bf57ff79 - 8.0 MB system,current io.github.Supertux/x86_64/eos3 eos-apps d3653836b491 - 96.5 MB system,current net.blockout.Blockout2/x86_64/eos3 eos-apps 0b0d208fd704 - 5.0 MB system,current net.gcompris.Gcompris/x86_64/eos3 eos-apps 0af79c448f69 - 249.2 MB system,current net.minetest.Minetest/x86_64/eos3 eos-apps 0b9b7cf329f7 - 21.8 MB system,current net.olofson.Kobodeluxe/x86_64/eos3 eos-apps 8c80f54d59b8 - 2.1 MB system,current net.sourceforge.Atanks/x86_64/eos3 eos-apps be25edb1a308 - 9.7 MB system,current net.sourceforge.Audacity/x86_64/eos3 eos-apps a5f9a53852f2 - 55.0 MB system,current net.sourceforge.Btanks/x86_64/eos3 eos-apps 713d10f74c8f - 36.8 MB system,current net.sourceforge.ChromiumBSU/x86_64/eos3 eos-apps 963f2c867fe9 - 2.6 MB system,current net.sourceforge.Extremetuxracer/x86_64/eos3 eos-apps 374f0aeea5b1 - 35.1 MB system,current net.sourceforge.Rili/x86_64/eos3 eos-apps ecce8675aaa5 - 140.8 MB system,current net.sourceforge.Supertuxkart/x86_64/eos3 eos-apps 933e169a4924 - 315.7 MB system,current net.sourceforge.Torcs/x86_64/eos3 eos-apps 009da6e406de - 458.1 MB system,current net.sourceforge.Tuxfootball/x86_64/eos3 eos-apps fc1c7d15a00f - 18.1 MB system,current net.sourceforge.Warmux/x86_64/eos3 eos-apps 47e3c612fa0f - 109.2 MB system,current net.wz2100.Warzone2100/x86_64/eos3 eos-apps 94ccb51320bb - 85.8 MB system,current org.armagetronad.Armagetronad/x86_64/eos3 eos-apps b1503e11fc1a - 3.9 MB system,current org.debian.Tuxpuck/x86_64/eos3 eos-apps 2378f3314b12 - 546.3 kB system,current org.debian.alioth.tux4kids.Tuxmath/x86_64/eos3 eos-apps 351462a7be06 - 11.3 MB system,current org.debian.alioth.tux4kids.Tuxtype/x86_64/eos3 eos-apps 3d50b0acd726 - 11.5 MB system,current org.freeciv.Freeciv/x86_64/eos3 eos-apps 5b3431fa4ef5 - 38.0 MB system,current org.frozenbubble.FrozenBubble/x86_64/eos3 eos-apps a0d4503a68da - 28.7 MB system,current org.gimp.Gimp/x86_64/eos3 eos-apps 37cc2eb2978f - 71.9 MB system,current org.gnome.Freecell/x86_64/eos3 eos-apps 63ec8da82228 - 28.2 MB system,current org.gnome.Genius/x86_64/eos3 eos-apps 4b6b1525b4ef - 13.0 MB system,current org.gnome.Gnote/x86_64/eos3 eos-apps 3c228ba5d49c - 11.0 MB system,current org.gnome.Iagno/x86_64/eos3 eos-apps 0cf327988d5c - 8.6 MB system,current org.gnome.Quadrapassel/x86_64/eos3 eos-apps abb0129307b1 - 6.0 MB system,current org.gnome.Solitaire/x86_64/eos3 eos-apps f7a9b9a91c09 - 28.2 MB system,current org.gnome.Tetravex/x86_64/eos3 eos-apps 343e449d5d2e - 6.2 MB system,current org.gnome.Weather/x86_64/stable gnome-apps d39bb71020fa - 10.7 MB system,current org.gnome.people.dscorgie.Labyrinth/x86_64/eos3 eos-apps 28d15912cdcd - 5.1 MB system,current org.inkscape.Inkscape/x86_64/eos3 eos-apps 4e380dfa8baa - 124.1 MB system,current org.kde.Kalzium/x86_64/eos3 eos-apps 6e09090a961b - 34.2 MB system,current org.kde.Kapman/x86_64/eos3 eos-apps 98ef8baad086 - 2.1 MB system,current org.kde.Katomic/x86_64/eos3 eos-apps e047ca637e14 - 944.6 kB system,current org.kde.Kblocks/x86_64/eos3 eos-apps 8d8d49c9f497 - 3.4 MB system,current org.kde.Kbounce/x86_64/eos3 eos-apps f58f28036d2d - 4.7 MB system,current org.kde.Kbruch/x86_64/eos3 eos-apps e75e916dec48 - 1.3 MB system,current org.kde.Kdiamond/x86_64/eos3 eos-apps 3a1b5710233f - 4.4 MB system,current org.kde.Kgeography/x86_64/eos3 eos-apps dfb52cea39f4 - 7.4 MB system,current org.kde.Kgoldrunner/x86_64/eos3 eos-apps 2f62cb64fcd8 - 5.4 MB system,current org.kde.Khangman/x86_64/eos3 eos-apps a65c7f3a2b55 - 3.0 MB system,current org.kde.Kigo/x86_64/eos3 eos-apps 4f8c1884768b - 10.1 MB system,current org.kde.Killbots/x86_64/eos3 eos-apps 7bf6d88964f9 - 1.3 MB system,current org.kde.Kjumpingcube/x86_64/eos3 eos-apps 0e91ba3f551e - 490.5 kB system,current org.kde.Klines/x86_64/eos3 eos-apps c7520136fb7b - 6.6 MB system,current org.kde.Knavalbattle/x86_64/eos3 eos-apps b69e09d40688 - 1.3 MB system,current org.kde.Knetwalk/x86_64/eos3 eos-apps b5aafad63150 - 1.0 MB system,current org.kde.Ksame/x86_64/eos3 eos-apps bebe7fdb71ae - 2.0 MB system,current org.kde.Ksquares/x86_64/eos3 eos-apps f339dd7a36e5 - 274.9 kB system,current org.kde.Ksudoku/x86_64/eos3 eos-apps f79fef8c2993 - 3.1 MB system,current org.kde.Ktuberling/x86_64/eos3 eos-apps ffbf8e9876d5 - 7.7 MB system,current org.kde.Kubrick/x86_64/eos3 eos-apps 116ceeb80810 - 419.8 kB system,current org.kde.Kwordquiz/x86_64/eos3 eos-apps b78d36ff3ca6 - 1.9 MB system,current org.kde.Palapeli/x86_64/eos3 eos-apps a2728d7113fe - 2.5 MB system,current org.maemo.Numptyphysics/x86_64/eos3 eos-apps 1ba89a0f7ac6 - 624.1 kB system,current org.marsshooter.Marsshooter/x86_64/eos3 eos-apps dcb07fd62548 - 71.3 MB system,current org.megaglest.MegaGlest/x86_64/eos3 eos-apps ff02fcc43969 - 502.7 MB system,current org.openarena.Openarena/x86_64/eos3 eos-apps 85d074f0e09c - 438.7 MB system,current org.openscad.Openscad/x86_64/eos3 eos-apps a60c2643099e - 6.6 MB system,current org.pitivi.Pitivi/x86_64/eos3 eos-apps f0b692b33ea6 - 25.1 MB system,current org.seul.Pingus/x86_64/eos3 eos-apps 08e8a3929bca - 24.6 MB system,current org.squeakland.Etoys/x86_64/eos3 eos-apps 29563aa1d4a1 - 43.3 MB system,current org.squeakland.Scratch/x86_64/eos3 eos-apps 91dbb1347170 - 48.5 MB system,current org.stellarium.Stellarium/x86_64/eos3 eos-apps 02d15baae1e0 - 81.3 MB system,current org.sugarlabs.Turtleblocks/x86_64/eos3 eos-apps 68ba5e69fba5 - 12.1 MB system,current org.tuxfamily.Xmoto/x86_64/eos3 eos-apps e8554e481991 - 71.9 MB system,current org.tuxpaint.Tuxpaint/x86_64/eos3 eos-apps c2d23d48782d - 6.7 MB system,current org.wesnoth.Wesnoth/x86_64/eos3 eos-apps 876264fc538a - 481.1 MB system,current ============= = Processes = ============= USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.2 0.0 202872 7252 ? Ss 21:53 0:03 /lib/systemd/systemd --switched-root --system --deserialize 24 root 2 0.0 0.0 0 0 ? S 21:53 0:00 [kthreadd] root 3 0.0 0.0 0 0 ? S 21:53 0:00 [kworker/0:0] root 4 0.0 0.0 0 0 ? S< 21:53 0:00 [kworker/0:0H] root 5 0.0 0.0 0 0 ? S 21:53 0:00 [kworker/u16:0] root 6 0.0 0.0 0 0 ? S< 21:53 0:00 [mm_percpu_wq] root 7 0.0 0.0 0 0 ? S 21:53 0:01 [ksoftirqd/0] root 8 0.1 0.0 0 0 ? S 21:53 0:02 [rcu_sched] root 9 0.0 0.0 0 0 ? S 21:53 0:00 [rcu_bh] root 10 0.0 0.0 0 0 ? S 21:53 0:00 [migration/0] root 11 0.0 0.0 0 0 ? S 21:53 0:00 [watchdog/0] root 12 0.0 0.0 0 0 ? S 21:53 0:00 [cpuhp/0] root 13 0.0 0.0 0 0 ? S 21:53 0:00 [cpuhp/1] root 14 0.0 0.0 0 0 ? S 21:53 0:00 [watchdog/1] root 15 0.0 0.0 0 0 ? S 21:53 0:00 [migration/1] root 16 0.0 0.0 0 0 ? S 21:53 0:00 [ksoftirqd/1] root 18 0.0 0.0 0 0 ? S< 21:53 0:00 [kworker/1:0H] root 19 0.0 0.0 0 0 ? S 21:53 0:00 [cpuhp/2] root 20 0.0 0.0 0 0 ? S 21:53 0:00 [watchdog/2] root 21 0.0 0.0 0 0 ? S 21:53 0:00 [migration/2] root 22 0.0 0.0 0 0 ? S 21:53 0:00 [ksoftirqd/2] root 24 0.0 0.0 0 0 ? S< 21:53 0:00 [kworker/2:0H] root 25 0.0 0.0 0 0 ? S 21:53 0:00 [cpuhp/3] root 26 0.0 0.0 0 0 ? S 21:53 0:00 [watchdog/3] root 27 0.0 0.0 0 0 ? S 21:53 0:00 [migration/3] root 28 0.0 0.0 0 0 ? S 21:53 0:00 [ksoftirqd/3] root 30 0.0 0.0 0 0 ? S< 21:53 0:00 [kworker/3:0H] root 31 0.0 0.0 0 0 ? S 21:53 0:00 [kdevtmpfs] root 32 0.0 0.0 0 0 ? S< 21:53 0:00 [netns] root 35 0.0 0.0 0 0 ? S 21:53 0:00 [khungtaskd] root 36 0.0 0.0 0 0 ? S 21:53 0:00 [oom_reaper] root 37 0.0 0.0 0 0 ? S< 21:53 0:00 [writeback] root 38 0.0 0.0 0 0 ? S 21:53 0:00 [kcompactd0] root 39 0.0 0.0 0 0 ? SN 21:53 0:00 [ksmd] root 40 0.0 0.0 0 0 ? SN 21:53 0:00 [khugepaged] root 41 0.0 0.0 0 0 ? S< 21:53 0:00 [crypto] root 42 0.0 0.0 0 0 ? S< 21:53 0:00 [kintegrityd] root 43 0.0 0.0 0 0 ? S< 21:53 0:00 [kblockd] root 44 0.0 0.0 0 0 ? S< 21:53 0:00 [ata_sff] root 45 0.0 0.0 0 0 ? S< 21:53 0:00 [md] root 46 0.0 0.0 0 0 ? S< 21:53 0:00 [edac-poller] root 48 0.0 0.0 0 0 ? S< 21:53 0:00 [devfreq_wq] root 49 0.0 0.0 0 0 ? S< 21:53 0:00 [watchdogd] root 50 0.0 0.0 0 0 ? S 21:53 0:01 [kworker/u16:1] root 54 0.0 0.0 0 0 ? S 21:53 0:00 [kauditd] root 55 0.0 0.0 0 0 ? S 21:53 0:00 [kswapd0] root 56 0.0 0.0 0 0 ? S 21:53 0:00 [ecryptfs-kthrea] root 97 0.0 0.0 0 0 ? S< 21:53 0:00 [kthrotld] root 98 0.0 0.0 0 0 ? S< 21:53 0:00 [acpi_thermal_pm] root 103 0.0 0.0 0 0 ? S< 21:53 0:00 [ipv6_addrconf] root 135 0.0 0.0 0 0 ? S< 21:53 0:00 [charger_manager] root 198 0.0 0.0 0 0 ? S 21:53 0:00 [scsi_eh_0] root 199 0.0 0.0 0 0 ? S< 21:53 0:00 [scsi_tmf_0] root 200 0.0 0.0 0 0 ? S 21:53 0:00 [scsi_eh_1] root 201 0.0 0.0 0 0 ? S< 21:53 0:00 [scsi_tmf_1] root 202 0.0 0.0 0 0 ? S 21:53 0:00 [scsi_eh_2] root 203 0.0 0.0 0 0 ? S< 21:53 0:00 [scsi_tmf_2] root 205 0.0 0.0 0 0 ? S< 21:53 0:00 [ttm_swap] root 206 0.0 0.0 0 0 ? S 21:53 0:00 [i915/signal:0] root 207 0.0 0.0 0 0 ? S 21:53 0:00 [i915/signal:1] root 208 0.0 0.0 0 0 ? S 21:53 0:00 [i915/signal:2] root 209 0.0 0.0 0 0 ? S 21:53 0:00 [i915/signal:4] root 211 0.0 0.0 0 0 ? S< 21:53 0:00 [kworker/1:1H] root 212 0.0 0.0 0 0 ? S< 21:53 0:00 [kworker/2:1H] root 213 0.0 0.0 0 0 ? S< 21:53 0:00 [kworker/0:1H] root 220 0.0 0.0 0 0 ? S< 21:53 0:00 [kworker/3:1H] root 293 0.1 0.0 0 0 ? S 21:54 0:01 [jbd2/sda3-8] root 294 0.0 0.0 0 0 ? S< 21:54 0:00 [ext4-rsv-conver] root 350 0.3 0.0 55660 5052 ? Ss 21:54 0:04 /lib/systemd/systemd-journald root 372 0.0 0.0 48740 4288 ? Ss 21:54 0:00 /lib/systemd/systemd-udevd root 408 0.0 0.0 0 0 ? S 21:54 0:00 [irq/17-smo8800] root 420 0.0 0.0 0 0 ? S 21:54 0:00 [irq/47-mei_me] root 423 0.0 0.0 0 0 ? S< 21:54 0:00 [kmemstick] root 424 0.0 0.0 0 0 ? S< 21:54 0:00 [cfg80211] root 432 0.0 0.0 0 0 ? S< 21:54 0:00 [kworker/u17:0] root 435 0.0 0.0 0 0 ? S< 21:54 0:00 [kworker/u17:1] root 440 0.7 0.0 0 0 ? S 21:54 0:10 [irq/49-iwlwifi] root 577 0.0 0.1 422652 9008 ? Ssl 21:54 0:00 /usr/sbin/ModemManager message+ 578 0.2 0.0 46484 5156 ? Ss 21:54 0:03 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation root 588 0.0 0.1 395400 9856 ? Ssl 21:54 0:00 /usr/lib/udisks2/udisksd --no-debug root 590 0.0 0.0 189848 5396 ? Ssl 21:54 0:00 /usr/sbin/eos-factory-test-helper metrics 591 0.0 0.1 456908 11808 ? Ssl 21:54 0:00 /usr/lib/eos-event-recorder-daemon/eos-metrics-event-recorder root 592 0.1 0.2 667080 17368 ? Ssl 21:54 0:02 /usr/sbin/NetworkManager --no-daemon root 594 0.0 0.1 418332 8292 ? Ssl 21:54 0:00 /usr/lib/accountsservice/accounts-daemon root 599 0.0 0.0 218372 7748 ? Ss 21:54 0:00 /usr/sbin/cupsd -l root 600 0.0 0.1 430016 8372 ? Ssl 21:54 0:00 /usr/lib/upower/upowerd geoclue 601 0.0 0.3 518096 24620 ? Ssl 21:54 0:00 /usr/lib/geoclue-2.0/geoclue -t 5 root 602 0.0 0.0 48556 4804 ? Ss 21:54 0:00 /lib/systemd/systemd-logind root 603 0.0 0.0 36072 4220 ? Ss 21:54 0:00 /usr/lib/bluetooth/bluetoothd polkitd 604 0.1 0.1 406164 15044 ? Ssl 21:54 0:02 /usr/lib/polkit-1/polkitd --no-debug root 608 0.0 0.1 272016 9448 ? Ssl 21:54 0:00 /usr/sbin/cups-browsed root 640 0.0 0.1 388104 11956 ? Ssl 21:54 0:00 /usr/lib/x86_64-linux-gnu/eos-metrics-instrumentation root 641 0.0 0.0 46252 7316 ? Ss 21:54 0:00 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant ntp 671 0.0 0.0 108344 4132 ? Ssl 21:54 0:00 /usr/sbin/ntpd -u ntp:ntp -g root 684 0.0 0.1 589236 9956 ? Ssl 21:54 0:00 /usr/sbin/gdm root 705 8.3 1.1 654356 96140 tty1 Ssl+ 21:54 1:52 /usr/lib/xorg/Xorg :0 -background none -noreset -verbose 3 -logfile /dev/null -auth /var/run/gdm3/auth-for-Debian-gdm-VOkkpI/database -seat seat0 vt1 gnome-i+ 729 0.0 0.0 65068 6592 ? Ss 21:54 0:00 /lib/systemd/systemd --user gnome-i+ 730 0.0 0.0 111820 2028 ? S 21:54 0:00 (sd-pam) gnome-i+ 740 0.0 0.0 45556 4336 ? Ss 21:54 0:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation gnome-i+ 742 0.0 0.0 403752 6576 ? Ssl 21:54 0:00 /usr/lib/gvfs/gvfsd gnome-i+ 752 0.0 0.0 368844 7768 ? Ssl 21:54 0:00 /usr/lib/at-spi2-core/at-spi-bus-launcher gnome-i+ 757 0.0 0.0 45016 3836 ? S 21:54 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 gnome-i+ 759 0.0 0.0 218028 5868 ? Sl 21:54 0:00 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session rtkit 775 0.0 0.0 187764 3012 ? SNsl 21:54 0:00 /usr/lib/rtkit/rtkit-daemon root 782 0.0 0.0 0 0 ? S< 21:54 0:00 [krfcommd] gnome-i+ 796 0.0 0.1 492660 10488 ? Sl 21:54 0:00 ibus-daemon --xim --panel disable gnome-i+ 800 0.0 0.1 487752 9792 ? Ssl 21:54 0:00 /usr/lib/flatpak/xdg-permission-store gnome-i+ 854 0.0 0.1 474492 12016 ? Ssl 21:54 0:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor gnome-i+ 889 0.0 0.0 401156 6324 ? Ssl 21:54 0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor root 897 0.0 0.1 450816 14244 ? Ssl 21:54 0:00 /usr/lib/colord/colord gnome-i+ 898 0.0 0.0 388864 4832 ? Ssl 21:54 0:00 /usr/lib/gvfs/gvfs-mtp-volume-monitor gnome-i+ 912 0.0 0.0 489716 7280 ? Ssl 21:54 0:00 /usr/lib/gvfs/gvfs-afc-volume-monitor gnome-i+ 920 0.0 0.0 388952 5892 ? Ssl 21:54 0:00 /usr/lib/gvfs/gvfs-goa-volume-monitor gnome-i+ 928 0.0 0.3 859796 29780 ? Sl 21:54 0:00 /usr/lib/gnome-online-accounts/goa-daemon gnome-i+ 948 0.0 0.1 504612 9532 ? Sl 21:54 0:00 /usr/lib/gnome-online-accounts/goa-identity-service gnome-i+ 975 0.0 0.1 408872 8136 ? Sl 21:54 0:00 /usr/lib/ibus/ibus-dconf gnome-i+ 977 0.0 0.2 468056 21328 ? Sl 21:54 0:00 /usr/lib/ibus/ibus-x11 --kill-daemon gnome-i+ 981 0.0 0.1 406820 8076 ? Sl 21:54 0:00 /usr/lib/ibus/ibus-portal gnome-i+ 1014 0.0 0.1 333024 8128 ? Sl 21:54 0:00 /usr/lib/ibus/ibus-engine-simple gnome-i+ 1023 0.0 0.0 187336 4956 ? Sl 21:54 0:00 /usr/lib/dconf/dconf-service root 1959 0.0 0.0 26788 4500 ? S 21:55 0:00 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/dhclient-wlp1s0.pid -lf /var/lib/NetworkManager/dhclient-7416d4e3-dbd5-4037-ab05-c59023d3f4d9-wlp1s0.lease -cf /var/lib/NetworkManager/dhclient-wlp1s0.conf wlp1s0 avahi 2031 0.0 0.0 49276 3464 ? Ss 21:55 0:00 avahi-daemon: running [endless.local] avahi 2036 0.0 0.0 49020 368 ? S 21:55 0:00 avahi-daemon: chroot helper root 2192 0.0 0.1 376332 8380 ? Sl 21:55 0:00 gdm-session-worker [pam/gdm-password] jeremy 2202 0.0 0.0 63172 6756 ? Ss 21:55 0:00 /lib/systemd/systemd --user jeremy 2203 0.0 0.0 259484 2260 ? S 21:55 0:00 (sd-pam) jeremy 2209 0.0 0.0 332660 7320 ? SLl 21:55 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login jeremy 2217 0.0 0.1 757100 15232 ? Ssl 21:55 0:00 /usr/lib/gnome-session/gnome-session-binary jeremy 2243 0.2 0.0 46032 4820 ? Ss 21:55 0:02 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation jeremy 2285 0.0 0.0 10992 312 ? Ss 21:55 0:00 /usr/bin/ssh-agent /usr/bin/im-launch gnome-session jeremy 2296 0.1 0.1 490608 9988 ? Ssl 21:55 0:01 /usr/bin/ibus-daemon --daemonize --xim jeremy 2310 0.0 0.0 403752 6364 ? Ssl 21:55 0:00 /usr/lib/gvfs/gvfsd jeremy 2320 0.0 0.1 368844 8512 ? Ssl 21:55 0:00 /usr/lib/at-spi2-core/at-spi-bus-launcher jeremy 2325 0.0 0.0 45144 3812 ? S 21:55 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 jeremy 2327 0.0 0.0 218024 5440 ? Sl 21:55 0:00 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session jeremy 2347 17.8 2.4 2875216 200136 ? Sl 21:55 3:43 /usr/bin/gnome-shell jeremy 2358 1.1 0.1 1807720 11980 ? S root 7248 0.0 0.0 0 0 ? S 22:13 0:00 [kworker/1:1] root 7273 0.0 0.0 0 0 ? S 22:14 0:00 [kworker/2:1] root 7274 0.0 0.0 0 0 ? S 22:14 0:00 [kworker/1:2] jeremy 7281 0.2 0.3 465932 27620 ? Sl 22:14 0:00 /usr/bin/python3 /usr/share/eos-google-chrome-helper/eos-google-chrome.py jeremy 7290 0.2 0.2 444828 23884 ? Sl 22:14 0:00 /usr/bin/python3 /var/lib/flatpak/app/com.google.Chrome/x86_64/eos3/3c53c34fbc70a8e845830056da453003619b9c3fcc7477766b67e4a6078f8fc2/files/bin/eos-google-chrome-app jeremy 7293 0.0 0.0 13156 1016 ? S 22:14 0:00 bwrap --args 15 bash -c read jeremy 7294 18.6 1.9 1336348 160576 ? SLl 22:14 0:21 /sysroot/flatpak/app/com.google.Chrome/x86_64/eos3/3c53c34fbc70a8e845830056da453003619b9c3fcc7477766b67e4a6078f8fc2/files/extra/opt/google/chrome/chrome jeremy 7299 0.0 0.0 125556 644 ? S 22:14 0:00 cat jeremy 7300 0.0 0.0 125556 692 ? S 22:14 0:00 cat jeremy 7304 0.0 0.0 13156 1020 ? S 22:14 0:00 bwrap --args 15 /usr/lib/flatpak/flatpak-dbus-proxy --fd=17 unix:path=/run/user/1001/bus /run/user/1001/.dbus-proxy/session-bus-proxy-R7VK9Y --filter --own=com.google.Chrome --own=com.google.Chrome.* --talk=org.freedesktop.portal.* jeremy 7305 0.0 0.0 113404 1880 ? Sl 22:14 0:00 /usr/lib/flatpak/flatpak-dbus-proxy --fd=17 unix:path=/run/user/1001/bus /run/user/1001/.dbus-proxy/session-bus-proxy-R7VK9Y --filter --own=com.google.Chrome --own=com.google.Chrome.* --talk=org.freedesktop.portal.* jeremy 7309 0.0 0.5 506348 43788 ? S 22:14 0:00 /sysroot/flatpak/app/com.google.Chrome/x86_64/eos3/3c53c34fbc70a8e845830056da453003619b9c3fcc7477766b67e4a6078f8fc2/files/extra/opt/google/chrome/chrome --type=zygote --enable-crash-reporter=2cb641fe-f6f5-422b-8773-d773d8e5c2bb, jeremy 7311 0.2 0.0 13892 1820 ? S 22:14 0:00 bwrap --args 15 bash -c read jeremy 7315 0.0 0.1 506348 11052 ? S 22:14 0:00 /sysroot/flatpak/app/com.google.Chrome/x86_64/eos3/3c53c34fbc70a8e845830056da453003619b9c3fcc7477766b67e4a6078f8fc2/files/extra/opt/google/chrome/chrome --type=zygote --enable-crash-reporter=2cb641fe-f6f5-422b-8773-d773d8e5c2bb, jeremy 7325 0.0 0.0 124536 2792 ? S 22:14 0:00 bash -c read jeremy 7379 2.3 1.0 1250412 86764 ? Sl 22:14 0:02 /sysroot/flatpak/app/com.google.Chrome/x86_64/eos3/3c53c34fbc70a8e845830056da453003619b9c3fcc7477766b67e4a6078f8fc2/files/extra/opt/google/chrome/chrome --type=renderer --field-trial-handle=5057911868596369903,14803899284002417088,131072 --service-pipe-token=A82BC2706E6771946CD6022F1E6F6FB1 --lang=en-US --enable-crash-reporter=2cb641fe-f6f5-422b-8773-d773d8e5c2bb, --extension-process --enable-offline-auto-reload --enable-offline-auto-reload-visible-only --blink-settings=disallowFetchForDocWrittenScriptsInMainFrame=false,disallowFetchForDocWrittenScriptsInMainFrameOnSlowConnections=true --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;0,16,3553;0,17,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;1,16,3553;1,17,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;2,16,3553;2,17,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553;3,16,3553;3,17,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553;4,16,3553;4,17,3553;5,0,3553;5,1,3553;5,2,3553;5,3,3553;5,4,3553;5,5,3553;5,6,3553;5,7,3553;5,8,3553;5,9,3553;5,10,3553;5,11,3553;5,12,3553;5,13,3553;5,14,3553;5,15,3553;5,16,3553;5,17,3553;6,0,3553;6,1,3553;6,2,3553;6,3,3553;6,4,3553;6,5,3553;6,6,3553;6,7,3553;6,8,3553;6,9,3553;6,10,3553;6,11,3553;6,12,3553;6,13,3553;6,14,3553;6,15,3553;6,16,3553;6,17,3553 --disable-accelerated-video-decode --disable-gpu-compositing --enable-gpu-async-worker-context --service-request-channel-token=A82BC2706E6771946CD6022F1E6F6FB1 --renderer-client-id=3 --shared-files=v8_natives_data:100,v8_snapshot_data:101 root 7534 0.0 0.0 0 0 ? S 22:14 0:00 [kworker/3:2] jeremy 7555 22.0 3.1 1449312 253328 ? Sl 22:14 0:22 /sysroot/flatpak/app/com.google.Chrome/x86_64/eos3/3c53c34fbc70a8e845830056da453003619b9c3fcc7477766b67e4a6078f8fc2/files/extra/opt/google/chrome/chrome --type=renderer --field-trial-handle=5057911868596369903,14803899284002417088,131072 --service-pipe-token=0A343EEFB5815DDE8F2C8D397BEAFB8E --lang=en-US --enable-crash-reporter=2cb641fe-f6f5-422b-8773-d773d8e5c2bb, --enable-offline-auto-reload --enable-offline-auto-reload-visible-only --blink-settings=disallowFetchForDocWrittenScriptsInMainFrame=false,disallowFetchForDocWrittenScriptsInMainFrameOnSlowConnections=true --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;0,16,3553;0,17,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;1,16,3553;1,17,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;2,16,3553;2,17,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553;3,16,3553;3,17,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553;4,16,3553;4,17,3553;5,0,3553;5,1,3553;5,2,3553;5,3,3553;5,4,3553;5,5,3553;5,6,3553;5,7,3553;5,8,3553;5,9,3553;5,10,3553;5,11,3553;5,12,3553;5,13,3553;5,14,3553;5,15,3553;5,16,3553;5,17,3553;6,0,3553;6,1,3553;6,2,3553;6,3,3553;6,4,3553;6,5,3553;6,6,3553;6,7,3553;6,8,3553;6,9,3553;6,10,3553;6,11,3553;6,12,3553;6,13,3553;6,14,3553;6,15,3553;6,16,3553;6,17,3553 --disable-accelerated-video-decode --disable-gpu-compositing --enable-gpu-async-worker-context --service-request-channel-token=0A343EEFB5815DDE8F2C8D397BEAFB8E --renderer-client-id=11 --shared-files=v8_natives_data:100,v8_snapshot_data:101 jeremy 7611 2.8 0.2 466020 21008 ? Sl 22:16 0:00 /usr/lib/gnome-control-center/gnome-control-center-search-provider jeremy 7613 0.7 0.0 13156 984 ? S 22:16 0:00 bwrap --args 13 /app/bin/eks-search-provider-v1 jeremy 7617 7.6 0.4 813768 36508 ? Ssl 22:16 0:00 /usr/lib/gnome-terminal/gnome-terminal-server jeremy 7618 4.1 0.4 898436 38320 ? Sl 22:16 0:00 /usr/lib/gnome-contacts/gnome-contacts-search-provider jeremy 7619 9.6 0.7 908884 62384 ? Sl 22:16 0:00 /usr/lib/x86_64-linux-gnu/yelp-search-provider jeremy 7629 1.0 0.0 13420 900 ? S 22:16 0:00 bwrap --args 13 /app/bin/eks-search-provider-v1 jeremy 7639 7.6 0.4 429356 38336 ? Sl 22:16 0:00 /app/bin/eks-search-provider-v1 jeremy 7682 1.4 0.0 140760 4860 pts/0 Ss 22:16 0:00 bash jeremy 7687 13.0 0.3 1045956 26412 pts/0 Sl+ 22:16 0:00 gjs /usr/bin/eos-diagnostics jeremy 7766 0.0 0.0 159908 3232 pts/0 R+ 22:16 0:00 ps aux =============== = Boot timing = =============== Startup finished in 3.442s (kernel) + 9.082s (initrd) + 1min 39.254s (userspace) = 1min 51.778s =========== = Journal = =========== -- Logs begin at Thu 2017-11-16 13:55:32 PST, end at Thu 2017-11-16 22:16:34 PST. -- Nov 16 13:55:32 endless eos-chrome-plugin-update[1913]: 9150K .......... .......... .......... .......... .......... 99% 5.82M 0s Nov 16 13:55:32 endless eos-chrome-plugin-update[1913]: 9200K .......... .......... .......... .......... . 100% 14.1M=1.9s Nov 16 13:55:32 endless eos-chrome-plugin-update[1913]: 2017-11-16 13:55:32 (4.83 MB/s) - ‘/tmp/tmp.3Q726nhVvz/flash_player_ppapi_linux.x86_64.tar.gz’ saved [9463140/9463140] Nov 16 13:55:32 endless eos-chrome-plugin-update[1913]: Verifying /tmp/tmp.3Q726nhVvz/flash_player_ppapi_linux.x86_64.tar.gz Nov 16 13:55:32 endless eos-chrome-plugin-update[1913]: Installing /tmp/tmp.3Q726nhVvz/flash_player_ppapi_linux.x86_64.tar.gz Nov 16 13:55:32 endless eos-chrome-plugin-update[1913]: libpepflashplayer.so Nov 16 13:55:32 endless nm-dispatcher[1832]: req:6 'connectivity-change': new request (5 scripts) Nov 16 13:55:32 endless nm-dispatcher[1832]: req:6 'connectivity-change': start running ordered scripts... Nov 16 13:55:32 endless systemd[1]: Started /bin/systemctl --no-block start eos-phone-home.service. Nov 16 13:55:32 endless nm-dispatcher[1832]: Running timer as unit: run-r79b9306c3c5e486b8a1eda6e6a803a16.timer Nov 16 13:55:32 endless nm-dispatcher[1832]: Will run service as unit: run-r79b9306c3c5e486b8a1eda6e6a803a16.service Nov 16 13:55:32 endless avahi-daemon[2031]: Server startup complete. Host name is endless.local. Local service cookie is 830237112. Nov 16 13:55:32 endless eos-chrome-plugin-update[1913]: manifest.json Nov 16 13:55:32 endless eos-chrome-plugin-update[1913]: readme.txt Nov 16 13:55:32 endless eos-chrome-plugin-update[1913]: license.pdf Nov 16 13:55:32 endless eos-chrome-plugin-update[1913]: LGPL/ Nov 16 13:55:32 endless eos-chrome-plugin-update[1913]: LGPL/LGPL.txt Nov 16 13:55:32 endless eos-chrome-plugin-update[1913]: LGPL/notice.txt Nov 16 13:55:33 endless eos-chrome-plugin-update[1913]: Flash plugin installed Nov 16 13:55:33 endless eos-chrome-plugin-update[1913]: Widevine plugin is not installed or might be too old. Checking for a new version Nov 16 13:55:33 endless eos-chrome-plugin-update[1913]: --2017-11-16 13:55:33-- http://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages Nov 16 13:55:33 endless NetworkManager[592]: [1510869333.0853] policy: set '30LanceaFaster' (wlp1s0) as default for IPv6 routing and DNS Nov 16 13:55:34 endless ntpd[671]: Listen normally on 4 wlp1s0 192.168.1.94:123 Nov 16 13:55:34 endless ntpd[671]: bind(24) AF_INET6 2600:1700:8810:3020:c6c4:4730:e679:44b5#123 flags 0x11 failed: Cannot assign requested address Nov 16 13:55:34 endless ntpd[671]: unable to create socket on wlp1s0 (5) for 2600:1700:8810:3020:c6c4:4730:e679:44b5#123 Nov 16 13:55:34 endless ntpd[671]: failed to init interface for address 2600:1700:8810:3020:c6c4:4730:e679:44b5 Nov 16 13:55:34 endless ntpd[671]: Listen normally on 6 wlp1s0 [fe80::b993:1da6:a5a8:a63a%3]:123 Nov 16 13:55:34 endless eos-chrome-plugin-update[1913]: Resolving dl.google.com (dl.google.com)... 216.58.195.78, 2607:f8b0:4000:813::200e Nov 16 13:55:34 endless eos-chrome-plugin-update[1913]: Connecting to dl.google.com (dl.google.com)|216.58.195.78|:80... connected. Nov 16 13:55:34 endless eos-chrome-plugin-update[1913]: HTTP request sent, awaiting response... 200 OK Nov 16 13:55:34 endless eos-chrome-plugin-update[1913]: Length: 4431 (4.3K) [application/octet-stream] Nov 16 13:55:34 endless eos-chrome-plugin-update[1913]: Saving to: ‘/tmp/tmp.3Q726nhVvz/Packages’ Nov 16 13:55:34 endless eos-chrome-plugin-update[1913]: 0K .... 100% 160M=0s Nov 16 13:55:34 endless eos-chrome-plugin-update[1913]: 2017-11-16 13:55:34 (160 MB/s) - ‘/tmp/tmp.3Q726nhVvz/Packages’ saved [4431/4431] Nov 16 13:55:34 endless eos-chrome-plugin-update[1913]: A new version of widevine is available: 62.0.3202.94-1 (Current: not installed) Nov 16 13:55:34 endless eos-chrome-plugin-update[1913]: Downloading google-chrome-stable_62.0.3202.94-1_amd64.deb Nov 16 13:55:34 endless eos-chrome-plugin-update[1913]: --2017-11-16 13:55:34-- http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_62.0.3202.94-1_amd64.deb Nov 16 13:55:34 endless eos-chrome-plugin-update[1913]: Resolving dl.google.com (dl.google.com)... 172.217.12.46, 2607:f8b0:4002:810::200e Nov 16 13:55:34 endless eos-chrome-plugin-update[1913]: Connecting to dl.google.com (dl.google.com)|172.217.12.46|:80... connected. Nov 16 13:55:34 endless avahi-daemon[2031]: Leaving mDNS multicast group on interface wlp1s0.IPv6 with address fe80::b993:1da6:a5a8:a63a. Nov 16 13:55:34 endless avahi-daemon[2031]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address 2600:1700:8810:3020:c6c4:4730:e679:44b5. Nov 16 13:55:34 endless avahi-daemon[2031]: Registering new address record for 2600:1700:8810:3020:c6c4:4730:e679:44b5 on wlp1s0.*. Nov 16 13:55:34 endless avahi-daemon[2031]: Withdrawing address record for fe80::b993:1da6:a5a8:a63a on wlp1s0. Nov 16 13:55:34 endless eos-chrome-plugin-update[1913]: HTTP request sent, awaiting response... 200 OK Nov 16 13:55:34 endless eos-chrome-plugin-update[1913]: Length: 48992922 (47M) [application/x-debian-package] Nov 16 13:55:34 endless eos-chrome-plugin-update[1913]: Saving to: ‘/tmp/tmp.3Q726nhVvz/google-chrome-stable_62.0.3202.94-1_amd64.deb’ Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 0K .......... .......... .......... .......... .......... 0% 246K 3m14s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 50K .......... .......... .......... .......... .......... 0% 242K 3m15s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 100K .......... .......... .......... .......... .......... 0% 1.08M 2m24s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 150K .......... .......... .......... .......... .......... 0% 1.72M 1m55s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 200K .......... .......... .......... .......... .......... 0% 383K 1m57s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 250K .......... .......... .......... .......... .......... 0% 10.2M 98s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 300K .......... .......... .......... .......... .......... 0% 1.17M 90s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 350K .......... .......... .......... .......... .......... 0% 5.12M 79s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 400K .......... .......... .......... .......... .......... 0% 4.98M 72s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 450K .......... .......... .......... .......... .......... 1% 3.93M 65s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 500K .......... .......... .......... .......... .......... 1% 5.77M 60s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 550K .......... .......... .......... .......... .......... 1% 405K 65s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 600K .......... .......... .......... .......... .......... 1% 13.2M 60s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 650K .......... .......... .......... .......... .......... 1% 22.0M 56s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 700K .......... .......... .......... .......... .......... 1% 259K 64s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 750K .......... .......... .......... .......... .......... 1% 19.7M 60s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 800K .......... .......... .......... .......... .......... 1% 126M 57s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 850K .......... .......... .......... .......... .......... 1% 132M 53s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 900K .......... .......... .......... .......... .......... 1% 134M 51s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 950K .......... .......... .......... .......... .......... 2% 119M 48s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 1000K .......... .......... .......... .......... .......... 2% 126M 46s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 1050K .......... .......... .......... .......... .......... 2% 121M 44s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 1100K .......... .......... .......... .......... .......... 2% 115M 42s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 1150K .......... .......... .......... .......... .......... 2% 106M 40s Nov 16 13:55:35 endless eos-chrome-plugin-update[1913]: 1200K .......... .......... .......... .......... .......... 2% 46.7M 38s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 1250K .......... .......... .......... .......... .......... 2% 685K 39s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 1300K .......... .......... .......... .......... .......... 2% 10.2M 38s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 1350K .......... .......... .......... .......... .......... 2% 407K 41s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 1400K .......... .......... .......... .......... .......... 3% 98.9M 39s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 1450K .......... .......... .......... .......... .......... 3% 136M 38s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 1500K .......... .......... .......... .......... .......... 3% 139M 37s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 1550K .......... .......... .......... .......... .......... 3% 126M 36s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 1600K .......... .......... .......... .......... .......... 3% 116M 34s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 1650K .......... .......... .......... .......... .......... 3% 139M 33s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 1700K .......... .......... .......... .......... .......... 3% 720K 34s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 1750K .......... .......... .......... .......... .......... 3% 9.67M 33s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 1800K .......... .......... .......... .......... .......... 3% 13.6M 33s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 1850K .......... .......... .......... .......... .......... 3% 180M 32s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 1900K .......... .......... .......... .......... .......... 4% 207M 31s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 1950K .......... .......... .......... .......... .......... 4% 20.1M 30s Nov 16 13:55:36 endless ntpd[671]: Listen normally on 7 wlp1s0 [2600:1700:8810:3020:c6c4:4730:e679:44b5]:123 Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2000K .......... .......... .......... .......... .......... 4% 409K 32s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2050K .......... .......... .......... .......... .......... 4% 149M 31s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2100K .......... .......... .......... .......... .......... 4% 29.6M 31s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2150K .......... .......... .......... .......... .......... 4% 114M 30s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2200K .......... .......... .......... .......... .......... 4% 135M 29s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2250K .......... .......... .......... .......... .......... 4% 133M 28s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2300K .......... .......... .......... .......... .......... 4% 144M 28s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2350K .......... .......... .......... .......... .......... 5% 147M 27s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2400K .......... .......... .......... .......... .......... 5% 767K 28s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2450K .......... .......... .......... .......... .......... 5% 7.29M 27s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2500K .......... .......... .......... .......... .......... 5% 194M 27s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2550K .......... .......... .......... .......... .......... 5% 30.8M 26s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2600K .......... .......... .......... .......... .......... 5% 10.1M 26s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2650K .......... .......... .......... .......... .......... 5% 411K 27s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2700K .......... .......... .......... .......... .......... 5% 24.6M 27s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2750K .......... .......... .......... .......... .......... 5% 21.0M 26s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2800K .......... .......... .......... .......... .......... 5% 252K 29s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2850K .......... .......... .......... .......... .......... 6% 24.0M 29s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2900K .......... .......... .......... .......... .......... 6% 10.5M 28s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 2950K .......... .......... .......... .......... .......... 6% 123M 28s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 3000K .......... .......... .......... .......... .......... 6% 251K 30s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 3050K .......... .......... .......... .......... .......... 6% 93.1M 30s Nov 16 13:55:36 endless eos-chrome-plugin-update[1913]: 3100K .......... .......... .......... .......... .......... 6% 212M 29s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3150K .......... .......... .......... .......... .......... 6% 207M 29s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3200K .......... .......... .......... .......... .......... 6% 188M 28s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3250K .......... .......... .......... .......... .......... 6% 216M 28s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3300K .......... .......... .......... .......... .......... 7% 188M 27s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3350K .......... .......... .......... .......... .......... 7% 190M 27s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3400K .......... .......... .......... .......... .......... 7% 174M 26s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3450K .......... .......... .......... .......... .......... 7% 223M 26s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3500K .......... .......... .......... .......... .......... 7% 142M 26s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3550K .......... .......... .......... .......... .......... 7% 176M 25s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3600K .......... .......... .......... .......... .......... 7% 188M 25s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3650K .......... .......... .......... .......... .......... 7% 216M 24s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3700K .......... .......... .......... .......... .......... 7% 226M 24s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3750K .......... .......... .......... .......... .......... 7% 211M 24s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3800K .......... .......... .......... .......... .......... 8% 49.6M 23s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3850K .......... .......... .......... .......... .......... 8% 24.2M 23s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3900K .......... .......... .......... .......... .......... 8% 251K 25s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 3950K .......... .......... .......... .......... .......... 8% 101M 25s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4000K .......... .......... .......... .......... .......... 8% 204M 24s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4050K .......... .......... .......... .......... .......... 8% 210M 24s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4100K .......... .......... .......... .......... .......... 8% 1.26M 24s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4150K .......... .......... .......... .......... .......... 8% 2.83M 24s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4200K .......... .......... .......... .......... .......... 8% 2.77M 24s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4250K .......... .......... .......... .......... .......... 8% 377K 25s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4300K .......... .......... .......... .......... .......... 9% 178M 25s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4350K .......... .......... .......... .......... .......... 9% 47.2M 24s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4400K .......... .......... .......... .......... .......... 9% 20.1M 24s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4450K .......... .......... .......... .......... .......... 9% 255K 26s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4500K .......... .......... .......... .......... .......... 9% 170M 25s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4550K .......... .......... .......... .......... .......... 9% 223M 25s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4600K .......... .......... .......... .......... .......... 9% 44.3M 25s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4650K .......... .......... .......... .......... .......... 9% 1.18M 25s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4700K .......... .......... .......... .......... .......... 9% 2.80M 25s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4750K .......... .......... .......... .......... .......... 10% 2.47M 25s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4800K .......... .......... .......... .......... .......... 10% 395K 25s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4850K .......... .......... .......... .......... .......... 10% 26.6M 25s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4900K .......... .......... .......... .......... .......... 10% 15.3M 25s Nov 16 13:55:37 endless eos-chrome-plugin-update[1913]: 4950K .......... .......... .......... .......... .......... 10% 25.6M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5000K .......... .......... .......... .......... .......... 10% 252K 26s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5050K .......... .......... .......... .......... .......... 10% 142M 26s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5100K .......... .......... .......... .......... .......... 10% 118M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5150K .......... .......... .......... .......... .......... 10% 30.6M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5200K .......... .......... .......... .......... .......... 10% 1.24M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5250K .......... .......... .......... .......... .......... 11% 2.81M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5300K .......... .......... .......... .......... .......... 11% 2.61M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5350K .......... .......... .......... .......... .......... 11% 392K 26s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5400K .......... .......... .......... .......... .......... 11% 14.5M 26s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5450K .......... .......... .......... .......... .......... 11% 27.1M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5500K .......... .......... .......... .......... .......... 11% 664K 26s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5550K .......... .......... .......... .......... .......... 11% 403K 26s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5600K .......... .......... .......... .......... .......... 11% 139M 26s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5650K .......... .......... .......... .......... .......... 11% 134M 26s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5700K .......... .......... .......... .......... .......... 12% 50.7M 26s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5750K .......... .......... .......... .......... .......... 12% 24.8M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5800K .......... .......... .......... .......... .......... 12% 1.09M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5850K .......... .......... .......... .......... .......... 12% 2.51M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5900K .......... .......... .......... .......... .......... 12% 371K 26s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 5950K .......... .......... .......... .......... .......... 12% 15.7M 26s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6000K .......... .......... .......... .......... .......... 12% 19.9M 26s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6050K .......... .......... .......... .......... .......... 12% 33.9M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6100K .......... .......... .......... .......... .......... 12% 653K 26s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6150K .......... .......... .......... .......... .......... 12% 119M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6200K .......... .......... .......... .......... .......... 13% 130M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6250K .......... .......... .......... .......... .......... 13% 2.88M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6300K .......... .......... .......... .......... .......... 13% 2.49M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6350K .......... .......... .......... .......... .......... 13% 2.63M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6400K .......... .......... .......... .......... .......... 13% 2.88M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6450K .......... .......... .......... .......... .......... 13% 2.72M 25s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6500K .......... .......... .......... .......... .......... 13% 2.79M 24s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6550K .......... .......... .......... .......... .......... 13% 2.50M 24s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6600K .......... .......... .......... .......... .......... 13% 2.75M 24s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6650K .......... .......... .......... .......... .......... 14% 2.83M 24s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6700K .......... .......... .......... .......... .......... 14% 2.77M 24s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6750K .......... .......... .......... .......... .......... 14% 2.47M 24s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6800K .......... .......... .......... .......... .......... 14% 3.00M 24s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6850K .......... .......... .......... .......... .......... 14% 2.79M 24s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6900K .......... .......... .......... .......... .......... 14% 2.48M 24s Nov 16 13:55:38 endless eos-chrome-plugin-update[1913]: 6950K .......... .......... .......... .......... .......... 14% 2.80M 24s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7000K .......... .......... .......... .......... .......... 14% 2.73M 23s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7050K .......... .......... .......... .......... .......... 14% 2.87M 23s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7100K .......... .......... .......... .......... .......... 14% 2.48M 23s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7150K .......... .......... .......... .......... .......... 15% 2.80M 23s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7200K .......... .......... .......... .......... .......... 15% 2.60M 23s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7250K .......... .......... .......... .......... .......... 15% 2.83M 23s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7300K .......... .......... .......... .......... .......... 15% 2.79M 23s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7350K .......... .......... .......... .......... .......... 15% 2.48M 23s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7400K .......... .......... .......... .......... .......... 15% 2.80M 23s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7450K .......... .......... .......... .......... .......... 15% 2.82M 23s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7500K .......... .......... .......... .......... .......... 15% 2.76M 23s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7550K .......... .......... .......... .......... .......... 15% 2.49M 23s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7600K .......... .......... .......... .......... .......... 15% 2.98M 22s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7650K .......... .......... .......... .......... .......... 16% 2.43M 22s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7700K .......... .......... .......... .......... .......... 16% 2.87M 22s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7750K .......... .......... .......... .......... .......... 16% 2.76M 22s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7800K .......... .......... .......... .......... .......... 16% 2.85M 22s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7850K .......... .......... .......... .......... .......... 16% 2.75M 22s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7900K .......... .......... .......... .......... .......... 16% 2.50M 22s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 7950K .......... .......... .......... .......... .......... 16% 2.81M 22s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8000K .......... .......... .......... .......... .......... 16% 2.82M 22s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8050K .......... .......... .......... .......... .......... 16% 2.77M 22s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8100K .......... .......... .......... .......... .......... 17% 2.48M 22s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8150K .......... .......... .......... .......... .......... 17% 2.82M 22s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8200K .......... .......... .......... .......... .......... 17% 2.76M 22s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8250K .......... .......... .......... .......... .......... 17% 2.51M 21s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8300K .......... .......... .......... .......... .......... 17% 2.80M 21s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8350K .......... .......... .......... .......... .......... 17% 2.78M 21s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8400K .......... .......... .......... .......... .......... 17% 2.81M 21s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8450K .......... .......... .......... .......... .......... 17% 2.44M 21s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8500K .......... .......... .......... .......... .......... 17% 2.85M 21s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8550K .......... .......... .......... .......... .......... 17% 2.77M 21s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8600K .......... .......... .......... .......... .......... 18% 2.81M 21s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8650K .......... .......... .......... .......... .......... 18% 2.73M 21s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8700K .......... .......... .......... .......... .......... 18% 2.55M 21s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8750K .......... .......... .......... .......... .......... 18% 2.75M 21s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8800K .......... .......... .......... .......... .......... 18% 2.82M 21s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8850K .......... .......... .......... .......... .......... 18% 2.79M 21s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8900K .......... .......... .......... .......... .......... 18% 2.58M 21s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 8950K .......... .......... .......... .......... .......... 18% 2.93M 21s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9000K .......... .......... .......... .......... .......... 18% 2.44M 20s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9050K .......... .......... .......... .......... .......... 19% 2.92M 20s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9100K .......... .......... .......... .......... .......... 19% 3.47M 20s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9150K .......... .......... .......... .......... .......... 19% 3.38M 20s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9200K .......... .......... .......... .......... .......... 19% 3.41M 20s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9250K .......... .......... .......... .......... .......... 19% 2.39M 20s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9300K .......... .......... .......... .......... .......... 19% 3.41M 20s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9350K .......... .......... .......... .......... .......... 19% 3.15M 20s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9400K .......... .......... .......... .......... .......... 19% 3.54M 20s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9450K .......... .......... .......... .......... .......... 19% 3.58M 20s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9500K .......... .......... .......... .......... .......... 19% 3.57M 20s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9550K .......... .......... .......... .......... .......... 20% 3.51M 20s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9600K .......... .......... .......... .......... .......... 20% 3.21M 20s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9650K .......... .......... .......... .......... .......... 20% 3.47M 20s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9700K .......... .......... .......... .......... .......... 20% 3.71M 19s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9750K .......... .......... .......... .......... .......... 20% 3.58M 19s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9800K .......... .......... .......... .......... .......... 20% 3.15M 19s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9850K .......... .......... .......... .......... .......... 20% 3.58M 19s Nov 16 13:55:39 endless eos-chrome-plugin-update[1913]: 9900K .......... .......... .......... .......... .......... 20% 3.56M 19s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 9950K .......... .......... .......... .......... .......... 20% 3.65M 19s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10000K .......... .......... .......... .......... .......... 21% 3.30M 19s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10050K .......... .......... .......... .......... .......... 21% 4.06M 19s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10100K .......... .......... .......... .......... .......... 21% 4.40M 19s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10150K .......... .......... .......... .......... .......... 21% 4.27M 19s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10200K .......... .......... .......... .......... .......... 21% 3.58M 19s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10250K .......... .......... .......... .......... .......... 21% 3.37M 19s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10300K .......... .......... .......... .......... .......... 21% 4.21M 19s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10350K .......... .......... .......... .......... .......... 21% 4.37M 19s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10400K .......... .......... .......... .......... .......... 21% 4.52M 18s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10450K .......... .......... .......... .......... .......... 21% 4.51M 18s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10500K .......... .......... .......... .......... .......... 22% 4.35M 18s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10550K .......... .......... .......... .......... .......... 22% 4.09M 18s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10600K .......... .......... .......... .......... .......... 22% 4.29M 18s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10650K .......... .......... .......... .......... .......... 22% 5.35M 18s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10700K .......... .......... .......... .......... .......... 22% 4.40M 18s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10750K .......... .......... .......... .......... .......... 22% 4.40M 18s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10800K .......... .......... .......... .......... .......... 22% 4.31M 18s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10850K .......... .......... .......... .......... .......... 22% 4.69M 18s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10900K .......... .......... .......... .......... .......... 22% 4.60M 18s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 10950K .......... .......... .......... .......... .......... 22% 4.45M 18s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11000K .......... .......... .......... .......... .......... 23% 4.30M 18s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11050K .......... .......... .......... .......... .......... 23% 4.66M 18s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11100K .......... .......... .......... .......... .......... 23% 5.59M 18s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11150K .......... .......... .......... .......... .......... 23% 4.49M 17s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11200K .......... .......... .......... .......... .......... 23% 4.38M 17s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11250K .......... .......... .......... .......... .......... 23% 5.00M 17s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11300K .......... .......... .......... .......... .......... 23% 4.90M 17s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11350K .......... .......... .......... .......... .......... 23% 7.00M 17s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11400K .......... .......... .......... .......... .......... 23% 5.60M 17s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11450K .......... .......... .......... .......... .......... 24% 5.79M 17s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11500K .......... .......... .......... .......... .......... 24% 3.23M 17s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11550K .......... .......... .......... .......... .......... 24% 5.67M 17s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11600K .......... .......... .......... .......... .......... 24% 5.31M 17s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11650K .......... .......... .......... .......... .......... 24% 5.22M 17s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11700K .......... .......... .......... .......... .......... 24% 4.93M 17s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11750K .......... .......... .......... .......... .......... 24% 6.50M 17s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11800K .......... .......... .......... .......... .......... 24% 5.55M 17s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11850K .......... .......... .......... .......... .......... 24% 7.31M 16s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11900K .......... .......... .......... .......... .......... 24% 5.04M 16s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 11950K .......... .......... .......... .......... .......... 25% 6.19M 16s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12000K .......... .......... .......... .......... .......... 25% 5.25M 16s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12050K .......... .......... .......... .......... .......... 25% 4.82M 16s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12100K .......... .......... .......... .......... .......... 25% 6.55M 16s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12150K .......... .......... .......... .......... .......... 25% 6.65M 16s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12200K .......... .......... .......... .......... .......... 25% 5.70M 16s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12250K .......... .......... .......... .......... .......... 25% 5.10M 16s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12300K .......... .......... .......... .......... .......... 25% 6.94M 16s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12350K .......... .......... .......... .......... .......... 25% 5.07M 16s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12400K .......... .......... .......... .......... .......... 26% 5.83M 16s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12450K .......... .......... .......... .......... .......... 26% 6.78M 16s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12500K .......... .......... .......... .......... .......... 26% 5.47M 16s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12550K .......... .......... .......... .......... .......... 26% 4.93M 16s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12600K .......... .......... .......... .......... .......... 26% 6.10M 16s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12650K .......... .......... .......... .......... .......... 26% 6.37M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12700K .......... .......... .......... .......... .......... 26% 5.65M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12750K .......... .......... .......... .......... .......... 26% 5.43M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12800K .......... .......... .......... .......... .......... 26% 6.19M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12850K .......... .......... .......... .......... .......... 26% 6.86M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12900K .......... .......... .......... .......... .......... 27% 8.36M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 12950K .......... .......... .......... .......... .......... 27% 7.66M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13000K .......... .......... .......... .......... .......... 27% 6.13M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13050K .......... .......... .......... .......... .......... 27% 6.93M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13100K .......... .......... .......... .......... .......... 27% 5.08M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13150K .......... .......... .......... .......... .......... 27% 5.06M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13200K .......... .......... .......... .......... .......... 27% 6.56M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13250K .......... .......... .......... .......... .......... 27% 6.64M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13300K .......... .......... .......... .......... .......... 27% 6.78M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13350K .......... .......... .......... .......... .......... 28% 5.92M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13400K .......... .......... .......... .......... .......... 28% 7.51M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13450K .......... .......... .......... .......... .......... 28% 6.13M 15s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13500K .......... .......... .......... .......... .......... 28% 8.09M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13550K .......... .......... .......... .......... .......... 28% 6.47M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13600K .......... .......... .......... .......... .......... 28% 6.67M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13650K .......... .......... .......... .......... .......... 28% 6.58M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13700K .......... .......... .......... .......... .......... 28% 7.89M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13750K .......... .......... .......... .......... .......... 28% 6.75M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13800K .......... .......... .......... .......... .......... 28% 6.25M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13850K .......... .......... .......... .......... .......... 29% 8.12M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13900K .......... .......... .......... .......... .......... 29% 6.46M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 13950K .......... .......... .......... .......... .......... 29% 7.16M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14000K .......... .......... .......... .......... .......... 29% 6.71M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14050K .......... .......... .......... .......... .......... 29% 7.23M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14100K .......... .......... .......... .......... .......... 29% 5.97M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14150K .......... .......... .......... .......... .......... 29% 8.29M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14200K .......... .......... .......... .......... .......... 29% 6.57M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14250K .......... .......... .......... .......... .......... 29% 7.51M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14300K .......... .......... .......... .......... .......... 29% 7.70M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14350K .......... .......... .......... .......... .......... 30% 7.99M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14400K .......... .......... .......... .......... .......... 30% 6.60M 14s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14450K .......... .......... .......... .......... .......... 30% 7.73M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14500K .......... .......... .......... .......... .......... 30% 5.48M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14550K .......... .......... .......... .......... .......... 30% 10.6M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14600K .......... .......... .......... .......... .......... 30% 5.93M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14650K .......... .......... .......... .......... .......... 30% 8.42M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14700K .......... .......... .......... .......... .......... 30% 8.31M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14750K .......... .......... .......... .......... .......... 30% 7.45M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14800K .......... .......... .......... .......... .......... 31% 9.82M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14850K .......... .......... .......... .......... .......... 31% 9.66M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14900K .......... .......... .......... .......... .......... 31% 7.85M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 14950K .......... .......... .......... .......... .......... 31% 8.97M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15000K .......... .......... .......... .......... .......... 31% 9.29M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15050K .......... .......... .......... .......... .......... 31% 9.25M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15100K .......... .......... .......... .......... .......... 31% 6.95M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15150K .......... .......... .......... .......... .......... 31% 5.31M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15200K .......... .......... .......... .......... .......... 31% 6.95M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15250K .......... .......... .......... .......... .......... 31% 10.4M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15300K .......... .......... .......... .......... .......... 32% 9.17M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15350K .......... .......... .......... .......... .......... 32% 7.49M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15400K .......... .......... .......... .......... .......... 32% 10.2M 13s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15450K .......... .......... .......... .......... .......... 32% 9.29M 12s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15500K .......... .......... .......... .......... .......... 32% 8.20M 12s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15550K .......... .......... .......... .......... .......... 32% 8.56M 12s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15600K .......... .......... .......... .......... .......... 32% 10.3M 12s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15650K .......... .......... .......... .......... .......... 32% 8.01M 12s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15700K .......... .......... .......... .......... .......... 32% 9.17M 12s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15750K .......... .......... .......... .......... .......... 33% 9.49M 12s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15800K .......... .......... .......... .......... .......... 33% 8.59M 12s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15850K .......... .......... .......... .......... .......... 33% 7.48M 12s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15900K .......... .......... .......... .......... .......... 33% 7.53M 12s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 15950K .......... .......... .......... .......... .......... 33% 6.90M 12s Nov 16 13:55:40 endless eos-chrome-plugin-update[1913]: 16000K .......... .......... .......... .......... .......... 33% 7.47M 12s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16050K .......... .......... .......... .......... .......... 33% 7.11M 12s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16100K .......... .......... .......... .......... .......... 33% 8.88M 12s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16150K .......... .......... .......... .......... .......... 33% 6.82M 12s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16200K .......... .......... .......... .......... .......... 33% 920K 12s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16250K .......... .......... .......... .......... .......... 34% 9.54M 12s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16300K .......... .......... .......... .......... .......... 34% 14.4M 12s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16350K .......... .......... .......... .......... .......... 34% 9.60M 12s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16400K .......... .......... .......... .......... .......... 34% 7.25M 12s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16450K .......... .......... .......... .......... .......... 34% 9.40M 12s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16500K .......... .......... .......... .......... .......... 34% 10.6M 12s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16550K .......... .......... .......... .......... .......... 34% 9.74M 12s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16600K .......... .......... .......... .......... .......... 34% 7.46M 12s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16650K .......... .......... .......... .......... .......... 34% 6.14M 12s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16700K .......... .......... .......... .......... .......... 35% 900K 12s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16750K .......... .......... .......... .......... .......... 35% 140M 12s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16800K .......... .......... .......... .......... .......... 35% 211M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16850K .......... .......... .......... .......... .......... 35% 218M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16900K .......... .......... .......... .......... .......... 35% 173M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 16950K .......... .......... .......... .......... .......... 35% 194M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17000K .......... .......... .......... .......... .......... 35% 223M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17050K .......... .......... .......... .......... .......... 35% 15.7M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17100K .......... .......... .......... .......... .......... 35% 14.7M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17150K .......... .......... .......... .......... .......... 35% 14.5M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17200K .......... .......... .......... .......... .......... 36% 14.6M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17250K .......... .......... .......... .......... .......... 36% 15.8M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17300K .......... .......... .......... .......... .......... 36% 14.1M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17350K .......... .......... .......... .......... .......... 36% 7.68M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17400K .......... .......... .......... .......... .......... 36% 10.1M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17450K .......... .......... .......... .......... .......... 36% 30.3M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17500K .......... .......... .......... .......... .......... 36% 178M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17550K .......... .......... .......... .......... .......... 36% 214M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17600K .......... .......... .......... .......... .......... 36% 205M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17650K .......... .......... .......... .......... .......... 36% 8.44M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17700K .......... .......... .......... .......... .......... 37% 963K 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17750K .......... .......... .......... .......... .......... 37% 9.58M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17800K .......... .......... .......... .......... .......... 37% 9.26M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17850K .......... .......... .......... .......... .......... 37% 10.8M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17900K .......... .......... .......... .......... .......... 37% 9.31M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 17950K .......... .......... .......... .......... .......... 37% 9.66M 11s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18000K .......... .......... .......... .......... .......... 37% 7.44M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18050K .......... .......... .......... .......... .......... 37% 10.1M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18100K .......... .......... .......... .......... .......... 37% 9.48M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18150K .......... .......... .......... .......... .......... 38% 4.29M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18200K .......... .......... .......... .......... .......... 38% 26.3M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18250K .......... .......... .......... .......... .......... 38% 166M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18300K .......... .......... .......... .......... .......... 38% 218M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18350K .......... .......... .......... .......... .......... 38% 2.23M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18400K .......... .......... .......... .......... .......... 38% 198M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18450K .......... .......... .......... .......... .......... 38% 2.32M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18500K .......... .......... .......... .......... .......... 38% 6.12M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18550K .......... .......... .......... .......... .......... 38% 13.9M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18600K .......... .......... .......... .......... .......... 38% 7.90M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18650K .......... .......... .......... .......... .......... 39% 9.82M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18700K .......... .......... .......... .......... .......... 39% 7.14M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18750K .......... .......... .......... .......... .......... 39% 9.42M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18800K .......... .......... .......... .......... .......... 39% 14.9M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18850K .......... .......... .......... .......... .......... 39% 6.03M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18900K .......... .......... .......... .......... .......... 39% 8.51M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 18950K .......... .......... .......... .......... .......... 39% 4.97M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19000K .......... .......... .......... .......... .......... 39% 10.4M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19050K .......... .......... .......... .......... .......... 39% 7.06M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19100K .......... .......... .......... .......... .......... 40% 6.94M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19150K .......... .......... .......... .......... .......... 40% 10.2M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19200K .......... .......... .......... .......... .......... 40% 7.79M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19250K .......... .......... .......... .......... .......... 40% 5.68M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19300K .......... .......... .......... .......... .......... 40% 7.93M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19350K .......... .......... .......... .......... .......... 40% 25.5M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19400K .......... .......... .......... .......... .......... 40% 9.69M 10s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19450K .......... .......... .......... .......... .......... 40% 14.0M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19500K .......... .......... .......... .......... .......... 40% 7.58M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19550K .......... .......... .......... .......... .......... 40% 9.57M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19600K .......... .......... .......... .......... .......... 41% 15.7M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19650K .......... .......... .......... .......... .......... 41% 8.82M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19700K .......... .......... .......... .......... .......... 41% 164M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19750K .......... .......... .......... .......... .......... 41% 216M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19800K .......... .......... .......... .......... .......... 41% 212M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19850K .......... .......... .......... .......... .......... 41% 12.4M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19900K .......... .......... .......... .......... .......... 41% 929K 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 19950K .......... .......... .......... .......... .......... 41% 7.53M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20000K .......... .......... .......... .......... .......... 41% 12.5M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20050K .......... .......... .......... .......... .......... 42% 9.61M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20100K .......... .......... .......... .......... .......... 42% 7.73M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20150K .......... .......... .......... .......... .......... 42% 9.61M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20200K .......... .......... .......... .......... .......... 42% 9.26M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20250K .......... .......... .......... .......... .......... 42% 8.52M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20300K .......... .......... .......... .......... .......... 42% 209M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20350K .......... .......... .......... .......... .......... 42% 190M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20400K .......... .......... .......... .......... .......... 42% 2.60M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20450K .......... .......... .......... .......... .......... 42% 4.95M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20500K .......... .......... .......... .......... .......... 42% 195M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20550K .......... .......... .......... .......... .......... 43% 2.48M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20600K .......... .......... .......... .......... .......... 43% 149M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20650K .......... .......... .......... .......... .......... 43% 4.86M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20700K .......... .......... .......... .......... .......... 43% 7.16M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20750K .......... .......... .......... .......... .......... 43% 8.73M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20800K .......... .......... .......... .......... .......... 43% 192M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20850K .......... .......... .......... .......... .......... 43% 157M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20900K .......... .......... .......... .......... .......... 43% 2.56M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 20950K .......... .......... .......... .......... .......... 43% 6.73M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21000K .......... .......... .......... .......... .......... 43% 5.96M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21050K .......... .......... .......... .......... .......... 44% 4.92M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21100K .......... .......... .......... .......... .......... 44% 160M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21150K .......... .......... .......... .......... .......... 44% 4.83M 9s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21200K .......... .......... .......... .......... .......... 44% 6.14M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21250K .......... .......... .......... .......... .......... 44% 27.2M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21300K .......... .......... .......... .......... .......... 44% 199M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21350K .......... .......... .......... .......... .......... 44% 194M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21400K .......... .......... .......... .......... .......... 44% 217M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21450K .......... .......... .......... .......... .......... 44% 1.98M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21500K .......... .......... .......... .......... .......... 45% 14.5M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21550K .......... .......... .......... .......... .......... 45% 7.50M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21600K .......... .......... .......... .......... .......... 45% 14.4M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21650K .......... .......... .......... .......... .......... 45% 8.14M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21700K .......... .......... .......... .......... .......... 45% 7.26M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21750K .......... .......... .......... .......... .......... 45% 114M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21800K .......... .......... .......... .......... .......... 45% 119M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21850K .......... .......... .......... .......... .......... 45% 136M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21900K .......... .......... .......... .......... .......... 45% 141M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 21950K .......... .......... .......... .......... .......... 45% 134M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22000K .......... .......... .......... .......... .......... 46% 10.7M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22050K .......... .......... .......... .......... .......... 46% 7.01M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22100K .......... .......... .......... .......... .......... 46% 7.51M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22150K .......... .......... .......... .......... .......... 46% 7.44M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22200K .......... .......... .......... .......... .......... 46% 7.56M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22250K .......... .......... .......... .......... .......... 46% 7.55M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22300K .......... .......... .......... .......... .......... 46% 6.91M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22350K .......... .......... .......... .......... .......... 46% 7.51M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22400K .......... .......... .......... .......... .......... 46% 7.72M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22450K .......... .......... .......... .......... .......... 47% 7.67M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22500K .......... .......... .......... .......... .......... 47% 7.09M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22550K .......... .......... .......... .......... .......... 47% 7.06M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22600K .......... .......... .......... .......... .......... 47% 7.38M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22650K .......... .......... .......... .......... .......... 47% 7.53M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22700K .......... .......... .......... .......... .......... 47% 7.46M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22750K .......... .......... .......... .......... .......... 47% 7.33M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22800K .......... .......... .......... .......... .......... 47% 7.56M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22850K .......... .......... .......... .......... .......... 47% 7.52M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22900K .......... .......... .......... .......... .......... 47% 7.53M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 22950K .......... .......... .......... .......... .......... 48% 7.09M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 23000K .......... .......... .......... .......... .......... 48% 7.24M 8s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 23050K .......... .......... .......... .......... .......... 48% 6.81M 7s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 23100K .......... .......... .......... .......... .......... 48% 7.48M 7s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 23150K .......... .......... .......... .......... .......... 48% 7.65M 7s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 23200K .......... .......... .......... .......... .......... 48% 7.44M 7s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 23250K .......... .......... .......... .......... .......... 48% 7.42M 7s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 23300K .......... .......... .......... .......... .......... 48% 7.09M 7s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 23350K .......... .......... .......... .......... .......... 48% 7.22M 7s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 23400K .......... .......... .......... .......... .......... 49% 7.40M 7s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 23450K .......... .......... .......... .......... .......... 49% 6.71M 7s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 23500K .......... .......... .......... .......... .......... 49% 7.43M 7s Nov 16 13:55:41 endless eos-chrome-plugin-update[1913]: 23550K .......... .......... .......... .......... .......... 49% 8.03M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 23600K .......... .......... .......... .......... .......... 49% 6.66M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 23650K .......... .......... .......... .......... .......... 49% 7.10M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 23700K .......... .......... .......... .......... .......... 49% 9.20M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 23750K .......... .......... .......... .......... .......... 49% 7.41M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 23800K .......... .......... .......... .......... .......... 49% 5.99M 7s Nov 16 13:55:42 endless accounts-daemon[594]: request by system-bus-name::1.58 [/usr/lib/gnome-initial-setup/gnome-initial-setup-exec pid:917 uid:110]: create user 'shared' Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 23850K .......... .......... .......... .......... .......... 49% 1.11M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 23900K .......... .......... .......... .......... .......... 50% 26.3M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 23950K .......... .......... .......... .......... .......... 50% 156M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24000K .......... .......... .......... .......... .......... 50% 221M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24050K .......... .......... .......... .......... .......... 50% 188M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24100K .......... .......... .......... .......... .......... 50% 213M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24150K .......... .......... .......... .......... .......... 50% 130M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24200K .......... .......... .......... .......... .......... 50% 9.31M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24250K .......... .......... .......... .......... .......... 50% 6.92M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24300K .......... .......... .......... .......... .......... 50% 9.73M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24350K .......... .......... .......... .......... .......... 50% 7.25M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24400K .......... .......... .......... .......... .......... 51% 7.32M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24450K .......... .......... .......... .......... .......... 51% 7.21M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24500K .......... .......... .......... .......... .......... 51% 7.41M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24550K .......... .......... .......... .......... .......... 51% 6.18M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24600K .......... .......... .......... .......... .......... 51% 7.20M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24650K .......... .......... .......... .......... .......... 51% 9.61M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24700K .......... .......... .......... .......... .......... 51% 6.93M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24750K .......... .......... .......... .......... .......... 51% 7.09M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24800K .......... .......... .......... .......... .......... 51% 7.11M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24850K .......... .......... .......... .......... .......... 52% 7.04M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24900K .......... .......... .......... .......... .......... 52% 7.56M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 24950K .......... .......... .......... .......... .......... 52% 7.31M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25000K .......... .......... .......... .......... .......... 52% 7.26M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25050K .......... .......... .......... .......... .......... 52% 7.57M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25100K .......... .......... .......... .......... .......... 52% 7.35M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25150K .......... .......... .......... .......... .......... 52% 7.64M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25200K .......... .......... .......... .......... .......... 52% 7.06M 7s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25250K .......... .......... .......... .......... .......... 52% 7.19M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25300K .......... .......... .......... .......... .......... 52% 7.37M 6s Nov 16 13:55:42 endless groupadd[2103]: group added to /etc/group: name=shared, GID=1000 Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25350K .......... .......... .......... .......... .......... 53% 7.26M 6s Nov 16 13:55:42 endless groupadd[2103]: group added to /etc/gshadow: name=shared Nov 16 13:55:42 endless groupadd[2103]: new group: name=shared, GID=1000 Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25400K .......... .......... .......... .......... .......... 53% 7.05M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25450K .......... .......... .......... .......... .......... 53% 7.26M 6s Nov 16 13:55:42 endless useradd[2107]: new user: name=shared, UID=1000, GID=1000, home=/sysroot/home/shared, shell=/bin/bash Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25500K .......... .......... .......... .......... .......... 53% 7.31M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25550K .......... .......... .......... .......... .......... 53% 7.51M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25600K .......... .......... .......... .......... .......... 53% 7.28M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25650K .......... .......... .......... .......... .......... 53% 8.73M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25700K .......... .......... .......... .......... .......... 53% 7.40M 6s Nov 16 13:55:42 endless systemd[1]: Started Send system activation/daily ping messages to Endless. Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25750K .......... .......... .......... .......... .......... 53% 5.21M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25800K .......... .......... .......... .......... .......... 54% 12.5M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25850K .......... .......... .......... .......... .......... 54% 7.61M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25900K .......... .......... .......... .......... .......... 54% 6.68M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 25950K .......... .......... .......... .......... .......... 54% 7.45M 6s Nov 16 13:55:42 endless chfn[2114]: changed user 'shared' information Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26000K .......... .......... .......... .......... .......... 54% 7.27M 6s Nov 16 13:55:42 endless accounts-daemon[594]: request by system-bus-name::1.58 [/usr/lib/gnome-initial-setup/gnome-initial-setup-exec pid:917 uid:110]: change password mode of user 'shared' (1000) to 2 Nov 16 13:55:42 endless passwd[2118]: password for 'shared' changed by 'root' Nov 16 13:55:42 endless accounts-daemon[594]: passwd: password expiry information changed. Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26050K .......... .......... .......... .......... .......... 54% 1.09M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26100K .......... .......... .......... .......... .......... 54% 14.9M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26150K .......... .......... .......... .......... .......... 54% 14.5M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26200K .......... .......... .......... .......... .......... 54% 129M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26250K .......... .......... .......... .......... .......... 54% 122M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26300K .......... .......... .......... .......... .......... 55% 138M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26350K .......... .......... .......... .......... .......... 55% 136M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26400K .......... .......... .......... .......... .......... 55% 54.9M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26450K .......... .......... .......... .......... .......... 55% 8.09M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26500K .......... .......... .......... .......... .......... 55% 7.25M 6s Nov 16 13:55:42 endless accounts-daemon[594]: request by system-bus-name::1.58 [/usr/lib/gnome-initial-setup/gnome-initial-setup-exec pid:917 uid:110]: create user 'jeremy' Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26550K .......... .......... .......... .......... .......... 55% 6.77M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26600K .......... .......... .......... .......... .......... 55% 7.97M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26650K .......... .......... .......... .......... .......... 55% 6.65M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26700K .......... .......... .......... .......... .......... 55% 8.54M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26750K .......... .......... .......... .......... .......... 56% 7.32M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26800K .......... .......... .......... .......... .......... 56% 6.94M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26850K .......... .......... .......... .......... .......... 56% 7.39M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26900K .......... .......... .......... .......... .......... 56% 6.61M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 26950K .......... .......... .......... .......... .......... 56% 8.04M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27000K .......... .......... .......... .......... .......... 56% 8.68M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27050K .......... .......... .......... .......... .......... 56% 7.01M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27100K .......... .......... .......... .......... .......... 56% 7.70M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27150K .......... .......... .......... .......... .......... 56% 7.36M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27200K .......... .......... .......... .......... .......... 56% 7.45M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27250K .......... .......... .......... .......... .......... 57% 7.33M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27300K .......... .......... .......... .......... .......... 57% 5.96M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27350K .......... .......... .......... .......... .......... 57% 7.72M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27400K .......... .......... .......... .......... .......... 57% 7.44M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27450K .......... .......... .......... .......... .......... 57% 7.45M 6s Nov 16 13:55:42 endless groupadd[2125]: group added to /etc/group: name=jeremy, GID=1001 Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27500K .......... .......... .......... .......... .......... 57% 6.82M 6s Nov 16 13:55:42 endless groupadd[2125]: group added to /etc/gshadow: name=jeremy Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27550K .......... .......... .......... .......... .......... 57% 8.44M 6s Nov 16 13:55:42 endless groupadd[2125]: new group: name=jeremy, GID=1001 Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27600K .......... .......... .......... .......... .......... 57% 7.08M 6s Nov 16 13:55:42 endless useradd[2129]: new user: name=jeremy, UID=1001, GID=1001, home=/sysroot/home/jeremy, shell=/bin/bash Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27650K .......... .......... .......... .......... .......... 57% 7.06M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27700K .......... .......... .......... .......... .......... 58% 7.87M 6s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27750K .......... .......... .......... .......... .......... 58% 7.26M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27800K .......... .......... .......... .......... .......... 58% 7.55M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27850K .......... .......... .......... .......... .......... 58% 7.08M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27900K .......... .......... .......... .......... .......... 58% 7.21M 5s Nov 16 13:55:42 endless systemd[1]: Started Send system activation/daily ping messages to Endless. Nov 16 13:55:42 endless systemd[1]: Started Send system activation/daily ping messages to Endless. Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 27950K .......... .......... .......... .......... .......... 58% 6.26M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28000K .......... .......... .......... .......... .......... 58% 8.73M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28050K .......... .......... .......... .......... .......... 58% 7.37M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28100K .......... .......... .......... .......... .......... 58% 7.03M 5s Nov 16 13:55:42 endless chfn[2136]: changed user 'jeremy' information Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28150K .......... .......... .......... .......... .......... 58% 1.04M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28200K .......... .......... .......... .......... .......... 59% 13.6M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28250K .......... .......... .......... .......... .......... 59% 10.2M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28300K .......... .......... .......... .......... .......... 59% 8.80M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28350K .......... .......... .......... .......... .......... 59% 9.46M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28400K .......... .......... .......... .......... .......... 59% 120M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28450K .......... .......... .......... .......... .......... 59% 129M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28500K .......... .......... .......... .......... .......... 59% 128M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28550K .......... .......... .......... .......... .......... 59% 92.7M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28600K .......... .......... .......... .......... .......... 59% 126M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28650K .......... .......... .......... .......... .......... 59% 10.2M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28700K .......... .......... .......... .......... .......... 60% 7.40M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28750K .......... .......... .......... .......... .......... 60% 7.43M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28800K .......... .......... .......... .......... .......... 60% 7.11M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28850K .......... .......... .......... .......... .......... 60% 7.28M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28900K .......... .......... .......... .......... .......... 60% 6.89M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 28950K .......... .......... .......... .......... .......... 60% 8.13M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29000K .......... .......... .......... .......... .......... 60% 6.84M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29050K .......... .......... .......... .......... .......... 60% 9.02M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29100K .......... .......... .......... .......... .......... 60% 7.31M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29150K .......... .......... .......... .......... .......... 61% 7.35M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29200K .......... .......... .......... .......... .......... 61% 7.05M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29250K .......... .......... .......... .......... .......... 61% 7.13M 5s Nov 16 13:55:42 endless accounts-daemon[594]: Adding user `jeremy' to group `sudo' ... Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29300K .......... .......... .......... .......... .......... 61% 7.54M 5s Nov 16 13:55:42 endless accounts-daemon[594]: Adding user jeremy to group sudo Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29350K .......... .......... .......... .......... .......... 61% 7.38M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29400K .......... .......... .......... .......... .......... 61% 7.66M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29450K .......... .......... .......... .......... .......... 61% 7.40M 5s Nov 16 13:55:42 endless gpasswd[2142]: user jeremy added by root to group sudo Nov 16 13:55:42 endless accounts-daemon[594]: Done. Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29500K .......... .......... .......... .......... .......... 61% 7.34M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29550K .......... .......... .......... .......... .......... 61% 6.83M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29600K .......... .......... .......... .......... .......... 61% 7.63M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29650K .......... .......... .......... .......... .......... 62% 6.76M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29700K .......... .......... .......... .......... .......... 62% 7.17M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29750K .......... .......... .......... .......... .......... 62% 7.12M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29800K .......... .......... .......... .......... .......... 62% 7.29M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29850K .......... .......... .......... .......... .......... 62% 7.59M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29900K .......... .......... .......... .......... .......... 62% 7.15M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 29950K .......... .......... .......... .......... .......... 62% 8.87M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30000K .......... .......... .......... .......... .......... 62% 6.30M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30050K .......... .......... .......... .......... .......... 62% 7.21M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30100K .......... .......... .......... .......... .......... 63% 9.19M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30150K .......... .......... .......... .......... .......... 63% 7.23M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30200K .......... .......... .......... .......... .......... 63% 7.31M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30250K .......... .......... .......... .......... .......... 63% 7.27M 5s Nov 16 13:55:42 endless accounts-daemon[594]: Adding user `jeremy' to group `adm' ... Nov 16 13:55:42 endless accounts-daemon[594]: Adding user jeremy to group adm Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30300K .......... .......... .......... .......... .......... 63% 1010K 5s Nov 16 13:55:42 endless gpasswd[2147]: user jeremy added by root to group adm Nov 16 13:55:42 endless accounts-daemon[594]: Done. Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30350K .......... .......... .......... .......... .......... 63% 9.49M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30400K .......... .......... .......... .......... .......... 63% 16.4M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30450K .......... .......... .......... .......... .......... 63% 12.5M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30500K .......... .......... .......... .......... .......... 63% 7.19M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30550K .......... .......... .......... .......... .......... 63% 9.89M 5s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30600K .......... .......... .......... .......... .......... 64% 21.8M 4s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30650K .......... .......... .......... .......... .......... 64% 155M 4s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30700K .......... .......... .......... .......... .......... 64% 122M 4s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30750K .......... .......... .......... .......... .......... 64% 131M 4s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30800K .......... .......... .......... .......... .......... 64% 110M 4s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30850K .......... .......... .......... .......... .......... 64% 16.4M 4s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30900K .......... .......... .......... .......... .......... 64% 7.16M 4s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 30950K .......... .......... .......... .......... .......... 64% 7.55M 4s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 31000K .......... .......... .......... .......... .......... 64% 7.37M 4s Nov 16 13:55:42 endless eos-chrome-plugin-update[1913]: 31050K .......... .......... .......... .......... .......... 65% 7.07M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31100K .......... .......... .......... .......... .......... 65% 7.31M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31150K .......... .......... .......... .......... .......... 65% 6.79M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31200K .......... .......... .......... .......... .......... 65% 7.58M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31250K .......... .......... .......... .......... .......... 65% 7.58M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31300K .......... .......... .......... .......... .......... 65% 7.11M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31350K .......... .......... .......... .......... .......... 65% 7.24M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31400K .......... .......... .......... .......... .......... 65% 7.74M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31450K .......... .......... .......... .......... .......... 65% 8.14M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31500K .......... .......... .......... .......... .......... 65% 7.29M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31550K .......... .......... .......... .......... .......... 66% 7.22M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31600K .......... .......... .......... .......... .......... 66% 5.84M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31650K .......... .......... .......... .......... .......... 66% 10.1M 4s Nov 16 13:55:43 endless accounts-daemon[594]: Adding user `jeremy' to group `dialout' ... Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31700K .......... .......... .......... .......... .......... 66% 4.58M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31750K .......... .......... .......... .......... .......... 66% 16.4M 4s Nov 16 13:55:43 endless accounts-daemon[594]: gpasswd: group 'dialout' does not exist in /etc/group Nov 16 13:55:43 endless accounts-daemon[594]: adduser: `/bin/gpasswd -a jeremy dialout' returned error code 3. Exiting. Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31800K .......... .......... .......... .......... .......... 66% 7.40M 4s Nov 16 13:55:43 endless accounts-daemon[594]: failed to add user jeremy to group dialout Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31850K .......... .......... .......... .......... .......... 66% 7.70M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31900K .......... .......... .......... .......... .......... 66% 6.80M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 31950K .......... .......... .......... .......... .......... 66% 7.07M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32000K .......... .......... .......... .......... .......... 66% 7.71M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32050K .......... .......... .......... .......... .......... 67% 7.39M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32100K .......... .......... .......... .......... .......... 67% 7.75M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32150K .......... .......... .......... .......... .......... 67% 6.98M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32200K .......... .......... .......... .......... .......... 67% 7.20M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32250K .......... .......... .......... .......... .......... 67% 7.62M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32300K .......... .......... .......... .......... .......... 67% 7.21M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32350K .......... .......... .......... .......... .......... 67% 7.18M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32400K .......... .......... .......... .......... .......... 67% 6.78M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32450K .......... .......... .......... .......... .......... 67% 8.93M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32500K .......... .......... .......... .......... .......... 68% 6.27M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32550K .......... .......... .......... .......... .......... 68% 7.52M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32600K .......... .......... .......... .......... .......... 68% 7.59M 4s Nov 16 13:55:43 endless accounts-daemon[594]: Adding user `jeremy' to group `lpadmin' ... Nov 16 13:55:43 endless accounts-daemon[594]: Adding user jeremy to group lpadmin Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32650K .......... .......... .......... .......... .......... 68% 1.07M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32700K .......... .......... .......... .......... .......... 68% 10.5M 4s Nov 16 13:55:43 endless gpasswd[2156]: user jeremy added by root to group lpadmin Nov 16 13:55:43 endless accounts-daemon[594]: Done. Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32750K .......... .......... .......... .......... .......... 68% 13.9M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32800K .......... .......... .......... .......... .......... 68% 131M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32850K .......... .......... .......... .......... .......... 68% 121M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32900K .......... .......... .......... .......... .......... 68% 143M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 32950K .......... .......... .......... .......... .......... 68% 146M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33000K .......... .......... .......... .......... .......... 69% 115M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33050K .......... .......... .......... .......... .......... 69% 11.0M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33100K .......... .......... .......... .......... .......... 69% 7.38M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33150K .......... .......... .......... .......... .......... 69% 7.31M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33200K .......... .......... .......... .......... .......... 69% 7.19M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33250K .......... .......... .......... .......... .......... 69% 7.45M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33300K .......... .......... .......... .......... .......... 69% 8.74M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33350K .......... .......... .......... .......... .......... 69% 7.19M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33400K .......... .......... .......... .......... .......... 69% 7.24M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33450K .......... .......... .......... .......... .......... 70% 5.24M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33500K .......... .......... .......... .......... .......... 70% 11.1M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33550K .......... .......... .......... .......... .......... 70% 7.32M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33600K .......... .......... .......... .......... .......... 70% 7.40M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33650K .......... .......... .......... .......... .......... 70% 7.06M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33700K .......... .......... .......... .......... .......... 70% 7.04M 4s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33750K .......... .......... .......... .......... .......... 70% 7.55M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33800K .......... .......... .......... .......... .......... 70% 8.63M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33850K .......... .......... .......... .......... .......... 70% 6.21M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33900K .......... .......... .......... .......... .......... 70% 8.67M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 33950K .......... .......... .......... .......... .......... 71% 7.19M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34000K .......... .......... .......... .......... .......... 71% 7.39M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34050K .......... .......... .......... .......... .......... 71% 7.36M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34100K .......... .......... .......... .......... .......... 71% 7.39M 3s Nov 16 13:55:43 endless accounts-daemon[594]: adduser: The group `sambashare' does not exist. Nov 16 13:55:43 endless accounts-daemon[594]: failed to add user jeremy to group sambashare Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34150K .......... .......... .......... .......... .......... 71% 7.28M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34200K .......... .......... .......... .......... .......... 71% 7.19M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34250K .......... .......... .......... .......... .......... 71% 7.00M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34300K .......... .......... .......... .......... .......... 71% 7.96M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34350K .......... .......... .......... .......... .......... 71% 7.29M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34400K .......... .......... .......... .......... .......... 72% 7.18M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34450K .......... .......... .......... .......... .......... 72% 7.26M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34500K .......... .......... .......... .......... .......... 72% 7.57M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34550K .......... .......... .......... .......... .......... 72% 7.17M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34600K .......... .......... .......... .......... .......... 72% 7.72M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34650K .......... .......... .......... .......... .......... 72% 7.31M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34700K .......... .......... .......... .......... .......... 72% 7.22M 3s Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Activation needed. Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Getting variable: dualboot Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Getting variable: cmdline Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__: - Cmdline: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-a7d4a286f29b21cc342a066d74a68b894ded66e4fcd88e20fcd025bad1c49609/vmlinuz-4.13.0-12-generic root=UUID=a2833eed-cc31-409c-b18d-e8a3571c0c55 rw splash plymouth.ignore-serial-consoles quiet ostree=/ostree/boot.1/eos/a7d4a286f29b21cc342a066d74a68b894ded66e4fcd88e20fcd025bad1c49609/0 Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Getting variable: live Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Getting variable: image Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__: - Image from /sysroot: eos-eos3.3-amd64-amd64.171026-021926.en Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Getting variable: release Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__: - Found version key Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__: - Release: 3.3.1 Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Getting variable: vendor Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__: - Found vendor: Acer Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Getting variable: product Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__: - Found product: TMP645-MG Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Getting variable: serial Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__: - Found serial: NXV8SAA001410099123400 Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Request data: {'live': False, 'release': '3.3.1', 'dualboot': False, 'product': 'TMP645-MG', 'vendor': 'Acer', 'serial': 'NXV8SAA001410099123400', 'image': 'eos-eos3.3-amd64-amd64.171026-021926.en'} Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Sending to server (https://home.endlessm.com/v1/activate)... Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34750K .......... .......... .......... .......... .......... 72% 1.01M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34800K .......... .......... .......... .......... .......... 72% 10.1M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34850K .......... .......... .......... .......... .......... 72% 8.97M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34900K .......... .......... .......... .......... .......... 73% 31.1M 3s Nov 16 13:55:43 endless accounts-daemon[594]: Adding user `jeremy' to group `systemd-journal' ... Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 34950K .......... .......... .......... .......... .......... 73% 7.50M 3s Nov 16 13:55:43 endless accounts-daemon[594]: Adding user jeremy to group systemd-journal Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35000K .......... .......... .......... .......... .......... 73% 13.2M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35050K .......... .......... .......... .......... .......... 73% 127M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35100K .......... .......... .......... .......... .......... 73% 102M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35150K .......... .......... .......... .......... .......... 73% 136M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35200K .......... .......... .......... .......... .......... 73% 127M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35250K .......... .......... .......... .......... .......... 73% 29.4M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35300K .......... .......... .......... .......... .......... 73% 7.01M 3s Nov 16 13:55:43 endless gpasswd[2167]: user jeremy added by root to group systemd-journal Nov 16 13:55:43 endless accounts-daemon[594]: Done. Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35350K .......... .......... .......... .......... .......... 73% 7.42M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35400K .......... .......... .......... .......... .......... 74% 7.46M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35450K .......... .......... .......... .......... .......... 74% 7.49M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35500K .......... .......... .......... .......... .......... 74% 6.91M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35550K .......... .......... .......... .......... .......... 74% 8.04M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35600K .......... .......... .......... .......... .......... 74% 7.25M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35650K .......... .......... .......... .......... .......... 74% 7.15M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35700K .......... .......... .......... .......... .......... 74% 7.66M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35750K .......... .......... .......... .......... .......... 74% 6.99M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35800K .......... .......... .......... .......... .......... 74% 7.50M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35850K .......... .......... .......... .......... .......... 75% 7.15M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35900K .......... .......... .......... .......... .......... 75% 8.88M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 35950K .......... .......... .......... .......... .......... 75% 5.81M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36000K .......... .......... .......... .......... .......... 75% 10.3M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36050K .......... .......... .......... .......... .......... 75% 5.78M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36100K .......... .......... .......... .......... .......... 75% 9.25M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36150K .......... .......... .......... .......... .......... 75% 7.31M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36200K .......... .......... .......... .......... .......... 75% 7.10M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36250K .......... .......... .......... .......... .......... 75% 7.81M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36300K .......... .......... .......... .......... .......... 75% 7.18M 3s Nov 16 13:55:43 endless accounts-daemon[594]: Adding user `jeremy' to group `tty' ... Nov 16 13:55:43 endless accounts-daemon[594]: gpasswd: group 'tty' does not exist in /etc/group Nov 16 13:55:43 endless accounts-daemon[594]: adduser: `/bin/gpasswd -a jeremy tty' returned error code 3. Exiting. Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36350K .......... .......... .......... .......... .......... 76% 6.69M 3s Nov 16 13:55:43 endless accounts-daemon[594]: failed to add user jeremy to group tty Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36400K .......... .......... .......... .......... .......... 76% 7.40M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36450K .......... .......... .......... .......... .......... 76% 7.32M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36500K .......... .......... .......... .......... .......... 76% 6.93M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36550K .......... .......... .......... .......... .......... 76% 9.08M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36600K .......... .......... .......... .......... .......... 76% 6.87M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36650K .......... .......... .......... .......... .......... 76% 7.38M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36700K .......... .......... .......... .......... .......... 76% 7.57M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36750K .......... .......... .......... .......... .......... 76% 6.86M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36800K .......... .......... .......... .......... .......... 77% 7.42M 3s Nov 16 13:55:43 endless accounts-daemon[594]: request by system-bus-name::1.58 [/usr/lib/gnome-initial-setup/gnome-initial-setup-exec pid:917 uid:110]: change password mode of user 'jeremy' (1001) to 2 Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36850K .......... .......... .......... .......... .......... 77% 7.30M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36900K .......... .......... .......... .......... .......... 77% 6.99M 3s Nov 16 13:55:43 endless passwd[2173]: password for 'jeremy' changed by 'root' Nov 16 13:55:43 endless accounts-daemon[594]: passwd: password expiry information changed. Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 36950K .......... .......... .......... .......... .......... 77% 7.12M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37000K .......... .......... .......... .......... .......... 77% 9.21M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37050K .......... .......... .......... .......... .......... 77% 1.10M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37100K .......... .......... .......... .......... .......... 77% 9.12M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37150K .......... .......... .......... .......... .......... 77% 9.47M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37200K .......... .......... .......... .......... .......... 77% 24.4M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37250K .......... .......... .......... .......... .......... 77% 117M 3s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37300K .......... .......... .......... .......... .......... 78% 133M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37350K .......... .......... .......... .......... .......... 78% 144M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37400K .......... .......... .......... .......... .......... 78% 135M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37450K .......... .......... .......... .......... .......... 78% 28.7M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37500K .......... .......... .......... .......... .......... 78% 7.58M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37550K .......... .......... .......... .......... .......... 78% 6.96M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37600K .......... .......... .......... .......... .......... 78% 7.51M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37650K .......... .......... .......... .......... .......... 78% 7.32M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37700K .......... .......... .......... .......... .......... 78% 6.11M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37750K .......... .......... .......... .......... .......... 79% 7.44M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37800K .......... .......... .......... .......... .......... 79% 7.14M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37850K .......... .......... .......... .......... .......... 79% 7.17M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37900K .......... .......... .......... .......... .......... 79% 9.52M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 37950K .......... .......... .......... .......... .......... 79% 7.46M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 38000K .......... .......... .......... .......... .......... 79% 7.21M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 38050K .......... .......... .......... .......... .......... 79% 6.37M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 38100K .......... .......... .......... .......... .......... 79% 6.84M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 38150K .......... .......... .......... .......... .......... 79% 8.33M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 38200K .......... .......... .......... .......... .......... 79% 7.88M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 38250K .......... .......... .......... .......... .......... 80% 7.09M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 38300K .......... .......... .......... .......... .......... 80% 7.29M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 38350K .......... .......... .......... .......... .......... 80% 7.07M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 38400K .......... .......... .......... .......... .......... 80% 7.08M 2s Nov 16 13:55:43 endless eos-chrome-plugin-update[1913]: 38450K .......... .......... .......... .......... .......... 80% 6.55M 2s Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Response: {'success': True} Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Server returned success message! Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Activated! Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:/var/lib/eos-phone-home/count doesn't exist yet Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Ping needed. Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Getting variable: count Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__: - Count: 0 Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Getting variable: metrics_enabled Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Getting variable: metrics Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__: - Metrics enabled: True Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Getting variable: metrics_environment Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__: - Metrics environment: production Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Request data: {'metrics_environment': 'production', 'image': 'eos-eos3.3-amd64-amd64.171026-021926.en', 'release': '3.3.1', 'dualboot': False, 'count': 0, 'vendor': 'Acer', 'metrics_enabled': True, 'product': 'TMP645-MG'} Nov 16 13:55:43 endless eos-phone-home[2137]: INFO:__main__:Sending to server (https://home.endlessm.com/v1/ping)... Nov 16 13:55:44 endless eos-phone-home[2137]: INFO:__main__:Response: {'success': True} Nov 16 13:55:44 endless eos-phone-home[2137]: INFO:__main__:Server returned success message! Nov 16 13:55:44 endless eos-phone-home[2137]: INFO:__main__: - Updated count: 1 Nov 16 13:55:44 endless eos-phone-home[2137]: INFO:__main__:Pinged! Nov 16 21:55:41 endless systemd[1]: Time has been changed Nov 16 21:55:41 endless systemd[1]: apt-daily.timer: Adding 6h 56min 47.748314s random time. Nov 16 21:55:41 endless systemd[1]: apt-daily-upgrade.timer: Adding 54min 31.834366s random time. Nov 16 21:55:41 endless systemd[729]: Time has been changed Nov 16 21:55:41 endless systemd[1]: eos-autoupdater.timer: Adding 1min 43.049243s random time. Nov 16 21:55:41 endless systemd[1]: Received SIGRTMIN+21 from PID 185 (plymouthd). Nov 16 21:55:41 endless systemd[1]: Started Hold until boot process finishes up. Nov 16 21:55:41 endless systemd[1]: Reached target Multi-User System. Nov 16 21:55:41 endless systemd[1]: Reached target Graphical Interface. Nov 16 21:55:41 endless systemd[1]: Starting Update UTMP about System Runlevel Changes... Nov 16 21:55:41 endless systemd[1]: Started Stop Read-Ahead Data Collection 10s After Completed Startup. Nov 16 21:55:41 endless systemd[1]: Started Update UTMP about System Runlevel Changes. Nov 16 21:55:41 endless systemd[1]: Startup finished in 3.442s (kernel) + 9.082s (initrd) + 1min 39.254s (userspace) = 1min 51.778s. Nov 16 21:55:41 endless dbus[578]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' Nov 16 21:55:41 endless systemd[1]: Starting Fingerprint Authentication Daemon... Nov 16 21:55:41 endless dbus[578]: [system] Successfully activated service 'net.reactivated.Fprint' Nov 16 21:55:41 endless systemd[1]: Started Fingerprint Authentication Daemon. Nov 16 21:55:41 endless fprintd[2200]: Launching FprintObject Nov 16 21:55:41 endless fprintd[2200]: D-Bus service launched with name: net.reactivated.Fprint Nov 16 21:55:41 endless fprintd[2200]: entering main loop Nov 16 21:55:41 endless gdm-password][2192]: gkr-pam: no password is available for user Nov 16 21:55:41 endless gdm-password][2192]: pam_unix(gdm-password:session): session opened for user jeremy by (uid=0) Nov 16 21:55:41 endless systemd[1]: Created slice User Slice of jeremy. Nov 16 21:55:41 endless systemd[1]: Starting User Manager for UID 1001... Nov 16 21:55:41 endless systemd[2202]: pam_unix(systemd-user:session): session opened for user jeremy by (uid=0) Nov 16 21:55:41 endless systemd[1]: Started Session 2 of user jeremy. Nov 16 21:55:41 endless systemd-logind[602]: New session 2 of user jeremy. Nov 16 21:55:42 endless systemd[2202]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Nov 16 21:55:42 endless systemd[2202]: Listening on GnuPG cryptographic agent (access for web browsers). Nov 16 21:55:42 endless systemd[2202]: Reached target Paths. Nov 16 21:55:42 endless systemd[2202]: Starting D-Bus User Message Bus Socket. Nov 16 21:55:42 endless systemd[2202]: Listening on GnuPG network certificate management daemon. Nov 16 21:55:42 endless systemd[2202]: Listening on GnuPG cryptographic agent and passphrase cache. Nov 16 21:55:42 endless systemd[2202]: Reached target Timers. Nov 16 21:55:42 endless systemd[2202]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Nov 16 21:55:42 endless systemd[2202]: Listening on D-Bus User Message Bus Socket. Nov 16 21:55:42 endless systemd[2202]: Reached target Sockets. Nov 16 21:55:42 endless systemd[2202]: Reached target Basic System. Nov 16 21:55:42 endless systemd[2202]: Reached target Default. Nov 16 21:55:42 endless systemd[2202]: Startup finished in 86ms. Nov 16 21:55:42 endless systemd[1]: Started User Manager for UID 1001. Nov 16 21:55:42 endless gnome-session[734]: gnome-session-binary[734]: WARNING: Application 'org.gnome.SettingsDaemon.A11ySettings.desktop' killed by signal 15 Nov 16 21:55:42 endless gnome-session-binary[734]: WARNING: Application 'org.gnome.SettingsDaemon.A11ySettings.desktop' killed by signal 15 Nov 16 21:55:42 endless gnome-session[734]: gnome-session-binary[734]: WARNING: Application 'org.gnome.SettingsDaemon.Housekeeping.desktop' killed by signal 15 Nov 16 21:55:42 endless gnome-session-binary[734]: WARNING: Application 'org.gnome.SettingsDaemon.Housekeeping.desktop' killed by signal 15 Nov 16 21:55:42 endless gnome-session[734]: gnome-session-binary[734]: WARNING: Application 'org.gnome.SettingsDaemon.Sound.desktop' killed by signal 15 Nov 16 21:55:42 endless gnome-session-binary[734]: WARNING: Application 'org.gnome.SettingsDaemon.Sound.desktop' killed by signal 15 Nov 16 21:55:42 endless colord[897]: device removed: xrandr-AU Optronics Nov 16 21:55:42 endless colord[897]: Profile removed: icc-8b62e4767fa11382d7330756c7d7f152 Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: /etc/gdm3/Xsession: Beginning session setup... Nov 16 21:55:42 endless systemd[2202]: Started D-Bus User Message Bus. Nov 16 21:55:42 endless gnome-shell[765]: JS ERROR: TypeError: target is null _getTweenState@resource:///org/gnome/shell/ui/tweener.js:67:9 _wrapTweening@resource:///org/gnome/shell/ui/tweener.js:44:17 addTween@resource:///org/gnome/shell/ui/tweener.js:39:5 LayoutManager<.prepareForOverview@resource:///org/gnome/shell/ui/layout.js:332:1 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:22 WorkspaceMonitor<._windowDisappearing@resource:///org/gnome/shell/ui/workspaceMonitor.js:54:13 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:22 Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting DISPLAY=:0 Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting XAUTHORITY=/var/run/gdm3/auth-for-jeremy-3bOtsB/database Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: localuser:jeremy being added to access control list Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: Creating new directory DESKTOP for . Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: Creating new directory DOCUMENTS for Documents Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: Creating new directory DOWNLOAD for Downloads Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: Creating new directory MUSIC for Music Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: Creating new directory PICTURES for Pictures Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: Creating new directory VIDEOS for Videos Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: I: Script for ibus started at run_im. Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: I: Script for auto started at run_im. Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: I: Script for default started at run_im. Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: gpgconf: warning: can not open config file /sysroot/home/jeremy/.gnupg/gpg-agent.conf: No such file or directory Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting USER=jeremy Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting TEXTDOMAIN=im-config Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11 Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting HOME=/sysroot/home/jeremy Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting QT4_IM_MODULE=xim Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting DESKTOP_SESSION=gnome Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting IM_CONFIG_PHASE=1 Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting LOGNAME=jeremy Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting GTK_IM_MODULE=ibus Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting USERNAME=jeremy Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting GTK_OVERLAY_SCROLLING=0 Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting WINDOWPATH=1 Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1001 Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting DISPLAY=:0 Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting LANG=en_US.utf8 Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting XDG_CURRENT_DESKTOP=GNOME Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=gnome Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting XAUTHORITY=/var/run/gdm3/auth-for-jeremy-3bOtsB/database Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting XMODIFIERS=@im=ibus Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting SHELL=/bin/bash Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting GDMSESSION=gnome Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting TEXTDOMAINDIR=/usr/share/locale/ Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1001/gnupg/S.gpg-agent:0:1 Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting QT_IM_MODULE=xim Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting PWD=/sysroot/home/jeremy Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting XDG_DATA_DIRS=/sysroot/home/jeremy/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/var/endless-extra/flatpak/exports/share/:/usr/local/share/:/usr/share/ Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: dbus-update-activation-environment: setting CLUTTER_IM_MODULE=xim Nov 16 21:55:42 endless gnome-shell[765]: JS ERROR: TypeError: target is null _getTweenState@resource:///org/gnome/shell/ui/tweener.js:67:9 _wrapTweening@resource:///org/gnome/shell/ui/tweener.js:44:17 addTween@resource:///org/gnome/shell/ui/tweener.js:39:5 LayoutManager<.prepareForOverview@resource:///org/gnome/shell/ui/layout.js:332:1 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:22 WorkspaceMonitor<._windowDisappearing@resource:///org/gnome/shell/ui/workspaceMonitor.js:54:13 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:22 Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: I: Script for ibus started at run_im. Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: I: Script for auto started at run_im. Nov 16 21:55:42 endless /etc/gdm3/Xsession[2217]: I: Script for default started at run_im. Nov 16 21:55:42 endless dbus-daemon[2243]: Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' Nov 16 21:55:42 endless systemd[2202]: Starting Virtual filesystem service... Nov 16 21:55:42 endless dbus-daemon[2243]: Successfully activated service 'org.gtk.vfs.Daemon' Nov 16 21:55:42 endless systemd[2202]: Started Virtual filesystem service. Nov 16 21:55:43 endless gnome-shell[765]: instance of invalid non-instantiatable type '(null)' Nov 16 21:55:43 endless gnome-shell[765]: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Nov 16 21:55:43 endless gnome-shell[765]: ../../../../gobject/gsignal.c:2641: instance '0x3f0f1c0' has no handler with id '5571' Nov 16 21:55:43 endless gnome-shell[765]: ../../../../gobject/gsignal.c:2641: instance '0x3e20a60' has no handler with id '7054' Nov 16 21:55:43 endless gnome-shell[765]: ../../../../gobject/gsignal.c:2641: instance '0x3cd2350' has no handler with id '6261' Nov 16 21:55:43 endless gnome-shell[765]: ../../../../gobject/gsignal.c:2641: instance '0x3af0fa0' has no handler with id '6658' Nov 16 21:55:43 endless dbus-daemon[2243]: Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' Nov 16 21:55:43 endless systemd[2202]: Starting Accessibility services bus... Nov 16 21:55:43 endless dbus-daemon[2243]: Successfully activated service 'org.a11y.Bus' Nov 16 21:55:43 endless systemd[2202]: Started Accessibility services bus. Nov 16 21:55:43 endless at-spi-bus-launcher[2320]: Activating service name='org.a11y.atspi.Registry' Nov 16 21:55:43 endless at-spi-bus-launcher[2320]: Successfully activated service 'org.a11y.atspi.Registry' Nov 16 21:55:43 endless org.a11y.atspi.Registry[2325]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Nov 16 21:55:43 endless gnome-session[2217]: gnome-session-binary[2217]: WARNING: Application 'gnome-initial-setup-copy-worker.desktop' killed by signal 15 Nov 16 21:55:43 endless gnome-session-binary[2217]: WARNING: Application 'gnome-initial-setup-copy-worker.desktop' killed by signal 15 Nov 16 21:55:43 endless gnome-initial-s[2336]: Unable to move /run/gnome-initial-setup/.config/gnome-initial-setup-done to /sysroot/home/jeremy/.config/gnome-initial-setup-done: Error opening file “/sysroot/home/jeremy/.config/gnome-initial-setup-done”: File exists Nov 16 21:55:43 endless gnome-initial-s[2336]: Unable to read user password file Nov 16 21:55:43 endless gnome-keyring-ssh.desktop[2339]: SSH_AUTH_SOCK=/run/user/1001/keyring/ssh Nov 16 21:55:43 endless gnome-keyring-secrets.desktop[2340]: SSH_AUTH_SOCK=/run/user/1001/keyring/ssh Nov 16 21:55:43 endless gnome-keyring-pkcs11.desktop[2343]: SSH_AUTH_SOCK=/run/user/1001/keyring/ssh Nov 16 21:55:44 endless rtkit-daemon[775]: Successfully made thread 2358 of process 2358 (/usr/bin/pulseaudio) owned by '1001' high priority at nice level -11. Nov 16 21:55:44 endless rtkit-daemon[775]: Supervising 4 threads of 2 processes of 2 users. Nov 16 21:55:44 endless dbus-daemon[2243]: Activating service name='org.freedesktop.portal.IBus' Nov 16 21:55:44 endless dbus-daemon[2243]: Successfully activated service 'org.freedesktop.portal.IBus' Nov 16 21:55:44 endless rtkit-daemon[775]: Supervising 4 threads of 2 processes of 2 users. Nov 16 21:55:44 endless rtkit-daemon[775]: Successfully made thread 2385 of process 2358 (/usr/bin/pulseaudio) owned by '1001' RT at priority 5. Nov 16 21:55:44 endless rtkit-daemon[775]: Supervising 5 threads of 2 processes of 2 users. Nov 16 21:55:44 endless rtkit-daemon[775]: Supervising 5 threads of 2 processes of 2 users. Nov 16 21:55:44 endless rtkit-daemon[775]: Successfully made thread 2386 of process 2358 (/usr/bin/pulseaudio) owned by '1001' RT at priority 5. Nov 16 21:55:44 endless rtkit-daemon[775]: Supervising 6 threads of 2 processes of 2 users. Nov 16 21:55:44 endless pulseaudio[2358]: [pulseaudio] authkey.c: Failed to open cookie file '/sysroot/home/jeremy/.config/pulse/cookie': No such file or directory Nov 16 21:55:44 endless pulseaudio[2358]: [pulseaudio] authkey.c: Failed to load authentication key '/sysroot/home/jeremy/.config/pulse/cookie': No such file or directory Nov 16 21:55:44 endless pulseaudio[2358]: [pulseaudio] authkey.c: Failed to open cookie file '/sysroot/home/jeremy/.pulse-cookie': No such file or directory Nov 16 21:55:44 endless pulseaudio[2358]: [pulseaudio] authkey.c: Failed to load authentication key '/sysroot/home/jeremy/.pulse-cookie': No such file or directory Nov 16 21:55:44 endless bluetoothd[603]: Endpoint registered: sender=:1.324 path=/MediaEndpoint/A2DPSource Nov 16 21:55:44 endless bluetoothd[603]: Endpoint registered: sender=:1.324 path=/MediaEndpoint/A2DPSink Nov 16 21:55:44 endless bluetoothd[603]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98) Nov 16 21:55:46 endless gnome-shell[2347]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 337]: reference to undefined property global.stage Nov 16 21:55:47 endless gnome-shell[2347]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 105]: reference to undefined property global.window_group Nov 16 21:55:47 endless gnome-shell[2347]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property Meta.MonitorManager Nov 16 21:55:47 endless org.gnome.Shell.desktop[2347]: current session already has an ibus-daemon. Nov 16 21:55:48 endless gnome-shell[2347]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 34]: reference to undefined property St.GenericAccessible Nov 16 21:55:48 endless dbus-daemon[2243]: Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' Nov 16 21:55:48 endless systemd[2202]: Starting sandboxed app permission store... Nov 16 21:55:48 endless dbus-daemon[2243]: Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' Nov 16 21:55:48 endless systemd[2202]: Started sandboxed app permission store. Nov 16 21:55:48 endless dbus-daemon[2243]: Activating service name='org.gnome.Shell.CalendarServer' Nov 16 21:55:48 endless dbus-daemon[2243]: Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service' Nov 16 21:55:48 endless systemd[2202]: Starting Evolution source registry... Nov 16 21:55:48 endless dbus-daemon[2243]: Activating service name='ca.desrt.dconf' Nov 16 21:55:48 endless dbus-daemon[2243]: Successfully activated service 'ca.desrt.dconf' Nov 16 21:55:48 endless polkitd[604]: Registered Authentication Agent for unix-session:2 (system bus name :1.319 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.utf8) Nov 16 21:55:48 endless gnome-shell[2347]: Telepathy is not available, chat integration will be disabled. Nov 16 21:55:49 endless dbus-daemon[2243]: Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' Nov 16 21:55:49 endless systemd[2202]: Starting Virtual filesystem service - disk device monitor... Nov 16 21:55:49 endless dbus-daemon[2243]: Activating service name='org.gnome.OnlineAccounts' Nov 16 21:55:49 endless dbus-daemon[2243]: Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor' Nov 16 21:55:49 endless systemd[2202]: Started Virtual filesystem service - disk device monitor. Nov 16 21:55:49 endless goa-daemon[2432]: goa-daemon version 3.22.6 starting Nov 16 21:55:49 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.evolution.dataserver.Sources5' Nov 16 21:55:49 endless systemd[2202]: Started Evolution source registry. Nov 16 21:55:49 endless dbus-daemon[2243]: Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' Nov 16 21:55:49 endless systemd[2202]: Starting Virtual filesystem service - digital camera monitor... Nov 16 21:55:49 endless dbus-daemon[2243]: Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor' Nov 16 21:55:49 endless systemd[2202]: Started Virtual filesystem service - digital camera monitor. Nov 16 21:55:49 endless dbus-daemon[2243]: Activating service name='org.gnome.Identity' Nov 16 21:55:49 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.OnlineAccounts' Nov 16 21:55:49 endless dbus-daemon[2243]: Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' Nov 16 21:55:49 endless systemd[2202]: Starting Virtual filesystem service - Media Transfer Protocol monitor... Nov 16 21:55:49 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Identity' Nov 16 21:55:49 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Shell.CalendarServer' Nov 16 21:55:49 endless dbus-daemon[2243]: Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor' Nov 16 21:55:49 endless systemd[2202]: Started Virtual filesystem service - Media Transfer Protocol monitor. Nov 16 21:55:49 endless dbus-daemon[2243]: Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' Nov 16 21:55:49 endless systemd[2202]: Starting Virtual filesystem service - Apple File Conduit monitor... Nov 16 21:55:49 endless gvfs-afc-volume-monitor[2455]: Volume monitor alive Nov 16 21:55:49 endless dbus-daemon[2243]: Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor' Nov 16 21:55:49 endless systemd[2202]: Started Virtual filesystem service - Apple File Conduit monitor. Nov 16 21:55:49 endless dbus-daemon[2243]: Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' Nov 16 21:55:49 endless systemd[2202]: Starting Virtual filesystem service - GNOME Online Accounts monitor... Nov 16 21:55:49 endless dbus-daemon[2243]: Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor' Nov 16 21:55:49 endless systemd[2202]: Started Virtual filesystem service - GNOME Online Accounts monitor. Nov 16 21:55:49 endless dbus[578]: [system] Activating via systemd: service name='com.endlessm.Updater' unit='eos-updater.service' Nov 16 21:55:49 endless systemd[1]: Starting Endless OS Updater... Nov 16 21:55:49 endless eos-updater[2465]: Acquired a message bus connection Nov 16 21:55:49 endless eos-updater[2465]: Changing to state Ready Nov 16 21:55:49 endless eos-updater[2465]: Exporting objects Nov 16 21:55:49 endless dbus[578]: [system] Successfully activated service 'com.endlessm.Updater' Nov 16 21:55:49 endless systemd[1]: Started Endless OS Updater. Nov 16 21:55:49 endless eos-updater[2465]: Acquired the name com.endlessm.Updater Nov 16 21:55:50 endless gnome-shell[2347]: JS WARNING: [resource:///org/gnome/gjs/modules/tweener/tweener.js 540]: reference to undefined property properties[istr].isSpecialProperty Nov 16 21:55:50 endless gnome-shell[2347]: JS WARNING: [resource:///org/gnome/shell/ui/search.js 499]: reference to undefined property provider.isRemoteProvider Nov 16 21:55:50 endless gnome-shell[2347]: Failed to add search provider /var/lib/flatpak/exports/share/gnome-shell/search-providers/org.gnome.Gnote.ini: TypeError: appInfo is null Nov 16 21:55:50 endless gnome-shell[2347]: No permission to trigger offline updates: Polkit.Error: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is not registered Nov 16 21:55:51 endless dbus[578]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Nov 16 21:55:51 endless systemd[1]: Starting Hostname Service... Nov 16 21:55:51 endless cupsd[599]: REQUEST localhost - - "POST / HTTP/1.1" 200 362 Create-Printer-Subscriptions successful-ok Nov 16 21:55:51 endless dbus[578]: [system] Successfully activated service 'org.freedesktop.hostname1' Nov 16 21:55:51 endless systemd[1]: Started Hostname Service. Nov 16 21:55:51 endless gsd-sharing[2479]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded. Nov 16 21:55:51 endless dbus[578]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' Nov 16 21:55:51 endless systemd[1]: Starting Locale Service... Nov 16 21:55:52 endless dbus-daemon[2243]: Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' Nov 16 21:55:52 endless systemd[2202]: Starting Tracker metadata database store and lookup manager... Nov 16 21:55:52 endless dbus[578]: [system] Successfully activated service 'org.freedesktop.locale1' Nov 16 21:55:52 endless systemd[1]: Started Locale Service. Nov 16 21:55:52 endless dbus-daemon[2243]: Successfully activated service 'org.freedesktop.Tracker1' Nov 16 21:55:52 endless systemd[2202]: Started Tracker metadata database store and lookup manager. Nov 16 21:55:52 endless tracker-store.desktop[2590]: (uint32 1,) Nov 16 21:55:52 endless gnome-session-binary[2217]: Entering running state Nov 16 21:55:54 endless com.endlessm.GoogleChromeInitialSetup.desktop[2592]: INFO:root:Read contents from configuration file at /etc/eos-google-chrome-helper/eos-google-chrome-helper.conf Nov 16 21:55:54 endless /usr/share/eos-google-chrome-helper/eos-google-chrome-installer.py[2592]: Read contents from configuration file at /etc/eos-google-chrome-helper/eos-google-chrome-helper.conf Nov 16 21:55:54 endless com.endlessm.GoogleChromeInitialSetup.desktop[2592]: INFO:root:AutomaticInstallEnabled = True Nov 16 21:55:54 endless /usr/share/eos-google-chrome-helper/eos-google-chrome-installer.py[2592]: AutomaticInstallEnabled = True Nov 16 21:55:54 endless com.endlessm.GoogleChromeInitialSetup.desktop[2592]: INFO:root:Chrome application is not installed Nov 16 21:55:54 endless /usr/share/eos-google-chrome-helper/eos-google-chrome-installer.py[2592]: Chrome application is not installed Nov 16 21:55:54 endless com.endlessm.GoogleChromeInitialSetup.desktop[2592]: INFO:root:Could not find flatpak launcher for Chrome. Nov 16 21:55:54 endless /usr/share/eos-google-chrome-helper/eos-google-chrome-installer.py[2592]: Could not find flatpak launcher for Chrome. Nov 16 21:55:54 endless com.endlessm.GoogleChromeInitialSetup.desktop[2592]: INFO:root:Checking network connectivity... Nov 16 21:55:54 endless /usr/share/eos-google-chrome-helper/eos-google-chrome-installer.py[2592]: Checking network connectivity... Nov 16 21:55:54 endless com.endlessm.GoogleChromeInitialSetup.desktop[2592]: INFO:root:Network connected Nov 16 21:55:54 endless /usr/share/eos-google-chrome-helper/eos-google-chrome-installer.py[2592]: Network connected Nov 16 21:55:54 endless com.endlessm.GoogleChromeInitialSetup.desktop[2592]: INFO:root:Opening App Center... Nov 16 21:55:54 endless /usr/share/eos-google-chrome-helper/eos-google-chrome-installer.py[2592]: Opening App Center... Nov 16 21:55:55 endless dbus-daemon[2243]: Activating via systemd: service name='org.gnome.evolution.dataserver.Calendar7' unit='evolution-calendar-factory.service' Nov 16 21:55:55 endless systemd[2202]: Starting Evolution calendar service... Nov 16 21:55:55 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.evolution.dataserver.Calendar7' Nov 16 21:55:55 endless systemd[2202]: Started Evolution calendar service. Nov 16 21:55:55 endless gnome-software[2599]: plugin appstream took 1.7 seconds to do setup Nov 16 21:55:55 endless gnome-software[2599]: enabled plugins: desktop-categories, provenance, external-appstream, os-release, appstream, provenance-license, hardcoded-popular, generic-updates, hardcoded-featured, flatpak, icons, desktop-menu-path, hardcoded-blacklist, rewrite-resource, key-colors, eos, key-colors-metadata Nov 16 21:55:55 endless gnome-software[2599]: disabled plugins: Nov 16 21:55:55 endless dbus-daemon[2243]: Activating via systemd: service name='org.gnome.evolution.dataserver.AddressBook9' unit='evolution-addressbook-factory.service' Nov 16 21:55:55 endless systemd[2202]: Starting Evolution address book service... Nov 16 21:55:56 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.evolution.dataserver.AddressBook9' Nov 16 21:55:56 endless systemd[2202]: Started Evolution address book service. Nov 16 21:55:56 endless dbus-daemon[2243]: Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' Nov 16 21:55:56 endless systemd[2202]: Starting Virtual filesystem metadata service... Nov 16 21:55:56 endless dbus-daemon[2243]: Successfully activated service 'org.gtk.vfs.Metadata' Nov 16 21:55:56 endless systemd[2202]: Started Virtual filesystem metadata service. Nov 16 21:56:00 endless systemd-journald[350]: Suppressed 190 messages from /system.slice/eos-chrome-plugin-update.service Nov 16 21:56:00 endless eos-chrome-plugin-update[1913]: Widevine plugin installed Nov 16 21:56:00 endless eos-chrome-plugin-update[1913]: All done Nov 16 21:56:02 endless dbus[578]: [system] Activating via systemd: service name='org.freedesktop.Flatpak.SystemHelper' unit='flatpak-system-helper.service' Nov 16 21:56:02 endless systemd[1]: Starting flatpak system helper... Nov 16 21:56:02 endless dbus[578]: [system] Successfully activated service 'org.freedesktop.Flatpak.SystemHelper' Nov 16 21:56:02 endless systemd[1]: Started flatpak system helper. Nov 16 21:56:02 endless gnome-software[2599]: running get-updates-historical with timeout=60 Nov 16 21:56:03 endless bluetoothd[603]: Endpoint unregistered: sender=:1.32 path=/MediaEndpoint/A2DPSource Nov 16 21:56:03 endless bluetoothd[603]: Endpoint unregistered: sender=:1.32 path=/MediaEndpoint/A2DPSink Nov 16 21:56:04 endless gnome-software[2599]: libostree HTTP error from remote gnome for : Server returned status 404: Not Found Nov 16 21:56:04 endless gnome-shell[2347]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation Nov 16 21:56:04 endless colord[897]: Device added: xrandr-AU Optronics Nov 16 21:56:04 endless upowerd[600]: up_kbd_backlight_brightness_read: assertion 'fd >= 0' failed Nov 16 21:56:04 endless gsd-power[2474]: Failed to get brightness: GDBus.Error:org.freedesktop.UPower.GeneralError: error reading brightness Nov 16 21:56:05 endless colord[897]: Automatic metadata add icc-13156682a65e66686bbb89dc02a43485 to xrandr-AU Optronics Nov 16 21:56:05 endless colord[897]: Profile added: icc-13156682a65e66686bbb89dc02a43485 Nov 16 21:56:05 endless gnome-software[2599]: libostree HTTP error from remote gnome for : Server returned status 404: Not Found Nov 16 21:56:05 endless gnome-software[2599]: libostree pull from 'gnome' for appstream/x86_64 complete security: GPG: summary+commit http: TLS non-delta: meta: 4 content: 0 transfer: secs: 2 size: 519 bytes Nov 16 21:56:05 endless gnome-shell[2347]: clutter_paint_volume_set_width: assertion 'width >= 0.0f' failed Nov 16 21:56:06 endless gnome-software[2599]: libostree pull from 'gnome' for appstream/x86_64 complete security: GPG: summary+commit http: TLS delta: parts: 1 loose: 1 transfer: secs: 0 size: 1.2 kB Nov 16 21:56:07 endless gnome-shell[2347]: GNOME Shell started at Thu Nov 16 2017 21:55:50 GMT-0800 (PST) Nov 16 21:56:08 endless gnome-software[2599]: Could not get app (from ID 'org.gnome.Weather.Application') for installed desktop file /var/lib/flatpak/exports/share/applications/org.gnome.Weather.Application.desktop: App org.gnome.Weather.Application no installed Nov 16 21:56:08 endless gnome-software[2599]: failed to parse /var/lib/flatpak/exports/share/applications/kde4: /var/lib/flatpak/exports/share/applications/kde4 has an unrecognised extension Nov 16 21:56:08 endless gnome-software[2599]: Could not get app (from ID 'org.freeciv.Freeciv.server') for installed desktop file /var/lib/flatpak/exports/share/applications/org.freeciv.Freeciv.server.desktop: App org.freeciv.Freeciv.server no installed Nov 16 21:56:08 endless gnome-software[2599]: Could not get app (from ID 'net.gcompris.Gcompris.Admin') for installed desktop file /var/lib/flatpak/exports/share/applications/net.gcompris.Gcompris.Admin.desktop: App net.gcompris.Gcompris.Admin no installed Nov 16 21:56:08 endless gnome-software[2599]: running refresh with failure-flags=use-events with timeout=60 with cache age=any on plugin=flatpak took 5627ms Nov 16 21:56:08 endless gnome-software[2599]: running get-distro-updates with refine-flags=require-version,require-setup-action,require-update-details,require-upgrade-removed,require-provenance,require-icon with failure-flags=use-events with timeout=60 on plugin=appstream took 2ms Nov 16 21:56:08 endless gnome-software[2599]: running refine with refine-flags=require-version,require-update-details,require-provenance,require-icon with failure-flags=fatal-any with timeout=60 took 6ms Nov 16 21:56:10 endless gnome-software[2599]: running refine with refine-flags=require-license,require-url,require-size,require-version,require-history,require-setup-action,require-origin,require-menu-path,require-addons,require-provenance,require-icon,require-permissions,require-origin-hostname,require-runtime,require-screenshots with failure-flags=use-events with timeout=60 on apps system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 took 2386ms Nov 16 21:56:10 endless gnome-software[2599]: running refine with refine-flags=require-rating,require-reviews,require-review-ratings with failure-flags=use-events with timeout=60 on apps system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 took 6ms Nov 16 21:56:11 endless gnome-software[2599]: running get-installed with refine-flags=require-license,require-description,require-size,require-rating,require-version,require-history,require-setup-action,require-origin,require-provenance,require-icon,require-permissions,require-origin-hostname,require-runtime with timeout=60 on plugin=flatpak on apps system/*/*/desktop/org.gnome.Nautilus.desktop/*,system/*/*/desktop/rhythmbox.desktop/*,system/*/*/desktop/gnome-system-monitor.desktop/*,system/*/*/desktop/simple-scan.desktop/*,system/*/*/desktop/org.gnome.font-viewer.desktop/*,system/*/*/desktop/eog.desktop/*,system/*/*/desktop/org.gnome.Cheese.desktop/*,system/*/*/desktop/org.gnome.clocks.desktop/*,system/*/*/desktop/org.gnome.Logs.desktop/*,system/*/*/desktop/evolution.desktop/*,system/*/*/desktop/brasero.desktop/*,system/*/*/desktop/gnome-calculator.desktop/*,system/*/*/desktop/gnome-control-center.desktop/*,system/*/*/desktop/shotwell.desktop/*,system/*/*/desktop/org.gnome.Totem.desktop/*,system/*/*/desktop/evince.desktop/*,system/*/*/desktop/vinagre.desktop/*,system/*/*/desktop/org.gnome.Screenshot.desktop/*,system/*/*/desktop/org.gnome.gedit.desktop/*,system/*/*/desktop/org.gnome.Terminal.desktop/*,system/*/*/desktop/org.gnome.FileRoller.desktop/*,system/*/*/desktop/org.gnome.DiskUtility.desktop/*,system/*/*/desktop/org.gnome.Contacts.desktop/*,system/*/*/desktop/libreoffice-calc.desktop/*,system/*/*/desktop/libreoffice-draw.desktop/*,system/*/*/desktop/libreoffice-base.desktop/*,system/*/*/desktop/libreoffice-writer.desktop/*,system/*/*/desktop/libreoffice-impress.desktop/*,system/*/*/desktop/com.endlessm.Coding.Chatbox.desktop/*,system/*/*/desktop/libreoffice-startcenter.desktop/*,system/package/*/desktop/chromium-browser.desktop/*,system/*/*/desktop/libreoffice-math.desktop/*,system/*/*/desktop/org.gnome.Yelp.desktop/*,system/flatpak/eos-apps/desktop/com.endlessm.animals.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.astronomy.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.biology.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.celebrities.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.cooking.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.dinosaurs.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.disabilities.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.encyclopedia.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.farming.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.finance.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.geography.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.health.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.healthy_teeth.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.history.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.howto.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.maternity.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.math.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.myths.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.photos.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.physics.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.programming_guide.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.resume.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.soccer.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.socialsciences.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.textbooks.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.translation.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.travel.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.water_and_sanitation.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.world_literature.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.github.Slingshot.desktop/eos3,system/flatpak/eos-apps/desktop/com.teeworlds.Teeworlds.desktop/eos3,system/flatpak/eos-apps/desktop/de.billardgl.Billardgl.desktop/eos3,system/flatpak/eos-apps/desktop/io.github.Supertux.desktop/eos3,system/flatpak/eos-apps/desktop/net.blockout.Blockout2.desktop/eos3,system/flatpak/eos-apps/desktop/net.gcompris.Gcompris.desktop/eos3,system/flatpak/eos-apps/desktop/net.minetest.Minetest.desktop/eos3,system/flatpak/eos-apps/desktop/net.olofson.Kobodeluxe.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Atanks.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Audacity.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Btanks.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.ChromiumBSU.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Extremetuxracer.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Rili.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Supertuxkart.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Torcs.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Tuxfootball.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Warmux.desktop/eos3,system/flatpak/eos-apps/desktop/net.wz2100.Warzone2100.desktop/eos3,system/flatpak/eos-apps/desktop/org.armagetronad.Armagetronad.desktop/eos3,system/flatpak/eos-apps/desktop/org.debian.Tuxpuck.desktop/eos3,system/flatpak/eos-apps/desktop/org.debian.alioth.tux4kids.Tuxmath.desktop/eos3,system/flatpak/eos-apps/desktop/org.debian.alioth.tux4kids.Tuxtype.desktop/eos3,system/flatpak/eos-apps/desktop/org.freeciv.Freeciv.desktop/eos3,system/flatpak/eos-apps/desktop/org.frozenbubble.FrozenBubble.desktop/eos3,system/flatpak/eos-apps/desktop/org.gimp.Gimp.desktop/eos3,system/flatpak/eos-apps/desktop/org.gnome.Freecell.desktop/eos3,system/flatpak/eos-apps/desktop/org.gnome.Genius.desktop/eos3,system/flatpak/eos-apps/desktop/org.gnome.Gnote.desktop/eos3,system/flatpak/eos-apps/desktop/org.gnome.Iagno.desktop/eos3,system/flatpak/eos-apps/desktop/org.gnome.Quadrapassel.desktop/eos3,system/flatpak/eos-apps/desktop/org.gnome.Solitaire.desktop/eos3,system/flatpak/eos-apps/desktop/org.gnome.Tetravex.desktop/eos3,system/flatpak/eos-apps/desktop/org.gnome.people.dscorgie.Labyrinth.desktop/eos3,system/flatpak/eos-apps/desktop/org.inkscape.Inkscape.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kalzium.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kapman.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Katomic.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kblocks.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kbounce.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kbruch.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kdiamond.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kgeography.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kgoldrunner.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Khangman.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kigo.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Killbots.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kjumpingcube.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Klines.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Knavalbattle.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Knetwalk.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Ksame.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Ksquares.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Ksudoku.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Ktuberling.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kubrick.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kwordquiz.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Palapeli.desktop/eos3,system/flatpak/eos-apps/desktop/org.maemo.Numptyphysics.desktop/eos3,system/flatpak/eos-apps/desktop/org.marsshooter.Marsshooter.desktop/eos3,system/flatpak/eos-apps/desktop/org.megaglest.MegaGlest.desktop/eos3,system/flatpak/eos-apps/desktop/org.openarena.Openarena.desktop/eos3,system/flatpak/eos-apps/desktop/org.openscad.Openscad.desktop/eos3,system/flatpak/eos-apps/desktop/org.pitivi.Pitivi.desktop/eos3,system/flatpak/eos-apps/desktop/org.seul.Pingus.desktop/eos3,system/flatpak/eos-apps/desktop/org.squeakland.Etoys.desktop/eos3,system/flatpak/eos-apps/desktop/org.squeakland.Scratch.desktop/eos3,system/flatpak/eos-apps/desktop/org.stellarium.Stellarium.desktop/eos3,system/flatpak/eos-apps/desktop/org.sugarlabs.Turtleblocks.desktop/eos3,system/flatpak/eos-apps/desktop/org.tuxfamily.Xmoto.desktop/eos3,system/flatpak/eos-apps/desktop/org.tuxpaint.Tuxpaint.desktop/eos3,system/flatpak/eos-apps/desktop/org.wesnoth.Wesnoth.desktop/eos3,system/flatpak/eos-runtimes/runtime/com.endlessm.Platform/eos3.1,system/flatpak/eos-runtimes/runtime/com.endlessm.Platform/eos3.2,system/flatpak/eos-sdk/runtime/com.endlessm.apps.Platform/1,system/flatpak/gnome/runtime/org.gnome.Platform/3.26 took 2888ms Nov 16 21:56:11 endless fprintd[2200]: No devices in use, exit Nov 16 21:56:11 endless systemd[1]: Starting Stop Read-Ahead Data Collection... Nov 16 21:56:11 endless systemd[1]: Started Stop Read-Ahead Data Collection. Nov 16 21:56:12 endless gnome-software[2599]: libostree HTTP error from remote eos-apps for : Server returned status 404: Not Found Nov 16 21:56:12 endless gnome-software[2599]: libostree pull from 'eos-apps' for app/com.google.Chrome/x86_64/eos3 complete security: GPG: summary+commit http: TLS non-delta: meta: 4 content: 0 transfer: secs: 2 size: 2.5 kB Nov 16 21:56:13 endless gnome-software[2599]: libostree HTTP error from remote eos-apps for : Server returned status 404: Not Found Nov 16 21:56:14 endless gnome-software[2599]: libostree pull from 'eos-apps' for app/com.google.Chrome/x86_64/eos3 complete security: GPG: summary+commit http: TLS non-delta: meta: 24 content: 10 transfer: secs: 2 size: 116.0 kB Nov 16 21:56:15 endless gnome-software[2599]: invalid cast from 'GsApp' to 'GsFlatpakApp' Nov 16 21:56:15 endless gnome-software[2599]: no source set by appstream for flatpak: GsApp: [0x260b030] kind: runtime state: updatable-live quirk: provenance,is-proxy id: com.endlessm.proxy.EOSUpdatesProxy unique-id: system/*/*/runtime/com.endlessm.proxy.EOSUpdatesProxy/* scope: system kudo-percentage: 0 name: Endless Platform icon-kind: stock icon-name: system-run-symbolic summary: Framework for applications management-plugin: eos reviews: 0 provides: 0 related: system/flatpak/eos-sdk/runtime/com.endlessm.apps.Platform/1 related: system/flatpak/eos-sdk/desktop/com.endlessm.EknServices.desktop/eos3 Nov 16 21:56:15 endless gnome-software[2599]: invalid cast from 'GsApp' to 'GsFlatpakApp' Nov 16 21:56:15 endless gnome-software[2599]: running get-updates with refine-flags=require-version,require-update-details,require-provenance,require-icon with timeout=60 on plugin=eos on apps system/flatpak/gnome/runtime/org.gnome.Platform/3.26,system/*/*/runtime/com.endlessm.proxy.EOSUpdatesProxy/* took 7566ms Nov 16 21:56:19 endless ntpd[671]: Soliciting pool server 2001:738:0:810:3::18 Nov 16 21:56:19 endless ntpd[671]: Soliciting pool server 165.227.172.2 Nov 16 21:56:20 endless ntpd[671]: Soliciting pool server 2001:4ba0:babe:1753::1 Nov 16 21:56:20 endless ntpd[671]: Soliciting pool server 51.15.49.133 Nov 16 21:56:20 endless ntpd[671]: Soliciting pool server 212.112.228.242 Nov 16 21:56:21 endless ntpd[671]: Soliciting pool server 2001:738:0:860:1::3 Nov 16 21:56:21 endless ntpd[671]: Soliciting pool server 94.244.80.51 Nov 16 21:56:22 endless ntpd[671]: Soliciting pool server 2a01:4f8:141:31c2::2 Nov 16 21:56:23 endless ntpd[671]: Soliciting pool server 139.112.153.36 Nov 16 21:56:24 endless ntpd[671]: Soliciting pool server 150.95.148.140 Nov 16 21:56:24 endless ntpd[671]: Soliciting pool server 46.163.88.228 Nov 16 21:56:25 endless ntpd[671]: Soliciting pool server 213.251.52.250 Nov 16 21:56:25 endless ntpd[671]: Soliciting pool server 46.235.112.25 Nov 16 21:56:31 endless flatpak-system-helper[2715]: Extracting chrome.deb of type deb Nov 16 21:56:45 endless eos-link-whatsapp.desktop[3248]: This tool has been deprecated, use 'gio open' instead. Nov 16 21:56:45 endless eos-link-whatsapp.desktop[3248]: See 'gio help open' for more info. Nov 16 21:56:45 endless dbus-daemon[2243]: Activating service name='com.endlessm.Speedwagon' Nov 16 21:56:45 endless dbus-daemon[2243]: Successfully activated service 'com.endlessm.Speedwagon' Nov 16 21:56:45 endless eos-link-whatsapp.desktop[3248]: Found default browser: Internet Nov 16 21:56:45 endless eos-link-whatsapp.desktop[3248]: Using chromium-browser to launch web application (config dir: /sysroot/home/jeremy/.config/chromium-appmode////web.whatsapp.com)... Nov 16 21:56:45 endless com.endlessm.GoogleChromeInitialSetup.desktop[2592]: INFO:root:com.google.Chrome has been installed Nov 16 21:56:45 endless /usr/share/eos-google-chrome-helper/eos-google-chrome-installer.py[2592]: com.google.Chrome has been installed Nov 16 21:56:45 endless com.endlessm.GoogleChromeInitialSetup.desktop[2592]: INFO:root:Chrome successfully installed Nov 16 21:56:45 endless /usr/share/eos-google-chrome-helper/eos-google-chrome-installer.py[2592]: Chrome successfully installed Nov 16 21:56:46 endless pkexec[3533]: pam_unix(polkit-1:session): session opened for user root by (uid=1001) Nov 16 21:56:46 endless pkexec[3533]: pam_systemd(polkit-1:session): Cannot create session: Already running in a session Nov 16 21:56:46 endless pkexec[3533]: jeremy: Executing command [USER=root] [TTY=unknown] [CWD=/sysroot/home/jeremy] [COMMAND=/usr/share/eos-google-chrome-helper/eos-google-chrome-system-helper.py] Nov 16 21:56:46 endless com.endlessm.GoogleChromeInitialSetup.desktop[2592]: INFO:root:Stamp file created at /var/lib/eos-google-chrome-helper/initial-setup-done Nov 16 21:56:46 endless /usr/share/eos-google-chrome-helper/eos-google-chrome-system-helper.py[3533]: Stamp file created at /var/lib/eos-google-chrome-helper/initial-setup-done Nov 16 21:56:46 endless com.endlessm.GoogleChromeInitialSetup.desktop[2592]: INFO:root:Post-installation configuration done Nov 16 21:56:46 endless /usr/share/eos-google-chrome-helper/eos-google-chrome-installer.py[2592]: Post-installation configuration done Nov 16 21:56:47 endless gnome-session[2217]: gnome-session-binary[2217]: WARNING: Not able to stop app from its condition: Not running Nov 16 21:56:47 endless gnome-session-binary[2217]: WARNING: Not able to stop app from its condition: Not running Nov 16 21:56:47 endless eos-link-whatsapp.desktop[3248]: [3274:3274:1116/215647.227543:ERROR:configuration_policy_handler_list.cc(92)] Unknown policy: ExtensionInstallForceList Nov 16 21:56:47 endless eos-link-whatsapp.desktop[3248]: [3274:3274:1116/215647.411413:ERROR:configuration_policy_handler_list.cc(92)] Unknown policy: ExtensionInstallForceList Nov 16 21:56:48 endless gnome-software[2599]: running install with refine-flags=require-origin with failure-flags=use-events,fatal-auth with timeout=60 on plugin=eos on apps system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 took 40562ms Nov 16 21:56:48 endless gnome-software[2599]: running refine with refine-flags=require-license,require-url,require-size,require-version,require-history,require-setup-action,require-origin,require-menu-path,require-addons,require-provenance,require-icon,require-permissions,require-origin-hostname,require-runtime,require-screenshots with failure-flags=use-events with timeout=60 on apps system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 took 14ms Nov 16 21:56:48 endless gnome-software[2599]: running refine with refine-flags=require-rating,require-reviews,require-review-ratings with failure-flags=use-events with timeout=60 on apps system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 took 12ms Nov 16 21:57:03 endless gnome-software[2599]: running get-distro-updates with refine-flags=require-setup-action with timeout=60 on plugin=appstream Nov 16 21:57:04 endless gnome-software[2599]: libostree HTTP error from remote eos-apps for : Server returned status 404: Not Found Nov 16 21:57:04 endless gnome-software[2599]: libostree pull from 'eos-apps' for appstream/x86_64 complete security: GPG: summary+commit http: TLS non-delta: meta: 4 content: 0 transfer: secs: 1 size: 1.3 kB Nov 16 21:57:05 endless gnome-software[2599]: libostree HTTP error from remote eos-apps for : Server returned status 404: Not Found Nov 16 21:57:06 endless gnome-software[2599]: libostree pull from 'eos-apps' for appstream/x86_64 complete security: GPG: summary+commit http: TLS non-delta: meta: 7 content: 80 transfer: secs: 1 size: 1.9 MB Nov 16 21:57:08 endless gnome-software[2599]: libostree HTTP error from remote eos-runtimes for : Server returned status 404: Not Found Nov 16 21:57:08 endless gnome-software[2599]: libostree pull from 'eos-runtimes' for appstream/x86_64 complete security: GPG: summary+commit http: TLS non-delta: meta: 3 content: 0 transfer: secs: 1 size: 1.1 kB Nov 16 21:57:09 endless gnome-software[2599]: libostree HTTP error from remote eos-runtimes for : Server returned status 404: Not Found Nov 16 21:57:09 endless gnome-software[2599]: libostree pull from 'eos-runtimes' for appstream/x86_64 complete security: GPG: summary+commit http: TLS non-delta: meta: 3 content: 0 transfer: secs: 0 size: 1.1 kB Nov 16 21:57:09 endless flatpak-system-helper[2715]: libostree pull from 'eos-runtimes' for appstream/x86_64 complete security: GPG: summary+commit non-delta: meta: 3 content: 0 transfer: secs: 0 size: 1.1 kB Nov 16 21:57:10 endless gnome-software[2599]: libostree HTTP error from remote eos-sdk for : Server returned status 404: Not Found Nov 16 21:57:10 endless gnome-software[2599]: libostree pull from 'eos-sdk' for appstream/x86_64 complete security: GPG: summary+commit http: TLS non-delta: meta: 4 content: 0 transfer: secs: 0 size: 1.3 kB Nov 16 21:57:11 endless gnome-software[2599]: libostree HTTP error from remote eos-sdk for : Server returned status 404: Not Found Nov 16 21:57:11 endless gnome-software[2599]: libostree pull from 'eos-sdk' for appstream/x86_64 complete security: GPG: summary+commit http: TLS non-delta: meta: 4 content: 1 transfer: secs: 0 size: 1.6 kB Nov 16 21:57:15 endless dbus-daemon[2243]: Activating service name='com.endlessm.Speedwagon' Nov 16 21:57:15 endless dbus-daemon[2243]: Successfully activated service 'com.endlessm.Speedwagon' Nov 16 21:57:15 endless google-chrome.desktop[3878]: INFO:root:Found flatpak launcher for Google Chrome: '/var/lib/flatpak/app/com.google.Chrome/x86_64/eos3/3c53c34fbc70a8e845830056da453003619b9c3fcc7477766b67e4a6078f8fc2/files/bin/eos-google-chrome-app' Nov 16 21:57:15 endless google-chrome.desktop[3878]: INFO:root:Flatpak launcher for Chrome found. Launching... Nov 16 21:57:15 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[3878]: Found flatpak launcher for Google Chrome: '/var/lib/flatpak/app/com.google.Chrome/x86_64/eos3/3c53c34fbc70a8e845830056da453003619b9c3fcc7477766b67e4a6078f8fc2/files/bin/eos-google-chrome-app' Nov 16 21:57:15 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[3878]: Flatpak launcher for Chrome found. Launching... Nov 16 21:57:15 endless google-chrome.desktop[3878]: INFO:root:Running Google Chrome launcher with PID 3887 Nov 16 21:57:15 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[3878]: Running Google Chrome launcher with PID 3887 Nov 16 21:57:15 endless dbus-daemon[2243]: Activating via systemd: service name='org.freedesktop.Flatpak' unit='flatpak-session-helper.service' Nov 16 21:57:15 endless systemd[2202]: Starting flatpak session helper... Nov 16 21:57:15 endless dbus-daemon[2243]: Successfully activated service 'org.freedesktop.Flatpak' Nov 16 21:57:15 endless systemd[2202]: Started flatpak session helper. Nov 16 21:57:15 endless dbus-daemon[2243]: Activating via systemd: service name='org.freedesktop.portal.Documents' unit='xdg-document-portal.service' Nov 16 21:57:15 endless systemd[2202]: Starting flatpak document portal service... Nov 16 21:57:15 endless dbus-daemon[2243]: Successfully activated service 'org.freedesktop.portal.Documents' Nov 16 21:57:15 endless systemd[2202]: Started flatpak document portal service. Nov 16 21:57:15 endless xdg-document-portal[3910]: FUSE library version: 2.9.7 Nov 16 21:57:15 endless xdg-document-portal[3910]: unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0 Nov 16 21:57:15 endless xdg-document-portal[3910]: INIT: 7.26 Nov 16 21:57:15 endless xdg-document-portal[3910]: flags=0x001ffffb Nov 16 21:57:15 endless xdg-document-portal[3910]: max_readahead=0x00020000 Nov 16 21:57:15 endless xdg-document-portal[3910]: INIT: 7.19 Nov 16 21:57:15 endless xdg-document-portal[3910]: flags=0x00000001 Nov 16 21:57:15 endless xdg-document-portal[3910]: max_readahead=0x00020000 Nov 16 21:57:15 endless xdg-document-portal[3910]: max_write=0x00020000 Nov 16 21:57:15 endless xdg-document-portal[3910]: max_background=0 Nov 16 21:57:15 endless xdg-document-portal[3910]: congestion_threshold=0 Nov 16 21:57:15 endless xdg-document-portal[3910]: unique: 1, success, outsize: 40 Nov 16 21:57:15 endless xdg-document-portal[3910]: unique: 2, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 3910 Nov 16 21:57:15 endless xdg-document-portal[3910]: unique: 2, success, outsize: 120 Nov 16 21:57:15 endless systemd[2202]: Started flatpak-com.google.Chrome-3894.scope. Nov 16 21:57:15 endless google-chrome.desktop[3878]: /sysroot/flatpak/app/com.google.Chrome/x86_64/eos3/3c53c34fbc70a8e845830056da453003619b9c3fcc7477766b67e4a6078f8fc2/files/extra/opt/google/chrome/nacl_helper: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory Nov 16 21:57:15 endless google-chrome.desktop[3878]: [1:1:1116/215715.888801:ERROR:nacl_fork_delegate_linux.cc(315)] Bad NaCl helper startup ack (0 bytes) Nov 16 21:57:15 endless xdg-document-portal[3910]: unique: 3, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 21:57:15 endless xdg-document-portal[3910]: unique: 3, success, outsize: 96 Nov 16 21:57:15 endless xdg-document-portal[3910]: unique: 4, opcode: LOOKUP (1), nodeid: 1, insize: 47, pid: 3933 Nov 16 21:57:15 endless xdg-document-portal[3910]: unique: 4, success, outsize: 144 Nov 16 21:57:16 endless xdg-document-portal[3910]: unique: 5, opcode: LOOKUP (1), nodeid: 2, insize: 58, pid: 3933 Nov 16 21:57:16 endless xdg-document-portal[3910]: unique: 5, success, outsize: 144 Nov 16 21:57:16 endless google-chrome.desktop[3878]: [3895:3895:1116/215716.211772:ERROR:configuration_policy_handler_list.cc(92)] Unknown policy: ExtensionInstallForceList Nov 16 21:57:16 endless google-chrome.desktop[3878]: [3895:3895:1116/215716.359536:ERROR:configuration_policy_handler_list.cc(92)] Unknown policy: ExtensionInstallForceList Nov 16 21:57:16 endless gnome-software[2599]: libostree HTTP error from remote flathub for : Server returned status 404: Not Found Nov 16 21:57:16 endless gnome-software[2599]: failed to rescan: Failed to parse /sysroot/home/jeremy/.local/share/applications/mimeapps.list file: cannot process file of type text/plain Nov 16 21:57:16 endless gnome-keyring-daemon[2209]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered Nov 16 21:57:17 endless gnome-software[2599]: libostree HTTP error from remote flathub for : Server returned status 404: Not Found Nov 16 21:57:17 endless gnome-shell[2347]: g_variant_new_string: assertion 'string != NULL' failed Nov 16 21:57:17 endless gnome-software[2599]: libostree pull from 'flathub' for appstream/x86_64 complete security: GPG: summary+commit http: TLS non-delta: meta: 4 content: 0 transfer: secs: 5 size: 775 bytes Nov 16 21:57:19 endless gnome-software[2599]: failed to rescan: Failed to parse /sysroot/home/jeremy/.local/share/applications/chrome-pjkljhegncpnkpknbcohdijeoejaedia-Default.desktop file: cannot process file of type application/x-desktop Nov 16 21:57:20 endless gnome-software[2599]: failed to rescan: Failed to parse /sysroot/home/jeremy/.local/share/applications/chrome-apdfllckaahabafndbhieahigkjlhalf-Default.desktop file: cannot process file of type application/x-desktop Nov 16 21:57:20 endless gnome-software[2599]: failed to rescan: Failed to parse /sysroot/home/jeremy/.local/share/applications/chrome-aohghmighlieiainnegkcijnfilokake-Default.desktop file: cannot process file of type application/x-desktop Nov 16 21:57:20 endless gnome-software[2599]: failed to rescan: Failed to parse /sysroot/home/jeremy/.local/share/applications/chrome-blpcfgokakmgnkcojhhkbfbldkacnbeo-Default.desktop file: cannot process file of type application/x-desktop Nov 16 21:57:23 endless gnome-software[2599]: libostree pull from 'flathub' for appstream/x86_64 complete security: GPG: summary+commit http: TLS delta: parts: 1 loose: 1 transfer: secs: 5 size: 2.7 MB Nov 16 21:57:25 endless gnome-software[2599]: libostree HTTP error from remote gnome-apps for : Server returned status 404: Not Found Nov 16 21:57:26 endless gnome-software[2599]: libostree HTTP error from remote gnome-apps for : Server returned status 404: Not Found Nov 16 21:57:26 endless systemd[1]: Started /bin/systemctl --no-block start eos-phone-home.service. Nov 16 21:57:26 endless systemd[1]: Started Send system activation/daily ping messages to Endless. Nov 16 21:57:26 endless gnome-software[2599]: libostree pull from 'gnome-apps' for appstream/x86_64 complete security: GPG: summary+commit http: TLS non-delta: meta: 4 content: 0 transfer: secs: 2 size: 519 bytes Nov 16 21:57:27 endless eos-phone-home[4791]: INFO:__main__:Already activated! Nov 16 21:57:27 endless eos-phone-home[4791]: INFO:__main__:Getting variable: live Nov 16 21:57:27 endless eos-phone-home[4791]: INFO:__main__:Getting variable: cmdline Nov 16 21:57:27 endless eos-phone-home[4791]: INFO:__main__: - Cmdline: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-a7d4a286f29b21cc342a066d74a68b894ded66e4fcd88e20fcd025bad1c49609/vmlinuz-4.13.0-12-generic root=UUID=a2833eed-cc31-409c-b18d-e8a3571c0c55 rw splash plymouth.ignore-serial-consoles quiet ostree=/ostree/boot.1/eos/a7d4a286f29b21cc342a066d74a68b894ded66e4fcd88e20fcd025bad1c49609/0 Nov 16 21:57:27 endless eos-phone-home[4791]: INFO:__main__:Count age: 28903.45299911499 Nov 16 21:57:27 endless eos-phone-home[4791]: INFO:__main__:Ping not due yet. Nov 16 21:57:27 endless gnome-software[2599]: libostree pull from 'gnome-apps' for appstream/x86_64 complete security: GPG: summary+commit http: TLS delta: parts: 1 loose: 1 transfer: secs: 1 size: 900.9 kB Nov 16 21:57:29 endless gnome-software[2599]: Could not get app (from ID 'org.gnome.Weather.Application') for installed desktop file /var/lib/flatpak/exports/share/applications/org.gnome.Weather.Application.desktop: App org.gnome.Weather.Application no installed Nov 16 21:57:29 endless gnome-software[2599]: failed to parse /var/lib/flatpak/exports/share/applications/kde4: /var/lib/flatpak/exports/share/applications/kde4 has an unrecognised extension Nov 16 21:57:29 endless gnome-software[2599]: Could not get app (from ID 'org.freeciv.Freeciv.server') for installed desktop file /var/lib/flatpak/exports/share/applications/org.freeciv.Freeciv.server.desktop: App org.freeciv.Freeciv.server no installed Nov 16 21:57:29 endless gnome-software[2599]: failed to parse /var/lib/flatpak/exports/share/applications/com.google.Chrome.desktop: NoDisplay=true Nov 16 21:57:29 endless gnome-software[2599]: Could not get app (from ID 'net.gcompris.Gcompris.Admin') for installed desktop file /var/lib/flatpak/exports/share/applications/net.gcompris.Gcompris.Admin.desktop: App net.gcompris.Gcompris.Admin no installed Nov 16 21:57:29 endless gnome-software[2599]: running refresh with timeout=60 with cache age=86400 on plugin=flatpak took 26397ms Nov 16 21:57:29 endless systemd[1]: Started /bin/systemctl --no-block start eos-phone-home.service. Nov 16 21:57:29 endless systemd[1]: Started Send system activation/daily ping messages to Endless. Nov 16 21:57:30 endless eos-phone-home[4869]: INFO:__main__:Already activated! Nov 16 21:57:30 endless eos-phone-home[4869]: INFO:__main__:Getting variable: live Nov 16 21:57:30 endless eos-phone-home[4869]: INFO:__main__:Getting variable: cmdline Nov 16 21:57:30 endless eos-phone-home[4869]: INFO:__main__: - Cmdline: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-a7d4a286f29b21cc342a066d74a68b894ded66e4fcd88e20fcd025bad1c49609/vmlinuz-4.13.0-12-generic root=UUID=a2833eed-cc31-409c-b18d-e8a3571c0c55 rw splash plymouth.ignore-serial-consoles quiet ostree=/ostree/boot.1/eos/a7d4a286f29b21cc342a066d74a68b894ded66e4fcd88e20fcd025bad1c49609/0 Nov 16 21:57:30 endless eos-phone-home[4869]: INFO:__main__:Count age: 28906.104977846146 Nov 16 21:57:30 endless eos-phone-home[4869]: INFO:__main__:Ping not due yet. Nov 16 21:57:32 endless gnome-software[2599]: invalid cast from 'GsApp' to 'GsFlatpakApp' Nov 16 21:57:32 endless gnome-software[2599]: no source set by appstream for flatpak: GsApp: [0x260b260] kind: runtime state: updatable-live quirk: is-proxy id: com.endlessm.proxy.EOSUpdatesProxy unique-id: system/*/*/runtime/com.endlessm.proxy.EOSUpdatesProxy/* scope: system kudo-percentage: 0 name: Endless Platform icon-kind: stock icon-name: system-run-symbolic summary: Framework for applications management-plugin: eos reviews: 0 provides: 0 related: system/flatpak/eos-sdk/runtime/com.endlessm.apps.Platform/1 related: system/flatpak/eos-sdk/desktop/com.endlessm.EknServices.desktop/eos3 Nov 16 21:57:32 endless gnome-software[2599]: running get-updates with refine-flags=require-update-details,require-update-severity with timeout=60 on plugin=eos on apps system/flatpak/gnome/runtime/org.gnome.Platform/3.26,system/*/*/runtime/com.endlessm.proxy.EOSUpdatesProxy/* took 2800ms Nov 16 21:57:50 endless gnome-keyring-daemon[2209]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered Nov 16 21:58:16 endless xdg-document-portal[3910]: unique: 6, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 21:58:16 endless xdg-document-portal[3910]: unique: 6, success, outsize: 96 Nov 16 21:59:16 endless xdg-document-portal[3910]: unique: 7, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 21:59:16 endless xdg-document-portal[3910]: unique: 7, success, outsize: 96 Nov 16 22:00:16 endless xdg-document-portal[3910]: unique: 8, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:00:16 endless xdg-document-portal[3910]: unique: 8, success, outsize: 96 Nov 16 22:00:53 endless ntpd[671]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Nov 16 22:00:56 endless google-chrome.desktop[3878]: INFO:root:Google Chrome launcher stopped Nov 16 22:00:56 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[3878]: Google Chrome launcher stopped Nov 16 22:01:06 endless dbus-daemon[2243]: Activating service name='org.gnome.ControlCenter.SearchProvider' Nov 16 22:01:06 endless dbus-daemon[2243]: Activating service name='com.endlessm.EknServices.SearchProviderV1' Nov 16 22:01:06 endless dbus-daemon[2243]: Activating service name='org.gnome.Calculator.SearchProvider' Nov 16 22:01:06 endless dbus-daemon[2243]: Activating service name='org.gnome.Contacts.SearchProvider' Nov 16 22:01:06 endless dbus-daemon[2243]: Activating service name='org.gnome.Yelp.SearchProvider' Nov 16 22:01:06 endless dbus-daemon[2243]: Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' Nov 16 22:01:07 endless systemd[2202]: Starting GNOME Terminal Server... Nov 16 22:01:07 endless systemd[2202]: Started flatpak-com.endlessm.EknServices-5202.scope. Nov 16 22:01:07 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.ControlCenter.SearchProvider' Nov 16 22:01:07 endless xdg-document-portal[3910]: unique: 9, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 5218 Nov 16 22:01:07 endless xdg-document-portal[3910]: unique: 9, success, outsize: 120 Nov 16 22:01:07 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Calculator.SearchProvider' Nov 16 22:01:07 endless xdg-document-portal[3910]: unique: 10, opcode: LOOKUP (1), nodeid: 1, insize: 47, pid: 5218 Nov 16 22:01:07 endless xdg-document-portal[3910]: unique: 10, success, outsize: 144 Nov 16 22:01:07 endless xdg-document-portal[3910]: unique: 11, opcode: LOOKUP (1), nodeid: 2, insize: 65, pid: 5218 Nov 16 22:01:07 endless xdg-document-portal[3910]: unique: 11, success, outsize: 144 Nov 16 22:01:07 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Terminal' Nov 16 22:01:07 endless systemd[2202]: Started GNOME Terminal Server. Nov 16 22:01:07 endless dbus-daemon[2243]: Successfully activated service 'com.endlessm.EknServices.SearchProviderV1' Nov 16 22:01:07 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Contacts.SearchProvider' Nov 16 22:01:07 endless gnome-contacts-[5206]: contacts-store.vala:335: Unable to check accounts caps The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files Nov 16 22:01:07 endless gnome-contacts-[5206]: backend-store.vala:434: Error preparing Backend 'telepathy': The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files Nov 16 22:01:07 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Yelp.SearchProvider' Nov 16 22:01:07 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=cheese on plugin=flatpak on apps system/*/*/desktop/org.gnome.Cheese.desktop/* took 47ms Nov 16 22:01:08 endless systemd[1]: Started xapian-bridge.service. Nov 16 22:01:08 endless gnome-shell[2347]: Failed to set the markup of the actor 'ClutterText': Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as & Nov 16 22:01:16 endless xdg-document-portal[3910]: unique: 12, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:01:16 endless xdg-document-portal[3910]: unique: 12, success, outsize: 96 Nov 16 22:01:16 endless dbus-daemon[2243]: Activating service name='org.gnome.Cheese' Nov 16 22:01:16 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Cheese' Nov 16 22:01:17 endless cheese[5255]: Theme parsing error: cheese.css:7:35: The style property GtkScrollbar:min-slider-length is deprecated and shouldn't be used anymore. It will be removed in a future version Nov 16 22:01:31 endless cheese[5255]: A lot of buffers are being dropped.: gstbasesink.c(2834): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Nov 16 22:01:32 endless cheese[5255]: A lot of buffers are being dropped.: gstbasesink.c(2834): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Nov 16 22:01:33 endless cheese[5255]: A lot of buffers are being dropped.: gstbasesink.c(2834): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Nov 16 22:01:34 endless cheese[5255]: A lot of buffers are being dropped.: gstbasesink.c(2834): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Nov 16 22:01:35 endless cheese[5255]: A lot of buffers are being dropped.: gstbasesink.c(2834): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Nov 16 22:01:36 endless cheese[5255]: A lot of buffers are being dropped.: gstbasesink.c(2834): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Nov 16 22:01:37 endless cheese[5255]: A lot of buffers are being dropped.: gstbasesink.c(2834): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Nov 16 22:01:38 endless cheese[5255]: A lot of buffers are being dropped.: gstbasesink.c(2834): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Nov 16 22:01:39 endless cheese[5255]: A lot of buffers are being dropped.: gstbasesink.c(2834): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Nov 16 22:01:40 endless cheese[5255]: A lot of buffers are being dropped.: gstbasesink.c(2834): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Nov 16 22:01:41 endless cheese[5255]: A lot of buffers are being dropped.: gstbasesink.c(2834): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Nov 16 22:01:43 endless cheese[5255]: A lot of buffers are being dropped.: gstbasesink.c(2834): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Nov 16 22:02:16 endless xdg-document-portal[3910]: unique: 13, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:02:16 endless xdg-document-portal[3910]: unique: 13, success, outsize: 96 Nov 16 22:02:17 endless dbus-daemon[2243]: Activating service name='com.endlessm.health.en' Nov 16 22:02:17 endless dbus-daemon[2243]: Activating service name='com.endlessm.Speedwagon' Nov 16 22:02:17 endless dbus-daemon[2243]: Successfully activated service 'com.endlessm.Speedwagon' Nov 16 22:02:17 endless systemd[2202]: Started flatpak-com.endlessm.health.en-5333.scope. Nov 16 22:02:17 endless xdg-document-portal[3910]: unique: 14, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 5351 Nov 16 22:02:17 endless xdg-document-portal[3910]: unique: 14, success, outsize: 120 Nov 16 22:02:17 endless xdg-document-portal[3910]: unique: 15, opcode: LOOKUP (1), nodeid: 1, insize: 47, pid: 5351 Nov 16 22:02:17 endless xdg-document-portal[3910]: unique: 15, success, outsize: 144 Nov 16 22:02:17 endless xdg-document-portal[3910]: unique: 16, opcode: LOOKUP (1), nodeid: 2, insize: 63, pid: 5351 Nov 16 22:02:17 endless xdg-document-portal[3910]: unique: 16, success, outsize: 144 Nov 16 22:02:17 endless dbus-daemon[2243]: Successfully activated service 'com.endlessm.health.en' Nov 16 22:02:18 endless dbus-daemon[2243]: Activating service name='org.freedesktop.portal.Desktop' Nov 16 22:02:18 endless dbus-daemon[2243]: Activating service name='org.freedesktop.impl.portal.desktop.gtk' Nov 16 22:02:18 endless dbus-daemon[2243]: Successfully activated service 'org.freedesktop.impl.portal.desktop.gtk' Nov 16 22:02:18 endless dbus-daemon[2243]: Successfully activated service 'org.freedesktop.portal.Desktop' Nov 16 22:02:35 endless gjs[5353]: Allocating size to EmeusConstraintLayout 0x10d0310 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:02:35 endless gjs[5353]: Allocating size to EmeusConstraintLayout 0x10d06f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:02:35 endless gjs[5353]: Allocating size to EmeusConstraintLayout 0x10d0ad0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:02:35 endless gjs[5353]: Allocating size to EmeusConstraintLayout 0x10d0eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:02:35 endless gjs[5353]: Allocating size to EmeusConstraintLayout 0xcbf330 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:02:43 endless dbus-daemon[2243]: Activating service name='com.endlessm.travel.en' Nov 16 22:02:43 endless systemd[2202]: Started flatpak-com.endlessm.travel.en-5397.scope. Nov 16 22:02:44 endless xdg-document-portal[3910]: unique: 17, opcode: LOOKUP (1), nodeid: 2, insize: 63, pid: 5410 Nov 16 22:02:44 endless xdg-document-portal[3910]: unique: 17, success, outsize: 144 Nov 16 22:02:44 endless dbus-daemon[2243]: Successfully activated service 'com.endlessm.travel.en' Nov 16 22:03:04 endless gjs[5412]: Allocating size to EknCard_Deck 0x20d0dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:04 endless gjs[5412]: Allocating size to EknCard_Deck 0x20d0f80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:04 endless gjs[5412]: Allocating size to EknCard_Deck 0x1f46180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:04 endless gjs[5412]: Allocating size to EknCard_Deck 0x1f46340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x3cdc340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x3cdcdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x3ef9880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x400f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x400fdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x4184880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x43b3340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x43b3dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x316edc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x32fd880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x3594340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x3594dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x3891880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x395f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x395fdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x3ae0880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x229f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x229fdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x302e880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:10 endless gjs[5412]: Allocating size to EknCard_Default 0x316e340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x3cdc340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2320 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x3cdcdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x3ef9880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2ae0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x400f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2ec0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x400fdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x4197310 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x4184880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x41976f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x43b3340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x4197ad0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x43b3dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x4197eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_ContentGroup 0x17eb590 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x316edc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x32f5310 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x32fd880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x32f56f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x3594340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x32f5ad0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x3594dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x32f5eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x3891880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x389d310 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x395f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x389d6f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x395fdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x389dad0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x3ae0880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x389deb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x229f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x1308330 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x229fdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x1308710 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x302e880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x1308af0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x316e340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x1308ed0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x3cdc340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2320 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x3cdcdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x3ef9880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2ae0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x400f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2ec0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x400fdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x4197310 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x4184880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x41976f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x43b3340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x4197ad0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x43b3dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x4197eb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_ContentGroup 0x17eb590 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x3891880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x389d310 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x395f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x389d6f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x395fdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x389dad0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EknCard_Default 0x3ae0880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x389deb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x1308330 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:16 endless xdg-document-portal[3910]: unique: 18, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:03:16 endless xdg-document-portal[3910]: unique: 18, success, outsize: 96 Nov 16 22:03:17 endless gjs[5412]: Allocating size to EknCard_Default 0x229f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:17 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x1308330 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:17 endless gjs[5412]: Allocating size to EknCard_Default 0x4184880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:17 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x41976f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:17 endless gjs[5412]: Allocating size to EknCard_ContentGroup 0x17eb590 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:17 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x1308330 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:17 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x41976f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:17 endless gjs[5412]: Allocating size to EknCard_Default 0x4184880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:17 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x41976f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:17 endless gjs[5412]: Allocating size to EknCard_ContentGroup 0x17eb590 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:17 endless gjs[5412]: Allocating size to EknCard_Default 0x395f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:17 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x389d6f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:17 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x41976f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:18 endless gjs[5412]: Allocating size to EknCard_ContentGroup 0x17eb590 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:18 endless gjs[5412]: Allocating size to EknCard_Default 0x395f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:18 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x389d6f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:18 endless gjs[5412]: Allocating size to EknCard_Default 0x229f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:18 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x1308330 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:18 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x1308330 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:18 endless gjs[5412]: Allocating size to EknCard_Default 0x229f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:18 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x1308330 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:18 endless gjs[5412]: Allocating size to EknCard_Default 0x302e880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:18 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x1308af0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:18 endless gjs[5412]: Allocating size to EknCard_Default 0x395f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:18 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x389d6f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:18 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x1308330 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:18 endless gjs[5412]: Allocating size to EknCard_Default 0x302e880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:18 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x1308af0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:19 endless gjs[5412]: Allocating size to EknCard_Default 0x3cdcdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:19 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:19 endless gjs[5412]: Allocating size to EknCard_ContentGroup 0x17eb590 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:19 endless gjs[5412]: Allocating size to EknCard_Default 0x395f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:19 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x389d6f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:19 endless gjs[5412]: Allocating size to EknCard_Default 0x3cdcdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:19 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:19 endless gjs[5412]: Allocating size to EknCard_Default 0x4184880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:19 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x41976f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:19 endless gjs[5412]: Allocating size to EknCard_ContentGroup 0x17eb590 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:19 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x41976f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:21 endless gjs[5412]: Allocating size to EknCard_Default 0x3cdcdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:21 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:21 endless gjs[5412]: Allocating size to EknCard_Default 0x4184880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:21 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x41976f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:21 endless gjs[5412]: Allocating size to EknCard_ContentGroup 0x17eb590 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:22 endless gjs[5412]: Allocating size to EknCard_Default 0x3cdcdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:22 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:22 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x41976f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:22 endless gjs[5412]: Allocating size to EknCard_ContentGroup 0x17eb590 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:22 endless gjs[5412]: Allocating size to EknCard_Default 0x395f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:22 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x389d6f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:22 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x389d6f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:23 endless gjs[5412]: Allocating size to EknCard_Default 0x395f340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:23 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x389d6f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:23 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x389d6f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:23 endless gjs[5412]: Allocating size to EknCard_Default 0x3cdcdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:23 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:23 endless gjs[5412]: Allocating size to EknCard_ContentGroup 0x17eb590 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:24 endless gjs[5412]: Allocating size to EknCard_Default 0x3cdcdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:24 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:24 endless gjs[5412]: Allocating size to EknCard_Default 0x4184880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:24 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x41976f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:24 endless gjs[5412]: Allocating size to EknCard_ContentGroup 0x17eb590 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:24 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x41976f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:24 endless gjs[5412]: Allocating size to EknCard_Default 0x4184880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:24 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x41976f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:24 endless gjs[5412]: Allocating size to EknCard_ContentGroup 0x17eb590 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:24 endless gjs[5412]: Allocating size to EknCard_Default 0x3cdcdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:24 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:24 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x41976f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:24 endless gjs[5412]: Allocating size to EknCard_ContentGroup 0x17eb590 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:25 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:25 endless gjs[5412]: Allocating size to EknCard_Default 0x3cdcdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:25 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:25 endless gjs[5412]: Allocating size to EknCard_Default 0x3ef9880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:25 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2ae0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:25 endless gjs[5412]: Allocating size to EknCard_ContentGroup 0x17eb590 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:25 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:25 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2ae0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:26 endless gjs[5412]: Allocating size to EknCard_Default 0x3ef9880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:26 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2ae0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:26 endless gjs[5412]: Allocating size to EknCard_ContentGroup 0x17eb590 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:26 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x3cd2ae0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:03:36 endless gst-plugin-scan[5516]: Failed to load plugin '/usr/lib/gstreamer-1.0/libgstdataurisrc.so': /usr/lib/gstreamer-1.0/libgstdataurisrc.so: file too short Nov 16 22:04:16 endless xdg-document-portal[3910]: unique: 19, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:04:16 endless xdg-document-portal[3910]: unique: 19, success, outsize: 96 Nov 16 22:04:49 endless gjs[5412]: Allocating size to EknCard_Deck 0x1f46340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:49 endless gjs[5412]: Allocating size to EknCard_Deck 0x1f46340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:51 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:51 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:51 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:51 endless gjs[5412]: Allocating size to EknCard_Deck 0x22436c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:51 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:51 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243a40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:51 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:51 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:51 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243f80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:51 endless gjs[5412]: Allocating size to EknCard_Deck 0x229f180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x22436c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243a40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243f80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x229f180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x102956c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x10295880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x10295a40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x10295c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x10295dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x10295f80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x102e0180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x102e0340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:53 endless gjs[5412]: Allocating size to EknCard_Deck 0x102e0500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:59 endless gjs[5412]: Allocating size to EknCard_Deck 0x2243dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:04:59 endless gjs[5412]: Allocating size to EknCard_Deck 0x22436c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:02 endless gjs[5412]: Allocating size to EknCard_Deck 0x1cf0880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:02 endless gjs[5412]: Allocating size to EknCard_Deck 0x1cf0a40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:02 endless gjs[5412]: Allocating size to EknCard_Deck 0x1cf0c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:02 endless gjs[5412]: Allocating size to EknCard_Deck 0x1cf0dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:09 endless gjs[5412]: Allocating size to EknCard_Default 0xfa9f6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:09 endless gjs[5412]: Allocating size to EknCard_Default 0xfb57180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:09 endless gjs[5412]: Allocating size to EknCard_Default 0xfb57c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:09 endless gjs[5412]: Allocating size to EknCard_Default 0xfcab6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:09 endless gjs[5412]: Allocating size to EknCard_Default 0xfcd0180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:09 endless gjs[5412]: Allocating size to EknCard_Default 0xfcd0c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:09 endless gjs[5412]: Allocating size to EknCard_Default 0xfe0e6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:09 endless gjs[5412]: Allocating size to EknCard_Default 0xfa68c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:09 endless gjs[5412]: Allocating size to EknCard_Default 0x7eeb180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:09 endless gjs[5412]: Allocating size to EknCard_Default 0x7eebc00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:09 endless gjs[5412]: Allocating size to EknCard_Default 0x35d26c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:09 endless gjs[5412]: Allocating size to EknCard_Default 0xf7ca180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:09 endless gjs[5412]: Allocating size to EknCard_Default 0xf7cac00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:09 endless gjs[5412]: Allocating size to EknCard_Default 0xf7f56c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0xf8d3180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0xf8d3c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0xff266c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0xfa68180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0xd4936c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0xd4b9180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0xd4b9c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x7e246c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x7e4a180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x7e4ac00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x7e806c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x7ea1180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x7ea1c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x7ec76c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x345a180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x345ac00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x122ff6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x19099180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x19099c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x11ecf6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x83de180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x83dec00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x11eb56c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x11edc180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x11edcc00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0x11f0b6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0xdd57180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0xdd57c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0xfa9f6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xfa7f6f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:10 endless gjs[5412]: Allocating size to EknCard_Default 0xfb57180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xfa7fad0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xfb57c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xfa7feb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xfcab6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xfca6300 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xfcd0180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xfca66e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xfcd0c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xfca6ac0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xfe0e6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xfca6ea0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xfa68c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xfa7f310 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x7eeb180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x36a2ac0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x7eebc00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x36a2ea0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x35d26c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x35cc330 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xf7ca180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x35cc710 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xf7cac00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x35ccaf0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xf7f56c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x35cced0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xf8d3180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xf8ce300 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xf8d3c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xf8ce6e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xff266c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xf8ceac0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xfa68180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xf8ceea0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xd4936c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xd48f320 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xd4b9180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xd48f700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xd4b9c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xd48fae0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x7e246c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xd48fec0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x7e4a180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x7e45340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x7e4ac00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x7e45720 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x7e806c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x7e45b00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x7ea1180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x7e45ee0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x7ea1c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x36a2300 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x7ec76c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x36a26e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x345a180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x11eeeb00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x345ac00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x11eeeee0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x122ff6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x122fb320 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x19099180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x122fb700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x19099c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x122fbae0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x11ecf6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x122fbec0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x83de180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x83da330 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x83dec00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x83da710 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x11eb56c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x83daaf0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x11edc180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x83daed0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x11edcc00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x11eee340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0x11f0b6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x11eee720 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xdd57180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x8ae1b00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xdd57c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x8ae1ee0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EknCard_Default 0xfa9f6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:11 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xfa7f6f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xfb57180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xfa7fad0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xfb57c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xfa7feb0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xfcab6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xfca6300 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xfcd0180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xfca66e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xfcd0c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xfca6ac0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xfe0e6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xfca6ea0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xfa68c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xfa7f310 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x7eeb180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x36a2ac0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x7eebc00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x36a2ea0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x35d26c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x35cc330 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xf7ca180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x35cc710 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xf7cac00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x35ccaf0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xf7f56c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x35cced0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xf8d3180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xf8ce300 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xf8d3c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xf8ce6e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xff266c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xf8ceac0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xfa68180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xf8ceea0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xd4936c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xd48f320 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xd4b9180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xd48f700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0xd4b9c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xd48fae0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x7e246c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0xd48fec0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x7e4a180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x7e45340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x7e4ac00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x7e45720 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x7e806c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x7e45b00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x7ea1180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x7e45ee0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x7ea1c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x36a2300 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x7ec76c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x36a26e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x345a180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x11eeeb00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x345ac00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x11eeeee0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x19099c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x122fbae0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x11ecf6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x122fbec0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x83de180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x83da330 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x83dec00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x83da710 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x11eb56c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x83daaf0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x11edc180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x83daed0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x11edcc00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x11eee340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EknCard_Default 0x11f0b6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:12 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x11eee720 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:16 endless xdg-document-portal[3910]: unique: 20, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:05:16 endless xdg-document-portal[3910]: unique: 20, success, outsize: 96 Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:18 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:19 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:20 endless gjs[5412]: Allocating size to EknCard_Default 0x83dec00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:20 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x83da710 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:20 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x83da710 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:21 endless gjs[5412]: Allocating size to EknCard_Default 0x83dec00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:21 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x83da710 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:21 endless gjs[5412]: Allocating size to EknCard_Default 0x83de180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:21 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x83da330 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:21 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x83da710 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:21 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x83da330 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:21 endless gjs[5412]: Allocating size to EmeusConstraintLayout 0x83da330 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:05:38 endless gjs[5412]: gtk_accessible_get_widget: assertion 'GTK_IS_ACCESSIBLE (accessible)' failed Nov 16 22:05:38 endless gjs[5412]: gtk_accessible_get_widget: assertion 'GTK_IS_ACCESSIBLE (accessible)' failed Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:05:39 endless gjs[5412]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most 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. Nov 16 22:06:16 endless xdg-document-portal[3910]: unique: 21, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:06:16 endless xdg-document-portal[3910]: unique: 21, success, outsize: 96 Nov 16 22:06:23 endless systemd-journald[350]: Suppressed 1292 messages from /user.slice/user-1001.slice Nov 16 22:06:23 endless gjs[5353]: gtk_accessible_get_widget: assertion 'GTK_IS_ACCESSIBLE (accessible)' failed Nov 16 22:06:23 endless gjs[5353]: gtk_accessible_get_widget: assertion 'GTK_IS_ACCESSIBLE (accessible)' failed Nov 16 22:06:29 endless dbus-daemon[2243]: Activating service name='com.endlessm.cooking.en' Nov 16 22:06:29 endless dbus-daemon[2243]: Activating service name='com.endlessm.Speedwagon' Nov 16 22:06:29 endless dbus-daemon[2243]: Successfully activated service 'com.endlessm.Speedwagon' Nov 16 22:06:29 endless systemd[2202]: Started flatpak-com.endlessm.cooking.en-5798.scope. Nov 16 22:06:29 endless xdg-document-portal[3910]: unique: 22, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 5815 Nov 16 22:06:29 endless xdg-document-portal[3910]: unique: 22, success, outsize: 120 Nov 16 22:06:29 endless xdg-document-portal[3910]: unique: 23, opcode: LOOKUP (1), nodeid: 1, insize: 47, pid: 5815 Nov 16 22:06:29 endless xdg-document-portal[3910]: unique: 23, success, outsize: 144 Nov 16 22:06:29 endless xdg-document-portal[3910]: unique: 24, opcode: LOOKUP (1), nodeid: 2, insize: 64, pid: 5815 Nov 16 22:06:29 endless xdg-document-portal[3910]: unique: 24, success, outsize: 144 Nov 16 22:06:30 endless dbus-daemon[2243]: Successfully activated service 'com.endlessm.cooking.en' Nov 16 22:06:46 endless gjs[5817]: Allocating size to EmeusConstraintLayout 0x16f8ec0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:06:46 endless gjs[5817]: Allocating size to EmeusConstraintLayout 0x16f8ae0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:06:46 endless gjs[5817]: Allocating size to EmeusConstraintLayout 0x16f8700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:06:46 endless gjs[5817]: Allocating size to EmeusConstraintLayout 0x16f8320 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:06:46 endless gjs[5817]: Allocating size to EmeusConstraintLayout 0x16f8ec0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:06:46 endless gjs[5817]: Allocating size to EmeusConstraintLayout 0x16f8ae0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:06:46 endless gjs[5817]: Allocating size to EmeusConstraintLayout 0x16f8700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:06:46 endless gjs[5817]: Allocating size to EmeusConstraintLayout 0x16f8320 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:06:48 endless gjs[5817]: Allocating size to EmeusConstraintLayout 0x16f8700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:06:49 endless gjs[5817]: Allocating size to EmeusConstraintLayout 0x16f8ec0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:06:49 endless gjs[5817]: Allocating size to EmeusConstraintLayout 0x16f8ae0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:06:49 endless gjs[5817]: Allocating size to EmeusConstraintLayout 0x16f8700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:06:49 endless gjs[5817]: Allocating size to EmeusConstraintLayout 0x16f8320 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Nov 16 22:06:58 endless gst-plugin-scan[5870]: Failed to load plugin '/usr/lib/gstreamer-1.0/libgstdataurisrc.so': /usr/lib/gstreamer-1.0/libgstdataurisrc.so: file too short Nov 16 22:07:16 endless xdg-document-portal[3910]: unique: 25, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:07:16 endless xdg-document-portal[3910]: unique: 25, success, outsize: 96 Nov 16 22:08:16 endless xdg-document-portal[3910]: unique: 26, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:08:16 endless xdg-document-portal[3910]: unique: 26, success, outsize: 96 Nov 16 22:08:17 endless gjs[5817]: gtk_accessible_get_widget: assertion 'GTK_IS_ACCESSIBLE (accessible)' failed Nov 16 22:08:17 endless gjs[5817]: gtk_accessible_get_widget: assertion 'GTK_IS_ACCESSIBLE (accessible)' failed Nov 16 22:08:24 endless dbus-daemon[2243]: Activating service name='org.gnome.ControlCenter.SearchProvider' Nov 16 22:08:24 endless dbus-daemon[2243]: Activating service name='com.endlessm.EknServices.SearchProviderV1' Nov 16 22:08:24 endless dbus-daemon[2243]: Activating service name='org.gnome.Calculator.SearchProvider' Nov 16 22:08:24 endless dbus-daemon[2243]: Activating service name='org.gnome.Contacts.SearchProvider' Nov 16 22:08:24 endless dbus-daemon[2243]: Activating service name='org.gnome.Yelp.SearchProvider' Nov 16 22:08:24 endless dbus-daemon[2243]: Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' Nov 16 22:08:24 endless systemd[2202]: Starting GNOME Terminal Server... Nov 16 22:08:24 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Calculator.SearchProvider' Nov 16 22:08:24 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.ControlCenter.SearchProvider' Nov 16 22:08:24 endless systemd[2202]: Started flatpak-com.endlessm.EknServices-5987.scope. Nov 16 22:08:24 endless xdg-document-portal[3910]: unique: 27, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 6005 Nov 16 22:08:24 endless xdg-document-portal[3910]: unique: 27, success, outsize: 120 Nov 16 22:08:24 endless xdg-document-portal[3910]: unique: 28, opcode: LOOKUP (1), nodeid: 1, insize: 47, pid: 6005 Nov 16 22:08:24 endless xdg-document-portal[3910]: unique: 28, success, outsize: 144 Nov 16 22:08:24 endless xdg-document-portal[3910]: unique: 29, opcode: LOOKUP (1), nodeid: 2, insize: 65, pid: 6005 Nov 16 22:08:24 endless xdg-document-portal[3910]: unique: 29, success, outsize: 144 Nov 16 22:08:24 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Terminal' Nov 16 22:08:24 endless systemd[2202]: Started GNOME Terminal Server. Nov 16 22:08:25 endless dbus-daemon[2243]: Successfully activated service 'com.endlessm.EknServices.SearchProviderV1' Nov 16 22:08:25 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Contacts.SearchProvider' Nov 16 22:08:25 endless gnome-contacts-[5993]: contacts-store.vala:335: Unable to check accounts caps The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files Nov 16 22:08:25 endless gnome-contacts-[5993]: backend-store.vala:434: Error preparing Backend 'telepathy': The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files Nov 16 22:08:25 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Yelp.SearchProvider' Nov 16 22:08:25 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=budge on plugin=flatpak on apps system/flatpak/flathub/desktop/fr.free.Homebank.desktop/stable,system/flatpak/eos-apps/desktop/com.endlessm.finance.desktop/eos3 took 39ms Nov 16 22:08:25 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=budget on plugin=flatpak on apps system/flatpak/flathub/desktop/fr.free.Homebank.desktop/stable,system/flatpak/eos-apps/desktop/com.endlessm.finance.desktop/eos3 took 31ms Nov 16 22:08:26 endless dbus-daemon[2243]: Activating service name='com.endlessm.finance' Nov 16 22:08:26 endless dbus-daemon[2243]: Activating service name='com.endlessm.Speedwagon' Nov 16 22:08:26 endless dbus-daemon[2243]: Successfully activated service 'com.endlessm.Speedwagon' Nov 16 22:08:26 endless systemd[2202]: Started flatpak-com.endlessm.finance-6042.scope. Nov 16 22:08:26 endless xdg-document-portal[3910]: unique: 30, opcode: LOOKUP (1), nodeid: 2, insize: 61, pid: 6049 Nov 16 22:08:26 endless xdg-document-portal[3910]: unique: 30, success, outsize: 144 Nov 16 22:08:26 endless dbus-daemon[2243]: Successfully activated service 'com.endlessm.finance' Nov 16 22:08:57 endless systemd[1]: Starting Cleanup of Temporary Directories... Nov 16 22:08:57 endless systemd[1]: Started Cleanup of Temporary Directories. Nov 16 22:09:07 endless org.freedesktop.portal.Desktop[2243]: handle open uri: file:///run/user/1001/doc/485dfff5/Monthly_personal_budget.ots 0 Nov 16 22:09:07 endless org.freedesktop.portal.Desktop[2243]: content type: application/vnd.oasis.opendocument.spreadsheet-template scheme: file Nov 16 22:09:07 endless xdg-document-portal[3910]: unique: 31, opcode: LOOKUP (1), nodeid: 1, insize: 49, pid: 6074 Nov 16 22:09:07 endless xdg-document-portal[3910]: unique: 31, success, outsize: 144 Nov 16 22:09:07 endless xdg-document-portal[3910]: unique: 32, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6074 Nov 16 22:09:07 endless xdg-document-portal[3910]: unique: 32, success, outsize: 144 Nov 16 22:09:07 endless xdg-document-portal[3910]: unique: 33, opcode: GETATTR (3), nodeid: 11, insize: 56, pid: 6074 Nov 16 22:09:07 endless xdg-document-portal[3910]: unique: 33, success, outsize: 120 Nov 16 22:09:07 endless xdg-desktop-por[5367]: Error updating permission store: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for application/vnd.oasis.opendocument.spreadsheet-template Nov 16 22:09:07 endless org.freedesktop.portal.Desktop[2243]: use first: 1 always ask 1, first choice: libreoffice-calc, latest count 0 threshold: 2147483647 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 34, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 34, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 35, opcode: ACCESS (34), nodeid: 11, insize: 48, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 35, success, outsize: 16 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 36, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 36, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 37, opcode: GETATTR (3), nodeid: 11, insize: 56, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 37, success, outsize: 120 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 38, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 38, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 39, opcode: OPEN (14), nodeid: 11, insize: 48, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 39, error: -13 (Permission denied), outsize: 16 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 40, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 40, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 41, opcode: ACCESS (34), nodeid: 11, insize: 48, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 41, success, outsize: 16 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 42, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 42, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 43, opcode: GETATTR (3), nodeid: 11, insize: 56, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 43, success, outsize: 120 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 44, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 44, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 45, opcode: ACCESS (34), nodeid: 11, insize: 48, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 45, success, outsize: 16 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 46, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 46, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 47, opcode: GETATTR (3), nodeid: 11, insize: 56, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 47, success, outsize: 120 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 48, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 48, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 49, opcode: OPEN (14), nodeid: 11, insize: 48, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 49, success, outsize: 32 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 50, opcode: GETATTR (3), nodeid: 11, insize: 56, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 50, success, outsize: 120 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 51, opcode: READ (15), nodeid: 11, insize: 80, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 51, success, outsize: 16400 (splice) Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 52, opcode: GETATTR (3), nodeid: 11, insize: 56, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 52, success, outsize: 120 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 53, opcode: READ (15), nodeid: 11, insize: 80, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 53, success, outsize: 1566 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 54, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 54, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 55, opcode: ACCESS (34), nodeid: 11, insize: 48, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 55, success, outsize: 16 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 56, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 56, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 57, opcode: GETATTR (3), nodeid: 11, insize: 56, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 57, success, outsize: 120 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 58, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 58, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 59, opcode: ACCESS (34), nodeid: 11, insize: 48, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 59, success, outsize: 16 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 60, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 60, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 61, opcode: GETATTR (3), nodeid: 11, insize: 56, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 61, success, outsize: 120 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 62, opcode: ACCESS (34), nodeid: 11, insize: 48, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 62, error: -13 (Permission denied), outsize: 16 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 63, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 63, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 64, opcode: ACCESS (34), nodeid: 11, insize: 48, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 64, success, outsize: 16 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 65, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 65, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 66, opcode: ACCESS (34), nodeid: 11, insize: 48, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 66, success, outsize: 16 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 67, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 67, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 68, opcode: GETATTR (3), nodeid: 11, insize: 56, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 68, success, outsize: 120 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 69, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 69, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 70, opcode: ACCESS (34), nodeid: 11, insize: 48, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 70, success, outsize: 16 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 71, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 71, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 72, opcode: GETATTR (3), nodeid: 11, insize: 56, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 72, success, outsize: 120 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 73, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 73, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 74, opcode: ACCESS (34), nodeid: 11, insize: 48, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 74, success, outsize: 16 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 75, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 75, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 76, opcode: GETATTR (3), nodeid: 11, insize: 56, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 76, success, outsize: 120 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 77, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 77, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 78, opcode: GETATTR (3), nodeid: 11, insize: 56, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 78, success, outsize: 120 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 79, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 79, success, outsize: 144 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 80, opcode: OPEN (14), nodeid: 11, insize: 48, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 80, success, outsize: 32 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 81, opcode: GETATTR (3), nodeid: 11, insize: 56, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 81, success, outsize: 120 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 82, opcode: READ (15), nodeid: 11, insize: 80, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 82, success, outsize: 17950 (splice) Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 83, opcode: FLUSH (25), nodeid: 11, insize: 64, pid: 6119 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 83, error: -38 (Function not implemented), outsize: 16 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 84, opcode: RELEASE (18), nodeid: 11, insize: 64, pid: 0 Nov 16 22:09:11 endless xdg-document-portal[3910]: unique: 84, success, outsize: 16 Nov 16 22:09:11 endless gnome-shell[2347]: g_variant_new_string: assertion 'string != NULL' failed Nov 16 22:09:12 endless xdg-document-portal[3910]: unique: 85, opcode: LOOKUP (1), nodeid: 9, insize: 68, pid: 6119 Nov 16 22:09:12 endless xdg-document-portal[3910]: unique: 85, success, outsize: 144 Nov 16 22:09:12 endless xdg-document-portal[3910]: unique: 86, opcode: ACCESS (34), nodeid: 11, insize: 48, pid: 6119 Nov 16 22:09:12 endless xdg-document-portal[3910]: unique: 86, success, outsize: 16 Nov 16 22:09:16 endless xdg-document-portal[3910]: unique: 87, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:09:16 endless xdg-document-portal[3910]: unique: 87, success, outsize: 96 Nov 16 22:09:16 endless xdg-document-portal[3910]: unique: 88, opcode: RELEASE (18), nodeid: 11, insize: 64, pid: 0 Nov 16 22:09:16 endless xdg-document-portal[3910]: unique: 88, success, outsize: 16 Nov 16 22:09:49 endless dbus-daemon[2243]: Activating service name='org.gnome.ControlCenter.SearchProvider' Nov 16 22:09:49 endless dbus-daemon[2243]: Activating service name='com.endlessm.EknServices.SearchProviderV1' Nov 16 22:09:49 endless dbus-daemon[2243]: Activating service name='org.gnome.Calculator.SearchProvider' Nov 16 22:09:49 endless dbus-daemon[2243]: Activating service name='org.gnome.Contacts.SearchProvider' Nov 16 22:09:49 endless dbus-daemon[2243]: Activating service name='org.gnome.Yelp.SearchProvider' Nov 16 22:09:49 endless dbus-daemon[2243]: Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' Nov 16 22:09:49 endless systemd[2202]: Starting GNOME Terminal Server... Nov 16 22:09:49 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Calculator.SearchProvider' Nov 16 22:09:49 endless systemd[2202]: Started flatpak-com.endlessm.EknServices-6167.scope. Nov 16 22:09:49 endless xdg-document-portal[3910]: unique: 89, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 6185 Nov 16 22:09:49 endless xdg-document-portal[3910]: unique: 89, success, outsize: 120 Nov 16 22:09:49 endless xdg-document-portal[3910]: unique: 90, opcode: LOOKUP (1), nodeid: 1, insize: 47, pid: 6185 Nov 16 22:09:49 endless xdg-document-portal[3910]: unique: 90, success, outsize: 144 Nov 16 22:09:49 endless xdg-document-portal[3910]: unique: 91, opcode: LOOKUP (1), nodeid: 2, insize: 65, pid: 6185 Nov 16 22:09:49 endless xdg-document-portal[3910]: unique: 91, success, outsize: 144 Nov 16 22:09:49 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.ControlCenter.SearchProvider' Nov 16 22:09:49 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Terminal' Nov 16 22:09:49 endless systemd[2202]: Started GNOME Terminal Server. Nov 16 22:09:49 endless dbus-daemon[2243]: Successfully activated service 'com.endlessm.EknServices.SearchProviderV1' Nov 16 22:09:50 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Contacts.SearchProvider' Nov 16 22:09:50 endless gnome-contacts-[6174]: contacts-store.vala:335: Unable to check accounts caps The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files Nov 16 22:09:50 endless gnome-contacts-[6174]: backend-store.vala:434: Error preparing Backend 'telepathy': The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files Nov 16 22:09:50 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Yelp.SearchProvider' Nov 16 22:09:50 endless gnome-software[2599]: Kind change on org.gtk.Gtk3theme.Pop-light from runtime to generic is not OK Nov 16 22:09:50 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=system on plugin=flatpak on apps system/flatpak/flathub/desktop/ca._0ldsk00l.Nestopia.desktop/stable,system/flatpak/flathub/runtime/org.gtk.Gtk3theme.Pop-light/3.22,system/*/*/desktop/gnome-system-monitor.desktop/*,system/*/*/desktop/gnome-system-monitor-kde.desktop/*,system/*/*/desktop/org.gnome.font-viewer.desktop/*,system/*/*/desktop/org.gnome.Logs.desktop/* took 57ms Nov 16 22:09:51 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=system u on plugin=flatpak on apps system/flatpak/flathub/desktop/ca._0ldsk00l.Nestopia.desktop/stable,system/flatpak/flathub/runtime/org.gtk.Gtk3theme.Pop-light/3.22,system/*/*/desktop/gnome-system-monitor.desktop/*,system/*/*/desktop/gnome-system-monitor-kde.desktop/*,system/*/*/desktop/org.gnome.font-viewer.desktop/*,system/*/*/desktop/org.gnome.Logs.desktop/* took 43ms Nov 16 22:09:52 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=system upd on plugin=flatpak took 14ms Nov 16 22:09:53 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=system update on plugin=flatpak took 6ms Nov 16 22:09:53 endless gnome-shell[2347]: Failed to set the markup of the actor 'ClutterText': Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as & Nov 16 22:09:55 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=system updat on plugin=flatpak took 6ms Nov 16 22:09:56 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=system on plugin=flatpak on apps system/flatpak/flathub/desktop/ca._0ldsk00l.Nestopia.desktop/stable,system/flatpak/flathub/runtime/org.gtk.Gtk3theme.Pop-light/3.22,system/*/*/desktop/gnome-system-monitor.desktop/*,system/*/*/desktop/gnome-system-monitor-kde.desktop/*,system/*/*/desktop/org.gnome.font-viewer.desktop/*,system/*/*/desktop/org.gnome.Logs.desktop/* took 41ms Nov 16 22:09:56 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=syst on plugin=flatpak on apps system/flatpak/flathub/desktop/ca._0ldsk00l.Nestopia.desktop/stable,system/flatpak/flathub/runtime/org.gtk.Gtk3theme.Pop-light/3.22,system/*/*/desktop/gnome-system-monitor.desktop/*,system/*/*/desktop/gnome-system-monitor-kde.desktop/*,system/*/*/desktop/org.gnome.font-viewer.desktop/*,system/*/*/desktop/org.gnome.Logs.desktop/* took 53ms Nov 16 22:09:58 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=upd on plugin=flatpak on apps system/flatpak/eos-apps/desktop/org.kde.Kigo.desktop/eos3 took 271ms Nov 16 22:09:58 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=upda on plugin=flatpak on apps system/flatpak/eos-apps/desktop/org.kde.Kigo.desktop/eos3 took 37ms Nov 16 22:09:59 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=update on plugin=flatpak on apps system/flatpak/eos-apps/desktop/org.kde.Kigo.desktop/eos3 took 99ms Nov 16 22:09:59 endless gnome-shell[2347]: Failed to set the markup of the actor 'ClutterText': Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as & Nov 16 22:10:01 endless dbus-daemon[2243]: Activating service name='org.gnome.Calculator.SearchProvider' Nov 16 22:10:01 endless dbus-daemon[2243]: Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' Nov 16 22:10:01 endless systemd[2202]: Starting GNOME Terminal Server... Nov 16 22:10:01 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Calculator.SearchProvider' Nov 16 22:10:01 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=updat on plugin=flatpak on apps system/flatpak/eos-apps/desktop/org.kde.Kigo.desktop/eos3 took 61ms Nov 16 22:10:01 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Terminal' Nov 16 22:10:01 endless systemd[2202]: Started GNOME Terminal Server. Nov 16 22:10:02 endless gnome-shell[2347]: Received error from DBus search provider org.gnome.Yelp.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.142 was not provided by any .service files Nov 16 22:10:03 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=set on plugin=flatpak took 5ms Nov 16 22:10:03 endless dbus-daemon[2243]: Activating service name='org.gnome.Yelp.SearchProvider' Nov 16 22:10:03 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=settin on plugin=flatpak took 4ms Nov 16 22:10:03 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Yelp.SearchProvider' Nov 16 22:10:03 endless gnome-shell[2347]: Failed to set the markup of the actor 'ClutterText': Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as & Nov 16 22:10:04 endless gnome-shell[2347]: Failed to set the markup of the actor 'ClutterText': Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as & Nov 16 22:10:04 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=settings on plugin=flatpak took 4ms Nov 16 22:10:12 endless dbus[578]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Nov 16 22:10:12 endless systemd[1]: Starting Hostname Service... Nov 16 22:10:12 endless dbus[578]: [system] Successfully activated service 'org.freedesktop.hostname1' Nov 16 22:10:12 endless systemd[1]: Started Hostname Service. Nov 16 22:10:12 endless xdg-document-portal[3910]: unique: 92, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 6293 Nov 16 22:10:12 endless xdg-document-portal[3910]: unique: 92, success, outsize: 96 Nov 16 22:10:16 endless xdg-document-portal[3910]: unique: 93, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:10:16 endless xdg-document-portal[3910]: unique: 93, success, outsize: 96 Nov 16 22:10:17 endless eos-updater[2465]: Changing to state Polling Nov 16 22:10:17 endless eos-updater[2465]: Using product branch os/eos/amd64/eos3 Nov 16 22:10:18 endless eos-updater[2465]: libostree HTTP error from remote eos for : Server returned status 404: Not Found Nov 16 22:10:19 endless eos-updater[2465]: libostree pull from 'eos' for os/eos/amd64/eos3 complete security: GPG: commit http: TLS non-delta: meta: 4 content: 0 transfer: secs: 1 size: 4.2 MB Nov 16 22:10:20 endless eos-updater[2465]: Using product branch os/eos/amd64/eos3 Nov 16 22:10:20 endless eos-updater[2465]: Recording metric event 99f48aac-b5a0-426d-95f4-18af7d081c4e: (Acer, TMP645-MG, os/eos/amd64/eos3) Nov 16 22:10:20 endless eos-updater[2465]: Changing to state UpdateAvailable Nov 16 22:10:22 endless eos-updater[2465]: Changing to state Fetching Nov 16 22:10:22 endless eos-updater[2465]: Fetch: eos:os/eos/amd64/eos3 resolved to: ed6c4ba1f16b358cddcb7cb0644f1f408bf307e1be25f7c7e5539bff1e298cdc Nov 16 22:10:22 endless eos-updater[2465]: libostree HTTP error from remote eos for : Server returned status 404: Not Found Nov 16 22:10:40 endless systemd[1]: Started Endless OS Automatic Updater. Nov 16 22:10:40 endless eos-autoupdater[6344]: EOS updater state is: Fetching Nov 16 22:10:56 endless eos-link-youtube.desktop[6365]: This tool has been deprecated, use 'gio open' instead. Nov 16 22:10:56 endless eos-link-youtube.desktop[6365]: See 'gio help open' for more info. Nov 16 22:10:56 endless dbus-daemon[2243]: Activating service name='com.endlessm.Speedwagon' Nov 16 22:10:56 endless dbus-daemon[2243]: Successfully activated service 'com.endlessm.Speedwagon' Nov 16 22:10:57 endless eos-link-youtube.desktop[6365]: Found default browser: Google Chrome Nov 16 22:10:57 endless eos-link-youtube.desktop[6365]: Chrome set as the default application and available. Selecting... Nov 16 22:10:57 endless eos-link-youtube.desktop[6365]: Using eos-google-chrome to launch web application (config dir: /sysroot/home/jeremy/.config/chrome-appmode////www.youtube.com)... Nov 16 22:10:57 endless eos-link-youtube.desktop[6365]: INFO:root:Found flatpak launcher for Google Chrome: '/var/lib/flatpak/app/com.google.Chrome/x86_64/eos3/3c53c34fbc70a8e845830056da453003619b9c3fcc7477766b67e4a6078f8fc2/files/bin/eos-google-chrome-app' Nov 16 22:10:57 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[6379]: Found flatpak launcher for Google Chrome: '/var/lib/flatpak/app/com.google.Chrome/x86_64/eos3/3c53c34fbc70a8e845830056da453003619b9c3fcc7477766b67e4a6078f8fc2/files/bin/eos-google-chrome-app' Nov 16 22:10:57 endless eos-link-youtube.desktop[6365]: INFO:root:Flatpak launcher for Chrome found. Launching... Nov 16 22:10:57 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[6379]: Flatpak launcher for Chrome found. Launching... Nov 16 22:10:57 endless eos-link-youtube.desktop[6365]: INFO:root:Running Google Chrome launcher with PID 6383 Nov 16 22:10:57 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[6379]: Running Google Chrome launcher with PID 6383 Nov 16 22:10:58 endless systemd[2202]: Started flatpak-com.google.Chrome-6386.scope. Nov 16 22:10:58 endless xdg-document-portal[3910]: unique: 94, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 6401 Nov 16 22:10:58 endless xdg-document-portal[3910]: unique: 94, success, outsize: 120 Nov 16 22:10:58 endless xdg-document-portal[3910]: unique: 95, opcode: LOOKUP (1), nodeid: 1, insize: 47, pid: 6401 Nov 16 22:10:58 endless xdg-document-portal[3910]: unique: 95, success, outsize: 144 Nov 16 22:10:58 endless xdg-document-portal[3910]: unique: 96, opcode: LOOKUP (1), nodeid: 2, insize: 58, pid: 6401 Nov 16 22:10:58 endless xdg-document-portal[3910]: unique: 96, success, outsize: 144 Nov 16 22:10:58 endless eos-link-youtube.desktop[6365]: /sysroot/flatpak/app/com.google.Chrome/x86_64/eos3/3c53c34fbc70a8e845830056da453003619b9c3fcc7477766b67e4a6078f8fc2/files/extra/opt/google/chrome/nacl_helper: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory Nov 16 22:10:58 endless eos-link-youtube.desktop[6365]: [1:1:1116/221058.482440:ERROR:nacl_fork_delegate_linux.cc(315)] Bad NaCl helper startup ack (0 bytes) Nov 16 22:10:59 endless eos-link-youtube.desktop[6365]: [6387:6387:1116/221059.147875:ERROR:configuration_policy_handler_list.cc(92)] Unknown policy: ExtensionInstallForceList Nov 16 22:10:59 endless eos-link-youtube.desktop[6365]: [6387:6387:1116/221059.473218:ERROR:configuration_policy_handler_list.cc(92)] Unknown policy: ExtensionInstallForceList Nov 16 22:10:59 endless gnome-keyring-daemon[2209]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered Nov 16 22:11:07 endless gnome-software[2599]: failed to rescan: Failed to parse /sysroot/home/jeremy/.local/share/applications/chrome-aohghmighlieiainnegkcijnfilokake-Default.desktop file: cannot process file of type application/x-desktop Nov 16 22:11:08 endless gnome-software[2599]: failed to rescan: Failed to parse /sysroot/home/jeremy/.local/share/applications/chrome-apdfllckaahabafndbhieahigkjlhalf-Default.desktop file: cannot process file of type application/x-desktop Nov 16 22:11:08 endless gnome-software[2599]: failed to rescan: Failed to parse /sysroot/home/jeremy/.local/share/applications/chrome-blpcfgokakmgnkcojhhkbfbldkacnbeo-Default.desktop file: cannot process file of type application/x-desktop Nov 16 22:11:08 endless gnome-software[2599]: failed to rescan: Failed to parse /sysroot/home/jeremy/.local/share/applications/chrome-pjkljhegncpnkpknbcohdijeoejaedia-Default.desktop file: cannot process file of type application/x-desktop Nov 16 22:11:11 endless eos-updater[2465]: libostree pull from 'eos' for 0 refs complete security: GPG: commit http: TLS non-delta: meta: 1598 content: 7127 transfer: secs: 49 size: 268.7 MB Nov 16 22:11:11 endless eos-updater[2465]: Fetch: pull() completed Nov 16 22:11:11 endless eos-updater[2465]: Fetch: commit ed6c4ba1f16b358cddcb7cb0644f1f408bf307e1be25f7c7e5539bff1e298cdc cached Nov 16 22:11:11 endless eos-updater[2465]: Changing to state UpdateReady Nov 16 22:11:11 endless eos-autoupdater[6344]: EOS updater state is: UpdateReady Nov 16 22:11:11 endless eos-updater[2465]: Changing to state ApplyUpdate Nov 16 22:11:11 endless eos-autoupdater[6344]: EOS updater state is: ApplyUpdate Nov 16 22:11:11 endless gnome-control-c[6287]: Failed to call Apply() on EOS updater: GDBus.Error:com.endlessm.Updater.Error.WrongState: Can't call Apply() while in state ApplyUpdate Nov 16 22:11:12 endless gnome-software[2599]: running get-categories with timeout=60 on plugin=flatpak took 94ms Nov 16 22:11:12 endless gnome-software[2599]: running get-distro-updates with refine-flags=require-version,require-setup-action,require-update-details,require-upgrade-removed,require-provenance,require-icon with failure-flags=use-events with timeout=60 on plugin=appstream took 21ms Nov 16 22:11:12 endless gnome-software[2599]: running refine with refine-flags=require-version,require-update-details,require-provenance,require-icon with failure-flags=fatal-any with timeout=60 took 71ms Nov 16 22:11:12 endless gnome-software[2599]: running refine with refine-flags=require-license,require-url,require-size,require-version,require-history,require-setup-action,require-origin,require-menu-path,require-addons,require-provenance,require-icon,require-permissions,require-origin-hostname,require-runtime,require-screenshots with failure-flags=use-events with timeout=60 on apps system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 took 102ms Nov 16 22:11:12 endless gnome-software[2599]: running refine with refine-flags=require-rating,require-reviews,require-review-ratings with failure-flags=use-events with timeout=60 on apps system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 took 35ms Nov 16 22:11:13 endless gnome-software[2599]: running get-installed with refine-flags=require-license,require-description,require-size,require-rating,require-version,require-history,require-setup-action,require-origin,require-provenance,require-icon,require-permissions,require-origin-hostname,require-runtime with timeout=60 on plugin=flatpak on apps system/*/*/desktop/org.gnome.Nautilus.desktop/*,system/*/*/desktop/rhythmbox.desktop/*,system/*/*/desktop/gnome-system-monitor.desktop/*,system/*/*/desktop/simple-scan.desktop/*,system/*/*/desktop/org.gnome.font-viewer.desktop/*,system/*/*/desktop/eog.desktop/*,system/*/*/desktop/org.gnome.Cheese.desktop/*,system/*/*/desktop/org.gnome.clocks.desktop/*,system/*/*/desktop/org.gnome.Logs.desktop/*,system/*/*/desktop/evolution.desktop/*,system/*/*/desktop/brasero.desktop/*,system/*/*/desktop/gnome-calculator.desktop/*,system/*/*/desktop/gnome-control-center.desktop/*,system/*/*/desktop/shotwell.desktop/*,system/*/*/desktop/org.gnome.Totem.desktop/*,system/*/*/desktop/evince.desktop/*,system/*/*/desktop/vinagre.desktop/*,system/*/*/desktop/org.gnome.Screenshot.desktop/*,system/*/*/desktop/org.gnome.gedit.desktop/*,system/*/*/desktop/org.gnome.Terminal.desktop/*,system/*/*/desktop/org.gnome.FileRoller.desktop/*,system/*/*/desktop/org.gnome.DiskUtility.desktop/*,system/*/*/desktop/org.gnome.Contacts.desktop/*,system/*/*/desktop/libreoffice-calc.desktop/*,system/*/*/desktop/libreoffice-draw.desktop/*,system/*/*/desktop/libreoffice-base.desktop/*,system/*/*/desktop/libreoffice-writer.desktop/*,system/*/*/desktop/libreoffice-impress.desktop/*,system/*/*/desktop/com.endlessm.Coding.Chatbox.desktop/*,system/*/*/desktop/libreoffice-startcenter.desktop/*,system/package/*/desktop/chromium-browser.desktop/*,system/*/*/desktop/libreoffice-math.desktop/*,system/*/*/desktop/org.gnome.Yelp.desktop/*,system/flatpak/eos-apps/desktop/com.endlessm.animals.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.astronomy.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.biology.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.celebrities.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.cooking.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.dinosaurs.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.disabilities.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.encyclopedia.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.farming.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.finance.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.geography.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.health.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.healthy_teeth.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.history.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.howto.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.maternity.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.math.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.myths.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.photos.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.physics.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.programming_guide.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.resume.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.soccer.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.socialsciences.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.textbooks.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.translation.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.travel.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.water_and_sanitation.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.world_literature.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.github.Slingshot.desktop/eos3,system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3,system/flatpak/eos-apps/desktop/com.teeworlds.Teeworlds.desktop/eos3,system/flatpak/eos-apps/desktop/de.billardgl.Billardgl.desktop/eos3,system/flatpak/eos-apps/desktop/io.github.Supertux.desktop/eos3,system/flatpak/eos-apps/desktop/net.blockout.Blockout2.desktop/eos3,system/flatpak/eos-apps/desktop/net.gcompris.Gcompris.desktop/eos3,system/flatpak/eos-apps/desktop/net.minetest.Minetest.desktop/eos3,system/flatpak/eos-apps/desktop/net.olofson.Kobodeluxe.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Atanks.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Audacity.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Btanks.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.ChromiumBSU.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Extremetuxracer.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Rili.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Supertuxkart.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Torcs.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Tuxfootball.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Warmux.desktop/eos3,system/flatpak/eos-apps/desktop/net.wz2100.Warzone2100.desktop/eos3,system/flatpak/eos-apps/desktop/org.armagetronad.Armagetronad.desktop/eos3,system/flatpak/eos-apps/desktop/org.debian.Tuxpuck.desktop/eos3,system/flatpak/eos-apps/desktop/org.debian.alioth.tux4kids.Tuxmath.desktop/eos3,system/flatpak/eos-apps/desktop/org.debian.alioth.tux4kids.Tuxtype.desktop/eos3,system/flatpak/eos-apps/desktop/org.freeciv.Freeciv.desktop/eos3,system/flatpak/eos-apps/desktop/org.frozenbubble.FrozenBubble.desktop/eos3,system/flatpak/eos-apps/desktop/org.gimp.Gimp.desktop/eos3,system/flatpak/eos-apps/desktop/org.gnome.Freecell.desktop/eos3,system/flatpak/eos-apps/desktop/org.gnome.Genius.desktop/eos3,system/flatpak/eos-apps/desktop/org.gnome.Gnote.desktop/eos3,system/flatpak/eos-apps/desktop/org.gnome.Iagno.desktop/eos3,system/flatpak/eos-apps/desktop/org.gnome.Quadrapassel.desktop/eos3,system/flatpak/eos-apps/desktop/org.gnome.Solitaire.desktop/eos3,system/flatpak/eos-apps/desktop/org.gnome.Tetravex.desktop/eos3,system/flatpak/eos-apps/desktop/org.gnome.people.dscorgie.Labyrinth.desktop/eos3,system/flatpak/eos-apps/desktop/org.inkscape.Inkscape.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kalzium.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kapman.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Katomic.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kblocks.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kbounce.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kbruch.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kdiamond.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kgeography.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kgoldrunner.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Khangman.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kigo.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Killbots.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kjumpingcube.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Klines.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Knavalbattle.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Knetwalk.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Ksame.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Ksquares.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Ksudoku.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Ktuberling.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kubrick.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Kwordquiz.desktop/eos3,system/flatpak/eos-apps/desktop/org.kde.Palapeli.desktop/eos3,system/flatpak/eos-apps/desktop/org.maemo.Numptyphysics.desktop/eos3,system/flatpak/eos-apps/desktop/org.marsshooter.Marsshooter.desktop/eos3,system/flatpak/eos-apps/desktop/org.megaglest.MegaGlest.desktop/eos3,system/flatpak/eos-apps/desktop/org.openarena.Openarena.desktop/eos3,system/flatpak/eos-apps/desktop/org.openscad.Openscad.desktop/eos3,system/flatpak/eos-apps/desktop/org.pitivi.Pitivi.desktop/eos3,system/flatpak/eos-apps/desktop/org.seul.Pingus.desktop/eos3,system/flatpak/eos-apps/desktop/org.squeakland.Etoys.desktop/eos3,system/flatpak/eos-apps/desktop/org.squeakland.Scratch.desktop/eos3,system/flatpak/eos-apps/desktop/org.stellarium.Stellarium.desktop/eos3,system/flatpak/eos-apps/desktop/org.sugarlabs.Turtleblocks.desktop/eos3,system/flatpak/eos-apps/desktop/org.tuxfamily.Xmoto.desktop/eos3,system/flatpak/eos-apps/desktop/org.tuxpaint.Tuxpaint.desktop/eos3,system/flatpak/eos-apps/desktop/org.wesnoth.Wesnoth.desktop/eos3,system/flatpak/eos-runtimes/runtime/com.endlessm.Platform/eos3.1,system/flatpak/eos-runtimes/runtime/com.endlessm.Platform/eos3.2,system/flatpak/eos-sdk/runtime/com.endlessm.apps.Platform/1,system/flatpak/gnome/runtime/org.gnome.Platform/3.26 took 978ms Nov 16 22:11:16 endless xdg-document-portal[3910]: unique: 97, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:11:16 endless xdg-document-portal[3910]: unique: 97, success, outsize: 96 Nov 16 22:11:17 endless gnome-software[2599]: invalid cast from 'GsApp' to 'GsFlatpakApp' Nov 16 22:11:17 endless gnome-software[2599]: no source set by appstream for flatpak: GsApp: [0x7ff6180b98f0] kind: runtime state: updatable-live quirk: provenance,is-proxy id: com.endlessm.proxy.EOSUpdatesProxy unique-id: system/*/*/runtime/com.endlessm.proxy.EOSUpdatesProxy/* scope: system kudo-percentage: 0 name: Endless Platform icon-kind: stock icon-name: system-run-symbolic summary: Framework for applications management-plugin: eos reviews: 0 provides: 0 related: system/flatpak/eos-sdk/runtime/com.endlessm.apps.Platform/1 related: system/flatpak/eos-sdk/desktop/com.endlessm.EknServices.desktop/eos3 Nov 16 22:11:17 endless gnome-software[2599]: invalid cast from 'GsApp' to 'GsFlatpakApp' Nov 16 22:11:17 endless gnome-software[2599]: running get-updates with refine-flags=require-version,require-update-details,require-provenance,require-icon with timeout=60 on plugin=eos on apps system/flatpak/gnome/runtime/org.gnome.Platform/3.26,system/*/*/runtime/com.endlessm.proxy.EOSUpdatesProxy/* took 4607ms Nov 16 22:11:17 endless gnome-software[2599]: running get-popular with refine-flags=require-rating,require-origin,require-key-colors,require-icon,require-origin-hostname with failure-flags=use-events with timeout=60 on plugin=eos on apps system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3,system/flatpak/eos-apps/desktop/com.spotify.Client.desktop/eos3,system/flatpak/eos-apps/desktop/com.transmissionbt.Transmission.desktop/eos3,system/flatpak/eos-apps/desktop/com.valvesoftware.Steam.desktop/eos3,system/flatpak/eos-apps/desktop/net.gcompris.Gcompris.desktop/eos3,system/flatpak/eos-apps/desktop/net.minetest.Minetest.desktop/eos3,system/flatpak/eos-apps/desktop/net.sourceforge.Audacity.desktop/eos3,system/flatpak/eos-apps/desktop/org.debian.alioth.tux4kids.Tuxmath.desktop/eos3,system/flatpak/eos-apps/desktop/org.gimp.Gimp.desktop/eos3,system/flatpak/eos-apps/desktop/org.inkscape.Inkscape.desktop/eos3,system/flatpak/eos-apps/desktop/org.mozilla.Firefox.desktop/eos3,system/flatpak/eos-apps/desktop/org.tuxpaint.Tuxpaint.desktop/eos3,system/flatpak/eos-apps/desktop/org.videolan.VLC.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.celebrities.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.physics.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.programming_guide.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.biology.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.astronomy.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.wiki_art.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.geography.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.farming.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.cooking.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.animals.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.finance.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.disabilities.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.textbooks.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.translation.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.resume.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.healthy_teeth.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.travel.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.water_and_sanitation.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.maternity.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.myths.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.socialsciences.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.dinosaurs.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.howto.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.encyclopedia.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.world_literature.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.health.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.soccer.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.history.en.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.photos.desktop/eos3,system/flatpak/eos-apps/desktop/com.endlessm.math.en.desktop/eos3 took 5853ms Nov 16 22:11:24 endless eos-updater[2465]: Copying /etc changes: 15 modified, 0 removed, 15 added Nov 16 22:11:25 endless eos-updater[2465]: Bootloader updated; bootconfig swap: yes deployment count change: 1 Nov 16 22:11:31 endless gnome-keyring-daemon[2209]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered Nov 16 22:12:05 endless eos-updater[2465]: Freed objects: 4.0 MB Nov 16 22:12:05 endless eos-updater[2465]: Changing to state UpdateApplied Nov 16 22:12:05 endless eos-autoupdater[6344]: EOS updater state is: UpdateApplied Nov 16 22:12:05 endless systemd[1]: eos-autoupdater.timer: Adding 22min 11.122267s random time. Nov 16 22:12:16 endless xdg-document-portal[3910]: unique: 98, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:12:16 endless xdg-document-portal[3910]: unique: 98, success, outsize: 96 Nov 16 22:13:16 endless xdg-document-portal[3910]: unique: 99, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:13:16 endless xdg-document-portal[3910]: unique: 99, success, outsize: 96 Nov 16 22:14:16 endless xdg-document-portal[3910]: unique: 100, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:14:16 endless xdg-document-portal[3910]: unique: 100, success, outsize: 96 Nov 16 22:14:33 endless pkexec[7259]: pam_unix(polkit-1:session): session opened for user root by (uid=1001) Nov 16 22:14:33 endless pkexec[7259]: pam_systemd(polkit-1:session): Cannot create session: Already running in a session Nov 16 22:14:33 endless pkexec[7259]: jeremy: Executing command [USER=root] [TTY=unknown] [CWD=/sysroot/home/jeremy] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 937] Nov 16 22:14:37 endless eos-link-youtube.desktop[6365]: [6387:6387:1116/221437.805976:ERROR:media_internals.cc(102)] Cannot get RenderProcessHost Nov 16 22:14:38 endless eos-link-youtube.desktop[6365]: INFO:root:Google Chrome launcher stopped Nov 16 22:14:38 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[6379]: Google Chrome launcher stopped Nov 16 22:14:42 endless dbus-daemon[2243]: Activating service name='com.endlessm.Speedwagon' Nov 16 22:14:42 endless dbus-daemon[2243]: Successfully activated service 'com.endlessm.Speedwagon' Nov 16 22:14:43 endless google-chrome.desktop[7281]: INFO:root:Found flatpak launcher for Google Chrome: '/var/lib/flatpak/app/com.google.Chrome/x86_64/eos3/3c53c34fbc70a8e845830056da453003619b9c3fcc7477766b67e4a6078f8fc2/files/bin/eos-google-chrome-app' Nov 16 22:14:43 endless google-chrome.desktop[7281]: INFO:root:Flatpak launcher for Chrome found. Launching... Nov 16 22:14:43 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[7281]: Found flatpak launcher for Google Chrome: '/var/lib/flatpak/app/com.google.Chrome/x86_64/eos3/3c53c34fbc70a8e845830056da453003619b9c3fcc7477766b67e4a6078f8fc2/files/bin/eos-google-chrome-app' Nov 16 22:14:43 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[7281]: Flatpak launcher for Chrome found. Launching... Nov 16 22:14:43 endless google-chrome.desktop[7281]: INFO:root:Running Google Chrome launcher with PID 7290 Nov 16 22:14:43 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[7281]: Running Google Chrome launcher with PID 7290 Nov 16 22:14:43 endless systemd[2202]: Started flatpak-com.google.Chrome-7293.scope. Nov 16 22:14:43 endless xdg-document-portal[3910]: unique: 101, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 7311 Nov 16 22:14:43 endless xdg-document-portal[3910]: unique: 101, success, outsize: 120 Nov 16 22:14:43 endless xdg-document-portal[3910]: unique: 102, opcode: LOOKUP (1), nodeid: 1, insize: 47, pid: 7311 Nov 16 22:14:43 endless xdg-document-portal[3910]: unique: 102, success, outsize: 144 Nov 16 22:14:43 endless xdg-document-portal[3910]: unique: 103, opcode: LOOKUP (1), nodeid: 2, insize: 58, pid: 7311 Nov 16 22:14:43 endless xdg-document-portal[3910]: unique: 103, success, outsize: 144 Nov 16 22:14:43 endless google-chrome.desktop[7281]: /sysroot/flatpak/app/com.google.Chrome/x86_64/eos3/3c53c34fbc70a8e845830056da453003619b9c3fcc7477766b67e4a6078f8fc2/files/extra/opt/google/chrome/nacl_helper: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory Nov 16 22:14:43 endless google-chrome.desktop[7281]: [1:1:1116/221443.753216:ERROR:nacl_fork_delegate_linux.cc(315)] Bad NaCl helper startup ack (0 bytes) Nov 16 22:14:44 endless google-chrome.desktop[7281]: [7294:7294:1116/221444.055530:ERROR:configuration_policy_handler_list.cc(92)] Unknown policy: ExtensionInstallForceList Nov 16 22:14:44 endless google-chrome.desktop[7281]: [7294:7294:1116/221444.200968:ERROR:configuration_policy_handler_list.cc(92)] Unknown policy: ExtensionInstallForceList Nov 16 22:14:44 endless gnome-keyring-daemon[2209]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered Nov 16 22:14:45 endless gnome-keyring-daemon[2209]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered Nov 16 22:15:16 endless xdg-document-portal[3910]: unique: 104, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:15:16 endless xdg-document-portal[3910]: unique: 104, success, outsize: 96 Nov 16 22:16:16 endless xdg-document-portal[3910]: unique: 105, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 2514 Nov 16 22:16:16 endless xdg-document-portal[3910]: unique: 105, success, outsize: 96 Nov 16 22:16:26 endless dbus-daemon[2243]: Activating service name='org.gnome.ControlCenter.SearchProvider' Nov 16 22:16:26 endless dbus-daemon[2243]: Activating service name='com.endlessm.EknServices.SearchProviderV1' Nov 16 22:16:26 endless dbus-daemon[2243]: Activating service name='org.gnome.Calculator.SearchProvider' Nov 16 22:16:26 endless dbus-daemon[2243]: Activating service name='org.gnome.Contacts.SearchProvider' Nov 16 22:16:26 endless dbus-daemon[2243]: Activating service name='org.gnome.Yelp.SearchProvider' Nov 16 22:16:26 endless dbus-daemon[2243]: Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' Nov 16 22:16:26 endless systemd[2202]: Starting GNOME Terminal Server... Nov 16 22:16:26 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Calculator.SearchProvider' Nov 16 22:16:26 endless systemd[2202]: Started flatpak-com.endlessm.EknServices-7613.scope. Nov 16 22:16:26 endless xdg-document-portal[3910]: unique: 106, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 7629 Nov 16 22:16:26 endless xdg-document-portal[3910]: unique: 106, success, outsize: 120 Nov 16 22:16:26 endless xdg-document-portal[3910]: unique: 107, opcode: LOOKUP (1), nodeid: 1, insize: 47, pid: 7629 Nov 16 22:16:26 endless xdg-document-portal[3910]: unique: 107, success, outsize: 144 Nov 16 22:16:26 endless xdg-document-portal[3910]: unique: 108, opcode: LOOKUP (1), nodeid: 2, insize: 65, pid: 7629 Nov 16 22:16:26 endless xdg-document-portal[3910]: unique: 108, success, outsize: 144 Nov 16 22:16:26 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.ControlCenter.SearchProvider' Nov 16 22:16:26 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Terminal' Nov 16 22:16:26 endless systemd[2202]: Started GNOME Terminal Server. Nov 16 22:16:26 endless dbus-daemon[2243]: Successfully activated service 'com.endlessm.EknServices.SearchProviderV1' Nov 16 22:16:26 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Contacts.SearchProvider' Nov 16 22:16:26 endless gnome-contacts-[7618]: contacts-store.vala:335: Unable to check accounts caps The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files Nov 16 22:16:26 endless gnome-contacts-[7618]: backend-store.vala:434: Error preparing Backend 'telepathy': The name org.freedesktop.Telepathy.AccountManager was not provided by any .service files Nov 16 22:16:26 endless dbus-daemon[2243]: Successfully activated service 'org.gnome.Yelp.SearchProvider' Nov 16 22:16:27 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=ter on plugin=flatpak on apps system/*/*/desktop/org.gnome.Nautilus.desktop/*,system/*/*/desktop/org.gnome.Terminal.desktop/* took 68ms Nov 16 22:16:28 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=termina on plugin=flatpak took 5ms Nov 16 22:16:28 endless gnome-software[2599]: running search with refine-flags=require-icon with timeout=60 with max-results=20 with search=terminal on plugin=flatpak on apps system/*/*/desktop/org.gnome.Nautilus.desktop/*,system/*/*/desktop/org.gnome.Terminal.desktop/* took 43ms Nov 16 22:16:34 endless xdg-document-portal[3910]: unique: 109, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 7741 Nov 16 22:16:34 endless xdg-document-portal[3910]: unique: 109, success, outsize: 96 ============ = Coredump = ============ systemd-coredump not enabled