===================== = EndlessOS version = ===================== NAME="Endless" VERSION="3.1.0" ID="endless" ID_LIKE="ubuntu debian" PRETTY_NAME="Endless 3.1.0" VERSION_ID="3.1.0" HOME_URL="http://www.endlessm.com/" BUILD_ID="eos-170114-201113" ========== = Kernel = ========== Linux endless 4.8.0-32-generic #34+dev147.48224f3beos3.1.1-Endless SMP Fri Jan 13 13:21:09 UTC x86_64 GNU/Linux cmdline: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-40a27c661924b10880bcde7db893844adc31bb8a90f0d6c3b247b9c423e57882/vmlinuz-4.8.0-32-generic root=UUID=817fe263-272d-47ba-945d-d9674912e832 rw splash plymouth.ignore-serial-consoles quiet ostree=/ostree/boot.1/eos/40a27c661924b10880bcde7db893844adc31bb8a90f0d6c3b247b9c423e57882/0 Module Size Used by nls_utf8 16384 1 isofs 40960 1 hid_multitouch 20480 0 rfcomm 77824 0 bnep 20480 2 intel_rapl 20480 0 intel_telemetry_pltdrv 20480 0 intel_pmc_ipc 20480 1 intel_telemetry_pltdrv intel_punit_ipc 16384 1 intel_telemetry_pltdrv intel_telemetry_core 20480 1 intel_telemetry_pltdrv x86_pkg_temp_thermal 16384 0 coretemp 16384 0 kvm_intel 192512 0 rtsx_usb_ms 20480 0 memstick 20480 1 rtsx_usb_ms kvm 598016 1 kvm_intel arc4 16384 2 rtl8723be 90112 0 btcoexist 53248 1 rtl8723be uvcvideo 90112 0 rtl8723_common 24576 1 rtl8723be rtl_pci 28672 1 rtl8723be snd_soc_skl 65536 0 irqbypass 16384 1 kvm rtlwifi 77824 2 rtl_pci,rtl8723be snd_soc_skl_ipc 45056 1 snd_soc_skl snd_soc_sst_ipc 16384 1 snd_soc_skl_ipc videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc snd_soc_sst_dsp 32768 1 snd_soc_skl_ipc snd_hda_ext_core 28672 1 snd_soc_skl mac80211 765952 3 rtl_pci,rtlwifi,rtl8723be crct10dif_pclmul 16384 0 videobuf2_v4l2 24576 1 uvcvideo snd_soc_sst_match 16384 1 snd_soc_skl snd_soc_core 233472 1 snd_soc_skl videobuf2_core 40960 2 uvcvideo,videobuf2_v4l2 i2c_designware_platform 16384 0 asus_nb_wmi 32768 0 asus_wmi 28672 1 asus_nb_wmi snd_hda_codec_hdmi 49152 1 snd_hda_codec_realtek 90112 1 snd_hda_codec_generic 73728 1 snd_hda_codec_realtek videodev 180224 3 uvcvideo,videobuf2_core,videobuf2_v4l2 crc32_pclmul 16384 0 i2c_designware_core 20480 1 i2c_designware_platform sparse_keymap 16384 1 asus_wmi ghash_clmulni_intel 16384 0 snd_compress 20480 1 snd_soc_core media 40960 2 uvcvideo,videodev ac97_bus 16384 1 snd_soc_core snd_pcm_dmaengine 16384 1 snd_soc_core aesni_intel 167936 0 joydev 20480 0 aes_x86_64 20480 1 aesni_intel lrw 16384 1 aesni_intel btusb 45056 0 cfg80211 593920 2 mac80211,rtlwifi btrtl 16384 1 btusb snd_hda_intel 36864 3 glue_helper 16384 1 aesni_intel ablk_helper 16384 1 aesni_intel btbcm 16384 1 btusb snd_hda_codec 135168 4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek snd_hda_core 86016 7 snd_hda_intel,snd_hda_codec,snd_hda_ext_core,snd_soc_skl,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek btintel 16384 1 btusb snd_hwdep 16384 1 snd_hda_codec bluetooth 561152 31 btrtl,btintel,bnep,btbcm,rfcomm,btusb cryptd 24576 3 ablk_helper,ghash_clmulni_intel,aesni_intel snd_pcm 110592 8 snd_hda_intel,snd_hda_codec,snd_pcm_dmaengine,snd_hda_ext_core,snd_hda_core,snd_soc_skl,snd_hda_codec_hdmi,snd_soc_core snd_timer 32768 1 snd_pcm mei_me 40960 0 snd 86016 16 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 r8169 86016 0 input_leds 16384 0 mii 16384 1 r8169 soundcore 16384 1 snd mei 102400 1 mei_me mac_hid 16384 0 fjes 28672 0 int3403_thermal 16384 0 processor_thermal_device 16384 0 intel_soc_dts_iosf 16384 1 processor_thermal_device shpchp 36864 0 tpm_crb 16384 0 idma64 20480 0 virt_dma 16384 1 idma64 intel_lpss_pci 16384 0 int3406_thermal 16384 0 intel_lpss 16384 1 intel_lpss_pci dptf_power 16384 0 int340x_thermal_zone 16384 2 int3403_thermal,processor_thermal_device int3400_thermal 16384 0 acpi_thermal_rel 16384 1 int3400_thermal asus_wireless 16384 0 hid_generic 16384 0 usbmouse 16384 0 rtsx_usb_sdmmc 28672 0 usbhid 53248 0 rtsx_usb 24576 2 rtsx_usb_sdmmc,rtsx_usb_ms i915 1339392 6 i2c_algo_bit 16384 1 i915 serio_raw 16384 0 drm_kms_helper 167936 1 i915 syscopyarea 16384 1 drm_kms_helper sysfillrect 16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper fb_sys_fops 16384 1 drm_kms_helper drm 368640 7 i915,drm_kms_helper ahci 36864 3 libahci 32768 1 ahci wmi 20480 1 asus_wmi i2c_hid 20480 0 hid 118784 4 i2c_hid,hid_generic,usbhid,hid_multitouch video 40960 3 asus_wmi,int3406_thermal,i915 =================== = EndlessOS image = =================== eosoem-eos3.1-amd64-amd64.170115-022433.en ========================= = EndlessOS personality = ========================= [Personality] PersonalityName=Global ========== = Uptime = ========== 17:02:43 up 50 min, 1 user, load average: 0,62, 0,93, 0,62 ================= = OSTree status = ================= * eos 2c22686c94be7fda0fab6ee22f453379e7d849c4a09fda80b76b239e1b56b220.0 origin refspec: eos:os/eos/amd64/eos3 GPG: Signature made Суб 14 Янв 2017 23:07:41 using RSA key ID 9E08D8DABA02FC46 GPG: Good signature from "EOS OSTree Signing Key 1 " ========================== = Product identification = ========================== sys_vendor: ASUSTeK COMPUTER INC. product_name: X541NA product_uuid: 5502D612-45B6-A44D-BF49-7A90CBAB04E6 product_version: 1.0 board_asset_tag: ATN12345678901234567 board_name: X541NA board_vendor: ASUSTeK COMPUTER INC. board_version: 1.0 bios_date: 08/10/2017 bios_vendor: American Megatrends Inc. bios_version: X541NA.313 chassis_asset_tag: No Asset Tag chassis_type: 10 chassis_vendor: ASUSTeK COMPUTER INC. chassis_version: 1.0 ======= = CPU = ======= processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 92 model name : Intel(R) Pentium(R) CPU N4200 @ 1.10GHz stepping : 9 microcode : 0x20 cpu MHz : 2481.646 cache size : 1024 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 21 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 art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust smep erms mpx rdseed smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts bugs : monitor bogomips : 2188.80 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 : 92 model name : Intel(R) Pentium(R) CPU N4200 @ 1.10GHz stepping : 9 microcode : 0x20 cpu MHz : 2470.166 cache size : 1024 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 4 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 21 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 art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust smep erms mpx rdseed smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts bugs : monitor bogomips : 2188.80 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 : 92 model name : Intel(R) Pentium(R) CPU N4200 @ 1.10GHz stepping : 9 microcode : 0x20 cpu MHz : 2414.776 cache size : 1024 KB physical id : 0 siblings : 4 core id : 2 cpu cores : 4 apicid : 4 initial apicid : 4 fpu : yes fpu_exception : yes cpuid level : 21 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 art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust smep erms mpx rdseed smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts bugs : monitor bogomips : 2188.80 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 : 92 model name : Intel(R) Pentium(R) CPU N4200 @ 1.10GHz stepping : 9 microcode : 0x20 cpu MHz : 2488.830 cache size : 1024 KB physical id : 0 siblings : 4 core id : 3 cpu cores : 4 apicid : 6 initial apicid : 6 fpu : yes fpu_exception : yes cpuid level : 21 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 art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust smep erms mpx rdseed smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts bugs : monitor bogomips : 2188.80 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: 3,7G 1,0G 971M 329M 1,8G 2,1G Swap: 4,0G 0B 4,0G MemTotal: 3906452 kB MemFree: 994708 kB MemAvailable: 2248000 kB Buffers: 134432 kB Cached: 1540464 kB SwapCached: 0 kB Active: 1729020 kB Inactive: 827444 kB Active(anon): 886064 kB Inactive(anon): 333272 kB Active(file): 842956 kB Inactive(file): 494172 kB Unevictable: 80 kB Mlocked: 80 kB SwapTotal: 4193984 kB SwapFree: 4193984 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 851424 kB Mapped: 352192 kB Shmem: 337772 kB Slab: 256116 kB SReclaimable: 209484 kB SUnreclaim: 46632 kB KernelStack: 7952 kB PageTables: 31744 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 6147208 kB Committed_AS: 4243588 kB VmallocTotal: 34359738367 kB VmallocUsed: 0 kB VmallocChunk: 0 kB HardwareCorrupted: 0 kB AnonHugePages: 262144 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: 139240 kB DirectMap2M: 3915776 kB DirectMap1G: 2097152 kB ========= = Disks = ========= /org/freedesktop/UDisks2/Manager: org.freedesktop.UDisks2.Manager: Version: 2.1.7 /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/ram0: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/ram0 DeviceNumber: 256 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/ram0 ReadOnly: false Size: 67108864 Symlinks: /org/freedesktop/UDisks2/block_devices/ram1: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/ram1 DeviceNumber: 257 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/ram1 ReadOnly: false Size: 67108864 Symlinks: /org/freedesktop/UDisks2/block_devices/ram10: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/ram10 DeviceNumber: 266 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/ram10 ReadOnly: false Size: 67108864 Symlinks: /org/freedesktop/UDisks2/block_devices/ram11: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/ram11 DeviceNumber: 267 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/ram11 ReadOnly: false Size: 67108864 Symlinks: /org/freedesktop/UDisks2/block_devices/ram12: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/ram12 DeviceNumber: 268 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/ram12 ReadOnly: false Size: 67108864 Symlinks: /org/freedesktop/UDisks2/block_devices/ram13: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/ram13 DeviceNumber: 269 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/ram13 ReadOnly: false Size: 67108864 Symlinks: /org/freedesktop/UDisks2/block_devices/ram14: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/ram14 DeviceNumber: 270 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/ram14 ReadOnly: false Size: 67108864 Symlinks: /org/freedesktop/UDisks2/block_devices/ram15: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/ram15 DeviceNumber: 271 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/ram15 ReadOnly: false Size: 67108864 Symlinks: /org/freedesktop/UDisks2/block_devices/ram2: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/ram2 DeviceNumber: 258 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/ram2 ReadOnly: false Size: 67108864 Symlinks: /org/freedesktop/UDisks2/block_devices/ram3: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/ram3 DeviceNumber: 259 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/ram3 ReadOnly: false Size: 67108864 Symlinks: /org/freedesktop/UDisks2/block_devices/ram4: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/ram4 DeviceNumber: 260 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/ram4 ReadOnly: false Size: 67108864 Symlinks: /org/freedesktop/UDisks2/block_devices/ram5: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/ram5 DeviceNumber: 261 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/ram5 ReadOnly: false Size: 67108864 Symlinks: /org/freedesktop/UDisks2/block_devices/ram6: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/ram6 DeviceNumber: 262 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/ram6 ReadOnly: false Size: 67108864 Symlinks: /org/freedesktop/UDisks2/block_devices/ram7: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/ram7 DeviceNumber: 263 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/ram7 ReadOnly: false Size: 67108864 Symlinks: /org/freedesktop/UDisks2/block_devices/ram8: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/ram8 DeviceNumber: 264 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/ram8 ReadOnly: false Size: 67108864 Symlinks: /org/freedesktop/UDisks2/block_devices/ram9: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/ram9 DeviceNumber: 265 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/ram9 ReadOnly: false Size: 67108864 Symlinks: /org/freedesktop/UDisks2/block_devices/sda: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/sda DeviceNumber: 2048 Drive: '/org/freedesktop/UDisks2/drives/ST1000LM035_1RK172_WDEBLQC2' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-ST1000LM035-1RK172_WDEBLQC2 IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sda ReadOnly: false Size: 1000204886016 Symlinks: /dev/disk/by-id/ata-ST1000LM035-1RK172_WDEBLQC2 /dev/disk/by-id/wwn-0x5000c500a9c334a2 /dev/disk/by-path/pci-0000:00:12.0-ata-1 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/ST1000LM035_1RK172_WDEBLQC2' HintAuto: false HintIconName: HintIgnore: true HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-ST1000LM035-1RK172_WDEBLQC2-part1 IdLabel: IdType: vfat IdUUID: 5271-53BA IdUsage: filesystem IdVersion: FAT16 MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sda1 ReadOnly: false Size: 65011712 Symlinks: /dev/disk/by-id/ata-ST1000LM035-1RK172_WDEBLQC2-part1 /dev/disk/by-id/wwn-0x5000c500a9c334a2-part1 /dev/disk/by-partuuid/93026996-0452-4e77-b860-017698c2b9fc /dev/disk/by-path/pci-0000:00:12.0-ata-1-part1 /dev/disk/by-uuid/5271-53BA 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: 93026996-0452-4e77-b860-017698c2b9fc /org/freedesktop/UDisks2/block_devices/sda2: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/sda2 DeviceNumber: 2050 Drive: '/org/freedesktop/UDisks2/drives/ST1000LM035_1RK172_WDEBLQC2' HintAuto: false HintIconName: HintIgnore: true HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-ST1000LM035-1RK172_WDEBLQC2-part2 IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sda2 ReadOnly: false Size: 1048576 Symlinks: /dev/disk/by-id/ata-ST1000LM035-1RK172_WDEBLQC2-part2 /dev/disk/by-id/wwn-0x5000c500a9c334a2-part2 /dev/disk/by-partuuid/bf00f15e-e1d9-49d1-8554-c6d76fa716e6 /dev/disk/by-path/pci-0000:00:12.0-ata-1-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: bf00f15e-e1d9-49d1-8554-c6d76fa716e6 /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/ST1000LM035_1RK172_WDEBLQC2' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-ST1000LM035-1RK172_WDEBLQC2-part3 IdLabel: ostree IdType: ext4 IdUUID: 817fe263-272d-47ba-945d-d9674912e832 IdUsage: filesystem IdVersion: 1.0 MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sda3 ReadOnly: false Size: 995843112960 Symlinks: /dev/disk/by-id/ata-ST1000LM035-1RK172_WDEBLQC2-part3 /dev/disk/by-id/wwn-0x5000c500a9c334a2-part3 /dev/disk/by-label/ostree /dev/disk/by-partuuid/f54d73b8-a5dc-4dfd-a465-ce4c0d31f0f6 /dev/disk/by-path/pci-0000:00:12.0-ata-1-part3 /dev/disk/by-uuid/817fe263-272d-47ba-945d-d9674912e832 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: 995843112960 Table: '/org/freedesktop/UDisks2/block_devices/sda' Type: 4f68bce3-e8cd-4db1-96e7-fbcaf984b709 UUID: f54d73b8-a5dc-4dfd-a465-ce4c0d31f0f6 /org/freedesktop/UDisks2/block_devices/sda4: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/sda4 DeviceNumber: 2052 Drive: '/org/freedesktop/UDisks2/drives/ST1000LM035_1RK172_WDEBLQC2' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-ST1000LM035-1RK172_WDEBLQC2-part4 IdLabel: eos-swap IdType: swap IdUUID: 68f3c57a-2dcb-47f6-b038-2afb66e6f6d1 IdUsage: other IdVersion: 1 MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sda4 ReadOnly: false Size: 4294647296 Symlinks: /dev/disk/by-id/ata-ST1000LM035-1RK172_WDEBLQC2-part4 /dev/disk/by-id/wwn-0x5000c500a9c334a2-part4 /dev/disk/by-label/eos-swap /dev/disk/by-partuuid/21b12576-e72e-473b-bcda-f2c09641b50d /dev/disk/by-path/pci-0000:00:12.0-ata-1-part4 /dev/disk/by-uuid/68f3c57a-2dcb-47f6-b038-2afb66e6f6d1 org.freedesktop.UDisks2.Partition: Flags: 0 IsContained: false IsContainer: false Name: Number: 4 Offset: 995910221824 Size: 4294647296 Table: '/org/freedesktop/UDisks2/block_devices/sda' Type: 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f UUID: 21b12576-e72e-473b-bcda-f2c09641b50d org.freedesktop.UDisks2.Swapspace: Active: true /org/freedesktop/UDisks2/block_devices/sr0: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/sr0 DeviceNumber: 2816 Drive: '/org/freedesktop/UDisks2/drives/HL_DT_ST_DVDRAM_GUE1N_KLIH3RK4822' HintAuto: true HintIconName: HintIgnore: false HintName: HintPartitionable: false HintSymbolicIconName: HintSystem: false Id: by-uuid-2004-05-06-20-51-11-00 IdLabel: 040506_1351 IdType: iso9660 IdUUID: 2004-05-06-20-51-11-00 IdUsage: filesystem IdVersion: Joliet Extension MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sr0 ReadOnly: true Size: 649076736 Symlinks: /dev/cdrom /dev/cdrw /dev/disk/by-id/ata-HL-DT-ST_DVDRAM_GUE1N_KLIH3RK4822 /dev/disk/by-id/wwn-0x5001480000000000 /dev/disk/by-label/040506_1351 /dev/disk/by-path/pci-0000:00:12.0-ata-2 /dev/disk/by-uuid/2004-05-06-20-51-11-00 /dev/dvd /dev/dvdrw org.freedesktop.UDisks2.Filesystem: MountPoints: /run/media/user/040506_1351 /org/freedesktop/UDisks2/drives/HL_DT_ST_DVDRAM_GUE1N_KLIH3RK4822: org.freedesktop.UDisks2.Drive: CanPowerOff: false Configuration: {} ConnectionBus: Ejectable: true Id: HL-DT-ST-DVDRAM-GUE1N-KLIH3RK4822 Media: optical_cd MediaAvailable: true MediaChangeDetected: true MediaCompatibility: optical_cd optical_cd_r optical_cd_rw optical_dvd optical_dvd_plus_r optical_dvd_plus_r_dl optical_dvd_plus_rw optical_dvd_r optical_dvd_ram optical_dvd_rw optical_mrw optical_mrw_w MediaRemovable: true Model: HL-DT-ST DVDRAM GUE1N Optical: true OpticalBlank: false OpticalNumAudioTracks: 0 OpticalNumDataTracks: 1 OpticalNumSessions: 1 OpticalNumTracks: 1 Removable: true Revision: AS00 RotationRate: -1 Seat: seat0 Serial: KLIH3RK4822 SiblingId: Size: 649076736 SortKey: 00coldplug/11removable/sr0 TimeDetected: 1525957929326966 TimeMediaDetected: 1525957929326966 Vendor: WWN: 0x5001480000000000 org.freedesktop.UDisks2.Drive.Ata: AamEnabled: false AamSupported: false AamVendorRecommendedValue: 0 ApmEnabled: false ApmSupported: false PmEnabled: false PmSupported: false ReadLookaheadEnabled: false ReadLookaheadSupported: false SecurityEnhancedEraseUnitMinutes: 0 SecurityEraseUnitMinutes: 0 SecurityFrozen: false SmartEnabled: false SmartFailing: false SmartNumAttributesFailedInThePast: -1 SmartNumAttributesFailing: -1 SmartNumBadSectors: 1 SmartPowerOnSeconds: 0 SmartSelftestPercentRemaining: -1 SmartSelftestStatus: SmartSupported: false SmartTemperature: 0.0 SmartUpdated: 0 WriteCacheEnabled: false WriteCacheSupported: false /org/freedesktop/UDisks2/drives/ST1000LM035_1RK172_WDEBLQC2: org.freedesktop.UDisks2.Drive: CanPowerOff: false Configuration: {} ConnectionBus: Ejectable: false Id: ST1000LM035-1RK172-WDEBLQC2 Media: MediaAvailable: true MediaChangeDetected: true MediaCompatibility: MediaRemovable: false Model: ST1000LM035-1RK172 Optical: false OpticalBlank: false OpticalNumAudioTracks: 0 OpticalNumDataTracks: 0 OpticalNumSessions: 0 OpticalNumTracks: 0 Removable: false Revision: SDM1 RotationRate: 5400 Seat: seat0 Serial: WDEBLQC2 SiblingId: Size: 1000204886016 SortKey: 00coldplug/00fixed/sd____a TimeDetected: 1525957927967255 TimeMediaDetected: 1525957927967255 Vendor: WWN: 0x5000c500a9c334a2 org.freedesktop.UDisks2.Drive.Ata: AamEnabled: false AamSupported: false AamVendorRecommendedValue: 0 ApmEnabled: true ApmSupported: true PmEnabled: true PmSupported: true ReadLookaheadEnabled: true ReadLookaheadSupported: true SecurityEnhancedEraseUnitMinutes: 164 SecurityEraseUnitMinutes: 164 SecurityFrozen: true SmartEnabled: true SmartFailing: false SmartNumAttributesFailedInThePast: 0 SmartNumAttributesFailing: 0 SmartNumBadSectors: 0 SmartPowerOnSeconds: 32400 SmartSelftestPercentRemaining: 0 SmartSelftestStatus: success SmartSupported: true SmartTemperature: 314.15000000000003 SmartUpdated: 1525960940 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=1938908k,nr_inodes=484727,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/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) 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/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) 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/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) /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 /var 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=12016) mqueue on /dev/mqueue type mqueue (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) tmpfs on /tmp type tmpfs (rw) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) tmpfs on /run/user/1001 type tmpfs (rw,nosuid,nodev,relatime,size=390648k,mode=700,uid=1001,gid=1001) /dev/sr0 on /run/media/user/040506_1351 type iso9660 (ro,nosuid,nodev,relatime,uid=1001,gid=1001,iocharset=utf8,mode=0400,dmode=0500,uhelper=udisks2) /dev/fuse on /run/user/1001/doc type fuse (rw,nosuid,nodev,relatime,user_id=1001,group_id=1001) Файловая система Размер Использовано Дост Использовано% Cмонтировано в devtmpfs 1,9G 0 1,9G 0% /dev tmpfs 1,9G 31M 1,9G 2% /dev/shm tmpfs 1,9G 14M 1,9G 1% /run tmpfs 5,0M 4,0K 5,0M 1% /run/lock tmpfs 1,9G 0 1,9G 0% /sys/fs/cgroup /dev/sda3 913G 24G 890G 3% / tmpfs 1,9G 20K 1,9G 1% /tmp tmpfs 382M 48K 382M 1% /run/user/1001 /dev/sr0 619M 619M 0 100% /run/media/user/040506_1351 ====================== = Network interfaces = ====================== enp1s0 Link encap:Ethernet HWaddr 10:7b:44:5d:47:b4 inet addr:192.168.1.38 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::4984:2bc4:ad3c:1bae/64 Scope:Link inet6 addr: fd78:6a89:f7e3:bd00:3247:ae9c:ae58:eb57/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:86933 errors:0 dropped:0 overruns:0 frame:0 TX packets:47774 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:119977480 (114.4 MiB) TX bytes:3723713 (3.5 MiB) 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:1870 errors:0 dropped:0 overruns:0 frame:0 TX packets:1870 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:396045 (386.7 KiB) TX bytes:396045 (386.7 KiB) wlp2s0 Link encap:Ethernet HWaddr f8:28:19:29:e0:f8 inet addr:192.168.1.37 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fd78:6a89:f7e3:bd00:8682:53ff:96df:6bb4/64 Scope:Global inet6 addr: fe80::5164:3b12:d3bd:4abc/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2288 errors:0 dropped:0 overruns:0 frame:0 TX packets:150 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:260918 (254.8 KiB) TX bytes:23056 (22.5 KiB) ============ = Graphics = ============ Renderer: Mesa DRI Intel(R) HD Graphics (Broxton) =========== = Display = =========== Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 eDP1 connected primary 1920x1080+0+0 (0x48) normal (normal left inverted right x axis y axis) 340mm x 190mm Identifier: 0x43 Timestamp: 86334 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: 00ffffffffffff0006afed3800000000 01190104952213780251259358578f28 1f505400000001010101010101010101 010101010101783780b470382e406c30 aa0058c1100000180000000f00000000 00000000000000000020000000fe0041 554f0a202020202020202020000000fe 004231353648544e30332e38200a0012 BACKLIGHT: 52705 range: (0, 96000) Backlight: 52705 range: (0, 96000) underscan vborder: 0 range: (0, 128) underscan hborder: 0 range: (0, 128) underscan: off supported: off, crop scaling mode: Full aspect supported: None, Full, Center, Full aspect Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on 1920x1080 (0x48) 142.000MHz -HSync -VSync *current +preferred h: width 1920 start 2028 end 2076 total 2100 skew 0 clock 67.62KHz v: height 1080 start 1090 end 1100 total 1126 clock 60.05Hz 1920x1080 (0x107) 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 (0x108) 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 (0x109) 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 (0x10a) 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 (0x10b) 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 (0x10c) 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 (0x10d) 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 (0x10e) 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 (0x10f) 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 (0x110) 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 (0x111) 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 (0x112) 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 (0x113) 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 (0x114) 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 (0x115) 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 (0x116) 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 (0x117) 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 (0x118) 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 (0x119) 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 (0x11a) 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 (0x11b) 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 (0x11c) 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: 0x44 Timestamp: 86334 Subpixel: unknown Clones: 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 HDMI1 disconnected (normal left inverted right x axis y axis) Identifier: 0x45 Timestamp: 86334 Subpixel: unknown Clones: 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 VIRTUAL1 disconnected (normal left inverted right x axis y axis) Identifier: 0x46 Timestamp: 86334 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 = ============== Звуковая плата №0 Имя: alsa_card.pci-0000_00_0e.0 Драйвер: module-alsa-card.c Модуль-владелец: 6 Свойства: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0x91318000 irq 374" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:0e.0" sysfs.path = "/devices/pci0000:00/0000:00:0e.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "5a98" device.form_factor = "internal" device.string = "0" device.description = "Встроенное аудио" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Профили: input:analog-stereo: Аналоговый стерео вход (sinks: 0, sources: 1, priority: 60, available: yes) output:analog-stereo: Аналоговый стерео выход (sinks: 1, sources: 0, priority: 6000, available: yes) output:analog-stereo+input:analog-stereo: Аналоговый стерео дуплекс (sinks: 1, sources: 1, priority: 6060, available: yes) output:hdmi-stereo: Digital Stereo (HDMI) выход (sinks: 1, sources: 0, priority: 5400, available: yes) output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) выход + Аналоговый стерео вход (sinks: 1, sources: 1, priority: 5460, available: yes) output:hdmi-surround: Digital Surround 5.1 (HDMI) выход (sinks: 1, sources: 0, priority: 300, available: yes) output:hdmi-surround+input:analog-stereo: Digital Surround 5.1 (HDMI) выход + Аналоговый стерео вход (sinks: 1, sources: 1, priority: 360, available: yes) output:hdmi-surround71: Digital Surround 7.1 (HDMI) выход (sinks: 1, sources: 0, priority: 300, available: yes) output:hdmi-surround71+input:analog-stereo: Digital Surround 7.1 (HDMI) выход + Аналоговый стерео вход (sinks: 1, sources: 1, priority: 360, available: yes) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) выход (sinks: 1, sources: 0, priority: 5200, available: yes) output:hdmi-stereo-extra1+input:analog-stereo: Digital Stereo (HDMI 2) выход + Аналоговый стерео вход (sinks: 1, sources: 1, priority: 5260, available: yes) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) выход (sinks: 1, sources: 0, priority: 100, available: yes) output:hdmi-surround-extra1+input:analog-stereo: Digital Surround 5.1 (HDMI 2) выход + Аналоговый стерео вход (sinks: 1, sources: 1, priority: 160, available: yes) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) выход (sinks: 1, sources: 0, priority: 100, available: yes) output:hdmi-surround71-extra1+input:analog-stereo: Digital Surround 7.1 (HDMI 2) выход + Аналоговый стерео вход (sinks: 1, sources: 1, priority: 160, available: yes) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) выход (sinks: 1, sources: 0, priority: 5200, available: yes) output:hdmi-stereo-extra2+input:analog-stereo: Digital Stereo (HDMI 3) выход + Аналоговый стерео вход (sinks: 1, sources: 1, priority: 5260, available: yes) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) выход (sinks: 1, sources: 0, priority: 100, available: yes) output:hdmi-surround-extra2+input:analog-stereo: Digital Surround 5.1 (HDMI 3) выход + Аналоговый стерео вход (sinks: 1, sources: 1, priority: 160, available: yes) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) выход (sinks: 1, sources: 0, priority: 100, available: yes) output:hdmi-surround71-extra2+input:analog-stereo: Digital Surround 7.1 (HDMI 3) выход + Аналоговый стерео вход (sinks: 1, sources: 1, priority: 160, available: yes) off: Выключено (sinks: 0, sources: 0, priority: 0, available: yes) Активный профиль: output:analog-stereo+input:analog-stereo Порты: analog-input-internal-mic: Встроенный микрофон (priority: 8900, latency offset: 0 usec) Свойства: device.icon_name = "audio-input-microphone" Входит в профиль(и): input:analog-stereo, output:analog-stereo+input:analog-stereo, output:hdmi-stereo+input:analog-stereo, output:hdmi-surround+input:analog-stereo, output:hdmi-surround71+input:analog-stereo, output:hdmi-stereo-extra1+input:analog-stereo, output:hdmi-surround-extra1+input:analog-stereo, output:hdmi-surround71-extra1+input:analog-stereo, output:hdmi-stereo-extra2+input:analog-stereo, output:hdmi-surround-extra2+input:analog-stereo, output:hdmi-surround71-extra2+input:analog-stereo analog-input-headset-mic: Микрофон гарнитуры (priority: 8700, latency offset: 0 usec, not available) Свойства: device.icon_name = "audio-input-microphone" Входит в профиль(и): input:analog-stereo, output:analog-stereo+input:analog-stereo, output:hdmi-stereo+input:analog-stereo, output:hdmi-surround+input:analog-stereo, output:hdmi-surround71+input:analog-stereo, output:hdmi-stereo-extra1+input:analog-stereo, output:hdmi-surround-extra1+input:analog-stereo, output:hdmi-surround71-extra1+input:analog-stereo, output:hdmi-stereo-extra2+input:analog-stereo, output:hdmi-surround-extra2+input:analog-stereo, output:hdmi-surround71-extra2+input:analog-stereo analog-output-speaker: Динамики (priority: 10000, latency offset: 0 usec) Свойства: device.icon_name = "audio-speakers" Входит в профиль(и): output:analog-stereo, output:analog-stereo+input:analog-stereo analog-output-headphones: Аналоговые наушники (priority: 9000, latency offset: 0 usec, not available) Свойства: device.icon_name = "audio-headphones" Входит в профиль(и): output:analog-stereo, output:analog-stereo+input:analog-stereo hdmi-output-0: HDMI / DisplayPort (priority: 5900, latency offset: 0 usec, not available) Свойства: device.icon_name = "video-display" Входит в профиль(и): output:hdmi-stereo, output:hdmi-stereo+input:analog-stereo, output:hdmi-surround, output:hdmi-surround+input:analog-stereo, output:hdmi-surround71, output:hdmi-surround71+input:analog-stereo hdmi-output-1: HDMI / DisplayPort 2 (priority: 5800, latency offset: 0 usec, not available) Свойства: device.icon_name = "video-display" Входит в профиль(и): output:hdmi-stereo-extra1, output:hdmi-stereo-extra1+input:analog-stereo, output:hdmi-surround-extra1, output:hdmi-surround-extra1+input:analog-stereo, output:hdmi-surround71-extra1, output:hdmi-surround71-extra1+input:analog-stereo hdmi-output-2: HDMI / DisplayPort 3 (priority: 5700, latency offset: 0 usec, not available) Свойства: device.icon_name = "video-display" Входит в профиль(и): output:hdmi-stereo-extra2, output:hdmi-stereo-extra2+input:analog-stereo, output:hdmi-surround-extra2, output:hdmi-surround-extra2+input:analog-stereo, output:hdmi-surround71-extra2, output:hdmi-surround71-extra2+input:analog-stereo Источник №0 Состояние: SUSPENDED Имя: alsa_output.pci-0000_00_0e.0.analog-stereo.monitor Описание: Monitor of Встроенное аудио Аналоговый стерео Драйвер: module-alsa-card.c Спецификация отсчётов: s16le 2-канальный 4410 Схема каналов: front-left,front-right Модуль-владелец: 6 Звук выключен: no Громкость: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB баланс 0,00 Базовая громкость: 65536 / 100% / 0,00 dB Является монитором аудиоприёмника: alsa_output.pci-0000_00_0e.0.analog-stereo Задержка: 0 мкс, настроено на 0 мкс Флаги: DECIBEL_VOLUME LATENCY Свойства: device.description = "Monitor of Встроенное аудио Аналоговый стерео" device.class = "monitor" alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0x91318000 irq 374" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:0e.0" sysfs.path = "/devices/pci0000:00/0000:00:0e.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "5a98" device.form_factor = "internal" device.string = "0" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Форматы: pcm Источник №1 Состояние: SUSPENDED Имя: alsa_input.pci-0000_00_0e.0.analog-stereo Описание: Встроенное аудио Аналоговый стерео Драйвер: module-alsa-card.c Спецификация отсчётов: s16le 2-канальный 4410 Схема каналов: front-left,front-right Модуль-владелец: 6 Звук выключен: no Громкость: front-left: 10387 / 16% / -48,00 dB, front-right: 10387 / 16% / -48,00 dB баланс 0,00 Базовая громкость: 6554 / 10% / -60,00 dB Является монитором аудиоприёмника: н/д Задержка: 0 мкс, настроено на 0 мкс Флаги: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Свойства: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC256 Analog" alsa.id = "ALC256 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0x91318000 irq 374" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:0e.0" sysfs.path = "/devices/pci0000:00/0000:00:0e.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "5a98" device.form_factor = "internal" device.string = "front:0" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Аналоговый стерео" device.description = "Встроенное аудио Аналоговый стерео" alsa.mixer_name = "Realtek ALC256" alsa.components = "HDA:10ec0256,104312e0,00100002 HDA:8086280a,80860101,00100000" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Порты: analog-input-internal-mic: Встроенный микрофон (priority: 8900) analog-input-headset-mic: Микрофон гарнитуры (priority: 8700, not available) Активный порт: analog-input-internal-mic Форматы: pcm Аудиоприёмник №0 Состояние: SUSPENDED Имя: alsa_output.pci-0000_00_0e.0.analog-stereo Описание: Встроенное аудио Аналоговый стерео Драйвер: module-alsa-card.c Спецификация отсчётов: s16le 2-канальный 4410 Схема каналов: front-left,front-right Модуль-владелец: 6 Звук выключен: no Громкость: front-left: 38131 / 58% / -14,11 dB, front-right: 38131 / 58% / -14,11 dB баланс 0,00 Базовая громкость: 65536 / 100% / 0,00 dB Мониторный источник: alsa_output.pci-0000_00_0e.0.analog-stereo.monitor Задержка: 0 мкс, настроено на 0 мкс Флаги: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Свойства: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC256 Analog" alsa.id = "ALC256 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0x91318000 irq 374" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:0e.0" sysfs.path = "/devices/pci0000:00/0000:00:0e.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "5a98" device.form_factor = "internal" device.string = "front:0" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Аналоговый стерео" device.description = "Встроенное аудио Аналоговый стерео" alsa.mixer_name = "Realtek ALC256" alsa.components = "HDA:10ec0256,104312e0,00100002 HDA:8086280a,80860101,00100000" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Порты: analog-output-speaker: Динамики (priority: 10000) analog-output-headphones: Аналоговые наушники (priority: 9000, not available) Активный порт: analog-output-speaker Форматы: pcm ================= = Input devices = ================= 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:13/PNP0C09:01/PNP0C0C:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=10000000000000 0 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:13/PNP0C09:01/PNP0C0D:01/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 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/PNP0C0E:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=4000 0 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/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=402000000 3803078f800d001 feffffdfffefffff 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/LNXVIDEO:00/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b00000000 0 0 0 I: Bus=0003 Vendor=248a Product=8366 Version=0111 N: Name="Telink SVEN Wireless Mouse" P: Phys=usb-0000:00:15.0-3/input0 S: Sysfs=/devices/pci0000:00/0000:00:15.0/usb1/1-3/1-3:1.0/0003:248A:8366.0001/input/input5 U: Uniq= H: Handlers=kbd mouse0 event5 B: PROP=0 B: EV=1f B: KEY=3007f 0 0 483ffff17aff32d bf54444600000000 1f0001 130f938b17c000 677bfad941dfed 9ed68000004400 10000002 B: REL=143 B: ABS=100000000 B: MSC=10 I: Bus=0019 Vendor=1043 Product=0000 Version=0000 N: Name="Asus Wireless Radio Control" P: Phys=asus-wireless/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/input/input6 U: Uniq= H: Handlers=rfkill kbd event6 B: PROP=0 B: EV=3 B: KEY=80000000000000 0 0 0 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:0e.0/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:0e.0/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:0e.0/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:0e.0/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0019 Vendor=0000 Product=0000 Version=0000 N: Name="Asus WMI hotkeys" P: Phys=asus-nb-wmi/input0 S: Sysfs=/devices/platform/asus-nb-wmi/input/input11 U: Uniq= H: Handlers=rfkill kbd event11 B: PROP=0 B: EV=100013 B: KEY=1000000080000 0 800000000000 0 0 a1606f00900000 8200027800501000 e000000000000 0 B: MSC=10 I: Bus=0003 Vendor=04f2 Product=b52b Version=9552 N: Name="USB2.0 VGA UVC WebCam" P: Phys=usb-0000:00:15.0-5/button S: Sysfs=/devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/input/input12 U: Uniq= H: Handlers=kbd event12 B: PROP=0 B: EV=3 B: KEY=100000 0 0 0 I: Bus=0018 Vendor=0b05 Product=0201 Version=0100 N: Name="FTE1200:00 0B05:0201 Touchpad" P: Phys=i2c-FTE1200:00 S: Sysfs=/devices/pci0000:00/0000:00:17.0/i2c_designware.1/i2c-6/i2c-FTE1200:00/0018:0B05:0201.0002/input/input13 U: Uniq= H: Handlers=mouse1 event13 B: PROP=5 B: EV=b B: KEY=e520 10000 0 0 0 0 B: ABS=260800000000003 =============== = PCI devices = =============== 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5af0] (rev 0b) Subsystem: ASUSTeK Computer Inc. Device [1043:16a0] Flags: bus master, fast devsel, latency 0 00:00.1 Signal processing controller [1180]: Intel Corporation Device [8086:5a8c] (rev 0b) Subsystem: ASUSTeK Computer Inc. Device [1043:16a0] Flags: bus master, fast devsel, latency 0, IRQ 24 Memory at 91310000 (64-bit, non-prefetchable) [size=32K] Capabilities: Kernel driver in use: proc_thermal 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:5a84] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:16a0] Flags: bus master, fast devsel, latency 0, IRQ 371 Memory at 90000000 (64-bit, non-prefetchable) [size=16M] Memory at 80000000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: Kernel driver in use: i915 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:5a98] (rev 0b) Subsystem: ASUSTeK Computer Inc. Device [1043:12e0] Flags: bus master, fast devsel, latency 32, IRQ 374 Memory at 91318000 (64-bit, non-prefetchable) [size=16K] Memory at 91000000 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: snd_hda_intel 00:0f.0 Communication controller [0780]: Intel Corporation Device [8086:5a9a] (rev 0b) Subsystem: ASUSTeK Computer Inc. Device [1043:16a0] Flags: bus master, fast devsel, latency 0, IRQ 373 Memory at 91327000 (64-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: mei_me 00:12.0 SATA controller [0106]: Intel Corporation Device [8086:5ae3] (rev 0b) (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. Device [1043:16a0] Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 370 Memory at 9131c000 (32-bit, non-prefetchable) [size=8K] Memory at 91324000 (32-bit, non-prefetchable) [size=256] I/O ports at f090 [size=8] I/O ports at f080 [size=4] I/O ports at f060 [size=32] Memory at 91323000 (32-bit, non-prefetchable) [size=2K] Capabilities: Kernel driver in use: ahci 00:13.0 PCI bridge [0604]: Intel Corporation Device [8086:5ad8] (rev fb) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 0000e000-0000efff Memory behind bridge: 91200000-912fffff Capabilities: Kernel driver in use: pcieport 00:13.1 PCI bridge [0604]: Intel Corporation Device [8086:5ad9] (rev fb) (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: 0000d000-0000dfff Memory behind bridge: 91100000-911fffff Capabilities: Kernel driver in use: pcieport 00:15.0 USB controller [0c03]: Intel Corporation Device [8086:5aa8] (rev 0b) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:16a0] Flags: bus master, medium devsel, latency 0, IRQ 369 Memory at 91300000 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: xhci_hcd 00:16.0 Signal processing controller [1180]: Intel Corporation Device [8086:5aac] (rev 0b) Subsystem: ASUSTeK Computer Inc. Device [1043:16a0] Flags: bus master, fast devsel, latency 0, IRQ 27 Memory at 91322000 (64-bit, non-prefetchable) [size=4K] Memory at 91321000 (64-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: intel-lpss 00:17.0 Signal processing controller [1180]: Intel Corporation Device [8086:5ab4] (rev 0b) Subsystem: ASUSTeK Computer Inc. Device [1043:16a0] Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at 91320000 (64-bit, non-prefetchable) [size=4K] Memory at 9131f000 (64-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: intel-lpss 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:5ae8] (rev 0b) Subsystem: ASUSTeK Computer Inc. Device [1043:16a0] Flags: bus master, medium devsel, latency 0 00:1f.1 SMBus [0c05]: Intel Corporation Device [8086:5ad4] (rev 0b) Subsystem: ASUSTeK Computer Inc. Device [1043:16a0] Flags: medium devsel, IRQ 255 Memory at 9131e000 (64-bit, non-prefetchable) [size=256] I/O ports at f040 [size=32] 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 07) Subsystem: ASUSTeK Computer Inc. Device [1043:200f] Flags: bus master, fast devsel, latency 0, IRQ 372 I/O ports at e000 [size=256] Memory at 91204000 (64-bit, non-prefetchable) [size=4K] Memory at 91200000 (64-bit, prefetchable) [size=16K] Capabilities: Kernel driver in use: r8169 02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723] Subsystem: Lite-On Communications Inc Device [11ad:1723] Flags: bus master, fast devsel, latency 0, IRQ 23 I/O ports at d000 [size=256] Memory at 91100000 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: rtl8723be =============== = USB devices = =============== Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 003: ID 0bda:b721 Realtek Semiconductor Corp. Bus 001 Device 002: ID 248a:8366 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub =============== = MMC devices = =============== mmc0 driver: rtsx_usb_sdmmc =============== = I2C devices = =============== i2c-0 name: i915 gmbus dpb driver: i915 i2c-1 name: i915 gmbus dpc driver: i915 i2c-2 name: i915 gmbus misc driver: i915 i2c-3 name: DPDDC-A i2c-4 name: DPDDC-C i2c-5 name: Synopsys DesignWare I2C adapter firmware_path: \_SB_.PCI0.I2C0 driver: i2c_designware i2c-6 name: Synopsys DesignWare I2C adapter firmware_path: \_SB_.PCI0.I2C4 driver: i2c_designware i2c-FTE1200:00 name: FTE1200:00 firmware_path: \_SB_.PCI0.I2C4.ETPD driver: i2c_hid ================ = ALSA devices = ================ 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x91318000 irq 374 ============= = Intel HDA = ============= card0 codec#0: Codec: Realtek ALC256 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0256 Subsystem Id: 0x104312e0 Revision Id: 0x100002 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 D3cold 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="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC256 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, 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="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: [0x44 0x44] Converter: stream=1, 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 [Audio Input] wcaps 0x10051b: Stereo Amp-In Device: name="ALC256 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 0x24 Node 0x08 [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 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 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x0c [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x0d [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x0e [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x0f [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x10 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x11 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-In vals: [0x00 0x00] Pincap 0x00000020: IN Pin Default 0x40000000: [N/A] Line Out at Ext N/A Conn = Unknown, Color = Unknown DefAssociation = 0x0, Sequence = 0x0 Pin-ctls: 0x00: Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Node 0x13 [Pin Complex] wcaps 0x40040b: Stereo Amp-In Control: name="Internal Mic Boost Volume", index=1, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-In vals: [0x00 0x00] Pincap 0x00000020: IN Pin Default 0x411111f0: [N/A] Speaker at Ext Rear Conn = 1/8, Color = Black DefAssociation = 0xf, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x20: IN Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Node 0x14 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out 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 0x411111f0: [N/A] Speaker at Ext Rear Conn = 1/8, Color = Black DefAssociation = 0xf, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x00: Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Connection: 1 0x02 Node 0x15 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x16 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x17 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x18 [Pin Complex] wcaps 0x40048b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-In vals: [0x00 0x00] Pincap 0x00003724: IN Detect Vref caps: HIZ 50 GRD 80 100 Pin Default 0x411111f0: [N/A] Speaker at Ext Rear Conn = 1/8, Color = Black DefAssociation = 0xf, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x20: IN VREF_HIZ Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Node 0x19 [Pin Complex] wcaps 0x40048b: Stereo Amp-In Control: name="Headset Mic Boost Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-In vals: [0x00 0x00] Pincap 0x00003724: IN Detect Vref caps: HIZ 50 GRD 80 100 Pin Default 0x411111f0: [N/A] Speaker at Ext Rear Conn = 1/8, Color = Black DefAssociation = 0xf, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x24: IN VREF_80 Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Node 0x1a [Pin Complex] wcaps 0x40048b: 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=0x27, mute=0 Amp-In vals: [0x00 0x00] Pincap 0x00003724: IN Detect Vref caps: HIZ 50 GRD 80 100 Pin Default 0x90a70130: [Fixed] Mic at Int N/A Conn = Analog, Color = Unknown DefAssociation = 0x3, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x24: IN VREF_80 Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x1b [Pin Complex] wcaps 0x40058f: Stereo Amp-In Amp-Out Control: name="Speaker Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-In vals: [0x00 0x00] Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x00013734: IN OUT EAPD Detect Vref caps: HIZ 50 GRD 80 100 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 VREF_HIZ Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 2 0x02 0x03* Node 0x1c [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x1d [Pin Complex] wcaps 0x400400: Mono Pincap 0x00000020: IN Pin Default 0x40489a6d: [N/A] SPDIF Out at Ext N/A Conn = DIN, Color = Pink DefAssociation = 0x6, Sequence = 0xd 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=91 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 0x0001001c: OUT HP EAPD Detect EAPD 0x2: EAPD Pin Default 0x03211020: [Jack] HP Out at Ext Left Conn = 1/8, Color = Black DefAssociation = 0x2, Sequence = 0x0 Pin-ctls: 0xc0: OUT HP Unsolicited: tag=01, enabled=1 Power states: D0 D1 D2 D3 EPSS Power: setting=D3, actual=D3 Connection: 2 0x02* 0x03 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] Connection: 5 0x18 0x19 0x1a 0x1b 0x1d 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] [0x00 0x00] [0x80 0x80] [0x80 0x80] [0x80 0x80] Connection: 6 0x18 0x19 0x1a 0x1b 0x1d 0x12 Node 0x24 [Audio Selector] wcaps 0x300101: Stereo Connection: 2 0x12* 0x13 card0 codec#2: Codec: Intel Broxton HDMI Address: 2 AFG Function Id: 0x1 (unsol 0) Vendor Id: 0x8086280a 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 [0x1a]: 16 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 [0x1a]: 16 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 [0x1a]: 16 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 Control: name="IEC958 Playback Con Mask", index=0, device=0 Control: name="IEC958 Playback Pro Mask", index=0, device=0 Control: name="IEC958 Playback Default", index=0, device=0 Control: name="IEC958 Playback Switch", index=0, device=0 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 Control: name="IEC958 Playback Con Mask", index=1, device=0 Control: name="IEC958 Playback Pro Mask", index=1, device=0 Control: name="IEC958 Playback Default", index=1, device=0 Control: name="IEC958 Playback Switch", index=1, device=0 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 Control: name="IEC958 Playback Con Mask", index=2, device=0 Control: name="IEC958 Playback Pro Mask", index=2, device=0 Control: name="IEC958 Playback Default", index=2, device=0 Control: name="IEC958 Playback Switch", index=2, device=0 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 hwC0D0: vendor: 0x10ec0256 subsystem: 0x104312e0 init_pin_configs: 0x12 0x40000000 0x13 0x411111f0 0x14 0x411111f0 0x18 0x411111f0 0x19 0x411111f0 0x1a 0x90a70130 0x1b 0x90170110 0x1d 0x40489a6d 0x1e 0x411111f0 0x21 0x03211020 driver_pin_configs: 0x13 0x90a60160 0x19 0x04a11120 hwC0D2: vendor: 0x8086280a subsystem: 0x80860101 init_pin_configs: 0x05 0x18560010 0x06 0x18560010 0x07 0x18560010 ============ = Printers = ============ CUPS status: ------------ scheduler is running no system default destination =============== = Temperature = =============== +42°C ==================== = Chromium plugins = ==================== Flash Version: 29.0.0.171 Widevine Version: 66.0.3359.139-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.4.4 License GPL 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 Файлы из чёрного списка: Общее количество: 0 файлов в чёрном списке =================== = Flatpak remotes = =================== eos-apps Endless Applications https://ostree.endlessm.com/ostree/eos-apps 1 eos-external-apps - file:///var/lib/flatpak-external-apps 1 no-gpg-verify eos-runtimes Endless OS and Runtimes https://ostree.endlessm.com/ostree/eos-amd64 1 gnome - https://sdk.gnome.org/repo/ 1 gnome-apps - https://sdk.gnome.org/repo-apps/ 1 ============= = Processes = ============= USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.1 119632 5812 ? Ss 16:12 0:02 /lib/systemd/systemd --switched-root --system --deserialize 24 root 2 0.0 0.0 0 0 ? S 16:12 0:00 [kthreadd] root 3 0.0 0.0 0 0 ? S 16:12 0:00 [ksoftirqd/0] root 5 0.0 0.0 0 0 ? S< 16:12 0:00 [kworker/0:0H] root 7 0.1 0.0 0 0 ? S 16:12 0:03 [rcu_sched] root 8 0.0 0.0 0 0 ? S 16:12 0:00 [rcu_bh] root 9 0.0 0.0 0 0 ? S 16:12 0:00 [migration/0] root 10 0.0 0.0 0 0 ? S< 16:12 0:00 [lru-add-drain] root 11 0.0 0.0 0 0 ? S 16:12 0:00 [watchdog/0] root 12 0.0 0.0 0 0 ? S 16:12 0:00 [cpuhp/0] root 13 0.0 0.0 0 0 ? S 16:12 0:00 [cpuhp/1] root 14 0.0 0.0 0 0 ? S 16:12 0:00 [watchdog/1] root 15 0.0 0.0 0 0 ? S 16:12 0:00 [migration/1] root 16 0.0 0.0 0 0 ? S 16:12 0:00 [ksoftirqd/1] root 18 0.0 0.0 0 0 ? S< 16:12 0:00 [kworker/1:0H] root 19 0.0 0.0 0 0 ? S 16:12 0:00 [cpuhp/2] root 20 0.0 0.0 0 0 ? S 16:12 0:00 [watchdog/2] root 21 0.0 0.0 0 0 ? S 16:12 0:00 [migration/2] root 22 0.0 0.0 0 0 ? S 16:12 0:00 [ksoftirqd/2] root 24 0.0 0.0 0 0 ? S< 16:12 0:00 [kworker/2:0H] root 25 0.0 0.0 0 0 ? S 16:12 0:00 [cpuhp/3] root 26 0.0 0.0 0 0 ? S 16:12 0:00 [watchdog/3] root 27 0.0 0.0 0 0 ? S 16:12 0:00 [migration/3] root 28 0.0 0.0 0 0 ? S 16:12 0:00 [ksoftirqd/3] root 30 0.0 0.0 0 0 ? S< 16:12 0:00 [kworker/3:0H] root 31 0.0 0.0 0 0 ? S 16:12 0:00 [kdevtmpfs] root 32 0.0 0.0 0 0 ? S< 16:12 0:00 [netns] root 33 0.0 0.0 0 0 ? S 16:12 0:00 [khungtaskd] root 34 0.0 0.0 0 0 ? S 16:12 0:00 [oom_reaper] root 35 0.0 0.0 0 0 ? S< 16:12 0:00 [writeback] root 36 0.0 0.0 0 0 ? S 16:12 0:00 [kcompactd0] root 37 0.0 0.0 0 0 ? SN 16:12 0:00 [ksmd] root 38 0.0 0.0 0 0 ? SN 16:12 0:00 [khugepaged] root 39 0.0 0.0 0 0 ? S< 16:12 0:00 [crypto] root 40 0.0 0.0 0 0 ? S< 16:12 0:00 [kintegrityd] root 41 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 42 0.0 0.0 0 0 ? S< 16:12 0:00 [kblockd] root 43 0.0 0.0 0 0 ? S< 16:12 0:00 [ata_sff] root 44 0.0 0.0 0 0 ? S< 16:12 0:00 [md] root 45 0.0 0.0 0 0 ? S< 16:12 0:00 [devfreq_wq] root 46 0.0 0.0 0 0 ? S< 16:12 0:00 [watchdogd] root 50 0.0 0.0 0 0 ? S 16:12 0:00 [kswapd0] root 51 0.0 0.0 0 0 ? S< 16:12 0:00 [vmstat] root 52 0.0 0.0 0 0 ? S 16:12 0:00 [ecryptfs-kthrea] root 91 0.0 0.0 0 0 ? S< 16:12 0:00 [kthrotld] root 92 0.0 0.0 0 0 ? S< 16:12 0:00 [acpi_thermal_pm] root 94 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 95 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 96 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 97 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 99 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 100 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 101 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 102 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 103 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 104 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 105 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 106 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 107 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 108 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 109 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 110 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 111 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 113 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 114 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 115 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 116 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 117 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 118 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 119 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 123 0.0 0.0 0 0 ? S< 16:12 0:00 [ipv6_addrconf] root 144 0.0 0.0 0 0 ? S< 16:12 0:00 [deferwq] root 145 0.0 0.0 0 0 ? S< 16:12 0:00 [charger_manager] root 158 0.0 0.0 0 0 ? S 16:12 0:00 [kworker/3:1] root 175 0.0 0.0 0 0 ? S 16:12 0:00 [kauditd] root 220 0.0 0.0 0 0 ? S 16:12 0:00 [scsi_eh_0] root 221 0.0 0.0 0 0 ? S< 16:12 0:00 [scsi_tmf_0] root 222 0.0 0.0 0 0 ? S 16:12 0:00 [scsi_eh_1] root 223 0.0 0.0 0 0 ? S< 16:12 0:00 [scsi_tmf_1] root 229 0.0 0.0 0 0 ? S 16:12 0:00 [i915/signal:0] root 230 0.0 0.0 0 0 ? S 16:12 0:00 [i915/signal:1] root 231 0.0 0.0 0 0 ? S 16:12 0:00 [i915/signal:2] root 232 0.0 0.0 0 0 ? S 16:12 0:00 [i915/signal:4] root 237 0.3 0.0 0 0 ? S 16:12 0:10 [kworker/u8:5] root 238 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 240 0.0 0.0 0 0 ? S< 16:12 0:00 [bioset] root 256 0.0 0.0 0 0 ? S< 16:12 0:00 [kworker/0:1H] root 260 0.0 0.0 0 0 ? S 16:12 0:00 [jbd2/sda3-8] root 261 0.0 0.0 0 0 ? S< 16:12 0:00 [ext4-rsv-conver] root 263 0.0 0.0 0 0 ? S 16:12 0:00 [ext4lazyinit] root 312 0.0 0.0 28980 3852 ? Ss 16:12 0:01 /lib/systemd/systemd-journald root 329 0.0 0.0 0 0 ? S< 16:12 0:00 [kworker/2:1H] root 331 0.0 0.0 0 0 ? S< 16:12 0:00 [kworker/3:1H] root 359 0.0 0.1 48668 5852 ? Ss 16:12 0:01 /lib/systemd/systemd-udevd root 431 0.0 0.0 0 0 ? S< 16:12 0:00 [asus_wireless_w] root 439 0.0 0.0 0 0 ? S< 16:12 0:00 [kworker/1:1H] root 443 0.0 0.0 0 0 ? S 16:12 0:00 [irq/373-mei_me] root 454 0.0 0.0 0 0 ? S< 16:12 0:00 [cfg80211] root 455 0.0 0.0 0 0 ? S< 16:12 0:00 [kworker/u9:0] root 456 0.0 0.0 0 0 ? S< 16:12 0:00 [hci0] root 457 0.0 0.0 0 0 ? S< 16:12 0:00 [hci0] root 459 0.0 0.0 0 0 ? S< 16:12 0:00 [kworker/u9:2] root 498 0.0 0.0 0 0 ? S< 16:12 0:00 [led_workqueue] root 500 0.0 0.0 0 0 ? S 16:12 0:00 [irq/117-FTE1200] root 544 0.0 0.0 0 0 ? S< 16:12 0:00 [kmemstick] root 545 0.0 0.0 0 0 ? D 16:12 0:00 [rtsx_usb_ms_1] root 546 0.0 0.0 0 0 ? S< 16:12 0:00 [kvm-irqfd-clean] polkitd 559 0.0 0.4 403116 18824 ? Ssl 16:12 0:00 /usr/lib/polkit-1/polkitd --no-debug message+ 560 0.0 0.1 44176 4872 ? Ss 16:12 0:01 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation root 562 0.0 0.2 391520 11064 ? Ssl 16:12 0:00 /usr/lib/udisks2/udisksd --no-debug root 566 0.0 0.1 207372 6904 ? Ss 16:12 0:00 /usr/sbin/cupsd -f root 567 0.0 0.2 414108 8460 ? Ssl 16:12 0:00 /usr/lib/accountsservice/accounts-daemon root 568 0.0 0.1 43460 6800 ? Ss 16:12 0:00 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant root 572 0.0 0.0 30680 3100 ? Ss 16:12 0:00 /lib/systemd/systemd-logind root 573 0.0 0.2 360536 9464 ? Ssl 16:12 0:00 /usr/lib/upower/upowerd geoclue 578 0.0 0.6 473592 25516 ? Ssl 16:12 0:00 /usr/lib/geoclue-2.0/geoclue -t 5 root 581 0.0 0.1 31912 4656 ? Ss 16:12 0:00 /usr/lib/bluetooth/bluetoothd root 583 0.0 0.4 632832 18132 ? Ssl 16:12 0:01 /usr/sbin/NetworkManager --no-daemon avahi 584 0.0 0.0 49016 3568 ? Ss 16:12 0:00 avahi-daemon: running [endless.local] metrics 586 0.0 0.2 344040 10148 ? Ssl 16:12 0:00 /usr/lib/eos-event-recorder-daemon/eos-metrics-event-recorder root 587 0.0 0.2 340212 9180 ? Ssl 16:12 0:00 /usr/sbin/ModemManager root 592 0.0 0.2 480816 8276 ? Ssl 16:12 0:00 /usr/sbin/gdm avahi 600 0.0 0.0 48892 372 ? S 16:12 0:00 avahi-daemon: chroot helper root 601 0.0 0.2 255624 8816 ? Ssl 16:12 0:00 /usr/sbin/cups-browsed root 622 3.1 1.2 495672 48512 tty1 Ssl+ 16:12 1:35 /usr/lib/xorg/Xorg :0 -background none -noreset -verbose 3 -logfile /dev/null -auth /var/run/gdm3/auth-for-Debian-gdm-FLBlx4/database -seat seat0 -nolisten tcp vt1 root 660 0.0 0.1 288824 7144 ? Ssl 16:12 0:00 /usr/lib/x86_64-linux-gnu/eos-metrics-instrumentation ntp 666 0.0 0.1 41988 4600 ? Ss 16:12 0:00 /usr/sbin/ntpd -u ntp:ntp -g root 726 0.0 0.1 26392 4440 ? S 16:12 0:00 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-enp1s0.pid -lf /var/lib/NetworkManager/dhclient-b2006f77-a4b4-3289-a06a-4e8137a59ed2-enp1s0.lease -cf /var/lib/NetworkManager/dhclient-enp1s0.conf enp1s0 root 748 0.0 0.1 26392 4424 ? S 16:12 0:00 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-wlp2s0.pid -lf /var/lib/NetworkManager/dhclient-9cf0bafd-2997-4f60-878a-93e2c58b88c3-wlp2s0.lease -cf /var/lib/NetworkManager/dhclient-wlp2s0.conf wlp2s0 root 785 0.0 0.3 439676 13864 ? Ssl 16:12 0:00 /usr/lib/colord/colord rtkit 796 0.0 0.0 187648 3156 ? SNsl 16:12 0:00 /usr/lib/rtkit/rtkit-daemon root 854 0.0 0.0 0 0 ? S< 16:12 0:00 [krfcommd] root 1099 0.0 0.2 366088 10520 ? Sl 16:13 0:00 gdm-session-worker [pam/gdm-password] user 1106 0.0 0.1 45252 5036 ? Ss 16:13 0:00 /lib/systemd/systemd --user user 1107 0.0 0.0 179304 2208 ? S 16:13 0:00 (sd-pam) user 1112 0.0 0.2 326668 7948 ? Sl 16:13 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login user 1117 0.0 0.3 660984 13808 ? Ssl 16:13 0:00 /usr/lib/gnome-session/gnome-session-binary --session=eos-shell user 1221 0.0 0.0 43604 1928 ? S 16:13 0:00 /usr/bin/dbus-launch --exit-with-session --sh-syntax user 1222 0.0 0.0 43516 3840 ? Ss 16:13 0:01 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session user 1237 0.0 0.0 10740 328 ? Ss 16:13 0:00 /usr/bin/ssh-agent /usr/bin/im-launch gnome-session --session=eos-shell user 1311 0.0 0.2 397932 9180 ? Sl 16:13 0:00 /usr/lib/gvfs/gvfsd user 1323 0.0 0.2 364056 7968 ? Sl 16:13 0:00 /usr/lib/at-spi2-core/at-spi-bus-launcher user 1328 0.0 0.1 42816 3964 ? S 16:13 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 user 1330 0.0 0.1 215800 5572 ? Sl 16:13 0:00 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session user 1347 0.0 0.9 1139276 38844 ? Sl 16:13 0:01 /usr/lib/gnome-settings-daemon/gnome-settings-daemon user 1365 0.0 0.3 553476 12248 ? S user 1764 0.0 0.2 453604 10212 ? Sl 16:14 0:00 /usr/lib/flatpak/flatpak-session-helper user 1769 0.0 0.2 677460 11192 ? Sl 16:14 0:00 /usr/lib/flatpak/xdg-document-portal user 1773 0.0 0.2 437024 7836 ? Sl 16:14 0:00 /usr/lib/flatpak/xdg-permission-store root 1819 0.0 0.3 176888 15388 ? Ssl 16:14 0:00 /usr/bin/xapian-bridge user 1897 0.0 0.2 425876 8724 ? Sl 16:15 0:00 /usr/lib/gvfs/gvfsd-http --spawner :1.6 /org/gtk/gvfs/exec_spaw/0 user 2043 0.8 4.8 3102188 190052 ? SLl 16:16 0:22 /usr/lib/chromium-browser/chromium-browser --ppapi-flash-path=/var/lib/chromium-plugins-extra/eos-chrome-plugin-updater/libpepflashplayer.so --ppapi-flash-version=29.0.0.171 --enable-pinch user 2100 0.0 0.2 486588 9064 ? Sl 16:16 0:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.6 /org/gtk/gvfs/exec_spaw/1 user 2113 0.0 0.1 471372 6700 ? Sl 16:16 0:00 /usr/lib/gvfs/gvfsd-burn --spawner :1.6 /org/gtk/gvfs/exec_spaw/2 user 2119 0.0 0.2 307136 7964 ? Sl 16:16 0:00 /usr/lib/gvfs/gvfsd-metadata user 2124 0.0 2.0 569212 78532 ? S 16:16 0:00 /usr/lib/chromium-browser/chromium-browser --type=zygote --ppapi-flash-path=/var/lib/chromium-plugins-extra/eos-chrome-plugin-updater/libpepflashplayer.so --ppapi-flash-version=29.0.0.171 user 2126 0.0 0.3 569212 14508 ? S 16:16 0:00 /usr/lib/chromium-browser/chromium-browser --type=zygote --ppapi-flash-path=/var/lib/chromium-plugins-extra/eos-chrome-plugin-updater/libpepflashplayer.so --ppapi-flash-version=29.0.0.171 user 2173 0.3 3.7 1102836 147460 ? Sl 16:16 0:10 /usr/lib/chromium-browser/chromium-browser --type=gpu-process --channel=2043.0.1697145542 --mojo-application-channel-token=69D0EFA26E7AC3C37B4E367C3E5A9232 --enable-features=DocumentWriteEvaluator root 3761 0.1 0.0 0 0 ? S 16:56 0:00 [kworker/2:0] root 3770 0.0 0.0 0 0 ? S 16:57 0:00 [kworker/0:2] root 3772 0.0 0.0 0 0 ? S 16:57 0:00 [kworker/2:3] root 3791 0.0 0.0 0 0 ? S 16:58 0:00 [kworker/3:0] user 3814 0.0 0.0 13304 1616 ? S 16:58 0:00 /usr/bin/bwrap --args 57 /usr/lib/flatpak/flatpak-dbus-proxy --fd=59 unix:abstract=/tmp/dbus-finfLFfhzC,guid=afce26a54a075720e218a5b45af44575 /run/user/1001/.session-bus-proxy-JLCWIZ user 3815 0.0 0.0 187272 2764 ? Sl 16:58 0:00 /usr/lib/flatpak/flatpak-dbus-proxy --fd=59 unix:abstract=/tmp/dbus-finfLFfhzC,guid=afce26a54a075720e218a5b45af44575 /run/user/1001/.session-bus-proxy-JLCWIZ user 3816 0.0 0.0 0 0 ? Z 16:58 0:00 [bwrap] root 3894 0.0 0.0 0 0 ? S 17:02 0:00 [kworker/1:1] user 3907 2.2 0.9 708628 35476 ? Sl 17:02 0:00 /usr/lib/gnome-terminal/gnome-terminal-server user 3913 0.5 0.1 139088 5408 pts/0 Ss 17:02 0:00 bash root 3920 0.0 0.0 0 0 ? S 17:02 0:00 [kworker/0:1] root 3921 0.0 0.0 0 0 ? S 17:02 0:00 [kworker/0:3] user 3922 16.0 0.6 579224 25852 pts/0 Sl+ 17:02 0:00 gjs /usr/bin/eos-diagnostics user 3973 0.0 0.0 151472 3324 pts/0 R+ 17:02 0:00 ps aux =============== = Boot timing = =============== Startup finished in 8.236s (firmware) + 6.800s (loader) + 1.813s (kernel) + 3.493s (initrd) + 15.541s (userspace) = 35.885s =========== = Journal = =========== -- Logs begin at Чтв 2018-05-10 16:12:04 EEST, end at Чтв 2018-05-10 17:02:44 EEST. -- Май 10 16:12:04 endless systemd-journald[312]: Runtime journal (/run/log/journal/) is 512.0K, max 4.0M, 3.5M free. Май 10 16:12:04 endless systemd-journald[166]: Received SIGTERM from PID 1 (systemd). Май 10 16:12:04 endless kernel: systemd: 20 output lines suppressed due to ratelimiting Май 10 16:12:04 endless systemd[1]: Failed to insert module 'kdbus': Function not implemented Май 10 16:12:04 endless kernel: random: crng init done Май 10 16:12:04 endless systemd-readahead[320]: Bumped block_nr parameter of 8:0 to 20480. This is a temporary hack and should be removed one day. Май 10 16:12:04 endless systemd-journald[312]: Journal started Май 10 16:12:02 endless systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) Май 10 16:12:02 endless systemd[1]: Detected architecture x86-64. Май 10 16:12:02 endless systemd[1]: Set hostname to . Май 10 16:12:03 endless systemd[1]: [/usr/lib/systemd/system/var-endless\x2dextra.mount:6] Unit dependency type RequiresOverridable= is obsolete, replacing by Requires=, please update your unit file Май 10 16:12:04 endless systemd[1]: Started Apply Kernel Variables. Май 10 16:12:04 endless kernel: EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro Май 10 16:12:04 endless systemd[1]: Mounted POSIX Message Queue File System. Май 10 16:12:04 endless systemd[1]: Mounted Huge Pages File System. Май 10 16:12:04 endless systemd[1]: Mounted FUSE Control File System. Май 10 16:12:04 endless systemd[1]: Mounted Debug File System. Май 10 16:12:04 endless systemd[1]: Mounted Temporary Directory. Май 10 16:12:04 endless systemd[1]: Started Remount Root and Kernel File Systems. Май 10 16:12:04 endless systemd[1]: Starting udev Coldplug all Devices... Май 10 16:12:04 endless systemd[1]: Starting OSTree Remount OS/ bind mounts... Май 10 16:12:04 endless kernel: EXT4-fs (sda3): re-mounted. Opts: (null) Май 10 16:12:04 endless kernel: EXT4-fs (sda3): re-mounted. Opts: (null) Май 10 16:12:04 endless systemd[1]: Started OSTree Remount OS/ bind mounts. Май 10 16:12:04 endless systemd[1]: Starting Flush Journal to Persistent Storage... Май 10 16:12:04 endless systemd[1]: Starting Load/Save Random Seed... Май 10 16:12:04 endless systemd[1]: Started Load/Save Random Seed. Май 10 16:12:04 endless fake-hwclock[317]: Current system time: 2018-05-10 13:12:04 Май 10 16:12:04 endless fake-hwclock[317]: fake-hwclock saved clock information is in the past: 2018-05-10 13:11:39 Май 10 16:12:04 endless fake-hwclock[317]: To set system time to this saved clock anyway, use "force" Май 10 16:12:04 endless systemd[1]: Started Restore / save the current clock. Май 10 16:12:04 endless systemd[1]: Started Create Static Device Nodes in /dev. Май 10 16:12:04 endless systemd[1]: Started Flush Journal to Persistent Storage. Май 10 16:12:04 endless systemd[1]: Reached target Local File Systems (Pre). Май 10 16:12:04 endless systemd[1]: Reached target Local File Systems. Май 10 16:12:04 endless systemd[1]: Starting Restore /run/initramfs on shutdown... Май 10 16:12:04 endless systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... Май 10 16:12:04 endless systemd[1]: Starting Create Volatile Files and Directories... Май 10 16:12:04 endless systemd[1]: Starting Helper script to deal with extra codecs... Май 10 16:12:04 endless systemd[1]: Starting Raise network interfaces... Май 10 16:12:04 endless systemd[1]: Starting udev Kernel Device Manager... Май 10 16:12:04 endless systemd[1]: Started Restore /run/initramfs on shutdown. Май 10 16:12:04 endless systemd[1]: Started Tell Plymouth To Write Out Runtime Data. Май 10 16:12:04 endless eos-codecs-activate[357]: No GPG keys found in /var/lib/codecs/.gnupg/keys.d, exiting Май 10 16:12:04 endless systemd[1]: Started Helper script to deal with extra codecs. Май 10 16:12:04 endless systemd[1]: Started udev Coldplug all Devices. Май 10 16:12:04 endless systemd-tmpfiles[354]: "/home" already exists and is not a directory. Май 10 16:12:05 endless systemd[1]: Started Create Volatile Files and Directories. Май 10 16:12:05 endless systemd[1]: Starting Update UTMP about System Boot/Shutdown... Май 10 16:12:05 endless systemd[1]: Started Update UTMP about System Boot/Shutdown. Май 10 16:12:05 endless systemd[1]: Started Raise network interfaces. Май 10 16:12:07 endless systemd[1]: Started udev Kernel Device Manager. Май 10 16:12:07 endless systemd-udevd[417]: Process '/bin/mount -t fusectl fusectl /sys/fs/fuse/connections' failed with exit code 32. Май 10 16:12:07 endless kernel: input: Asus Wireless Radio Control as /devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/input/input6 Май 10 16:12:07 endless kernel: idma64 idma64.0: Found Intel integrated DMA 64-bit Май 10 16:12:07 endless kernel: idma64 idma64.1: Found Intel integrated DMA 64-bit Май 10 16:12:07 endless kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xfed40080-0xfed40fff] Май 10 16:12:07 endless kernel: tpm_crb: probe of MSFT0101:00 failed with error -16 Май 10 16:12:07 endless kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Май 10 16:12:07 endless kernel: FUJITSU Extended Socket Network Device Driver - version 1.1 - Copyright (c) 2015 FUJITSU LIMITED Май 10 16:12:07 endless systemd[1]: Created slice system-systemd\x2dbacklight.slice. Май 10 16:12:07 endless systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight... Май 10 16:12:07 endless kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded Май 10 16:12:07 endless kernel: r8169 0000:01:00.0 eth0: RTL8106e at 0xffffc20d407bc000, 10:7b:44:5d:47:b4, XID 04900000 IRQ 372 Май 10 16:12:07 endless systemd[1]: Started Load/Save Screen Backlight Brightness of backlight:intel_backlight. Май 10 16:12:08 endless mtp-probe[444]: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:15.0/usb1/1-7" Май 10 16:12:08 endless mtp-probe[436]: checking bus 1, device 2: "/sys/devices/pci0000:00/0000:00:15.0/usb1/1-3" Май 10 16:12:08 endless mtp-probe[438]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:15.0/usb1/1-5" Май 10 16:12:08 endless mtp-probe[436]: bus: 1, device: 2 was not an MTP device Май 10 16:12:08 endless mtp-probe[438]: bus: 1, device: 4 was not an MTP device Май 10 16:12:08 endless kernel: Bluetooth: Core ver 2.21 Май 10 16:12:08 endless kernel: NET: Registered protocol family 31 Май 10 16:12:08 endless kernel: Bluetooth: HCI device and connection manager initialized Май 10 16:12:08 endless kernel: Bluetooth: HCI socket layer initialized Май 10 16:12:08 endless kernel: Bluetooth: L2CAP socket layer initialized Май 10 16:12:08 endless kernel: Bluetooth: SCO socket layer initialized Май 10 16:12:08 endless mtp-probe[444]: bus: 1, device: 5 was not an MTP device Май 10 16:12:08 endless kernel: snd_hda_intel 0000:00:0e.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Май 10 16:12:08 endless kernel: usbcore: registered new interface driver btusb Май 10 16:12:08 endless kernel: Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723 Май 10 16:12:08 endless kernel: Bluetooth: hci0: rtl: loading rtl_bt/rtl8723b_fw.bin Май 10 16:12:08 endless systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... Май 10 16:12:08 endless systemd[1]: Starting Helper script to deal with extra codecs... Май 10 16:12:08 endless systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. Май 10 16:12:08 endless systemd[1]: Starting Load/Save RF Kill Switch Status... Май 10 16:12:08 endless systemd[1]: Started Tell Plymouth To Write Out Runtime Data. Май 10 16:12:08 endless kernel: SSE version of gcm_enc/dec engaged. Май 10 16:12:08 endless eos-codecs-activate[465]: No GPG keys found in /var/lib/codecs/.gnupg/keys.d, exiting Май 10 16:12:08 endless systemd[1]: Started Helper script to deal with extra codecs. Май 10 16:12:08 endless kernel: Bluetooth: hci0: rom_version status=0 version=1 Май 10 16:12:08 endless kernel: media: Linux media interface: v0.10 Май 10 16:12:08 endless kernel: Linux video capture interface: v2.00 Май 10 16:12:08 endless kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: line_outs=1 (0x1b/0x0/0x0/0x0/0x0) type:speaker Май 10 16:12:08 endless kernel: snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) Май 10 16:12:08 endless kernel: snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) Май 10 16:12:08 endless kernel: snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0 Май 10 16:12:08 endless kernel: snd_hda_codec_realtek hdaudioC0D0: inputs: Май 10 16:12:08 endless kernel: snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 Май 10 16:12:08 endless kernel: snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x1a Май 10 16:12:08 endless kernel: snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x13 Май 10 16:12:08 endless kernel: input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:0e.0/sound/card0/input7 Май 10 16:12:08 endless kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:0e.0/sound/card0/input8 Май 10 16:12:08 endless kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:0e.0/sound/card0/input9 Май 10 16:12:08 endless kernel: asus_wmi: ASUS WMI generic driver loaded Май 10 16:12:08 endless kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:0e.0/sound/card0/input10 Май 10 16:12:08 endless kernel: asus_wmi: Initialization: 0x1 Май 10 16:12:08 endless kernel: asus_wmi: BIOS WMI version: 9.0 Май 10 16:12:08 endless kernel: asus_wmi: SFUN value: 0x21 Май 10 16:12:08 endless kernel: input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input11 Май 10 16:12:08 endless kernel: asus_wmi: Number of fans: 0 Май 10 16:12:08 endless kernel: r8169 0000:01:00.0 enp1s0: renamed from eth0 Май 10 16:12:08 endless systemd[1]: Starting Helper script to deal with extra codecs... Май 10 16:12:08 endless systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... Май 10 16:12:09 endless eos-codecs-activate[506]: No GPG keys found in /var/lib/codecs/.gnupg/keys.d, exiting Май 10 16:12:09 endless systemd[1]: Started Helper script to deal with extra codecs. Май 10 16:12:09 endless systemd[1]: Started Tell Plymouth To Write Out Runtime Data. Май 10 16:12:09 endless systemd[1]: Starting Helper script to deal with extra codecs... Май 10 16:12:09 endless systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... Май 10 16:12:09 endless eos-codecs-activate[515]: No GPG keys found in /var/lib/codecs/.gnupg/keys.d, exiting Май 10 16:12:09 endless systemd[1]: Started Helper script to deal with extra codecs. Май 10 16:12:09 endless systemd[1]: Reached target Sound Card. Май 10 16:12:09 endless systemd[1]: Started Tell Plymouth To Write Out Runtime Data. Май 10 16:12:09 endless kernel: uvcvideo: Found UVC 1.00 device USB2.0 VGA UVC WebCam (04f2:b52b) Май 10 16:12:09 endless kernel: uvcvideo 1-5:1.0: Entity type for entity Extension 4 was not initialized! Май 10 16:12:09 endless kernel: uvcvideo 1-5:1.0: Entity type for entity Processing 2 was not initialized! Май 10 16:12:09 endless kernel: uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not initialized! Май 10 16:12:09 endless kernel: input: USB2.0 VGA UVC WebCam as /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/input/input12 Май 10 16:12:09 endless kernel: usbcore: registered new interface driver uvcvideo Май 10 16:12:09 endless kernel: USB Video Class driver (1.1.1) Май 10 16:12:09 endless kernel: rtl8723be 0000:02:00.0: enabling device (0000 -> 0003) Май 10 16:12:09 endless kernel: rtl8723be: Using firmware rtlwifi/rtl8723befw.bin Май 10 16:12:09 endless kernel: ieee80211 phy0: Selected rate control algorithm 'rtl_rc' Май 10 16:12:09 endless kernel: rtlwifi: rtlwifi: wireless switch is on Май 10 16:12:09 endless kernel: rtl8723be 0000:02:00.0 wlp2s0: renamed from wlan0 Май 10 16:12:09 endless systemd-udevd[414]: Process '/sbin/crda' failed with exit code 255. Май 10 16:12:09 endless systemd[1]: Started Load/Save RF Kill Switch Status. Май 10 16:12:09 endless systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... Май 10 16:12:09 endless systemd[1]: Starting Helper script to deal with extra codecs... Май 10 16:12:09 endless systemd[1]: Started Tell Plymouth To Write Out Runtime Data. Май 10 16:12:09 endless eos-codecs-activate[548]: No GPG keys found in /var/lib/codecs/.gnupg/keys.d, exiting Май 10 16:12:09 endless systemd[1]: Started Helper script to deal with extra codecs. Май 10 16:12:10 endless kernel: intel_telemetry_core Init Май 10 16:12:10 endless kernel: intel_telemetry: version 1.0.0 loaded Май 10 16:12:10 endless kernel: intel_rapl: Found RAPL domain package Май 10 16:12:10 endless kernel: intel_rapl: Found RAPL domain core Май 10 16:12:10 endless kernel: intel_rapl: Found RAPL domain uncore Май 10 16:12:10 endless kernel: intel_rapl: Found RAPL domain dram Май 10 16:12:10 endless systemd-udevd[417]: Process '/usr/sbin/alsactl -E HOME=/var/run/alsa restore 0' failed with exit code 99. Май 10 16:12:11 endless systemd[1]: Found device ST1000LM035-1RK172 eos-swap. Май 10 16:12:11 endless systemd[1]: Activating swap Swap Partition... Май 10 16:12:11 endless kernel: Adding 4193984k swap on /dev/sda4. Priority:-1 extents:1 across:4193984k FS Май 10 16:12:11 endless systemd[1]: Activated swap Swap Partition. Май 10 16:12:11 endless systemd[1]: Reached target Swap. Май 10 16:12:11 endless systemd[1]: Reached target System Initialization. Май 10 16:12:11 endless systemd[1]: Started CUPS Printer Service Spool. Май 10 16:12:11 endless systemd[1]: Reached target Paths. Май 10 16:12:11 endless systemd[1]: Listening on xapian-bridge.socket. Май 10 16:12:11 endless systemd[1]: Started Send system activation/daily ping messages to Endless. Май 10 16:12:11 endless systemd[1]: Started Daily Cleanup of Temporary Directories. Май 10 16:12:11 endless systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket. Май 10 16:12:11 endless systemd[1]: Listening on KA Lite Server. Май 10 16:12:11 endless systemd[1]: Listening on EndlessOS License Service Socket. Май 10 16:12:11 endless systemd[1]: Listening on CUPS Printing Service Sockets. Май 10 16:12:11 endless systemd[1]: Listening on D-Bus System Message Bus Socket. Май 10 16:12:11 endless systemd[1]: Reached target Sockets. Май 10 16:12:11 endless systemd[1]: Reached target Basic System. Май 10 16:12:11 endless systemd[1]: Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down... Май 10 16:12:11 endless systemd[1]: Starting Authorization Manager... Май 10 16:12:11 endless systemd[1]: Started D-Bus System Message Bus. Май 10 16:12:11 endless systemd[1]: Starting Disk Manager... Май 10 16:12:11 endless systemd[1]: Starting Permit User Sessions... Май 10 16:12:11 endless systemd-udevd[419]: Process '/sbin/crda' failed with exit code 255. Май 10 16:12:11 endless systemd[1]: Started CUPS Printing Service. Май 10 16:12:11 endless systemd[1]: Starting Accounts Service... Май 10 16:12:11 endless systemd[1]: Starting WPA supplicant... Май 10 16:12:11 endless systemd[1]: Starting IIO Sensor Proxy service... Май 10 16:12:11 endless systemd[1]: Starting LSB: Speech Dispatcher... Май 10 16:12:11 endless systemd[1]: Starting LSB: VirtualBox Linux Additions... Май 10 16:12:11 endless systemd[1]: Starting Login Service... Май 10 16:12:11 endless systemd[1]: Starting Daemon for power management... Май 10 16:12:11 endless systemd[1]: Started Bluetooth UART. Май 10 16:12:11 endless systemd[1]: Starting Location Lookup Service... Май 10 16:12:11 endless systemd[1]: Starting Bluetooth service... Май 10 16:12:11 endless systemd[1]: Starting LSB: Record successful boot for GRUB... Май 10 16:12:11 endless systemd[1]: Starting Network Manager... Май 10 16:12:11 endless systemd[1]: Reached target Login Prompts. Май 10 16:12:11 endless systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Май 10 16:12:11 endless systemd[1]: Starting EndlessOS Metrics Event Recorder Server... Май 10 16:12:11 endless systemd[1]: Starting Modem Manager... Май 10 16:12:11 endless systemd[1]: Started EndlessOS Automatic Update Timer. Май 10 16:12:11 endless systemd[1]: Reached target Timers. Май 10 16:12:11 endless systemd[1]: Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down. Май 10 16:12:11 endless systemd[1]: Started Permit User Sessions. Май 10 16:12:11 endless speech-dispatcher[570]: * speech-dispatcher disabled; edit /etc/default/speech-dispatcher Май 10 16:12:11 endless systemd[1]: Started LSB: Speech Dispatcher. Май 10 16:12:11 endless grub-common[582]: * Recording successful boot for GRUB Май 10 16:12:11 endless systemd[1]: Starting Hold until boot process finishes up... Май 10 16:12:11 endless systemd[1]: Starting GNOME Display Manager... Май 10 16:12:11 endless udisksd[562]: udisks daemon version 2.1.7 starting Май 10 16:12:12 endless dbus[560]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' Май 10 16:12:12 endless systemd[1]: Started IIO Sensor Proxy service. Май 10 16:12:12 endless avahi-daemon[584]: Found user 'avahi' (UID 102) and group 'avahi' (GID 106). Май 10 16:12:12 endless avahi-daemon[584]: Successfully dropped root privileges. Май 10 16:12:12 endless avahi-daemon[584]: avahi-daemon 0.6.31 starting up. Май 10 16:12:12 endless systemd[1]: Started Avahi mDNS/DNS-SD Stack. Май 10 16:12:12 endless avahi-daemon[584]: Successfully called chroot(). Май 10 16:12:12 endless avahi-daemon[584]: Successfully dropped remaining capabilities. Май 10 16:12:12 endless avahi-daemon[600]: chroot.c: open() failed: No such file or directory Май 10 16:12:12 endless avahi-daemon[584]: Failed to open /etc/resolv.conf: Invalid argument Май 10 16:12:12 endless systemd[1]: Started Make remote CUPS printers available locally. Май 10 16:12:12 endless avahi-daemon[584]: No service file found in /etc/avahi/services. Май 10 16:12:12 endless avahi-daemon[584]: Network interface enumeration completed. Май 10 16:12:12 endless avahi-daemon[584]: Registering HINFO record with values 'X86_64'/'LINUX'. Май 10 16:12:12 endless avahi-daemon[584]: Server startup complete. Host name is endless.local. Local service cookie is 2727515080. Май 10 16:12:12 endless systemd[1]: Started Login Service. Май 10 16:12:12 endless systemd-logind[572]: New seat seat0. Май 10 16:12:12 endless systemd-logind[572]: Watching system buttons on /dev/input/event6 (Asus Wireless Radio Control) Май 10 16:12:12 endless systemd-logind[572]: Watching system buttons on /dev/input/event4 (Video Bus) Май 10 16:12:12 endless systemd-logind[572]: Watching system buttons on /dev/input/event0 (Power Button) Май 10 16:12:12 endless systemd-logind[572]: Watching system buttons on /dev/input/event1 (Lid Switch) Май 10 16:12:12 endless systemd-logind[572]: Watching system buttons on /dev/input/event2 (Sleep Button) Май 10 16:12:12 endless systemd-logind[572]: Watching system buttons on /dev/input/event11 (Asus WMI hotkeys) Май 10 16:12:12 endless polkitd[559]: Started polkitd version 0.113 Май 10 16:12:12 endless bluetoothd[581]: Bluetooth daemon 5.43 Май 10 16:12:12 endless systemd[1]: Started Bluetooth service. Май 10 16:12:12 endless systemd[1]: Reached target Bluetooth. Май 10 16:12:12 endless bluetoothd[581]: Starting SDP server Май 10 16:12:12 endless kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Май 10 16:12:12 endless kernel: Bluetooth: BNEP filters: protocol multicast Май 10 16:12:12 endless kernel: Bluetooth: BNEP socket layer initialized Май 10 16:12:12 endless dbus[560]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Май 10 16:12:12 endless bluetoothd[581]: Bluetooth management interface 1.13 initialized Май 10 16:12:12 endless bluetoothd[581]: Failed to obtain handles for "Service Changed" characteristic Май 10 16:12:12 endless bluetoothd[581]: Sap driver initialization failed. Май 10 16:12:12 endless bluetoothd[581]: sap-server: Operation not permitted (1) Май 10 16:12:12 endless systemd[1]: Starting Hostname Service... Май 10 16:12:12 endless bluetoothd[581]: Failed to set mode: Blocked through rfkill (0x12) Май 10 16:12:12 endless dbus[560]: [system] Successfully activated service 'org.freedesktop.hostname1' Май 10 16:12:12 endless systemd[1]: Started Hostname Service. Май 10 16:12:12 endless virtualbox-guest-utils[571]: * VirtualBox Additions disabled, not in a Virtual Machine Май 10 16:12:12 endless systemd[1]: Started LSB: VirtualBox Linux Additions. Май 10 16:12:12 endless systemd[1]: Started Daemon for power management. Май 10 16:12:12 endless ModemManager[587]: ModemManager (version 1.4.15) starting in system bus... Май 10 16:12:12 endless cupsd[566]: Listening to [v1.::1]:631 (IPv6) Май 10 16:12:12 endless cupsd[566]: Listening to 127.0.0.1:631 (IPv4) Май 10 16:12:12 endless cupsd[566]: Listening to /var/run/cups/cups.sock (Domain) Май 10 16:12:12 endless cupsd[566]: Remote access is disabled. Май 10 16:12:12 endless cupsd[566]: Added auto ServerAlias endless Май 10 16:12:12 endless cupsd[566]: Loaded configuration file "/etc/cups/cupsd.conf" Май 10 16:12:12 endless cupsd[566]: Repairing ownership of "/var/run/cups" Май 10 16:12:12 endless cupsd[566]: Creating missing directory "/var/run/cups/certs" Май 10 16:12:12 endless cupsd[566]: Repairing ownership of "/var/run/cups/certs" Май 10 16:12:12 endless cupsd[566]: Repairing access permissions of "/var/run/cups/certs" Май 10 16:12:12 endless cupsd[566]: Using default TempDir of /var/spool/cups/tmp... Май 10 16:12:12 endless cupsd[566]: Configured for up to 100 clients. Май 10 16:12:12 endless cupsd[566]: Allowing up to 100 client connections per host. Май 10 16:12:12 endless cupsd[566]: Using policy "default" as the default. Май 10 16:12:12 endless cupsd[566]: Full reload is required. Май 10 16:12:12 endless systemd[1]: Started WPA supplicant. Май 10 16:12:12 endless wpa_supplicant[568]: Successfully initialized wpa_supplicant Май 10 16:12:12 endless systemd[1]: Started GNOME Display Manager. Май 10 16:12:13 endless dbus[560]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' Май 10 16:12:13 endless systemd[1]: Started Location Lookup Service. Май 10 16:12:13 endless cupsd[566]: Loaded MIME database from "/usr/share/cups/mime" and "/etc/cups": 44 types, 83 filters... Май 10 16:12:13 endless grub-common[582]: ...done. Май 10 16:12:13 endless systemd[1]: Started LSB: Record successful boot for GRUB. Май 10 16:12:13 endless dbus[560]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' Май 10 16:12:13 endless polkitd[559]: Loading rules from directory /etc/polkit-1/rules.d Май 10 16:12:13 endless polkitd[559]: Loading rules from directory /usr/share/polkit-1/rules.d Май 10 16:12:13 endless polkitd[559]: Finished loading, compiling and executing 11 rules Май 10 16:12:13 endless dbus[560]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' Май 10 16:12:13 endless polkitd[559]: Acquired the name org.freedesktop.PolicyKit1 on the system bus Май 10 16:12:13 endless systemd[1]: Started Authorization Manager. Май 10 16:12:13 endless dbus[560]: [system] Successfully activated service 'org.freedesktop.ModemManager1' Май 10 16:12:13 endless systemd[1]: Started Modem Manager. Май 10 16:12:13 endless accounts-daemon[567]: started daemon version 0.6.40 Май 10 16:12:13 endless dbus[560]: [system] Successfully activated service 'org.freedesktop.Accounts' Май 10 16:12:13 endless systemd[1]: Started Accounts Service. Май 10 16:12:14 endless NetworkManager[583]: [1525957934.0050] NetworkManager (version 1.2.2) is starting... Май 10 16:12:14 endless gdm-Xorg-:0[622]: X.Org X Server 1.17.3 Май 10 16:12:14 endless gdm-Xorg-:0[622]: Release Date: 2015-10-26 Май 10 16:12:14 endless gdm-Xorg-:0[622]: X Protocol Version 11, Revision 0 Май 10 16:12:14 endless gdm-Xorg-:0[622]: Build Operating System: Linux 3.16.0-4-amd64 x86_64 Endless Май 10 16:12:14 endless gdm-Xorg-:0[622]: Current Operating System: Linux endless 4.8.0-32-generic #34+dev147.48224f3beos3.1.1-Endless SMP Fri Jan 13 13:21:09 UTC x86_64 Май 10 16:12:14 endless gdm-Xorg-:0[622]: Kernel command line: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-40a27c661924b10880bcde7db893844adc31bb8a90f0d6c3b247b9c423e57882/vmlinuz-4.8.0-32-generic root=UUID=817fe263-272d-47ba-945d-d9674912e832 rw splash plymouth.ignore-serial-consoles quiet ostree=/ostree/boot.1/eos/40a27c661924b10880bcde7db893844adc31bb8a90f0d6c3b247b9c423e57882/0 Май 10 16:12:14 endless gdm-Xorg-:0[622]: Build Date: 25 March 2016 09:10:30PM Май 10 16:12:14 endless gdm-Xorg-:0[622]: xorg-server 2:1.17.3-2ubuntu2endless4bem1 (For technical support please see http://www.ubuntu.com/support) Май 10 16:12:14 endless gdm-Xorg-:0[622]: Current version of pixman: 0.32.6 Май 10 16:12:14 endless gdm-Xorg-:0[622]: Before reporting problems, check http://wiki.x.org Май 10 16:12:14 endless gdm-Xorg-:0[622]: to make sure that you have the latest version. Май 10 16:12:14 endless gdm-Xorg-:0[622]: Markers: (--) probed, (**) from config file, (==) default setting, Май 10 16:12:14 endless gdm-Xorg-:0[622]: (++) from command line, (!!) notice, (II) informational, Май 10 16:12:14 endless gdm-Xorg-:0[622]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown. Май 10 16:12:14 endless gdm-Xorg-:0[622]: (++) Log file: "/dev/null", Time: Thu May 10 16:12:14 2018 Май 10 16:12:14 endless NetworkManager[583]: [1525957934.0595] Read config: /etc/NetworkManager/NetworkManager.conf Май 10 16:12:14 endless kernel: i2c_hid i2c-FTE1200:00: failed to reset device. Май 10 16:12:14 endless NetworkManager[583]: [1525957934.2131] manager[0x2373220]: monitoring kernel firmware directory '/lib/firmware'. Май 10 16:12:14 endless NetworkManager[583]: [1525957934.2131] monitoring ifupdown state file '/run/network/ifstate'. Май 10 16:12:14 endless NetworkManager[583]: [1525957934.2167] dns-mgr[0x23880b0]: set resolv-conf-mode: default Май 10 16:12:14 endless NetworkManager[583]: [1525957934.2168] dns-mgr[0x23880b0]: using resolv.conf manager 'resolvconf' Май 10 16:12:14 endless NetworkManager[583]: [1525957934.2187] rfkill3: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:13.1/0000:02:00.0/ieee80211/phy0/rfkill3) (driver rtl8723be) Май 10 16:12:14 endless NetworkManager[583]: [1525957934.2190] rfkill1: found WiFi radio killswitch (at /sys/devices/platform/asus-nb-wmi/rfkill/rfkill1) (platform driver asus-nb-wmi) Май 10 16:12:14 endless NetworkManager[583]: [1525957934.2197] WiFi hardware radio set enabled Май 10 16:12:14 endless NetworkManager[583]: [1525957934.2198] WWAN hardware radio set enabled Май 10 16:12:14 endless systemd[1]: Started Network Manager. Май 10 16:12:14 endless systemd[1]: Reached target Network. Май 10 16:12:14 endless dbus[560]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Май 10 16:12:14 endless systemd[1]: Starting Network Time Service... Май 10 16:12:14 endless systemd[1]: Started Journal Remote Upload Service. Май 10 16:12:14 endless systemd[652]: systemd-journal-upload.service: Failed at step USER spawning /lib/systemd/systemd-journal-upload: No such process Май 10 16:12:14 endless systemd[1]: systemd-journal-upload.service: Main process exited, code=exited, status=217/USER Май 10 16:12:14 endless systemd[1]: systemd-journal-upload.service: Unit entered failed state. Май 10 16:12:14 endless systemd[1]: systemd-journal-upload.service: Failed with result 'exit-code'. Май 10 16:12:14 endless systemd[1]: Starting Network Manager Script Dispatcher Service... Май 10 16:12:14 endless systemd[1]: Started EndlessOS Metrics Event Recorder Server. Май 10 16:12:14 endless systemd[1]: Started EndlessOS Metrics Instrumentation. Май 10 16:12:14 endless cupsd[566]: Generating printcap /var/run/cups/printcap... Май 10 16:12:14 endless cupsd[566]: Loading job cache file "/var/cache/cups/job.cache"... Май 10 16:12:14 endless gdm-Xorg-:0[622]: (==) Using config directory: "/etc/X11/xorg.conf.d" Май 10 16:12:14 endless gdm-Xorg-:0[622]: (==) Using system config directory "/usr/share/X11/xorg.conf.d" Май 10 16:12:14 endless gdm-Xorg-:0[622]: (==) No Layout section. Using the first Screen section. Май 10 16:12:14 endless gdm-Xorg-:0[622]: (==) No screen section available. Using defaults. Май 10 16:12:14 endless gdm-Xorg-:0[622]: (**) |-->Screen "Default Screen Section" (0) Май 10 16:12:14 endless gdm-Xorg-:0[622]: (**) | |-->Monitor "" Май 10 16:12:14 endless gdm-Xorg-:0[622]: (==) No monitor specified for screen "Default Screen Section". Май 10 16:12:14 endless gdm-Xorg-:0[622]: Using a default monitor configuration. Май 10 16:12:14 endless gdm-Xorg-:0[622]: (==) Automatically adding devices Май 10 16:12:14 endless gdm-Xorg-:0[622]: (==) Automatically enabling devices Май 10 16:12:14 endless gdm-Xorg-:0[622]: (==) Automatically adding GPU devices Май 10 16:12:14 endless gdm-Xorg-:0[622]: (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Май 10 16:12:14 endless gdm-Xorg-:0[622]: Entry deleted from font path. Май 10 16:12:14 endless gdm-Xorg-:0[622]: (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. Май 10 16:12:14 endless gdm-Xorg-:0[622]: Entry deleted from font path. Май 10 16:12:14 endless gdm-Xorg-:0[622]: (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. Май 10 16:12:14 endless gdm-Xorg-:0[622]: Entry deleted from font path. Май 10 16:12:14 endless gdm-Xorg-:0[622]: (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. Май 10 16:12:14 endless gdm-Xorg-:0[622]: Entry deleted from font path. Май 10 16:12:14 endless gdm-Xorg-:0[622]: (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. Май 10 16:12:14 endless gdm-Xorg-:0[622]: Entry deleted from font path. Май 10 16:12:14 endless gdm-Xorg-:0[622]: (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. Май 10 16:12:14 endless gdm-Xorg-:0[622]: Entry deleted from font path. Май 10 16:12:14 endless gdm-Xorg-:0[622]: (==) FontPath set to: Май 10 16:12:14 endless gdm-Xorg-:0[622]: /usr/share/fonts/X11/misc, Май 10 16:12:14 endless gdm-Xorg-:0[622]: built-ins Май 10 16:12:14 endless gdm-Xorg-:0[622]: (==) ModulePath set to "/usr/lib/x86_64-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules" Май 10 16:12:14 endless gdm-Xorg-:0[622]: (II) The server relies on udev to provide the list of input devices. Май 10 16:12:14 endless gdm-Xorg-:0[622]: If no devices become available, reconfigure udev or disable AutoAddDevices. Май 10 16:12:14 endless gdm-Xorg-:0[622]: (II) Loader magic: 0x560798239e00 Май 10 16:12:14 endless gdm-Xorg-:0[622]: (II) Module ABI versions: Май 10 16:12:14 endless gdm-Xorg-:0[622]: X.Org ANSI C Emulation: 0.4 Май 10 16:12:14 endless gdm-Xorg-:0[622]: X.Org Video Driver: 19.0 Май 10 16:12:14 endless gdm-Xorg-:0[622]: X.Org XInput driver : 21.0 Май 10 16:12:14 endless gdm-Xorg-:0[622]: X.Org Server Extension : 9.0 Май 10 16:12:14 endless gdm-Xorg-:0[622]: (EE) systemd-logind: failed to get session: PID 622 does not belong to any known session Май 10 16:12:14 endless gdm-Xorg-:0[622]: (II) xfree86: Adding drm device (/dev/dri/card0) Май 10 16:12:14 endless gdm-Xorg-:0[622]: (--) PCI:*(0:0:2:0) 8086:5a84:1043:16a0 rev 11, Mem @ 0x90000000/16777216, 0x80000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072 Май 10 16:12:14 endless gdm-Xorg-:0[622]: (II) LoadModule: "glx" Май 10 16:12:14 endless cupsd[566]: Full reload complete. Май 10 16:12:14 endless cupsd[566]: cupsdCleanFiles(path="/var/spool/cups/tmp", pattern="(null)") Май 10 16:12:14 endless cupsd[566]: Cleaning out old files in "/var/spool/cups/tmp". Май 10 16:12:14 endless cupsd[566]: cupsdCleanFiles(path="/var/cache/cups", pattern="*.ipp") Май 10 16:12:14 endless cupsd[566]: Cleaning out old files in "/var/cache/cups". Май 10 16:12:14 endless cupsd[566]: Listening to [v1.::1]:631 on fd 8... Май 10 16:12:14 endless cupsd[566]: Listening to 127.0.0.1:631 on fd 9... Май 10 16:12:14 endless cupsd[566]: Listening to /var/run/cups/cups.sock:631 on fd 10... Май 10 16:12:14 endless cupsd[566]: Resuming new connection processing... Май 10 16:12:14 endless cupsd[566]: cupsdSetBusyState: newbusy="Not busy", busy="Not busy" Май 10 16:12:14 endless cupsd[566]: Discarding unused server-started event... Май 10 16:12:14 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:12:14 endless dbus[560]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Май 10 16:12:14 endless systemd[1]: Started Network Manager Script Dispatcher Service. Май 10 16:12:14 endless gdm-Xorg-:0[622]: (II) Loading /usr/lib/xorg/modules/extensions/libglx.so Май 10 16:12:14 endless ntpd[651]: ntpd 4.2.6p5@1.2349-o Wed Jun 22 13:54:02 UTC 2016 (1) Май 10 16:12:14 endless systemd[1]: Started Network Time Service. Май 10 16:12:14 endless systemd[1]: Reached target System Time Synchronized. Май 10 16:12:14 endless ntpd[666]: proto: precision = 0.259 usec Май 10 16:12:14 endless systemd[1]: Started Disk Manager. Май 10 16:12:14 endless udisksd[562]: Acquired the name org.freedesktop.UDisks2 on the system message bus Май 10 16:12:14 endless NetworkManager[583]: [1525957934.9032] init! Май 10 16:12:14 endless NetworkManager[583]: [1525957934.9034] interface-parser: parsing file /etc/network/interfaces Май 10 16:12:14 endless NetworkManager[583]: [1525957934.9035] ignoring out-of-block data 'source-directory /etc/network/interfaces.d' Май 10 16:12:14 endless NetworkManager[583]: [1525957934.9035] interface-parser: finished parsing file /etc/network/interfaces Май 10 16:12:14 endless NetworkManager[583]: [1525957934.9035] management mode: unmanaged Май 10 16:12:14 endless NetworkManager[583]: [1525957934.9042] devices added (path: /sys/devices/pci0000:00/0000:00:13.0/0000:01:00.0/net/enp1s0, iface: enp1s0) Май 10 16:12:14 endless NetworkManager[583]: [1525957934.9042] device added (path: /sys/devices/pci0000:00/0000:00:13.0/0000:01:00.0/net/enp1s0, iface: enp1s0): no ifupdown configuration found. Май 10 16:12:14 endless NetworkManager[583]: [1525957934.9043] devices added (path: /sys/devices/pci0000:00/0000:00:13.1/0000:02:00.0/net/wlp2s0, iface: wlp2s0) Май 10 16:12:14 endless NetworkManager[583]: [1525957934.9043] device added (path: /sys/devices/pci0000:00/0000:00:13.1/0000:02:00.0/net/wlp2s0, iface: wlp2s0): no ifupdown configuration found. Май 10 16:12:14 endless NetworkManager[583]: [1525957934.9043] devices added (path: /sys/devices/virtual/net/lo, iface: lo) Май 10 16:12:14 endless NetworkManager[583]: [1525957934.9043] device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found. Май 10 16:12:14 endless NetworkManager[583]: [1525957934.9043] end _init. Май 10 16:12:14 endless NetworkManager[583]: [1525957934.9044] settings: loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-settings-plugin-ifupdown.so) Май 10 16:12:14 endless NetworkManager[583]: [1525957934.9045] settings: loaded plugin keyfile: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Май 10 16:12:14 endless NetworkManager[583]: [1525957934.9045] (37303040) ... get_connections. Май 10 16:12:14 endless NetworkManager[583]: [1525957934.9045] (37303040) ... get_connections (managed=false): return empty list. Май 10 16:12:14 endless ntpd[666]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Май 10 16:12:14 endless ntpd[666]: Listen and drop on 1 v6wildcard :: UDP 123 Май 10 16:12:14 endless ntpd[666]: Listen normally on 2 lo 127.0.0.1 UDP 123 Май 10 16:12:14 endless ntpd[666]: Listen normally on 3 lo ::1 UDP 123 Май 10 16:12:14 endless ntpd[666]: peers refreshed Май 10 16:12:14 endless ntpd[666]: Listening on routing socket on fd #20 for interface updates Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0099] keyfile: new connection /etc/NetworkManager/system-connections/ORN (9cf0bafd-2997-4f60-878a-93e2c58b88c3,"ORN") Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Module glx: vendor="X.Org Foundation" Май 10 16:12:15 endless gdm-Xorg-:0[622]: compiled for 1.17.3, module version = 1.0.0 Май 10 16:12:15 endless gdm-Xorg-:0[622]: ABI class: X.Org Server Extension, version 9.0 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) AIGLX enabled Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) Matched intel as autoconfigured driver 0 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) Matched intel as autoconfigured driver 1 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) Matched modesetting as autoconfigured driver 2 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) Matched fbdev as autoconfigured driver 3 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) Matched vesa as autoconfigured driver 4 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) Assigned the driver to the xf86ConfigLayout Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) LoadModule: "intel" Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0952] get unmanaged devices count: 0 Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0974] settings: hostname: using hostnamed Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0975] settings: hostname changed from (none) to "endless" Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0979] Using DHCP client 'dhclient' Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0980] manager: WiFi enabled by radio killswitch; enabled by state file Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0980] manager: WWAN enabled by radio killswitch; enabled by state file Май 10 16:12:15 endless nm-dispatcher[659]: req:1 'hostname': new request (4 scripts) Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0980] manager: Networking is enabled by state file Май 10 16:12:15 endless nm-dispatcher[659]: req:1 'hostname': start running ordered scripts... Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0981] Loaded device plugin: NMVxlanFactory (internal) Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0981] Loaded device plugin: NMVlanFactory (internal) Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0982] Loaded device plugin: NMVethFactory (internal) Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0982] Loaded device plugin: NMTunFactory (internal) Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0983] Loaded device plugin: NMMacvlanFactory (internal) Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0984] Loaded device plugin: NMIPTunnelFactory (internal) Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0984] Loaded device plugin: NMInfinibandFactory (internal) Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0984] Loaded device plugin: NMEthernetFactory (internal) Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0985] Loaded device plugin: NMBridgeFactory (internal) Май 10 16:12:15 endless NetworkManager[583]: [1525957935.0985] Loaded device plugin: NMBondFactory (internal) Май 10 16:12:15 endless systemd-udevd[419]: Process '/sbin/crda' failed with exit code 255. Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Module intel: vendor="X.Org Foundation" Май 10 16:12:15 endless gdm-Xorg-:0[622]: compiled for 1.17.3, module version = 2.99.917 Май 10 16:12:15 endless gdm-Xorg-:0[622]: Module class: X.Org Video Driver Май 10 16:12:15 endless gdm-Xorg-:0[622]: ABI class: X.Org Video Driver, version 19.0 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) LoadModule: "modesetting" Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Module modesetting: vendor="X.Org Foundation" Май 10 16:12:15 endless gdm-Xorg-:0[622]: compiled for 1.17.3, module version = 1.17.3 Май 10 16:12:15 endless gdm-Xorg-:0[622]: Module class: X.Org Video Driver Май 10 16:12:15 endless gdm-Xorg-:0[622]: ABI class: X.Org Video Driver, version 19.0 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) LoadModule: "fbdev" Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Module fbdev: vendor="X.Org Foundation" Май 10 16:12:15 endless gdm-Xorg-:0[622]: compiled for 1.17.3, module version = 0.4.4 Май 10 16:12:15 endless gdm-Xorg-:0[622]: Module class: X.Org Video Driver Май 10 16:12:15 endless gdm-Xorg-:0[622]: ABI class: X.Org Video Driver, version 19.0 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) LoadModule: "vesa" Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Module vesa: vendor="X.Org Foundation" Май 10 16:12:15 endless gdm-Xorg-:0[622]: compiled for 1.17.3, module version = 2.3.3 Май 10 16:12:15 endless gdm-Xorg-:0[622]: Module class: X.Org Video Driver Май 10 16:12:15 endless gdm-Xorg-:0[622]: ABI class: X.Org Video Driver, version 19.0 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: Май 10 16:12:15 endless gdm-Xorg-:0[622]: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, Май 10 16:12:15 endless gdm-Xorg-:0[622]: 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Май 10 16:12:15 endless gdm-Xorg-:0[622]: Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, Май 10 16:12:15 endless gdm-Xorg-:0[622]: GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel: Driver for Intel(R) HD Graphics: 2000-6000 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) modesetting: Driver for Modesetting Kernel Drivers: kms Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) FBDEV: driver for framebuffer: fbdev Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) VESA: driver for VESA chipsets: vesa Май 10 16:12:15 endless gdm-Xorg-:0[622]: (++) using VT number 1 Май 10 16:12:15 endless ntpd[666]: Deferring DNS for 0.debian.pool.ntp.org 1 Май 10 16:12:15 endless ntpd[666]: Deferring DNS for 1.debian.pool.ntp.org 1 Май 10 16:12:15 endless ntpd[666]: Deferring DNS for 2.debian.pool.ntp.org 1 Май 10 16:12:15 endless ntpd[666]: Deferring DNS for 3.debian.pool.ntp.org 1 Май 10 16:12:15 endless ntpd[666]: Deferring DNS for ntp.ubuntu.com 1 Май 10 16:12:15 endless ntpd[673]: signal_no_reset: signal 17 had flags 4000000 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20160711 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): SNA compiled: xf86-video-intel 3:2.99.917+git20160706+dev46.f09cb89-2bem1 (Autobuild ) Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): SNA compiled for use with valgrind Май 10 16:12:15 endless gdm-Xorg-:0[622]: (WW) Falling back to old probe method for modesetting Май 10 16:12:15 endless gdm-Xorg-:0[622]: (WW) Falling back to old probe method for fbdev Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Loading sub module "fbdevhw" Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) LoadModule: "fbdevhw" Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Loading /usr/lib/xorg/modules/libfbdevhw.so Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Module fbdevhw: vendor="X.Org Foundation" Май 10 16:12:15 endless gdm-Xorg-:0[622]: compiled for 1.17.3, module version = 0.0.2 Май 10 16:12:15 endless gdm-Xorg-:0[622]: ABI class: X.Org Video Driver, version 19.0 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (WW) Falling back to old probe method for vesa Май 10 16:12:15 endless gdm-Xorg-:0[622]: (--) intel(0): gen9 engineering sample Май 10 16:12:15 endless gdm-Xorg-:0[622]: (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2; using a maximum of 4 threads Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): Creating default Display subsection in Screen section Май 10 16:12:15 endless gdm-Xorg-:0[622]: "Default Screen Section" for depth/fbbpp 24/32 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) intel(0): Depth 24, (--) framebuffer bpp 32 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) intel(0): RGB weight 888 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) intel(0): Default visual is TrueColor Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): Output eDP1 has no monitor section Май 10 16:12:15 endless gdm-Xorg-:0[622]: (--) intel(0): Found backlight control interface intel_backlight (type 'raw') for output eDP1 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): Enabled output eDP1 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): Output HDMI1 has no monitor section Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): Enabled output HDMI1 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): Output DP1 has no monitor section Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): Enabled output DP1 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (--) intel(0): Using a maximum size of 256x256 for hardware cursors Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): Output VIRTUAL1 has no monitor section Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): Enabled output VIRTUAL1 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (--) intel(0): Output eDP1 using initial mode 1920x1080 on pipe 0 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) intel(0): TearFree disabled Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) intel(0): DPI set to (96, 96) Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Loading sub module "dri2" Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) LoadModule: "dri2" Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Module "dri2" already built-in Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Loading sub module "present" Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) LoadModule: "present" Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Module "present" already built-in Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) UnloadModule: "modesetting" Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Unloading modesetting Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) UnloadModule: "fbdev" Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Unloading fbdev Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) UnloadSubModule: "fbdevhw" Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Unloading fbdevhw Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) UnloadModule: "vesa" Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) Unloading vesa Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) Depth 24 pixmap format is 32 bpp Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): SNA initialized with Broxton (gen9) backend Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) intel(0): Backing store enabled Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) intel(0): Silken mouse enabled Май 10 16:12:15 endless NetworkManager[583]: [1525957935.6397] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Май 10 16:12:15 endless cupsd[566]: Report: clients=0 Май 10 16:12:15 endless cupsd[566]: Report: jobs=0 Май 10 16:12:15 endless cupsd[566]: Report: jobs-active=0 Май 10 16:12:15 endless cupsd[566]: Report: printers=0 Май 10 16:12:15 endless cupsd[566]: Report: stringpool-string-count=223 Май 10 16:12:15 endless cupsd[566]: Report: stringpool-alloc-bytes=3016 Май 10 16:12:15 endless cupsd[566]: Report: stringpool-total-bytes=3296 Май 10 16:12:15 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): HW Cursor enabled Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message. Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) intel(0): DPMS enabled Май 10 16:12:15 endless gdm-Xorg-:0[622]: (==) intel(0): Display hotplug detection enabled Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): [DRI2] Setup complete Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): [DRI2] DRI driver: i965 Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): [DRI2] VDPAU driver: va_gl Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): direct rendering: DRI2 enabled Май 10 16:12:15 endless gdm-Xorg-:0[622]: (II) intel(0): hardware support for Present enabled Май 10 16:12:15 endless gdm-Xorg-:0[622]: (--) RandR disabled Май 10 16:12:16 endless gdm-Xorg-:0[622]: (II) SELinux: Disabled on system Май 10 16:12:16 endless NetworkManager[583]: [1525957936.1927] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so) Май 10 16:12:16 endless NetworkManager[583]: [1525957936.2813] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so) Май 10 16:12:16 endless NetworkManager[583]: [1525957936.3719] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so) Май 10 16:12:16 endless NetworkManager[583]: [1525957936.3736] (wlp2s0): using nl80211 for WiFi device control Май 10 16:12:16 endless NetworkManager[583]: [1525957936.3766] device (wlp2s0): driver supports Access Point (AP) mode Май 10 16:12:16 endless NetworkManager[583]: [1525957936.4935] manager: (wlp2s0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/0) Май 10 16:12:16 endless NetworkManager[583]: [1525957936.4953] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Май 10 16:12:16 endless kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Май 10 16:12:16 endless gdm-Xorg-:0[622]: (II) AIGLX: enabled GLX_MESA_copy_sub_buffer Май 10 16:12:16 endless gdm-Xorg-:0[622]: (II) AIGLX: enabled GLX_ARB_create_context Май 10 16:12:16 endless gdm-Xorg-:0[622]: (II) AIGLX: enabled GLX_ARB_create_context_profile Май 10 16:12:16 endless gdm-Xorg-:0[622]: (II) AIGLX: enabled GLX_EXT_create_context_es2_profile Май 10 16:12:16 endless gdm-Xorg-:0[622]: (II) AIGLX: enabled GLX_INTEL_swap_event Май 10 16:12:16 endless gdm-Xorg-:0[622]: (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control Май 10 16:12:16 endless gdm-Xorg-:0[622]: (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB Май 10 16:12:16 endless gdm-Xorg-:0[622]: (II) AIGLX: enabled GLX_ARB_fbconfig_float Май 10 16:12:16 endless gdm-Xorg-:0[622]: (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects Май 10 16:12:16 endless gdm-Xorg-:0[622]: (II) AIGLX: enabled GLX_ARB_create_context_robustness Май 10 16:12:16 endless gdm-Xorg-:0[622]: (II) AIGLX: Loaded and initialized i965 Май 10 16:12:16 endless gdm-Xorg-:0[622]: (II) GLX: Initialized DRI2 GL provider for screen 0 Май 10 16:12:16 endless gdm-Xorg-:0[622]: (II) intel(0): switch to mode 1920x1080@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none Май 10 16:12:16 endless gdm-Xorg-:0[622]: (II) intel(0): Setting screen physical size to 508 x 285 Май 10 16:12:16 endless ModemManager[587]: Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:13.0/0000:01:00.0': not supported by any plugin Май 10 16:12:16 endless ModemManager[587]: Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:13.1/0000:02:00.0': not supported by any plugin Май 10 16:12:16 endless gdm-Xorg-:0[622]: (II) XKB: generating xkmfile /tmp/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) config/udev: Adding input device Asus Wireless Radio Control (/dev/input/event6) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Asus Wireless Radio Control: Applying InputClass "evdev keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Asus Wireless Radio Control: Applying InputClass "libinput keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Asus Wireless Radio Control: Applying InputClass "system-keyboard" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) LoadModule: "libinput" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) Module libinput: vendor="X.Org Foundation" Май 10 16:12:17 endless gdm-Xorg-:0[622]: compiled for 1.17.3, module version = 0.18.0 Май 10 16:12:17 endless gdm-Xorg-:0[622]: Module class: X.Org XInput Driver Май 10 16:12:17 endless gdm-Xorg-:0[622]: ABI class: X.Org XInput driver, version 21.0 Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) Using input driver 'libinput' for 'Asus Wireless Radio Control' Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Asus Wireless Radio Control: always reports core events Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "Device" "/dev/input/event6" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "_source" "server/udev" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Asus Wireless Radio Control', /dev/input/event6 is tagged by udev as: Keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Asus Wireless Radio Control', /dev/input/event6 is a keyboard Май 10 16:12:17 endless NetworkManager[583]: [1525957937.0820] manager: (enp1s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/1) Май 10 16:12:17 endless kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Май 10 16:12:17 endless NetworkManager[583]: [1525957937.0833] keyfile: add connection in-memory (b2006f77-a4b4-3289-a06a-4e8137a59ed2,"Проводное соединение 1") Май 10 16:12:17 endless NetworkManager[583]: [1525957937.0839] settings: (enp1s0): created default wired connection 'Проводное соединение 1' Май 10 16:12:17 endless NetworkManager[583]: [1525957937.0850] device (enp1s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Май 10 16:12:17 endless kernel: IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/input/input6/event6" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) XINPUT: Adding extended input device "Asus Wireless Radio Control" (type: KEYBOARD, id 6) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_model" "pc105" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_layout" "ru" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_variant" "phonetic_winkeys" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) XKB: generating xkmfile /tmp/server-90A72D501CBB43337BD0416BE47C4A3ACF701353.xkm Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Asus Wireless Radio Control', /dev/input/event6 is tagged by udev as: Keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Asus Wireless Radio Control', /dev/input/event6 is a keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) config/udev: Adding input device Video Bus (/dev/input/event4) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Video Bus: Applying InputClass "evdev keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Video Bus: Applying InputClass "libinput keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Video Bus: Applying InputClass "system-keyboard" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) Using input driver 'libinput' for 'Video Bus' Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Video Bus: always reports core events Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "Device" "/dev/input/event4" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "_source" "server/udev" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Video Bus', /dev/input/event4 is tagged by udev as: Keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Video Bus', /dev/input/event4 is a keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4/event4" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_model" "pc105" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_layout" "ru" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_variant" "phonetic_winkeys" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Video Bus', /dev/input/event4 is tagged by udev as: Keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Video Bus', /dev/input/event4 is a keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) config/udev: Adding input device Power Button (/dev/input/event0) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Power Button: Applying InputClass "evdev keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Power Button: Applying InputClass "libinput keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Power Button: Applying InputClass "system-keyboard" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) Using input driver 'libinput' for 'Power Button' Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Power Button: always reports core events Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "Device" "/dev/input/event0" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "_source" "server/udev" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Power Button', /dev/input/event0 is tagged by udev as: Keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Power Button', /dev/input/event0 is a keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/PNP0C09:01/PNP0C0C:00/input/input0/event0" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_model" "pc105" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_layout" "ru" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_variant" "phonetic_winkeys" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Power Button', /dev/input/event0 is tagged by udev as: Keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Power Button', /dev/input/event0 is a keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) config/udev: Adding input device Lid Switch (/dev/input/event1) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) No input driver specified, ignoring this device. Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) This device may have been added with another device file. Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) config/udev: Adding input device Sleep Button (/dev/input/event2) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Sleep Button: Applying InputClass "evdev keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Sleep Button: Applying InputClass "libinput keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Sleep Button: Applying InputClass "system-keyboard" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) Using input driver 'libinput' for 'Sleep Button' Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Sleep Button: always reports core events Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "Device" "/dev/input/event2" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "_source" "server/udev" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Sleep Button', /dev/input/event2 is tagged by udev as: Keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Sleep Button', /dev/input/event2 is a keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2/event2" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_model" "pc105" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_layout" "ru" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_variant" "phonetic_winkeys" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Sleep Button', /dev/input/event2 is tagged by udev as: Keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Sleep Button', /dev/input/event2 is a keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event10) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) No input driver specified, ignoring this device. Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) This device may have been added with another device file. Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event7) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) No input driver specified, ignoring this device. Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) This device may have been added with another device file. Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event8) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) No input driver specified, ignoring this device. Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) This device may have been added with another device file. Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event9) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) No input driver specified, ignoring this device. Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) This device may have been added with another device file. Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) config/udev: Adding input device Telink SVEN Wireless Mouse (/dev/input/event5) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Telink SVEN Wireless Mouse: Applying InputClass "evdev pointer catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Telink SVEN Wireless Mouse: Applying InputClass "evdev keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Telink SVEN Wireless Mouse: Applying InputClass "libinput pointer catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Telink SVEN Wireless Mouse: Applying InputClass "libinput keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Telink SVEN Wireless Mouse: Applying InputClass "system-keyboard" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) Using input driver 'libinput' for 'Telink SVEN Wireless Mouse' Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Telink SVEN Wireless Mouse: always reports core events Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "Device" "/dev/input/event5" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "_source" "server/udev" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Telink SVEN Wireless Mouse', /dev/input/event5 is tagged by udev as: Keyboard Mouse Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Telink SVEN Wireless Mouse', /dev/input/event5 is a pointer caps Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Telink SVEN Wireless Mouse', /dev/input/event5 is a keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) libinput: Telink SVEN Wireless Mouse: needs a virtual subdevice Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:15.0/usb1/1-3/1-3:1.0/0003:248A:8366.0001/input/input5/event5" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) XINPUT: Adding extended input device "Telink SVEN Wireless Mouse" (type: MOUSE, id 10) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "AccelerationScheme" "none" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Telink SVEN Wireless Mouse: (accel) selected scheme none/0 Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Telink SVEN Wireless Mouse: (accel) acceleration factor: 2.000 Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Telink SVEN Wireless Mouse: (accel) acceleration threshold: 4 Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Telink SVEN Wireless Mouse', /dev/input/event5 is tagged by udev as: Keyboard Mouse Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Telink SVEN Wireless Mouse', /dev/input/event5 is a pointer caps Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Telink SVEN Wireless Mouse', /dev/input/event5 is a keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) config/udev: Adding input device Telink SVEN Wireless Mouse (/dev/input/mouse0) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Telink SVEN Wireless Mouse: Applying InputClass "system-keyboard" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) No input driver specified, ignoring this device. Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) This device may have been added with another device file. Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) config/udev: Adding input device USB2.0 VGA UVC WebCam (/dev/input/event12) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) USB2.0 VGA UVC WebCam: Applying InputClass "evdev keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) USB2.0 VGA UVC WebCam: Applying InputClass "libinput keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) USB2.0 VGA UVC WebCam: Applying InputClass "system-keyboard" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) Using input driver 'libinput' for 'USB2.0 VGA UVC WebCam' Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) USB2.0 VGA UVC WebCam: always reports core events Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "Device" "/dev/input/event12" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "_source" "server/udev" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'USB2.0 VGA UVC WebCam', /dev/input/event12 is tagged by udev as: Keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'USB2.0 VGA UVC WebCam', /dev/input/event12 is a keyboard Май 10 16:12:17 endless ntpd_intres[673]: host name not found: 0.debian.pool.ntp.org Май 10 16:12:17 endless ntpd_intres[673]: host name not found: 1.debian.pool.ntp.org Май 10 16:12:17 endless ntpd_intres[673]: host name not found: 2.debian.pool.ntp.org Май 10 16:12:17 endless ntpd_intres[673]: host name not found: 3.debian.pool.ntp.org Май 10 16:12:17 endless ntpd_intres[673]: host name not found: ntp.ubuntu.com Май 10 16:12:17 endless kernel: r8169 0000:01:00.0 enp1s0: link down Май 10 16:12:17 endless kernel: r8169 0000:01:00.0 enp1s0: link down Май 10 16:12:17 endless kernel: IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/input/input12/event12" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) XINPUT: Adding extended input device "USB2.0 VGA UVC WebCam" (type: KEYBOARD, id 11) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_model" "pc105" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_layout" "ru" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_variant" "phonetic_winkeys" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'USB2.0 VGA UVC WebCam', /dev/input/event12 is tagged by udev as: Keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'USB2.0 VGA UVC WebCam', /dev/input/event12 is a keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) config/udev: Adding input device Asus WMI hotkeys (/dev/input/event11) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Asus WMI hotkeys: Applying InputClass "evdev keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Asus WMI hotkeys: Applying InputClass "libinput keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Asus WMI hotkeys: Applying InputClass "system-keyboard" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) Using input driver 'libinput' for 'Asus WMI hotkeys' Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Asus WMI hotkeys: always reports core events Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "Device" "/dev/input/event11" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "_source" "server/udev" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Asus WMI hotkeys', /dev/input/event11 is tagged by udev as: Keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Asus WMI hotkeys', /dev/input/event11 is a keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "config_info" "udev:/sys/devices/platform/asus-nb-wmi/input/input11/event11" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) XINPUT: Adding extended input device "Asus WMI hotkeys" (type: KEYBOARD, id 12) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_model" "pc105" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_layout" "ru" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_variant" "phonetic_winkeys" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Asus WMI hotkeys', /dev/input/event11 is tagged by udev as: Keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'Asus WMI hotkeys', /dev/input/event11 is a keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event3) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) AT Translated Set 2 keyboard: Applying InputClass "system-keyboard" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard' Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) AT Translated Set 2 keyboard: always reports core events Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "Device" "/dev/input/event3" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "_source" "server/udev" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'AT Translated Set 2 keyboard', /dev/input/event3 is tagged by udev as: Keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'AT Translated Set 2 keyboard', /dev/input/event3 is a keyboard Май 10 16:12:17 endless NetworkManager[583]: [1525957937.3048] device (lo): link connected Май 10 16:12:17 endless NetworkManager[583]: [1525957937.3059] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/2) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input3/event3" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 13) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_model" "pc105" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_layout" "ru" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_variant" "phonetic_winkeys" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'AT Translated Set 2 keyboard', /dev/input/event3 is tagged by udev as: Keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) input device 'AT Translated Set 2 keyboard', /dev/input/event3 is a keyboard Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Telink SVEN Wireless Mouse: Applying InputClass "evdev pointer catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Telink SVEN Wireless Mouse: Applying InputClass "evdev keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Telink SVEN Wireless Mouse: Applying InputClass "libinput pointer catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Telink SVEN Wireless Mouse: Applying InputClass "libinput keyboard catchall" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Telink SVEN Wireless Mouse: Applying InputClass "system-keyboard" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) Using input driver 'libinput' for 'Telink SVEN Wireless Mouse' Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Telink SVEN Wireless Mouse: always reports core events Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "Device" "/dev/input/event5" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "_source" "_driver/libinput" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) libinput: Telink SVEN Wireless Mouse: is a virtual subdevice Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:15.0/usb1/1-3/1-3:1.0/0003:248A:8366.0001/input/input5/event5" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) XINPUT: Adding extended input device "Telink SVEN Wireless Mouse" (type: KEYBOARD, id 14) Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_model" "pc105" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_layout" "ru" Май 10 16:12:17 endless gdm-Xorg-:0[622]: (**) Option "xkb_variant" "phonetic_winkeys" Май 10 16:12:17 endless systemd[1]: Received SIGRTMIN+21 from PID 215 (plymouthd). Май 10 16:12:17 endless systemd[1]: Started Hold until boot process finishes up. Май 10 16:12:17 endless systemd[1]: Reached target Multi-User System. Май 10 16:12:17 endless systemd[1]: Reached target Graphical Interface. Май 10 16:12:17 endless systemd[1]: Started Stop Read-Ahead Data Collection 10s After Completed Startup. Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) intel(0): EDID vendor "AUO", prod id 14573 Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) intel(0): Printing DDC gathered Modelines: Май 10 16:12:17 endless gdm-Xorg-:0[622]: (II) intel(0): Modeline "1920x1080"x0.0 142.00 1920 2028 2076 2100 1080 1090 1100 1126 -hsync -vsync (67.6 kHz eP) Май 10 16:12:17 endless systemd[1]: Starting Update UTMP about System Runlevel Changes... Май 10 16:12:17 endless systemd[1]: Started Update UTMP about System Runlevel Changes. Май 10 16:12:17 endless systemd[1]: Startup finished in 1.813s (kernel) + 3.493s (initrd) + 15.541s (userspace) = 35.885s. Май 10 16:12:17 endless NetworkManager[583]: [1525957937.5515] bluez: use BlueZ version 5 Май 10 16:12:17 endless NetworkManager[583]: [1525957937.5530] ModemManager available in the bus Май 10 16:12:17 endless NetworkManager[583]: [1525957937.5533] supplicant: wpa_supplicant running Май 10 16:12:17 endless NetworkManager[583]: [1525957937.5533] device (wlp2s0): supplicant interface state: init -> starting Май 10 16:12:17 endless NetworkManager[583]: [1525957937.6669] sup-iface[0x23af1f0,wlp2s0]: supports 4 scan SSIDs Май 10 16:12:17 endless NetworkManager[583]: [1525957937.6682] device (wlp2s0): supplicant interface state: starting -> ready Май 10 16:12:17 endless NetworkManager[583]: [1525957937.6683] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] Май 10 16:12:17 endless kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Май 10 16:12:18 endless gdm-launch-environment][686]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0) Май 10 16:12:18 endless systemd[1]: Created slice User Slice of Debian-gdm. Май 10 16:12:18 endless systemd[1]: Starting User Manager for UID 109... Май 10 16:12:18 endless systemd[1]: Started Session c1 of user Debian-gdm. Май 10 16:12:18 endless systemd-logind[572]: New session c1 of user Debian-gdm. Май 10 16:12:18 endless systemd[697]: pam_unix(systemd-user:session): session opened for user Debian-gdm by (uid=0) Май 10 16:12:18 endless systemd[697]: Reached target Paths. Май 10 16:12:18 endless systemd[697]: Reached target Timers. Май 10 16:12:18 endless systemd[697]: Reached target Sockets. Май 10 16:12:18 endless systemd[697]: Reached target Basic System. Май 10 16:12:18 endless systemd[697]: Reached target Default. Май 10 16:12:18 endless systemd[697]: Startup finished in 52ms. Май 10 16:12:18 endless systemd[1]: Started User Manager for UID 109. Май 10 16:12:18 endless systemd-udevd[419]: Process '/sbin/crda' failed with exit code 255. Май 10 16:12:18 endless kernel: r8169 0000:01:00.0 enp1s0: link up Май 10 16:12:18 endless kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready Май 10 16:12:18 endless NetworkManager[583]: [1525957938.8824] device (enp1s0): link connected Май 10 16:12:18 endless NetworkManager[583]: [1525957938.8834] device (enp1s0): state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] Май 10 16:12:18 endless NetworkManager[583]: [1525957938.8845] policy: auto-activating connection 'Проводное соединение 1' Май 10 16:12:18 endless NetworkManager[583]: [1525957938.8860] device (enp1s0): Activation: starting connection 'Проводное соединение 1' (b2006f77-a4b4-3289-a06a-4e8137a59ed2) Май 10 16:12:18 endless NetworkManager[583]: [1525957938.8862] device (enp1s0): state change: disconnected -> prepare (reason 'none') [30 40 0] Май 10 16:12:18 endless NetworkManager[583]: [1525957938.8866] manager: NetworkManager state is now CONNECTING Май 10 16:12:18 endless NetworkManager[583]: [1525957938.8873] device (enp1s0): state change: prepare -> config (reason 'none') [40 50 0] Май 10 16:12:18 endless NetworkManager[583]: [1525957938.8885] device (enp1s0): state change: config -> ip-config (reason 'none') [50 70 0] Май 10 16:12:18 endless NetworkManager[583]: [1525957938.8899] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds) Май 10 16:12:19 endless NetworkManager[583]: [1525957939.0559] dhcp4 (enp1s0): dhclient started with pid 726 Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1314] device (wlp2s0): supplicant interface state: ready -> inactive Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1332] policy: auto-activating connection 'ORN' Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1345] device (wlp2s0): Activation: starting connection 'ORN' (9cf0bafd-2997-4f60-878a-93e2c58b88c3) Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1348] device (wlp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0] Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1354] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1357] device (wlp2s0): Activation: (wifi) access point 'ORN' has security, but secrets are required. Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1357] device (wlp2s0): state change: config -> need-auth (reason 'none') [50 60 0] Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1420] device (wlp2s0): state change: need-auth -> prepare (reason 'none') [60 40 0] Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1427] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1433] device (wlp2s0): Activation: (wifi) connection 'ORN' has security, and secrets exist. No new secrets needed. Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1434] Config: added 'ssid' value 'ORN' Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1435] Config: added 'scan_ssid' value '1' Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1435] Config: added 'key_mgmt' value 'WPA-PSK' Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1435] Config: added 'auth_alg' value 'OPEN' Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1435] Config: added 'psk' value '' Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1443] sup-iface[0x23af1f0,wlp2s0]: config: set interface ap_scan to 1 Май 10 16:12:19 endless wpa_supplicant[568]: wlp2s0: SME: Trying to authenticate with 78:6a:89:f7:e3:c4 (SSID='ORN' freq=2417 MHz) Май 10 16:12:19 endless kernel: wlp2s0: authenticate with 78:6a:89:f7:e3:c4 Май 10 16:12:19 endless kernel: wlp2s0: send auth to 78:6a:89:f7:e3:c4 (try 1/3) Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1703] device (wlp2s0): supplicant interface state: inactive -> authenticating Май 10 16:12:19 endless wpa_supplicant[568]: wlp2s0: Trying to associate with 78:6a:89:f7:e3:c4 (SSID='ORN' freq=2417 MHz) Май 10 16:12:19 endless kernel: wlp2s0: authenticated Май 10 16:12:19 endless kernel: rtl8723be 0000:02:00.0 wlp2s0: disabling HT/VHT due to WEP/TKIP use Май 10 16:12:19 endless kernel: wlp2s0: associate with 78:6a:89:f7:e3:c4 (try 1/3) Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1816] device (wlp2s0): supplicant interface state: authenticating -> associating Май 10 16:12:19 endless wpa_supplicant[568]: wlp2s0: Associated with 78:6a:89:f7:e3:c4 Май 10 16:12:19 endless kernel: wlp2s0: RX AssocResp from 78:6a:89:f7:e3:c4 (capab=0x431 status=0 aid=2) Май 10 16:12:19 endless kernel: wlp2s0: associated Май 10 16:12:19 endless kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready Май 10 16:12:19 endless systemd-udevd[419]: Process '/sbin/crda' failed with exit code 255. Май 10 16:12:19 endless NetworkManager[583]: [1525957939.1921] device (wlp2s0): supplicant interface state: associating -> associated Май 10 16:12:19 endless org.a11y.Bus[708]: Activating service name='org.a11y.atspi.Registry' Май 10 16:12:19 endless at-spi-bus-laun[730]: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Май 10 16:12:19 endless org.a11y.Bus[708]: Successfully activated service 'org.a11y.atspi.Registry' Май 10 16:12:19 endless org.a11y.atspi.Registry[736]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Май 10 16:12:19 endless dhclient[726]: DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 3 Май 10 16:12:19 endless NetworkManager[583]: [1525957939.4324] device (wlp2s0): supplicant interface state: associated -> 4-way handshake Май 10 16:12:19 endless wpa_supplicant[568]: wlp2s0: WPA: Key negotiation completed with 78:6a:89:f7:e3:c4 [PTK=TKIP GTK=TKIP] Май 10 16:12:19 endless wpa_supplicant[568]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 78:6a:89:f7:e3:c4 completed [id=0 id_str=] Май 10 16:12:19 endless NetworkManager[583]: [1525957939.4439] device (wlp2s0): supplicant interface state: 4-way handshake -> completed Май 10 16:12:19 endless NetworkManager[583]: [1525957939.4439] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'ORN'. Май 10 16:12:19 endless NetworkManager[583]: [1525957939.4440] device (wlp2s0): state change: config -> ip-config (reason 'none') [50 70 0] Май 10 16:12:19 endless NetworkManager[583]: [1525957939.4446] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) Май 10 16:12:19 endless NetworkManager[583]: [1525957939.4469] dhcp4 (wlp2s0): dhclient started with pid 748 Май 10 16:12:19 endless gnome-session[701]: gnome-session-binary[701]: WARNING: Could not parse desktop file caribou-autostart.desktop or it references a not found TryExec binary Май 10 16:12:19 endless gnome-session-binary[701]: WARNING: Could not parse desktop file caribou-autostart.desktop or it references a not found TryExec binary Май 10 16:12:19 endless dhclient[748]: DHCPREQUEST of 192.168.1.37 on wlp2s0 to 255.255.255.255 port 67 Май 10 16:12:19 endless dhclient[748]: DHCPACK of 192.168.1.37 from 192.168.1.1 Май 10 16:12:19 endless NetworkManager[583]: [1525957939.5299] address 192.168.1.37 Май 10 16:12:19 endless NetworkManager[583]: [1525957939.5309] plen 24 (255.255.255.0) Май 10 16:12:19 endless NetworkManager[583]: [1525957939.5316] gateway 192.168.1.1 Май 10 16:12:19 endless NetworkManager[583]: [1525957939.5320] server identifier 192.168.1.1 Май 10 16:12:19 endless NetworkManager[583]: [1525957939.5324] lease time 259200 Май 10 16:12:19 endless NetworkManager[583]: [1525957939.5327] nameserver '212.90.160.2' Май 10 16:12:19 endless NetworkManager[583]: [1525957939.5344] nameserver '212.90.160.8' Май 10 16:12:19 endless NetworkManager[583]: [1525957939.5344] domain name 'dsl.ukrtel.net' Май 10 16:12:19 endless NetworkManager[583]: [1525957939.5345] dhcp4 (wlp2s0): state changed unknown -> bound Май 10 16:12:19 endless avahi-daemon[584]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.37. Май 10 16:12:19 endless avahi-daemon[584]: New relevant interface wlp2s0.IPv4 for mDNS. Май 10 16:12:19 endless avahi-daemon[584]: Registering new address record for 192.168.1.37 on wlp2s0.IPv4. Май 10 16:12:19 endless NetworkManager[583]: [1525957939.5364] device (wlp2s0): state change: ip-config -> ip-check (reason 'none') [70 80 0] Май 10 16:12:19 endless NetworkManager[583]: [1525957939.5371] device (wlp2s0): state change: ip-check -> secondaries (reason 'none') [80 90 0] Май 10 16:12:19 endless NetworkManager[583]: [1525957939.5374] device (wlp2s0): state change: secondaries -> activated (reason 'none') [90 100 0] Май 10 16:12:19 endless dhclient[748]: bound to 192.168.1.37 -- renewal in 120849 seconds. Май 10 16:12:19 endless NetworkManager[583]: [1525957939.6687] policy: set 'ORN' (wlp2s0) as default for IPv4 routing and DNS Май 10 16:12:19 endless NetworkManager[583]: [1525957939.7043] device (wlp2s0): Activation: successful, device activated. Май 10 16:12:19 endless nm-dispatcher[659]: req:2 'up' [wlp2s0]: new request (4 scripts) Май 10 16:12:19 endless nm-dispatcher[659]: req:2 'up' [wlp2s0]: start running ordered scripts... Май 10 16:12:19 endless dbus[560]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' Май 10 16:12:19 endless systemd[1]: Starting Manage, Install and Generate Color Profiles... Май 10 16:12:19 endless colord[785]: Using mapping database file /var/lib/colord/mapping.db Май 10 16:12:20 endless colord[785]: Using device database file /var/lib/colord/storage.db Май 10 16:12:20 endless colord[785]: Using profile database file /var/lib/colord/storage.db Май 10 16:12:20 endless colord[785]: loaded plugin libcd_plugin_sane.so Май 10 16:12:20 endless colord[785]: loaded plugin libcd_plugin_camera.so Май 10 16:12:20 endless colord[785]: loaded plugin libcd_plugin_scanner.so Май 10 16:12:20 endless colord[785]: Daemon ready for requests Май 10 16:12:20 endless dbus[560]: [system] Successfully activated service 'org.freedesktop.ColorManager' Май 10 16:12:20 endless systemd[1]: Started Manage, Install and Generate Color Profiles. Май 10 16:12:20 endless dbus[560]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' Май 10 16:12:20 endless systemd[1]: [/usr/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service' Май 10 16:12:20 endless kernel: i2c_hid i2c-FTE1200:00: failed to reset device. Май 10 16:12:20 endless systemd[1]: Starting RealtimeKit Scheduling Policy Service... Май 10 16:12:20 endless dbus[560]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1' Май 10 16:12:20 endless systemd[1]: Started RealtimeKit Scheduling Policy Service. Май 10 16:12:20 endless rtkit-daemon[796]: Successfully called chroot. Май 10 16:12:20 endless rtkit-daemon[796]: Successfully dropped privileges. Май 10 16:12:20 endless rtkit-daemon[796]: Successfully limited resources. Май 10 16:12:20 endless rtkit-daemon[796]: Running. Май 10 16:12:20 endless rtkit-daemon[796]: Canary thread running. Май 10 16:12:20 endless rtkit-daemon[796]: Watchdog thread running. Май 10 16:12:20 endless rtkit-daemon[796]: Successfully made thread 795 of process 795 (/usr/bin/pulseaudio) owned by '109' high priority at nice level -11. Май 10 16:12:20 endless rtkit-daemon[796]: Supervising 1 threads of 1 processes of 1 users. Май 10 16:12:20 endless rtkit-daemon[796]: Supervising 1 threads of 1 processes of 1 users. Май 10 16:12:20 endless rtkit-daemon[796]: Successfully made thread 850 of process 795 (/usr/bin/pulseaudio) owned by '109' RT at priority 5. Май 10 16:12:20 endless rtkit-daemon[796]: Supervising 2 threads of 1 processes of 1 users. Май 10 16:12:20 endless rtkit-daemon[796]: Supervising 2 threads of 1 processes of 1 users. Май 10 16:12:20 endless rtkit-daemon[796]: Successfully made thread 851 of process 795 (/usr/bin/pulseaudio) owned by '109' RT at priority 5. Май 10 16:12:20 endless rtkit-daemon[796]: Supervising 3 threads of 1 processes of 1 users. Май 10 16:12:20 endless pulseaudio[795]: [pulseaudio] authkey.c: Failed to open cookie file '/var/lib/gdm3/.config/pulse/cookie': Нет такого файла или каталога Май 10 16:12:20 endless pulseaudio[795]: [pulseaudio] authkey.c: Failed to load authentication key '/var/lib/gdm3/.config/pulse/cookie': Нет такого файла или каталога Май 10 16:12:20 endless pulseaudio[795]: [pulseaudio] authkey.c: Failed to open cookie file '/var/lib/gdm3/.pulse-cookie': Нет такого файла или каталога Май 10 16:12:20 endless pulseaudio[795]: [pulseaudio] authkey.c: Failed to load authentication key '/var/lib/gdm3/.pulse-cookie': Нет такого файла или каталога Май 10 16:12:20 endless avahi-daemon[584]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::5164:3b12:d3bd:4abc. Май 10 16:12:20 endless bluetoothd[581]: Endpoint registered: sender=:1.32 path=/MediaEndpoint/A2DPSource Май 10 16:12:20 endless avahi-daemon[584]: New relevant interface wlp2s0.IPv6 for mDNS. Май 10 16:12:20 endless avahi-daemon[584]: Registering new address record for fe80::5164:3b12:d3bd:4abc on wlp2s0.*. Май 10 16:12:20 endless bluetoothd[581]: Endpoint registered: sender=:1.32 path=/MediaEndpoint/A2DPSink Май 10 16:12:20 endless kernel: Bluetooth: RFCOMM TTY layer initialized Май 10 16:12:20 endless kernel: Bluetooth: RFCOMM socket layer initialized Май 10 16:12:20 endless kernel: Bluetooth: RFCOMM ver 1.11 Май 10 16:12:20 endless avahi-daemon[584]: Joining mDNS multicast group on interface enp1s0.IPv6 with address fe80::4984:2bc4:ad3c:1bae. Май 10 16:12:20 endless avahi-daemon[584]: New relevant interface enp1s0.IPv6 for mDNS. Май 10 16:12:20 endless avahi-daemon[584]: Registering new address record for fe80::4984:2bc4:ad3c:1bae on enp1s0.*. Май 10 16:12:20 endless dbus[560]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' Май 10 16:12:20 endless gnome-settings-[755]: g_task_return_error: assertion 'error != NULL' failed Май 10 16:12:20 endless eos-shell[784]: Accessibility: clutter has no accessibility enabled skipping the atk-bridge load Май 10 16:12:20 endless systemd[1]: Starting Locale Service... Май 10 16:12:21 endless dbus[560]: [system] Successfully activated service 'org.freedesktop.locale1' Май 10 16:12:21 endless systemd[1]: Started Locale Service. Май 10 16:12:21 endless colord-sane[852]: [bjnp] create_broadcast_socket: ERROR - bind socket to local address failed - Cannot assign requested address Май 10 16:12:21 endless systemd-udevd[419]: Process '/sbin/crda' failed with exit code 255. Май 10 16:12:21 endless ntpd[666]: Listen normally on 4 wlp2s0 192.168.1.37 UDP 123 Май 10 16:12:21 endless ntpd[666]: Listen normally on 5 enp1s0 fe80::4984:2bc4:ad3c:1bae UDP 123 Май 10 16:12:21 endless ntpd[666]: Listen normally on 6 wlp2s0 fe80::5164:3b12:d3bd:4abc UDP 123 Май 10 16:12:21 endless ntpd[666]: peers refreshed Май 10 16:12:22 endless dhclient[726]: DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 3 Май 10 16:12:22 endless dhclient[726]: DHCPREQUEST of 192.168.1.38 on enp1s0 to 255.255.255.255 port 67 Май 10 16:12:22 endless dhclient[726]: DHCPOFFER of 192.168.1.38 from 192.168.1.1 Май 10 16:12:22 endless dhclient[726]: DHCPACK of 192.168.1.38 from 192.168.1.1 Май 10 16:12:22 endless NetworkManager[583]: [1525957942.1741] address 192.168.1.38 Май 10 16:12:22 endless NetworkManager[583]: [1525957942.1742] plen 24 (255.255.255.0) Май 10 16:12:22 endless NetworkManager[583]: [1525957942.1742] gateway 192.168.1.1 Май 10 16:12:22 endless NetworkManager[583]: [1525957942.1742] server identifier 192.168.1.1 Май 10 16:12:22 endless NetworkManager[583]: [1525957942.1742] lease time 259200 Май 10 16:12:22 endless NetworkManager[583]: [1525957942.1742] nameserver '212.90.160.2' Май 10 16:12:22 endless NetworkManager[583]: [1525957942.1743] nameserver '212.90.160.8' Май 10 16:12:22 endless NetworkManager[583]: [1525957942.1743] domain name 'dsl.ukrtel.net' Май 10 16:12:22 endless NetworkManager[583]: [1525957942.1744] dhcp4 (enp1s0): state changed unknown -> bound Май 10 16:12:22 endless avahi-daemon[584]: Joining mDNS multicast group on interface enp1s0.IPv4 with address 192.168.1.38. Май 10 16:12:22 endless avahi-daemon[584]: New relevant interface enp1s0.IPv4 for mDNS. Май 10 16:12:22 endless avahi-daemon[584]: Registering new address record for 192.168.1.38 on enp1s0.IPv4. Май 10 16:12:22 endless NetworkManager[583]: [1525957942.1766] device (enp1s0): state change: ip-config -> ip-check (reason 'none') [70 80 0] Май 10 16:12:22 endless NetworkManager[583]: [1525957942.1779] device (enp1s0): state change: ip-check -> secondaries (reason 'none') [80 90 0] Май 10 16:12:22 endless NetworkManager[583]: [1525957942.1819] device (enp1s0): state change: secondaries -> activated (reason 'none') [90 100 0] Май 10 16:12:22 endless NetworkManager[583]: [1525957942.1827] manager: NetworkManager state is now CONNECTED_SITE Май 10 16:12:22 endless dhclient[726]: bound to 192.168.1.38 -- renewal in 120080 seconds. Май 10 16:12:22 endless NetworkManager[583]: [1525957942.3634] manager: NetworkManager state is now CONNECTED_LOCAL Май 10 16:12:22 endless NetworkManager[583]: [1525957942.3638] manager: NetworkManager state is now CONNECTED_SITE Май 10 16:12:22 endless NetworkManager[583]: [1525957942.3640] policy: set 'Проводное соединение 1' (enp1s0) as default for IPv4 routing and DNS Май 10 16:12:22 endless NetworkManager[583]: [1525957942.3644] device (enp1s0): Activation: successful, device activated. Май 10 16:12:22 endless nm-dispatcher[659]: req:3 'up' [enp1s0]: new request (4 scripts) Май 10 16:12:22 endless nm-dispatcher[659]: req:3 'up' [enp1s0]: start running ordered scripts... Май 10 16:12:22 endless gdm-Xorg-:0[622]: (II) XKB: generating xkmfile /tmp/server-277A7C3E496C7FF8072160FA921DAD853791F8E7.xkm Май 10 16:12:22 endless NetworkManager[583]: [1525957942.6789] manager: NetworkManager state is now CONNECTED_GLOBAL Май 10 16:12:22 endless nm-dispatcher[659]: req:4 'connectivity-change': new request (4 scripts) Май 10 16:12:22 endless nm-dispatcher[659]: req:4 'connectivity-change': start running ordered scripts... Май 10 16:12:22 endless systemd[1]: Started Update or install Google Chrome plugins. Май 10 16:12:22 endless systemd[1]: Started Update or install codecs via GStreamer plugins. Май 10 16:12:22 endless avahi-daemon[584]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::5164:3b12:d3bd:4abc. Май 10 16:12:22 endless avahi-daemon[584]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fd78:6a89:f7e3:bd00:8682:53ff:96df:6bb4. Май 10 16:12:22 endless avahi-daemon[584]: Registering new address record for fd78:6a89:f7e3:bd00:8682:53ff:96df:6bb4 on wlp2s0.*. Май 10 16:12:22 endless avahi-daemon[584]: Withdrawing address record for fe80::5164:3b12:d3bd:4abc on wlp2s0. Май 10 16:12:22 endless polkitd[559]: Registered Authentication Agent for unix-session:c1 (system bus name :1.34 [/usr/bin/eos-shell --mode=gdm], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale ru_UA.UTF-8) Май 10 16:12:22 endless eos-shell[784]: JS LOG: GNOME Shell started at Thu May 10 2018 16:12:22 GMT+0300 (EEST) Май 10 16:12:22 endless gnome-session-binary[701]: Entering running state Май 10 16:12:22 endless systemd[1]: Started /bin/systemctl --no-block start eos-phone-home.service. Май 10 16:12:22 endless nm-dispatcher[659]: Running timer as unit run-r2e6473f3fc2340c4acee31866f1bce6a.timer. Май 10 16:12:22 endless nm-dispatcher[659]: Will run service as unit run-r2e6473f3fc2340c4acee31866f1bce6a.service. Май 10 16:12:23 endless org.gtk.vfs.AfcVolumeMonitor[708]: Volume monitor alive Май 10 16:12:23 endless eos-chrome-plugin-update[961]: No need to check the Flash plugin yet (version: 29.0.0.171) Май 10 16:12:23 endless eos-gstreamer-codecs-update[967]: MP3 codec available via libav. No need to update Май 10 16:12:23 endless eos-chrome-plugin-update[961]: No need to check the Widevine plugin yet (version: 66.0.3359.139-1) Май 10 16:12:23 endless eos-chrome-plugin-update[961]: All done Май 10 16:12:23 endless gdm-eos-shell.desktop[784]: /usr/share/ibus-anthy/engine/main.py:37: PyGIWarning: IBus was imported without specifying a version first. Use gi.require_version('IBus', '1.0') before import to ensure that the right version gets loaded. Май 10 16:12:23 endless gdm-eos-shell.desktop[784]: from gi.repository import IBus Май 10 16:12:23 endless gdm-eos-shell.desktop[784]: /usr/share/ibus-anthy/engine/engine.py:42: PyGIWarning: Anthy was imported without specifying a version first. Use gi.require_version('Anthy', '9000') before import to ensure that the right version gets loaded. Май 10 16:12:23 endless gdm-eos-shell.desktop[784]: from gi.repository import Anthy Май 10 16:12:23 endless goa-daemon[1008]: goa-daemon version 3.20.1 starting Май 10 16:12:23 endless NetworkManager[583]: [1525957943.7026] manager: startup complete Май 10 16:12:23 endless gdm-eos-shell.desktop[784]: /usr/share/ibus-table/engine/main.py:27: PyGIWarning: IBus was imported without specifying a version first. Use gi.require_version('IBus', '1.0') before import to ensure that the right version gets loaded. Май 10 16:12:23 endless gdm-eos-shell.desktop[784]: from gi.repository import IBus Май 10 16:12:23 endless ntpd[666]: Listen normally on 7 enp1s0 192.168.1.38 UDP 123 Май 10 16:12:23 endless ntpd[666]: Listen normally on 8 wlp2s0 fd78:6a89:f7e3:bd00:8682:53ff:96df:6bb4 UDP 123 Май 10 16:12:23 endless ntpd[666]: peers refreshed Май 10 16:12:23 endless ntpd_intres[673]: DNS 0.debian.pool.ntp.org -> 82.193.117.90 Май 10 16:12:23 endless ntpd_intres[673]: DNS 1.debian.pool.ntp.org -> 178.136.117.33 Май 10 16:12:23 endless ntpd_intres[673]: DNS 2.debian.pool.ntp.org -> 91.235.212.22 Май 10 16:12:23 endless ntpd_intres[673]: DNS 3.debian.pool.ntp.org -> 185.51.192.34 Май 10 16:12:23 endless ntpd_intres[673]: DNS ntp.ubuntu.com -> 91.189.91.157 Май 10 16:12:23 endless gdm-Xorg-:0[622]: (II) XKB: generating xkmfile /tmp/server-86630844AC9AC4556B74CD2F3E1EC536648250DE.xkm Май 10 16:12:24 endless systemd-bootchart[316]: systemd-bootchart wrote /run/log/bootchart-20180510-1612.svg Май 10 16:12:24 endless systemd-bootchart[316]: Bootchart created: /run/log/bootchart-20180510-1612.svg Май 10 16:12:24 endless dbus[560]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' Май 10 16:12:24 endless systemd[1]: Starting Fingerprint Authentication Daemon... Май 10 16:12:24 endless dbus[560]: [system] Successfully activated service 'net.reactivated.Fprint' Май 10 16:12:24 endless systemd[1]: Started Fingerprint Authentication Daemon. Май 10 16:12:24 endless fprintd[1055]: Launching FprintObject Май 10 16:12:24 endless fprintd[1055]: D-Bus service launched with name: net.reactivated.Fprint Май 10 16:12:24 endless fprintd[1055]: entering main loop Май 10 16:12:24 endless colord[785]: Device added: xrandr-AU Optronics Май 10 16:12:24 endless gdm-Xorg-:0[622]: (II) XKB: generating xkmfile /tmp/server-86630844AC9AC4556B74CD2F3E1EC536648250DE.xkm Май 10 16:12:24 endless colord[785]: Automatic metadata add icc-b7673975af8ac1825a392645971858e9 to xrandr-AU Optronics Май 10 16:12:24 endless colord[785]: Profile added: icc-b7673975af8ac1825a392645971858e9 Май 10 16:12:25 endless systemd-udevd[419]: Process '/sbin/crda' failed with exit code 255. Май 10 16:12:25 endless avahi-daemon[584]: Leaving mDNS multicast group on interface enp1s0.IPv6 with address fe80::4984:2bc4:ad3c:1bae. Май 10 16:12:25 endless avahi-daemon[584]: Joining mDNS multicast group on interface enp1s0.IPv6 with address fd78:6a89:f7e3:bd00:3247:ae9c:ae58:eb57. Май 10 16:12:25 endless avahi-daemon[584]: Registering new address record for fd78:6a89:f7e3:bd00:3247:ae9c:ae58:eb57 on enp1s0.*. Май 10 16:12:25 endless avahi-daemon[584]: Withdrawing address record for fe80::4984:2bc4:ad3c:1bae on enp1s0. Май 10 16:12:26 endless kernel: i2c_hid i2c-FTE1200:00: failed to reset device. Май 10 16:12:26 endless ntpd[666]: Listen normally on 9 enp1s0 fd78:6a89:f7e3:bd00:3247:ae9c:ae58:eb57 UDP 123 Май 10 16:12:26 endless ntpd[666]: peers refreshed Май 10 16:12:27 endless kernel: input: FTE1200:00 0B05:0201 Touchpad as /devices/pci0000:00/0000:00:17.0/i2c_designware.1/i2c-6/i2c-FTE1200:00/0018:0B05:0201.0002/input/input13 Май 10 16:12:27 endless kernel: hid-multitouch 0018:0B05:0201.0002: input,hidraw1: I2C HID v1.00 Mouse [FTE1200:00 0B05:0201] on i2c-FTE1200:00 Май 10 16:12:28 endless systemd-udevd[1069]: Process '/sbin/crda' failed with exit code 255. Май 10 16:12:35 endless systemd[697]: Time has been changed Май 10 16:12:35 endless systemd[1]: Time has been changed Май 10 16:12:36 endless systemd-udevd[1071]: Process '/sbin/crda' failed with exit code 255. Май 10 16:12:40 endless systemd-udevd[1074]: Process '/sbin/crda' failed with exit code 255. Май 10 16:12:43 endless systemd-udevd[1076]: Process '/sbin/crda' failed with exit code 255. Май 10 16:12:46 endless systemd-udevd[1078]: Process '/sbin/crda' failed with exit code 255. Май 10 16:12:50 endless systemd-udevd[1080]: Process '/sbin/crda' failed with exit code 255. Май 10 16:12:52 endless systemd[1]: Starting Stop Read-Ahead Data Collection... Май 10 16:12:52 endless systemd[1]: Started Stop Read-Ahead Data Collection. Май 10 16:12:53 endless systemd-udevd[1085]: Process '/sbin/crda' failed with exit code 255. Май 10 16:12:56 endless systemd-udevd[1087]: Process '/sbin/crda' failed with exit code 255. Май 10 16:12:59 endless fprintd[1055]: No devices in use, exit Май 10 16:13:18 endless cupsd[566]: [Client 13] Accepted from localhost (Domain) Май 10 16:13:18 endless cupsd[566]: [Client 13] Waiting for request. Май 10 16:13:18 endless cupsd[566]: Report: clients=1 Май 10 16:13:18 endless cupsd[566]: Report: jobs=0 Май 10 16:13:18 endless cupsd[566]: Report: jobs-active=0 Май 10 16:13:18 endless cupsd[566]: Report: printers=0 Май 10 16:13:18 endless cupsd[566]: Report: stringpool-string-count=223 Май 10 16:13:18 endless cupsd[566]: Report: stringpool-alloc-bytes=3016 Май 10 16:13:18 endless cupsd[566]: Report: stringpool-total-bytes=3296 Май 10 16:13:18 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:18 endless cupsd[566]: [Client 13] POST / HTTP/1.1 Май 10 16:13:18 endless cupsd[566]: cupsdSetBusyState: newbusy="Active clients", busy="Not busy" Май 10 16:13:18 endless cupsd[566]: [Client 13] No authentication data provided. Май 10 16:13:18 endless cupsd[566]: [Client 13] 2.0 CUPS-Get-Printers 2 Май 10 16:13:18 endless cupsd[566]: CUPS-Get-Printers Май 10 16:13:18 endless cupsd[566]: CUPS-Get-Printers client-error-not-found: Нет добавленных назначений. Май 10 16:13:18 endless cupsd[566]: [Client 13] Returning IPP client-error-not-found for CUPS-Get-Printers (no URI) from localhost Май 10 16:13:18 endless cupsd[566]: [Client 13] Content-Length: 145 Май 10 16:13:18 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:18 endless cupsd[566]: [Client 13] cupsdWriteClient error=0, used=0, state=HTTP_STATE_POST_SEND, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=145, response=0x55fb83ceb250(IPP_IDLE), pipe_pid=0, file=-1 Май 10 16:13:18 endless cupsd[566]: [Client 13] Writing IPP response, ipp_state=DATA, old wused=0, new wused=0 Май 10 16:13:18 endless cupsd[566]: [Client 13] bytes=0, http_state=0, data_remaining=0 Май 10 16:13:18 endless cupsd[566]: [Client 13] Waiting for request. Май 10 16:13:18 endless cupsd[566]: cupsdSetBusyState: newbusy="Not busy", busy="Active clients" Май 10 16:13:18 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:18 endless cupsd[566]: [Client 13] POST / HTTP/1.1 Май 10 16:13:18 endless cupsd[566]: cupsdSetBusyState: newbusy="Active clients", busy="Not busy" Май 10 16:13:18 endless cupsd[566]: [Client 13] No authentication data provided. Май 10 16:13:18 endless cupsd[566]: [Client 13] 2.0 CUPS-Get-Default 3 Май 10 16:13:18 endless cupsd[566]: CUPS-Get-Default Май 10 16:13:18 endless cupsd[566]: CUPS-Get-Default client-error-not-found: No default printer. Май 10 16:13:18 endless cupsd[566]: [Client 13] Returning IPP client-error-not-found for CUPS-Get-Default (no URI) from localhost Май 10 16:13:18 endless cupsd[566]: [Client 13] Content-Length: 113 Май 10 16:13:18 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:18 endless cupsd[566]: [Client 13] cupsdWriteClient error=0, used=0, state=HTTP_STATE_POST_SEND, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=113, response=0x55fb83ceb250(IPP_IDLE), pipe_pid=0, file=-1 Май 10 16:13:18 endless cupsd[566]: [Client 13] Writing IPP response, ipp_state=DATA, old wused=0, new wused=0 Май 10 16:13:18 endless cupsd[566]: [Client 13] bytes=0, http_state=0, data_remaining=0 Май 10 16:13:18 endless cupsd[566]: [Client 13] Waiting for request. Май 10 16:13:18 endless cupsd[566]: cupsdSetBusyState: newbusy="Not busy", busy="Active clients" Май 10 16:13:18 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:18 endless cupsd[566]: [Client 13] POST / HTTP/1.1 Май 10 16:13:18 endless cupsd[566]: cupsdSetBusyState: newbusy="Active clients", busy="Not busy" Май 10 16:13:18 endless cupsd[566]: [Client 13] No authentication data provided. Май 10 16:13:18 endless cupsd[566]: [Client 13] 2.0 Create-Printer-Subscriptions 4 Май 10 16:13:18 endless cupsd[566]: Create-Printer-Subscriptions / Май 10 16:13:18 endless cupsd[566]: create_subscriptions(con=0x55fb83cceee0(13), uri="/") Май 10 16:13:18 endless cupsd[566]: recipient="dbus://" Май 10 16:13:18 endless cupsd[566]: notify-lease-duration=86400 Май 10 16:13:18 endless cupsd[566]: notify-time-interval=0 Май 10 16:13:18 endless cupsd[566]: cupsdAddSubscription(mask=1fffff, dest=(nil)(), job=(nil)(0), uri="dbus://") Май 10 16:13:18 endless cupsd[566]: Added subscription #4 for server. Май 10 16:13:18 endless cupsd[566]: cupsdMarkDirty(----S) Май 10 16:13:18 endless cupsd[566]: cupsdSetBusyState: newbusy="Active clients and dirty files", busy="Active clients" Май 10 16:13:18 endless cupsd[566]: [Client 13] Returning IPP successful-ok for Create-Printer-Subscriptions (/) from localhost Май 10 16:13:18 endless cupsd[566]: [Client 13] Content-Length: 107 Май 10 16:13:18 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:18 endless cupsd[566]: [Client 13] cupsdWriteClient error=0, used=0, state=HTTP_STATE_POST_SEND, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=107, response=0x55fb83cfcdc0(IPP_IDLE), pipe_pid=0, file=-1 Май 10 16:13:18 endless cupsd[566]: [Client 13] Writing IPP response, ipp_state=DATA, old wused=0, new wused=0 Май 10 16:13:18 endless cupsd[566]: [Client 13] bytes=0, http_state=0, data_remaining=0 Май 10 16:13:18 endless cupsd[566]: REQUEST localhost - - "POST / HTTP/1.1" 200 176 Create-Printer-Subscriptions successful-ok Май 10 16:13:18 endless cupsd[566]: [Client 13] Waiting for request. Май 10 16:13:18 endless cupsd[566]: cupsdSetBusyState: newbusy="Dirty files", busy="Active clients and dirty files" Май 10 16:13:18 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:19 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:21 endless dbus[560]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' Май 10 16:13:21 endless systemd[1]: Starting Fingerprint Authentication Daemon... Май 10 16:13:21 endless dbus[560]: [system] Successfully activated service 'net.reactivated.Fprint' Май 10 16:13:21 endless systemd[1]: Started Fingerprint Authentication Daemon. Май 10 16:13:21 endless fprintd[1098]: Launching FprintObject Май 10 16:13:21 endless fprintd[1098]: D-Bus service launched with name: net.reactivated.Fprint Май 10 16:13:21 endless fprintd[1098]: entering main loop Май 10 16:13:24 endless gdm-password][1099]: pam_unix(gdm-password:session): session opened for user user by (unknown)(uid=0) Май 10 16:13:24 endless systemd[1]: Created slice User Slice of user. Май 10 16:13:24 endless systemd[1]: Starting User Manager for UID 1001... Май 10 16:13:24 endless systemd[1]: Started Session 1 of user user. Май 10 16:13:24 endless systemd-logind[572]: New session 1 of user user. Май 10 16:13:24 endless systemd[1106]: pam_unix(systemd-user:session): session opened for user user by (uid=0) Май 10 16:13:24 endless systemd[1106]: Reached target Sockets. Май 10 16:13:24 endless systemd[1106]: Reached target Paths. Май 10 16:13:24 endless systemd[1106]: Reached target Timers. Май 10 16:13:24 endless systemd[1106]: Reached target Basic System. Май 10 16:13:24 endless systemd[1106]: Reached target Default. Май 10 16:13:24 endless systemd[1106]: Startup finished in 48ms. Май 10 16:13:24 endless systemd[1]: Started User Manager for UID 1001. Май 10 16:13:25 endless org.gtk.vfs.Daemon[708]: A connection to the bus can't be made Май 10 16:13:25 endless gnome-settings-[755]: Error releasing name org.gnome.SettingsDaemon: Соединение закрыто Май 10 16:13:25 endless eos-shell[784]: JS ERROR: TypeError: target is undefined _getTweenState@resource:///org/gnome/shell/ui/tweener.js:65:9 _wrapTweening@resource:///org/gnome/shell/ui/tweener.js:44:9 addTween@resource:///org/gnome/shell/ui/tweener.js:39:5 LayoutManager<.prepareForOverview@resource:///org/gnome/shell/ui/layout.js:591:28 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:13 WorkspaceMonitor<._windowDisappearing@resource:///org/gnome/shell/ui/workspaceMonitor.js:54:13 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:13 Май 10 16:13:25 endless gnome-settings-[755]: Invalid id 4 passed to g_bus_unown_name() Май 10 16:13:25 endless gnome-session-binary[701]: WARNING: Lost name on bus: org.gnome.SessionManager Май 10 16:13:25 endless gnome-session[701]: gnome-session-binary[701]: WARNING: Lost name on bus: org.gnome.SessionManager Май 10 16:13:25 endless colord[785]: device removed: xrandr-AU Optronics Май 10 16:13:25 endless colord[785]: Profile removed: icc-b7673975af8ac1825a392645971858e9 Май 10 16:13:25 endless gnome-session[701]: Unable to init server: Could not connect: Connection refused Май 10 16:13:25 endless kernel: gnome-session-f[1115]: segfault at 0 ip 00007f9126eb2649 sp 00007ffd35b0f2b0 error 4 in libgtk-3.so.0.2200.4[7f9126bce000+6fd000] Май 10 16:13:25 endless polkitd[559]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.34, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale ru_UA.UTF-8) (disconnected from bus) Май 10 16:13:25 endless /etc/gdm3/Xsession[1117]: /etc/gdm3/Xsession: Beginning session setup... Май 10 16:13:25 endless /etc/gdm3/Xsession[1117]: localuser:user being added to access control list Май 10 16:13:25 endless /etc/gdm3/Xsession[1117]: I: Script for none started at run_im. Май 10 16:13:25 endless /etc/gdm3/Xsession[1117]: I: Script for auto started at run_im. Май 10 16:13:25 endless /etc/gdm3/Xsession[1117]: I: Script for default started at run_im. Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting USER=user Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting TEXTDOMAIN=im-config Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting HOME=/sysroot/home/user Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting DESKTOP_SESSION=eos-session Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-finfLFfhzC,guid=afce26a54a075720e218a5b45af44575 Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting IM_CONFIG_PHASE=1 Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting LOGNAME=user Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting USERNAME=user Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting GTK_OVERLAY_SCROLLING=0 Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting WINDOWPATH=1 Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1001 Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting DISPLAY=:0 Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting LANG=ru_UA.UTF-8 Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting XDG_CURRENT_DESKTOP=Endless:GNOME Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=eos-session Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting XAUTHORITY=/var/run/gdm3/auth-for-user-zq8tVY/database Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting SHELL=/bin/bash Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting GDMSESSION=eos-session Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting TEXTDOMAINDIR=/usr/share/locale/ Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting PWD=/sysroot/home/user Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/eos-session:/sysroot/home/user/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share/:/var/endless-extra/flatpak/exports/share/:/usr/local/share/:/usr/share/ Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-eos-session:/etc/xdg Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: I: Script for none started at run_im. Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: I: Script for auto started at run_im. Май 10 16:13:27 endless /etc/gdm3/Xsession[1117]: I: Script for default started at run_im. Май 10 16:13:27 endless org.a11y.Bus[1222]: Activating service name='org.a11y.atspi.Registry' Май 10 16:13:27 endless at-spi-bus-laun[1323]: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Май 10 16:13:27 endless org.a11y.Bus[1222]: Successfully activated service 'org.a11y.atspi.Registry' Май 10 16:13:27 endless org.a11y.atspi.Registry[1328]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Май 10 16:13:27 endless gnome-keyring-ssh.desktop[1341]: SSH_AUTH_SOCK=/run/user/1001/keyring/ssh Май 10 16:13:27 endless rtkit-daemon[796]: Successfully made thread 1365 of process 1365 (/usr/bin/pulseaudio) owned by '1001' high priority at nice level -11. Май 10 16:13:27 endless rtkit-daemon[796]: Supervising 4 threads of 2 processes of 2 users. Май 10 16:13:27 endless dbus[560]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Май 10 16:13:27 endless systemd[1]: Starting Hostname Service... Май 10 16:13:27 endless rtkit-daemon[796]: Supervising 4 threads of 2 processes of 2 users. Май 10 16:13:27 endless dbus[560]: [system] Successfully activated service 'org.freedesktop.hostname1' Май 10 16:13:27 endless systemd[1]: Started Hostname Service. Май 10 16:13:27 endless rtkit-daemon[796]: Successfully made thread 1370 of process 1365 (/usr/bin/pulseaudio) owned by '1001' RT at priority 5. Май 10 16:13:27 endless rtkit-daemon[796]: Supervising 5 threads of 2 processes of 2 users. Май 10 16:13:27 endless rtkit-daemon[796]: Supervising 5 threads of 2 processes of 2 users. Май 10 16:13:27 endless rtkit-daemon[796]: Successfully made thread 1371 of process 1365 (/usr/bin/pulseaudio) owned by '1001' RT at priority 5. Май 10 16:13:27 endless rtkit-daemon[796]: Supervising 6 threads of 2 processes of 2 users. Май 10 16:13:27 endless cupsd[566]: [Client 14] Accepted from localhost (Domain) Май 10 16:13:27 endless cupsd[566]: [Client 14] Waiting for request. Май 10 16:13:27 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:27 endless cupsd[566]: [Client 14] POST / HTTP/1.1 Май 10 16:13:27 endless cupsd[566]: cupsdSetBusyState: newbusy="Active clients and dirty files", busy="Dirty files" Май 10 16:13:27 endless cupsd[566]: [Client 14] No authentication data provided. Май 10 16:13:27 endless cupsd[566]: [Client 14] 2.0 CUPS-Get-Printers 1 Май 10 16:13:27 endless cupsd[566]: CUPS-Get-Printers Май 10 16:13:27 endless cupsd[566]: CUPS-Get-Printers client-error-not-found: Нет добавленных назначений. Май 10 16:13:27 endless cupsd[566]: [Client 14] Returning IPP client-error-not-found for CUPS-Get-Printers (no URI) from localhost Май 10 16:13:27 endless bluetoothd[581]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource Май 10 16:13:27 endless cupsd[566]: [Client 14] Content-Length: 145 Май 10 16:13:27 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:27 endless cupsd[566]: [Client 14] cupsdWriteClient error=0, used=0, state=HTTP_STATE_POST_SEND, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=145, response=0x55fb83d01550(IPP_IDLE), pipe_pid=0, file=-1 Май 10 16:13:27 endless cupsd[566]: [Client 14] Writing IPP response, ipp_state=DATA, old wused=0, new wused=0 Май 10 16:13:27 endless bluetoothd[581]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink Май 10 16:13:27 endless cupsd[566]: [Client 14] bytes=0, http_state=0, data_remaining=0 Май 10 16:13:27 endless cupsd[566]: [Client 14] Waiting for request. Май 10 16:13:27 endless cupsd[566]: cupsdSetBusyState: newbusy="Dirty files", busy="Active clients and dirty files" Май 10 16:13:27 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:27 endless bluetoothd[581]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98) Май 10 16:13:27 endless cupsd[566]: [Client 15] Accepted from localhost (Domain) Май 10 16:13:27 endless cupsd[566]: [Client 15] Waiting for request. Май 10 16:13:27 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:27 endless cupsd[566]: [Client 15] POST / HTTP/1.1 Май 10 16:13:27 endless cupsd[566]: cupsdSetBusyState: newbusy="Active clients and dirty files", busy="Dirty files" Май 10 16:13:27 endless cupsd[566]: [Client 15] No authentication data provided. Май 10 16:13:27 endless cupsd[566]: [Client 15] 2.0 Create-Printer-Subscriptions 2 Май 10 16:13:27 endless cupsd[566]: Create-Printer-Subscriptions / Май 10 16:13:27 endless cupsd[566]: create_subscriptions(con=0x55fb83d01550(15), uri="/") Май 10 16:13:27 endless cupsd[566]: recipient="dbus://" Май 10 16:13:27 endless cupsd[566]: pullmethod="ippget" Май 10 16:13:27 endless cupsd[566]: notify-lease-duration=3600 Май 10 16:13:27 endless cupsd[566]: notify-time-interval=0 Май 10 16:13:27 endless cupsd[566]: cupsdAddSubscription(mask=798f, dest=(nil)(), job=(nil)(0), uri="dbus://") Май 10 16:13:27 endless cupsd[566]: Added subscription #5 for server. Май 10 16:13:27 endless cupsd[566]: cupsdMarkDirty(----S) Май 10 16:13:27 endless cupsd[566]: cupsdSetBusyState: newbusy="Active clients and dirty files", busy="Active clients and dirty files" Май 10 16:13:27 endless cupsd[566]: [Client 15] Returning IPP successful-ok for Create-Printer-Subscriptions (/) from localhost Май 10 16:13:27 endless cupsd[566]: [Client 15] Content-Length: 107 Май 10 16:13:27 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:27 endless cupsd[566]: [Client 15] cupsdWriteClient error=0, used=0, state=HTTP_STATE_POST_SEND, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=107, response=0x55fb83cfce60(IPP_IDLE), pipe_pid=0, file=-1 Май 10 16:13:27 endless cupsd[566]: [Client 15] Writing IPP response, ipp_state=DATA, old wused=0, new wused=0 Май 10 16:13:27 endless cupsd[566]: [Client 15] bytes=0, http_state=0, data_remaining=0 Май 10 16:13:27 endless cupsd[566]: REQUEST localhost - - "POST / HTTP/1.1" 200 360 Create-Printer-Subscriptions successful-ok Май 10 16:13:27 endless cupsd[566]: [Client 15] Waiting for request. Май 10 16:13:27 endless cupsd[566]: cupsdSetBusyState: newbusy="Dirty files", busy="Active clients and dirty files" Май 10 16:13:27 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:27 endless cupsd[566]: [Client 15] HTTP_STATE_WAITING Closing on EOF Май 10 16:13:27 endless cupsd[566]: [Client 15] Closing connection. Май 10 16:13:27 endless cupsd[566]: cupsdSetBusyState: newbusy="Dirty files", busy="Dirty files" Май 10 16:13:27 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:27 endless gnome-settings-[1347]: g_task_return_error: assertion 'error != NULL' failed Май 10 16:13:27 endless dbus[560]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' Май 10 16:13:28 endless systemd[1]: Starting Locale Service... Май 10 16:13:28 endless colord[785]: Profile added: icc-f84e9c7026aaf919970ac39adf84acce Май 10 16:13:28 endless dbus[560]: [system] Successfully activated service 'org.freedesktop.locale1' Май 10 16:13:28 endless systemd[1]: Started Locale Service. Май 10 16:13:28 endless eos-shell[1383]: Accessibility: clutter has no accessibility enabled skipping the atk-bridge load Май 10 16:13:28 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:31 endless systemd-journald[312]: Suppressed 22 messages from /system.slice/gdm.service Май 10 16:13:31 endless gdm-Xorg-:0[622]: (II) XKB: generating xkmfile /tmp/server-F892E65091CEBD2D54C7A234CA4711927D13FDBE.xkm Май 10 16:13:31 endless goa-daemon[1431]: goa-daemon version 3.20.1 starting Май 10 16:13:31 endless polkitd[559]: Registered Authentication Agent for unix-session:1 (system bus name :1.60 [/usr/bin/eos-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale ru_UA.UTF-8) Май 10 16:13:31 endless org.gtk.vfs.AfcVolumeMonitor[1222]: Volume monitor alive Май 10 16:13:31 endless dbus[560]: [system] Activating service name='com.endlessm.Updater' (using servicehelper) Май 10 16:13:31 endless eos-updater[1472]: Acquired a message bus connection Май 10 16:13:31 endless eos-updater[1472]: Exporting objects Май 10 16:13:31 endless dbus[560]: [system] Successfully activated service 'com.endlessm.Updater' Май 10 16:13:31 endless eos-updater[1472]: Acquired the name com.endlessm.Updater Май 10 16:13:32 endless eos-shell[1383]: JS LOG: Failed to add search provider /var/lib/flatpak/exports/share/gnome-shell/search-providers/org.gnome.Gnote.ini: TypeError: appInfo is null Май 10 16:13:32 endless eos-shell[1383]: JS LOG: GNOME Shell started at Thu May 10 2018 16:13:32 GMT+0300 (EEST) Май 10 16:13:32 endless gnome-session-binary[1117]: Entering running state Май 10 16:13:32 endless bluetoothd[581]: Failed to set mode: Blocked through rfkill (0x12) Май 10 16:13:33 endless gdm-Xorg-:0[622]: (II) XKB: generating xkmfile /tmp/server-F892E65091CEBD2D54C7A234CA4711927D13FDBE.xkm Май 10 16:13:33 endless colord[785]: Automatic metadata add icc-f84e9c7026aaf919970ac39adf84acce to xrandr-AU Optronics Май 10 16:13:33 endless colord[785]: Device added: xrandr-AU Optronics Май 10 16:13:33 endless tracker-store.desktop[1490]: (uint32 1,) Май 10 16:13:33 endless eos-shell[1383]: JS LOG: Access point was already seen, not adding again Май 10 16:13:33 endless eos-shell[1383]: JS LOG: Access point was already seen, not adding again Май 10 16:13:33 endless eos-shell[1383]: JS LOG: Access point was already seen, not adding again Май 10 16:13:35 endless dbus[560]: [system] Activating via systemd: service name='org.freedesktop.Flatpak.SystemHelper' unit='flatpak-system-helper.service' Май 10 16:13:35 endless systemd[1]: Starting flatpak system helper... Май 10 16:13:35 endless dbus[560]: [system] Successfully activated service 'org.freedesktop.Flatpak.SystemHelper' Май 10 16:13:35 endless systemd[1]: Started flatpak system helper. Май 10 16:13:35 endless kernel: ISO 9660 Extensions: Microsoft Joliet Level 1 Май 10 16:13:35 endless kernel: ISOFS: changing to secondary root Май 10 16:13:35 endless udisksd[562]: Mounted /dev/sr0 at /run/media/user/040506_1351 on behalf of uid 1001 Май 10 16:13:35 endless org.gtk.vfs.UDisks2VolumeMonitor[1222]: index_parse.c:191: indx_parse(): error opening /run/media/user/040506_1351/BDMV/index.bdmv Май 10 16:13:35 endless org.gtk.vfs.UDisks2VolumeMonitor[1222]: index_parse.c:191: indx_parse(): error opening /run/media/user/040506_1351/BDMV/BACKUP/index.bdmv Май 10 16:13:35 endless gnome-software-service.desktop[1488]: 13:13:35:0817 Gs Failed to get AppStream metadata: No such branch 'appstream/x86_64' in repository summary Май 10 16:13:35 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:13:35:0818 Gs Failed to get AppStream metadata: No such branch 'appstream/x86_64' in repository summary Май 10 16:13:36 endless gnome-software-service.desktop[1488]: 13:13:36:0207 Gs failed to parse /var/lib/flatpak/exports/share/applications/kde4: /var/lib/flatpak/exports/share/applications/kde4 has an unrecognised extension Май 10 16:13:36 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:13:36:0212 Gs failed to parse /var/lib/flatpak/exports/share/applications/kde4: /var/lib/flatpak/exports/share/applications/kde4 has an unrecognised extension Май 10 16:13:38 endless gnome-software-service.desktop[1488]: Unable to acquire bus name 'org.gnome.Software' Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:13:39:0256 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: unknown Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:13:39:0256 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: unknown Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:13:39:0264 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: unknown Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:13:39:0264 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: unknown Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:13:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:13:40:0733 Gs unknown flatpak kind: (null) Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:13:40:0734 Gs failed to call gs_plugin_app_install on flatpak: [system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3] Not application or runtime Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:13:40:0735 Gs unknown flatpak kind: (null) Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:13:40:0735 Gs unknown flatpak kind: (null) Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:13:40:0736 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: available Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:13:40:0736 Gs not GsPlugin error from plugin flatpak g-file-error-quark:1: failed to get size: Произошла ошибка при чтении файла «/var/lib/flatpak»: Это каталог Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:13:40:0736 Gs failed to call gs_plugin_refine_app on flatpak: failed to get size: Произошла ошибка при чтении файла «/var/lib/flatpak»: Это каталог Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:13:40:0744 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: available Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin-ui: Endless Applications Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:13:40 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: {EndlessOS::system-desktop-file}: google-chrome.desktop Май 10 16:13:45 endless bluetoothd[581]: Endpoint unregistered: sender=:1.32 path=/MediaEndpoint/A2DPSource Май 10 16:13:45 endless bluetoothd[581]: Endpoint unregistered: sender=:1.32 path=/MediaEndpoint/A2DPSink Май 10 16:13:45 endless systemd-logind[572]: Removed session c1. Май 10 16:13:45 endless systemd[1]: Stopping User Manager for UID 109... Май 10 16:13:45 endless systemd[697]: Reached target Shutdown. Май 10 16:13:45 endless systemd[697]: Starting Exit the Session... Май 10 16:13:45 endless systemd[697]: Stopped target Default. Май 10 16:13:45 endless systemd[697]: Stopped target Basic System. Май 10 16:13:45 endless systemd[697]: Stopped target Timers. Май 10 16:13:45 endless systemd[697]: Stopped target Paths. Май 10 16:13:45 endless systemd[697]: Stopped target Sockets. Май 10 16:13:45 endless systemd[697]: Received SIGRTMIN+24 from PID 1723 (kill). Май 10 16:13:45 endless systemd[698]: pam_unix(systemd-user:session): session closed for user Debian-gdm Май 10 16:13:45 endless systemd[1]: Stopped User Manager for UID 109. Май 10 16:13:45 endless systemd[1]: Removed slice User Slice of Debian-gdm. Май 10 16:13:49 endless cupsd[566]: Saving subscriptions.conf... Май 10 16:13:50 endless cupsd[566]: cupsdSetBusyState: newbusy="Not busy", busy="Dirty files" Май 10 16:13:50 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:13:51 endless fprintd[1098]: No devices in use, exit Май 10 16:14:03 endless eos-shell[1383]: json_object_get_object_member: assertion 'node != NULL' failed Май 10 16:14:04 endless systemd[1106]: Started flatpak-com.endlessm.EknServices-1738.scope. Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_new_string: assertion 'string != NULL' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_new_variant: assertion 'value != NULL' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_get_type: assertion 'value != NULL' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_builder_add_value: assertion '!GVSB(builder)->expected_type || g_variant_is_of_type (value, GVSB(builder)->expected_type)' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_builder_end: assertion 'GVSB(builder)->offset >= GVSB(builder)->min_items' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_get_type: assertion 'value != NULL' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_builder_add_value: assertion '!GVSB(builder)->expected_type || g_variant_is_of_type (value, GVSB(builder)->expected_type)' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_new_string: assertion 'string != NULL' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_new_variant: assertion 'value != NULL' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_get_type: assertion 'value != NULL' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_builder_add_value: assertion '!GVSB(builder)->expected_type || g_variant_is_of_type (value, GVSB(builder)->expected_type)' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_builder_end: assertion 'GVSB(builder)->offset >= GVSB(builder)->min_items' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_get_type: assertion 'value != NULL' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed Май 10 16:14:05 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:05:0001 GLib g_variant_builder_add_value: assertion '!GVSB(builder)->expected_type || g_variant_is_of_type (value, GVSB(builder)->expected_type)' failed Май 10 16:14:09 endless systemd[1]: Started xapian-bridge.service. Май 10 16:14:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:14:21:0192 Gs failed to call gs_plugin_app_install on flatpak: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:15:00 endless systemd[1]: Started /bin/systemctl --no-block start eos-phone-home.service. Май 10 16:15:00 endless systemd[1]: Started Send system activation/daily ping messages to Endless. Май 10 16:15:01 endless eos-phone-home[1870]: Already activated! Май 10 16:15:01 endless eos-phone-home[1870]: Getting variable: live Май 10 16:15:01 endless eos-phone-home[1870]: Getting variable: cmdline Май 10 16:15:01 endless eos-phone-home[1870]: - Cmdline: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-40a27c661924b10880bcde7db893844adc31bb8a90f0d6c3b247b9c423e57882/vmlinuz-4.8.0-32-generic root=UUID=817fe263-272d-47ba-945d-d9674912e832 rw splash plymouth.ignore-serial-consoles quiet ostree=/ostree/boot.1/eos/40a27c661924b10880bcde7db893844adc31bb8a90f0d6c3b247b9c423e57882/0 Май 10 16:15:01 endless eos-phone-home[1870]: Count age: 20567.433134794235 Май 10 16:15:01 endless eos-phone-home[1870]: Ping not due yet. Май 10 16:15:03 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:03:0421 Gs failed to call gs_plugin_app_install on flatpak: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:15:07 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:07:0085 Gtk gtk_show_uri_on_window: assertion 'uri != NULL' failed Май 10 16:15:07 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:07:0902 Gs Failed to get AppStream metadata: No such branch 'appstream/x86_64' in repository summary Май 10 16:15:08 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:08:0083 Gs failed to parse /var/lib/flatpak/exports/share/applications/kde4: /var/lib/flatpak/exports/share/applications/kde4 has an unrecognised extension Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:10:0188 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: available Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin-ui: Endless Applications Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: {EndlessOS::system-desktop-file}: google-chrome.desktop Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:10:0188 Gs unknown flatpak kind: (null) Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:10:0189 Gs not GsPlugin error from plugin flatpak g-file-error-quark:1: failed to get size: Произошла ошибка при чтении файла «/var/lib/flatpak»: Это каталог Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:10:0189 Gs failed to call gs_plugin_refine_app on flatpak: failed to get size: Произошла ошибка при чтении файла «/var/lib/flatpak»: Это каталог Май 10 16:15:10 endless eos-shell.desktop[1383]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1800008 (App Center) Май 10 16:15:10 endless eos-shell.desktop[1383]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1800008 (App Center) Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:10:0227 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: available Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin-ui: Endless Applications Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:15:10 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: {EndlessOS::system-desktop-file}: google-chrome.desktop Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:12:0543 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: available Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin-ui: Endless Applications Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: {EndlessOS::system-desktop-file}: google-chrome.desktop Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:12:0545 Gs failed to call gs_plugin_app_install on flatpak: [system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3] Not application or runtime Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:12:0546 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: available Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin-ui: Endless Applications Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: {EndlessOS::system-desktop-file}: google-chrome.desktop Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:12:0548 Gtk gtk_container_remove: assertion 'GTK_IS_CONTAINER (container)' failed Май 10 16:15:12 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:12:0548 Gtk gtk_container_remove: assertion 'GTK_IS_CONTAINER (container)' failed Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:18:0180 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: available Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin-ui: Endless Applications Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: {EndlessOS::system-desktop-file}: google-chrome.desktop Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:18:0181 Gs failed to call gs_plugin_app_install on flatpak: [system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3] Not application or runtime Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:18:0181 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: available Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin-ui: Endless Applications Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:15:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: {EndlessOS::system-desktop-file}: google-chrome.desktop Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:19:0288 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: available Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin-ui: Endless Applications Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: {EndlessOS::system-desktop-file}: google-chrome.desktop Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:19:0289 Gs failed to call gs_plugin_app_install on flatpak: [system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3] Not application or runtime Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:19:0294 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: available Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin-ui: Endless Applications Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:15:19 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: {EndlessOS::system-desktop-file}: google-chrome.desktop Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:21:0903 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: available Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin-ui: Endless Applications Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: {EndlessOS::system-desktop-file}: google-chrome.desktop Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:21:0903 Gs failed to call gs_plugin_app_install on flatpak: [system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3] Not application or runtime Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:21:0904 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: available Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin-ui: Endless Applications Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:15:21 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: {EndlessOS::system-desktop-file}: google-chrome.desktop Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:39:0278 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: available Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin-ui: Endless Applications Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: {EndlessOS::system-desktop-file}: google-chrome.desktop Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:39:0282 Gs failed to call gs_plugin_app_install on flatpak: [system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3] Not application or runtime Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:39:0285 Gs no source set by appstream for flatpak: GsApp: [0x560cd0bf8400] Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kind: desktop Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: state: available Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: quirk: provenance Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: id: com.google.Chrome.desktop Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: unique-id: system/flatpak/eos-apps/desktop/com.google.Chrome.desktop/eos3 Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: scope: system Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: bundle-kind: flatpak Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: kudo-percentage: 0 Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: pixbuf: (nil) Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: management-plugin: flatpak Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: branch: eos3 Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin: eos-apps Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: origin-ui: Endless Applications Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: reviews: 0 Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: provides: 0 Май 10 16:15:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: {EndlessOS::system-desktop-file}: google-chrome.desktop Май 10 16:15:47 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:15:47:0121 Gs failed to call gs_plugin_app_install on flatpak: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:16:03 endless eos-shell.desktop[1383]: 13:16:03:0414 Gs Failed to get AppStream metadata: No such branch 'appstream/x86_64' in repository summary Май 10 16:16:03 endless eos-shell.desktop[1383]: 13:16:03:0551 Gs failed to parse /var/lib/flatpak/exports/share/applications/kde4: /var/lib/flatpak/exports/share/applications/kde4 has an unrecognised extension Май 10 16:16:07 endless nautilus[2092]: Theme parsing error: Adwaita.css:51:71: Using one color stop with linear-gradient() is deprecated. Май 10 16:16:07 endless nautilus[2092]: Theme parsing error: Adwaita.css:52:71: Using one color stop with linear-gradient() is deprecated. Май 10 16:16:08 endless nautilus[2092]: Theme parsing error: :1:0: Failed to import: Ресурс из «/org/gnome/libgd/tagged-entry/default.css» не существует Май 10 16:16:23 endless totem[2245]: Missing plugin: gstreamer|1.0|totem|Декодер MPEG-1 Video|decoder-video/mpeg, mpegversion=(int)1, systemstream=(boolean)false (Декодер MPEG-1 Video) Май 10 16:16:23 endless eos-gst-codec-i[2261]: eos-gst-codec-install: xid = 39845903 Май 10 16:16:23 endless eos-gst-codec-i[2261]: eos-gst-codec-install: desktop_id = org.gnome.Totem.desktop Май 10 16:16:23 endless eos-gst-codec-i[2261]: eos-gst-codec-install: field is: mpegversion, type: gint Май 10 16:16:23 endless eos-gst-codec-i[2261]: eos-gst-codec-install: field is: systemstream, type: gboolean Май 10 16:16:23 endless eos-gst-codec-i[2261]: eos-gst-codec-install: Reporting to EOS metrics system: ('1.0', 'totem', 'decoder', 'video/mpeg', {'mpegversion': <1>, 'systemstream': }) Май 10 16:16:23 endless totem[2245]: No installation candidate for missing plugins found. Май 10 16:17:01 endless kernel: mce: [Hardware Error]: Machine check events logged Май 10 16:18:02 endless NetworkManager[583]: [1525958282.8467] connectivity: check for uri 'http://status.endlessm.com/network_status_check.txt' failed with 'Ошибка разрешения «status.endlessm.com»: Имя или служба не известны' Май 10 16:18:02 endless NetworkManager[583]: [1525958282.8469] manager: NetworkManager state is now CONNECTED_SITE Май 10 16:18:02 endless dbus[560]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Май 10 16:18:02 endless systemd[1]: Starting Network Manager Script Dispatcher Service... Май 10 16:18:02 endless dbus[560]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Май 10 16:18:02 endless systemd[1]: Started Network Manager Script Dispatcher Service. Май 10 16:18:02 endless nm-dispatcher[2289]: req:1 'connectivity-change': new request (4 scripts) Май 10 16:18:02 endless nm-dispatcher[2289]: req:1 'connectivity-change': start running ordered scripts... Май 10 16:18:03 endless NetworkManager[583]: [1525958283.1588] manager: NetworkManager state is now CONNECTED_GLOBAL Май 10 16:18:03 endless nm-dispatcher[2289]: req:2 'connectivity-change': new request (4 scripts) Май 10 16:18:03 endless nm-dispatcher[2289]: req:2 'connectivity-change': start running ordered scripts... Май 10 16:18:03 endless systemd[1]: Started Update or install Google Chrome plugins. Май 10 16:18:03 endless systemd[1]: Started Update or install codecs via GStreamer plugins. Май 10 16:18:03 endless systemd[1]: Started /bin/systemctl --no-block start eos-phone-home.service. Май 10 16:18:03 endless nm-dispatcher[2289]: Running timer as unit run-ra2300ac471e84d9a9ca5bdcab82870e2.timer. Май 10 16:18:03 endless nm-dispatcher[2289]: Will run service as unit run-ra2300ac471e84d9a9ca5bdcab82870e2.service. Май 10 16:18:03 endless eos-chrome-plugin-update[2299]: No need to check the Flash plugin yet (version: 29.0.0.171) Май 10 16:18:03 endless eos-chrome-plugin-update[2299]: No need to check the Widevine plugin yet (version: 66.0.3359.139-1) Май 10 16:18:03 endless eos-chrome-plugin-update[2299]: All done Май 10 16:18:03 endless eos-gstreamer-codecs-update[2305]: MP3 codec available via libav. No need to update Май 10 16:18:19 endless cupsd[566]: Closing client 13 after 300 seconds of inactivity... Май 10 16:18:19 endless cupsd[566]: [Client 13] Closing connection. Май 10 16:18:19 endless cupsd[566]: cupsdSetBusyState: newbusy="Not busy", busy="Not busy" Май 10 16:18:19 endless cupsd[566]: Report: clients=1 Май 10 16:18:19 endless cupsd[566]: Report: jobs=0 Май 10 16:18:19 endless cupsd[566]: Report: jobs-active=0 Май 10 16:18:19 endless cupsd[566]: Report: printers=0 Май 10 16:18:19 endless cupsd[566]: Report: stringpool-string-count=223 Май 10 16:18:19 endless cupsd[566]: Report: stringpool-alloc-bytes=3016 Май 10 16:18:19 endless cupsd[566]: Report: stringpool-total-bytes=3296 Май 10 16:18:19 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:18:28 endless cupsd[566]: Closing client 14 after 300 seconds of inactivity... Май 10 16:18:28 endless cupsd[566]: [Client 14] Closing connection. Май 10 16:18:28 endless cupsd[566]: cupsdSetBusyState: newbusy="Not busy", busy="Not busy" Май 10 16:18:28 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 16:19:25 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:25:0770 Gs not GsPlugin error from plugin flatpak g-dbus-error-quark:0: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:19:25 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:25:0770 Gs failed to call gs_plugin_update_app on flatpak: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:19:25 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:25:0781 Gs failed to call gs_plugin_update_app on flatpak: [system/flatpak/*/runtime/com.endlessm.apps.Platform.runtime/3] Not found com.endlessm.apps.Platform/x86_64/3 Май 10 16:19:25 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:25:0792 Gs failed to call gs_plugin_update_app on flatpak: [system/flatpak/*/runtime/com.endlessm.apps.Platform.runtime/3] Not found com.endlessm.apps.Platform/x86_64/3 Май 10 16:19:28 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:28:0837 Gs not GsPlugin error from plugin flatpak g-dbus-error-quark:0: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:19:28 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:28:0837 Gs failed to call gs_plugin_update_app on flatpak: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:19:28 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:28:0847 Gs failed to call gs_plugin_update_app on flatpak: [system/flatpak/*/runtime/com.endlessm.apps.Platform.runtime/3] Not found com.endlessm.apps.Platform/x86_64/3 Май 10 16:19:28 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:28:0858 Gs failed to call gs_plugin_update_app on flatpak: [system/flatpak/*/runtime/com.endlessm.apps.Platform.runtime/3] Not found com.endlessm.apps.Platform/x86_64/3 Май 10 16:19:31 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:31:0629 Gs not GsPlugin error from plugin flatpak g-dbus-error-quark:0: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:19:31 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:31:0629 Gs failed to call gs_plugin_update_app on flatpak: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:19:31 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:31:0640 Gs failed to call gs_plugin_update_app on flatpak: [system/flatpak/*/runtime/com.endlessm.apps.Platform.runtime/3] Not found com.endlessm.apps.Platform/x86_64/3 Май 10 16:19:31 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:31:0649 Gs failed to call gs_plugin_update_app on flatpak: [system/flatpak/*/runtime/com.endlessm.apps.Platform.runtime/3] Not found com.endlessm.apps.Platform/x86_64/3 Май 10 16:19:31 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:31:0659 Gs failed to call gs_plugin_update_app on flatpak: [system/flatpak/*/runtime/com.endlessm.apps.Platform.runtime/3] Not found com.endlessm.apps.Platform/x86_64/3 Май 10 16:19:34 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:34:0393 Gs not GsPlugin error from plugin flatpak g-dbus-error-quark:0: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:19:34 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:34:0393 Gs failed to call gs_plugin_update_app on flatpak: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:19:37 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:37:0078 Gs not GsPlugin error from plugin flatpak g-dbus-error-quark:0: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:19:37 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:37:0078 Gs failed to call gs_plugin_update_app on flatpak: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:19:37 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:37:0088 Gs failed to call gs_plugin_update_app on flatpak: [system/flatpak/*/runtime/com.endlessm.apps.Platform.runtime/3] Not found com.endlessm.apps.Platform/x86_64/3 Май 10 16:19:37 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:37:0107 Gs failed to call gs_plugin_update_app on flatpak: [system/flatpak/*/runtime/com.endlessm.apps.Platform.runtime/3] Not found com.endlessm.apps.Platform/x86_64/3 Май 10 16:19:37 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:37:0127 Gs failed to call gs_plugin_update_app on flatpak: [system/flatpak/*/runtime/com.endlessm.apps.Platform.runtime/3] Not found com.endlessm.apps.Platform/x86_64/3 Май 10 16:19:37 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:37:0137 Gs failed to call gs_plugin_update_app on flatpak: [system/flatpak/*/runtime/com.endlessm.apps.Platform.runtime/3] Not found com.endlessm.apps.Platform/x86_64/3 Май 10 16:19:37 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:37:0147 Gs failed to call gs_plugin_update_app on flatpak: [system/flatpak/*/runtime/com.endlessm.apps.Platform.runtime/3] Not found com.endlessm.apps.Platform/x86_64/3 Май 10 16:19:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:39:0853 Gs not GsPlugin error from plugin flatpak g-dbus-error-quark:0: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:19:39 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:39:0853 Gs failed to call gs_plugin_update_app on flatpak: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:19:43 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:43:0232 Gs not GsPlugin error from plugin flatpak g-dbus-error-quark:0: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:19:43 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:43:0232 Gs failed to call gs_plugin_update_app on flatpak: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:19:45 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:45:0965 Gs not GsPlugin error from plugin flatpak g-dbus-error-quark:0: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:19:45 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: 13:19:45:0965 Gs failed to call gs_plugin_update_app on flatpak: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 16:20:02 endless dbus[560]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Май 10 16:20:02 endless systemd[1]: Starting Hostname Service... Май 10 16:20:02 endless dbus[560]: [system] Successfully activated service 'org.freedesktop.hostname1' Май 10 16:20:02 endless systemd[1]: Started Hostname Service. Май 10 16:20:04 endless systemd[1]: Started /bin/systemctl --no-block start eos-phone-home.service. Май 10 16:20:04 endless systemd[1]: Started Send system activation/daily ping messages to Endless. Май 10 16:20:04 endless eos-phone-home[2617]: Already activated! Май 10 16:20:04 endless eos-phone-home[2617]: Getting variable: live Май 10 16:20:04 endless eos-phone-home[2617]: Getting variable: cmdline Май 10 16:20:04 endless eos-phone-home[2617]: - Cmdline: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-40a27c661924b10880bcde7db893844adc31bb8a90f0d6c3b247b9c423e57882/vmlinuz-4.8.0-32-generic root=UUID=817fe263-272d-47ba-945d-d9674912e832 rw splash plymouth.ignore-serial-consoles quiet ostree=/ostree/boot.1/eos/40a27c661924b10880bcde7db893844adc31bb8a90f0d6c3b247b9c423e57882/0 Май 10 16:20:04 endless eos-phone-home[2617]: Count age: 20871.142425775528 Май 10 16:20:04 endless eos-phone-home[2617]: Ping not due yet. Май 10 16:20:07 endless gnome-control-c[2607]: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed Май 10 16:20:08 endless eos-shell[1383]: JS LOG: Failed to add search provider /var/lib/flatpak/exports/share/gnome-shell/search-providers/org.gnome.Gnote.ini: TypeError: appInfo is null Май 10 16:20:08 endless systemd[1106]: Started flatpak-com.endlessm.EknServices-2623.scope. Май 10 16:20:08 endless eos-shell[1383]: JS LOG: Failed to add search provider /var/lib/flatpak/exports/share/gnome-shell/search-providers/org.gnome.Gnote.ini: TypeError: appInfo is null Май 10 16:20:08 endless org.gnome.Software[1222]: 13:20:08:0937 Gs Failed to get AppStream metadata: No such branch 'appstream/x86_64' in repository summary Май 10 16:20:09 endless org.gnome.Software[1222]: 13:20:09:0084 Gs failed to parse /var/lib/flatpak/exports/share/applications/kde4: /var/lib/flatpak/exports/share/applications/kde4 has an unrecognised extension Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_new_string: assertion 'string != NULL' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_new_variant: assertion 'value != NULL' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_get_type: assertion 'value != NULL' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_builder_add_value: assertion '!GVSB(builder)->expected_type || g_variant_is_of_type (value, GVSB(builder)->expected_type)' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_builder_end: assertion 'GVSB(builder)->offset >= GVSB(builder)->min_items' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_get_type: assertion 'value != NULL' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_builder_add_value: assertion '!GVSB(builder)->expected_type || g_variant_is_of_type (value, GVSB(builder)->expected_type)' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_new_string: assertion 'string != NULL' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_new_variant: assertion 'value != NULL' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_get_type: assertion 'value != NULL' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_builder_add_value: assertion '!GVSB(builder)->expected_type || g_variant_is_of_type (value, GVSB(builder)->expected_type)' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_builder_end: assertion 'GVSB(builder)->offset >= GVSB(builder)->min_items' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_get_type: assertion 'value != NULL' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed Май 10 16:20:11 endless org.gnome.Software[1222]: 13:20:11:0402 GLib g_variant_builder_add_value: assertion '!GVSB(builder)->expected_type || g_variant_is_of_type (value, GVSB(builder)->expected_type)' failed Май 10 16:20:22 endless eos-updater[1472]: Product group: ASUSTeK COMPUTER INC. X541NA Май 10 16:20:22 endless eos-updater[1472]: Branches configuration URI: https://ostree.endlessm.com/ostree/eos-amd64/eos-branch?product_version=1.0&sys_vendor=ASUSTeK+COMPUTER+INC.&ref=os%2Feos%2Famd64%2Feos3&board_vendor=ASUSTeK+COMPUTER+INC.&board_name=X541NA&bios_version=X541NA.313&commit=2c22686c94be7fda0fab6ee22f453379e7d849c4a09fda80b76b239e1b56b220&chassis_vendor=ASUSTeK+COMPUTER+INC.&chassis_version=1.0&bios_date=08%2F10%2F2017&bios_vendor=American+Megatrends+Inc.&board_version=1.0&product_name=X541NA Май 10 16:20:22 endless eos-updater[1472]: No product-specific branch configuration or Default found, following the origin file Май 10 16:20:22 endless eos-updater[1472]: Using product branch os/eos/amd64/eos3 Май 10 16:20:22 endless eos-updater[1472]: Recording metric event 99f48aac-b5a0-426d-95f4-18af7d081c4e: (ASUSTeK COMPUTER INC., X541NA, os/eos/amd64/eos3, 0) Май 10 16:20:33 endless eos-updater[1472]: Fetch: eos:os/eos/amd64/eos3 resolved to: 1350835e3381b79abd6a1623035830752735789fb4968ffadd8419c48d9aba57 Май 10 16:20:36 endless eos-updater[1472]: Fetch: pull() completed Май 10 16:20:36 endless eos-updater[1472]: Fetch: commit 1350835e3381b79abd6a1623035830752735789fb4968ffadd8419c48d9aba57 cached Май 10 16:20:36 endless eos-updater[1472]: System redeployed same boot version Май 10 16:20:40 endless evince[2736]: Allocating size to EvSidebar 0x5654336b54e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:27:04 endless systemd[1]: Started EndlessOS Automatic Updater. Май 10 16:27:04 endless systemd[1]: Starting Cleanup of Temporary Directories... Май 10 16:27:04 endless systemd[1]: Started Send system activation/daily ping messages to Endless. Май 10 16:27:04 endless systemd[1]: Started Cleanup of Temporary Directories. Май 10 16:27:04 endless eos-autoupdater[2823]: EOS updater state is: 1 Май 10 16:27:04 endless eos-updater[1472]: Product group: ASUSTeK COMPUTER INC. X541NA Май 10 16:27:04 endless eos-updater[1472]: Branches configuration URI: https://ostree.endlessm.com/ostree/eos-amd64/eos-branch?product_version=1.0&sys_vendor=ASUSTeK+COMPUTER+INC.&ref=os%2Feos%2Famd64%2Feos3&board_vendor=ASUSTeK+COMPUTER+INC.&board_name=X541NA&bios_version=X541NA.313&commit=2c22686c94be7fda0fab6ee22f453379e7d849c4a09fda80b76b239e1b56b220&chassis_vendor=ASUSTeK+COMPUTER+INC.&chassis_version=1.0&bios_date=08%2F10%2F2017&bios_vendor=American+Megatrends+Inc.&board_version=1.0&product_name=X541NA Май 10 16:27:04 endless eos-phone-home[2825]: Already activated! Май 10 16:27:04 endless eos-phone-home[2825]: Getting variable: live Май 10 16:27:04 endless eos-phone-home[2825]: Getting variable: cmdline Май 10 16:27:04 endless eos-phone-home[2825]: - Cmdline: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-40a27c661924b10880bcde7db893844adc31bb8a90f0d6c3b247b9c423e57882/vmlinuz-4.8.0-32-generic root=UUID=817fe263-272d-47ba-945d-d9674912e832 rw splash plymouth.ignore-serial-consoles quiet ostree=/ostree/boot.1/eos/40a27c661924b10880bcde7db893844adc31bb8a90f0d6c3b247b9c423e57882/0 Май 10 16:27:04 endless eos-phone-home[2825]: Count age: 21291.148463964462 Май 10 16:27:04 endless eos-phone-home[2825]: Ping not due yet. Май 10 16:27:04 endless eos-autoupdater[2823]: EOS updater state is: 3 Май 10 16:27:05 endless eos-updater[1472]: No product-specific branch configuration or Default found, following the origin file Май 10 16:27:05 endless eos-updater[1472]: Using product branch os/eos/amd64/eos3 Май 10 16:27:05 endless eos-autoupdater[2823]: EOS updater state is: 4 Май 10 16:27:05 endless eos-updater[1472]: Fetch: eos:os/eos/amd64/eos3 resolved to: 1350835e3381b79abd6a1623035830752735789fb4968ffadd8419c48d9aba57 Май 10 16:27:05 endless eos-autoupdater[2823]: EOS updater state is: 5 Май 10 16:27:05 endless gnome-control-c[2607]: Failed to call Fetch() on EOS updater: GDBus.Error:com.endlessm.Updater.Error.WrongState: Can't call Fetch() while in state Fetching Май 10 16:27:08 endless eos-updater[1472]: Fetch: pull() completed Май 10 16:27:08 endless eos-updater[1472]: Fetch: commit 1350835e3381b79abd6a1623035830752735789fb4968ffadd8419c48d9aba57 cached Май 10 16:27:08 endless eos-autoupdater[2823]: EOS updater state is: 6 Май 10 16:27:08 endless gnome-control-c[2607]: Failed to call Apply() on EOS updater: GDBus.Error:com.endlessm.Updater.Error.WrongState: Can't call Apply() while in state ApplyUpdate Май 10 16:27:08 endless eos-autoupdater[2823]: EOS updater state is: 7 Май 10 16:27:08 endless eos-updater[1472]: System redeployed same boot version Май 10 16:27:08 endless eos-autoupdater[2823]: EOS updater state is: 2 Май 10 16:27:08 endless eos-autoupdater[2823]: EOS updater error (org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code1): Checking out tree: Couldn't find file object 'ffa452c68acce6b7c3435fb4e89934c6588ec32f47659c9d681634b7fa7324e2' Май 10 16:27:08 endless systemd[1]: eos-autoupdater.service: Main process exited, code=exited, status=1/FAILURE Май 10 16:27:08 endless systemd[1]: eos-autoupdater.service: Unit entered failed state. Май 10 16:27:08 endless systemd[1]: eos-autoupdater.service: Failed with result 'exit-code'. Май 10 16:33:01 endless systemd[1106]: Started flatpak-com.endlessm.videonet-2863.scope. Май 10 16:36:00 endless gnome-calculato[2962]: number_reciprocal: assertion 'self != NULL' failed Май 10 16:36:00 endless gnome-calculato[2962]: currency_set_value: assertion 'value != NULL' failed Май 10 16:36:00 endless gnome-calculato[2962]: number_reciprocal: assertion 'self != NULL' failed Май 10 16:36:00 endless gnome-calculato[2962]: currency_set_value: assertion 'value != NULL' failed Май 10 16:36:00 endless gnome-calculato[2962]: number_reciprocal: assertion 'self != NULL' failed Май 10 16:36:00 endless gnome-calculato[2962]: currency_set_value: assertion 'value != NULL' failed Май 10 16:36:00 endless gnome-calculato[2962]: currency.vala:406: Currency KZT is not provided by IMF or ECB Май 10 16:36:00 endless gnome-calculato[2962]: currency.vala:406: Currency UYU is not provided by IMF or ECB Май 10 16:36:00 endless gnome-calculato[2962]: currency.vala:406: Currency VEF is not provided by IMF or ECB Май 10 16:36:43 endless kernel: WebKitWebProces[2925]: segfault at 10 ip 00007f6e466e1a1a sp 00007f6ddaffc690 error 4 in libwebkit2gtk-4.0.so.37.14.7[7f6e45142000+2536000] Май 10 16:36:58 endless systemd[1106]: Started flatpak-net.minetest.Minetest-2980.scope. Май 10 16:36:59 endless eos-shell.desktop[1383]: Irrlicht log: Irrlicht Engine version 1.8.1 Май 10 16:36:59 endless eos-shell.desktop[1383]: Irrlicht log: Linux 4.8.0-32-generic #34+dev147.48224f3beos3.1.1-Endless SMP Fri Jan 13 13:21:09 UTC x86_64 Май 10 16:37:00 endless eos-shell.desktop[1383]: Irrlicht log: Irrlicht Engine version 1.8.1 Май 10 16:37:00 endless eos-shell.desktop[1383]: Irrlicht log: Linux 4.8.0-32-generic #34+dev147.48224f3beos3.1.1-Endless SMP Fri Jan 13 13:21:09 UTC x86_64 Май 10 16:37:01 endless eos-shell.desktop[1383]: Irrlicht log: Using renderer: OpenGL 3.0 Май 10 16:37:01 endless eos-shell.desktop[1383]: Irrlicht log: Mesa DRI Intel(R) HD Graphics (Broxton) : Intel Open Source Technology Center Май 10 16:37:01 endless eos-shell.desktop[1383]: Irrlicht log: OpenGL driver version is 1.2 or better. Май 10 16:37:01 endless eos-shell.desktop[1383]: Irrlicht log: GLSL version: 1.3 Май 10 16:37:01 endless eos-shell[1383]: shell_app_state_transition: assertion '!(app->state == SHELL_APP_STATE_RUNNING && state == SHELL_APP_STATE_STARTING)' failed Май 10 16:37:01 endless eos-shell[1383]: shell_app_state_transition: assertion '!(app->state == SHELL_APP_STATE_RUNNING && state == SHELL_APP_STATE_STARTING)' failed Май 10 16:37:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: ERROR:root:Gnome Software installed some new application but not Google Chrome. Most probably, user decided to install something else. Quitting... Май 10 16:37:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: ERROR:dbus.connection:Exception in handler for D-Bus signal: Май 10 16:37:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: Traceback (most recent call last): Май 10 16:37:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: File "/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in maybe_handle_message Май 10 16:37:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: self._handler(*args, **kwargs) Май 10 16:37:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: File "/usr/lib/x86_64-linux-gnu/eos-google-chrome-helper/eos-google-chrome-installer", line 141, in handler Май 10 16:37:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: exit_with_error("Gnome Software installed some new application but not Google Chrome. " Май 10 16:37:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: File "/usr/lib/x86_64-linux-gnu/eos-google-chrome-helper/eos-google-chrome-installer", line 45, in exit_with_error Май 10 16:37:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: sys.exit(1) Май 10 16:37:18 endless com.endlessm.GoogleChromeInitialSetup.desktop[1486]: SystemExit: 1 Май 10 16:37:28 endless eos-shell[1383]: JS ERROR: Exception in callback for signal: destroy: TypeError: obj is null MessageTray<._removeSource@resource:///org/gnome/shell/ui/messageTray.js:2075:13 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:13 MessageTray<._onSourceDestroy@resource:///org/gnome/shell/ui/messageTray.js:2123:9 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:13 _emit@resource:///org/gnome/gjs/modules/signals.js:124:21 Source<.destroy@resource:///org/gnome/shell/ui/messageTray.js:1411:9 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:13 Source<._lastNotificationRemoved@resource:///org/gnome/shell/ui/messageTray.js:1447:9 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:13 Source<.pushNotification/<@resource:///org/gnome/shell/ui/messageTray.js:1385:21 _emit@resource:///org/gnome/gjs/modules/signals.js:124:21 Notification<._onDestroy@resource:///org/gnome/shell/ui/messageTray.js:1142:9 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:13 Notification<.destroy@resource:///org/gnome/shell/ui/messageTray.js:1147:9 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:13 MessageTray<._hideNotificationCompleted@resource:///org/gnome/shell/ui/messageTray.js:2708:13 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:13 MessageTray<._tweenComplete@resource:///org/gnome/shell/ui/messageTray.js:2453:13 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:13 _addHandler/params[name]@resource:///org/gnome/shell/ui/tweener.js:89:13 _callOnFunction@resource:///org/gnome/gjs/modules/tweener/tweener.js:203:13 _updateTweenByIndex@resource:///org/gnome/gjs/modules/tweener/tweener.js:333:1 _updateTweens@resource:///org/gnome/gjs/modules/tweener/tweener.js:345:17 _onEnterFrame@resource:///org/gnome/gjs/modules/tweener/tweener.js:360:9 _emit@resource:///org/gnome/gjs/modules/signals.js:124:21 ClutterFrameTicker<._onNewFrame@resource:///org/gnome/shell/ui/tweener.js:206:9 wrapper@resource:///org/gnome/gjs/modules/lang.js:178:13 ClutterFrameTicker<._init/<@resource:///org/gnome/shell/ui/tweener.js:181:17 Май 10 16:37:33 endless eos-shell[1383]: JS LOG: Failed to add search provider /var/lib/flatpak/exports/share/gnome-shell/search-providers/org.gnome.Gnote.ini: TypeError: appInfo is null Май 10 16:37:50 endless eos-shell.desktop[1383]: [1:1:0510/163750:ERROR:PlatformKeyboardEvent.cpp(94)] Not implemented reached in static bool blink::PlatformKeyboardEvent::currentCapsLockState() Май 10 16:38:01 endless eos-shell.desktop[1383]: [1:1:0510/163801:ERROR:PlatformKeyboardEvent.cpp(94)] Not implemented reached in static bool blink::PlatformKeyboardEvent::currentCapsLockState() Май 10 16:38:11 endless eos-shell.desktop[1383]: [1:1:0510/163811:ERROR:PlatformKeyboardEvent.cpp(94)] Not implemented reached in static bool blink::PlatformKeyboardEvent::currentCapsLockState() Май 10 16:38:18 endless eos-shell.desktop[1383]: [1:1:0510/163818:ERROR:PlatformKeyboardEvent.cpp(94)] Not implemented reached in static bool blink::PlatformKeyboardEvent::currentCapsLockState() Май 10 16:38:21 endless eos-shell.desktop[1383]: [1:1:0510/163821:ERROR:PlatformKeyboardEvent.cpp(94)] Not implemented reached in static bool blink::PlatformKeyboardEvent::currentCapsLockState() Май 10 16:41:59 endless eos-shell.desktop[1383]: [1:1:0510/164159:ERROR:PlatformKeyboardEvent.cpp(94)] Not implemented reached in static bool blink::PlatformKeyboardEvent::currentCapsLockState() Май 10 16:42:13 endless eos-shell.desktop[1383]: [1:1:0510/164213:ERROR:PlatformKeyboardEvent.cpp(94)] Not implemented reached in static bool blink::PlatformKeyboardEvent::currentCapsLockState() Май 10 16:42:36 endless systemd[1106]: Started flatpak-com.endlessm.travel.en-3242.scope. Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Deck 0x3f3edc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Deck 0x3f3ef80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Deck 0x3e16180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Deck 0x3e16340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Thumb 0x62cbc00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x630f500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x630f6b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Thumb 0x62cbdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x630f860 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x630fa10 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Thumb 0x62cbf80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x630fbc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x630fd70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Thumb 0x4351180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x630ff20 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x63481f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Thumb 0x4351340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x63483a0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x6348550 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Thumb 0x4351500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x6348700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x63488b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Thumb 0x43516c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x6348a60 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x6348c10 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Thumb 0x4351880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x6348dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x6348f70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Thumb 0x2b83a40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x6039200 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x60393b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Thumb 0x2b83c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x6039560 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x6039710 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Thumb 0x2b83dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x60398c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x6039a70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Thumb 0x2b83f80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x6039c20 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x6039dd0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to EknCard_Thumb 0x6072180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x6039f80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:52 endless gjs[3261]: Allocating size to GtkFrame 0x607b1a0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x6072340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x607b350 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x607b500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x6072500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x607b6b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x607b860 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x60726c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x607ba10 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x607bbc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Post 0x2b83340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Post 0x2b83500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Post 0x2b836c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Post 0x2b83880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Deck 0x3f3edc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Deck 0x3f3ef80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Deck 0x3e16180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Deck 0x3e16340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x62cbc00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x630f6b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x62cbdc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x630fa10 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x62cbf80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x630fd70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x4351180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x63481f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x4351340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x6348550 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x4351500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x63488b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x43516c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x6348c10 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x4351880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x6348f70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x2b83a40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x60393b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x2b83c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x6039710 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x2b83dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x6039a70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x2b83f80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x6039dd0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x6072180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x607b1a0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x6072340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x607b500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x6072500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x607b860 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Thumb 0x60726c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to GtkFrame 0x607bbc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Post 0x2b83340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Post 0x2b83500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Post 0x2b836c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:42:53 endless gjs[3261]: Allocating size to EknCard_Post 0x2b83880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to EknCard_Deck 0x4490dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to EknCard_Deck 0x4490f80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to EknCard_Deck 0x45de180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to EknCard_Deck 0x45de340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to EknCard_Thumb 0x47c7dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to GtkFrame 0x7101d40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to GtkFrame 0x7101ef0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to EknCard_Thumb 0x47c7f80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to GtkFrame 0x41751d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to GtkFrame 0x4175380 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to EknCard_Thumb 0x4098180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to GtkFrame 0x4175530 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to GtkFrame 0x41756e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to EknCard_Thumb 0x4098340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to GtkFrame 0x4175890 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to GtkFrame 0x4175a40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to EknCard_Deck 0x4490dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to EknCard_Deck 0x4490f80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to EknCard_Deck 0x45de180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to EknCard_Deck 0x45de340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to EknCard_Thumb 0x47c7dc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to GtkFrame 0x7101ef0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to EknCard_Thumb 0x47c7f80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to GtkFrame 0x4175380 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to EknCard_Thumb 0x4098180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to GtkFrame 0x41756e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to EknCard_Thumb 0x4098340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:11 endless gjs[3261]: Allocating size to GtkFrame 0x4175a40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:42 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:43:42 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:43:42 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:43:42 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:43:42 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:43:42 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:43:42 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:43:42 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:43:42 endless gjs[3261]: Error parsing model property outgoing-links: Некорректное строковое значение для преобразования к GVariant Май 10 16:43:43 endless gjs[3261]: Allocating size to EknCard_Thumb 0x98adc00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to GtkFrame 0x89fef40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to GtkFrame 0x98fe200 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to EknCard_Thumb 0x98addc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to GtkFrame 0x98fe3b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to GtkFrame 0x98fe560 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to EknCard_Thumb 0x98adf80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to GtkFrame 0x98fe710 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to GtkFrame 0x98fe8c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to EknCard_Thumb 0x991a180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to GtkFrame 0x98fea70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to GtkFrame 0x98fec20 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:43:43 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:43:43 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:43:43 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:43:43 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:43:43 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:43:43 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:43:43 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:43:43 endless gjs[3261]: Allocating size to EknCard_Thumb 0x98adc00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to GtkFrame 0x98fe200 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to EknCard_Thumb 0x98addc0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to GtkFrame 0x98fe560 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to EknCard_Thumb 0x98adf80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to GtkFrame 0x98fe8c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to EknCard_Thumb 0x991a180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:43:43 endless gjs[3261]: Allocating size to GtkFrame 0x98fec20 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:01 endless gjs[3261]: Allocating size to EknCard_Thumb 0x53b7340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:01 endless gjs[3261]: Allocating size to GtkFrame 0x4175380 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:01 endless gjs[3261]: Allocating size to GtkFrame 0x41751d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:01 endless gjs[3261]: Allocating size to EknCard_Thumb 0x53b7500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:01 endless gjs[3261]: Allocating size to GtkFrame 0x4175a40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:01 endless gjs[3261]: Allocating size to GtkFrame 0x4175890 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:01 endless gjs[3261]: Allocating size to EknCard_Thumb 0x53b76c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:01 endless gjs[3261]: Allocating size to GtkFrame 0x7101ef0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:01 endless gjs[3261]: Allocating size to GtkFrame 0x7101d40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:01 endless gjs[3261]: Allocating size to EknCard_Thumb 0x53b7880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:01 endless gjs[3261]: Allocating size to GtkFrame 0x41756e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:01 endless gjs[3261]: Allocating size to GtkFrame 0x4175530 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:02 endless gjs[3261]: Allocating size to EknCard_Thumb 0x53b7340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:02 endless gjs[3261]: Allocating size to GtkFrame 0x41751d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:02 endless gjs[3261]: Allocating size to EknCard_Thumb 0x53b7500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:02 endless gjs[3261]: Allocating size to GtkFrame 0x4175890 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:02 endless gjs[3261]: Allocating size to EknCard_Thumb 0x53b76c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:02 endless gjs[3261]: Allocating size to GtkFrame 0x7101d40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:02 endless gjs[3261]: Allocating size to EknCard_Thumb 0x53b7880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:02 endless gjs[3261]: Allocating size to GtkFrame 0x4175530 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to EknCard_Thumb 0xa0fd180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to GtkFrame 0x268c510 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to GtkFrame 0x268c6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to EknCard_Thumb 0xa0fd340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to GtkFrame 0x268c870 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to GtkFrame 0x268ca20 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:27 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:27 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:27 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:27 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:27 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:27 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:27 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:27 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:27 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:27 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:27 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:27 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:27 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:27 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:27 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:27 endless gjs[3261]: Allocating size to EknCard_Thumb 0xa0fd500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to GtkFrame 0x268cbd0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to GtkFrame 0x268cd80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to EknCard_Thumb 0xa0fd6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to GtkFrame 0x268cf30 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to GtkFrame 0x974d1f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to EknCard_Thumb 0xa0fd180 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to GtkFrame 0x268c6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to EknCard_Thumb 0xa0fd340 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to GtkFrame 0x268ca20 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to EknCard_Thumb 0xa0fd500 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to GtkFrame 0x268cd80 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to EknCard_Thumb 0xa0fd6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:27 endless gjs[3261]: Allocating size to GtkFrame 0x974d1f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:36 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:44:37 endless gjs[3261]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy() or dispose() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Май 10 16:54:29 endless systemd-journald[312]: Suppressed 1534 messages from /user.slice/user-1001.slice Май 10 16:54:29 endless gjs[3261]: Allocating size to EknCard_Post 0x2b836c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Май 10 16:56:01 endless dbus[560]: [system] Activating via systemd: service name='org.freedesktop.Flatpak.SystemHelper' unit='flatpak-system-helper.service' Май 10 16:56:01 endless systemd[1]: Starting flatpak system helper... Май 10 16:56:01 endless dbus[560]: [system] Successfully activated service 'org.freedesktop.Flatpak.SystemHelper' Май 10 16:56:01 endless systemd[1]: Started flatpak system helper. Май 10 16:56:01 endless eos-shell.desktop[1383]: 13:56:01:0553 Gs Failed to get AppStream metadata: No such branch 'appstream/x86_64' in repository summary Май 10 16:56:01 endless eos-shell.desktop[1383]: 13:56:01:0687 Gs failed to parse /var/lib/flatpak/exports/share/applications/kde4: /var/lib/flatpak/exports/share/applications/kde4 has an unrecognised extension Май 10 16:56:05 endless org.gnome.Software[1222]: 13:56:05:0467 Gs Failed to get AppStream metadata: No such branch 'appstream/x86_64' in repository summary Май 10 16:56:19 endless systemd[1106]: Started flatpak-org.pitivi.Pitivi-2628.scope. Май 10 16:56:20 endless org.gnome.Software[1222]: /app/lib/x86_64-linux-gnu/pitivi/python/pitivi/check.py:252: PyGIWarning: Gdk was imported without specifying a version first. Use gi.require_version('Gdk', '3.0') before import to ensure that the right version gets loaded. Май 10 16:56:20 endless org.gnome.Software[1222]: from gi.repository import Gdk Май 10 16:56:20 endless org.gnome.Software[1222]: ** (pitivi:3): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-bSIFi2QCiQ: В соединении отказано Май 10 16:56:20 endless org.gnome.Software[1222]: /app/lib/x86_64-linux-gnu/pitivi/python/pitivi/check.py:254: PyGIWarning: GtkClutter was imported without specifying a version first. Use gi.require_version('GtkClutter', '1.0') before import to ensure that the right version gets loaded. Май 10 16:56:20 endless org.gnome.Software[1222]: from gi.repository import GtkClutter Май 10 16:56:20 endless org.gnome.Software[1222]: /app/lib/x86_64-linux-gnu/pitivi/python/pitivi/check.py:256: PyGIWarning: ClutterGst was imported without specifying a version first. Use gi.require_version('ClutterGst', '2.0') before import to ensure that the right version gets loaded. Май 10 16:56:20 endless org.gnome.Software[1222]: from gi.repository import ClutterGst Май 10 16:56:21 endless org.gnome.Software[1222]: /app/lib/x86_64-linux-gnu/pitivi/python/pitivi/check.py:266: PyGIWarning: GES was imported without specifying a version first. Use gi.require_version('GES', '1.0') before import to ensure that the right version gets loaded. Май 10 16:56:21 endless org.gnome.Software[1222]: from gi.repository import GES Май 10 16:56:22 endless org.gnome.Software[1222]: /app/lib/x86_64-linux-gnu/pitivi/python/pitivi/timeline/elements.py:36: PyGIWarning: GstController was imported without specifying a version first. Use gi.require_version('GstController', '1.0') before import to ensure that the right version gets loaded. Май 10 16:56:22 endless org.gnome.Software[1222]: from gi.repository import Clutter, Gtk, GtkClutter, GES, Gdk, Gst, GstController Май 10 16:56:27 endless org.gnome.Software[1222]: Missing soft dependency: Май 10 16:56:27 endless org.gnome.Software[1222]: - pycanberra not found on the system Май 10 16:56:27 endless org.gnome.Software[1222]: -> enables sound notifications when rendering is complete Май 10 16:56:27 endless org.gnome.Software[1222]: Missing soft dependency: Май 10 16:56:27 endless org.gnome.Software[1222]: - GnomeDesktop not found on the system Май 10 16:56:27 endless org.gnome.Software[1222]: -> file thumbnails provided by GNOME's thumbnailers Май 10 16:56:27 endless org.gnome.Software[1222]: Missing soft dependency: Май 10 16:56:27 endless org.gnome.Software[1222]: - Notify not found on the system Май 10 16:56:27 endless org.gnome.Software[1222]: -> enables visual notifications when rendering is complete Май 10 16:56:27 endless org.gnome.Software[1222]: Traceback (most recent call last): Май 10 16:56:27 endless org.gnome.Software[1222]: File "/app/lib/x86_64-linux-gnu/pitivi/python/pitivi/titleeditor.py", line 877, in tabSwitchedCb Май 10 16:56:27 endless org.gnome.Software[1222]: self._connect_signals() Май 10 16:56:27 endless org.gnome.Software[1222]: File "/app/lib/x86_64-linux-gnu/pitivi/python/pitivi/titleeditor.py", line 814, in _connect_signals Май 10 16:56:27 endless org.gnome.Software[1222]: self.app.gui.viewer.target.connect("motion-notify-event", self.drag_notify_event) Май 10 16:56:27 endless org.gnome.Software[1222]: AttributeError: 'NoneType' object has no attribute 'viewer' Май 10 16:56:36 endless org.gnome.Software[1222]: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.vfs.UDisks2VolumeMonitor:: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown (g-dbus-error-quark, 2) Май 10 16:56:37 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:37 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:37 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:40 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:42 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:42 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:42 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:42 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:42 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:42 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:43 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:46 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:47 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:48 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:49 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:51 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:53 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:53 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:53 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:53 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:53 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:53 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:53 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:53 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:53 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:53 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:54 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:54 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:54 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:54 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:54 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:54 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:54 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:55 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:56 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:57 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:58 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:58 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:58 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:58 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:58 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:58 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:58 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:58 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:58 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:58 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:58 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:56:58 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:02 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:02 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:02 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:02 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:02 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:02 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:02 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:02 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:02 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:04 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:04 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:05 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:05 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:05 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:05 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:05 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:05 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:05 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:05 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:05 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:05 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:06 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:06 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:06 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:06 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:06 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:06 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:06 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:06 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:06 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:07 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:07 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:07 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:07 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:07 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:07 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:07 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:07 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:07 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:07 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:08 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:09 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:09 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:09 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:09 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:09 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:09 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:09 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:09 endless org.gnome.Software[1222]: (pitivi:3): dconf-WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown Май 10 16:57:46 endless kernel: perf: interrupt took too long (2669 > 2500), lowering kernel.perf_event_max_sample_rate to 74750 Май 10 16:57:48 endless eos-shell[1383]: JS LOG: Failed to add search provider /var/lib/flatpak/exports/share/gnome-shell/search-providers/org.gnome.Gnote.ini: TypeError: appInfo is null Май 10 16:57:48 endless eos-shell[1383]: JS LOG: Failed to add search provider /var/lib/flatpak/exports/share/gnome-shell/search-providers/org.gnome.Gnote.ini: TypeError: appInfo is null Май 10 16:57:49 endless eos-shell[1383]: JS LOG: Failed to add search provider /var/lib/flatpak/exports/share/gnome-shell/search-providers/org.gnome.Gnote.ini: TypeError: appInfo is null Май 10 16:58:12 endless eos-shell[1383]: JS LOG: Failed to add search provider /var/lib/flatpak/exports/share/gnome-shell/search-providers/org.gnome.Gnote.ini: TypeError: appInfo is null Май 10 16:58:12 endless eos-shell[1383]: JS LOG: Failed to add search provider /var/lib/flatpak/exports/share/gnome-shell/search-providers/org.gnome.Gnote.ini: TypeError: appInfo is null Май 10 16:58:23 endless systemd[1106]: Started flatpak-org.gnome.Iagno-2628.scope. Май 10 16:58:23 endless org.gnome.Software[1222]: ** (iagno:3): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-bSIFi2QCiQ: В соединении отказано Май 10 17:01:53 endless org.gnome.Software[1222]: 14:01:53:0286 Gs failed to install org.gnome.Iagno.desktop: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error pulling from repo: While pulling runtime/com.endlessm.Platform/x86_64/eos3.2 from remote eos-runtimes: Couldn't find file object 'd6176116095d42eef2b4aac9c70d320a718528e6ef3d492d92df3cd2ae15b71e' Май 10 17:02:44 endless cupsd[566]: [Client 13] Accepted from localhost (Domain) Май 10 17:02:44 endless cupsd[566]: [Client 13] Waiting for request. Май 10 17:02:44 endless cupsd[566]: Report: clients=1 Май 10 17:02:44 endless cupsd[566]: Report: jobs=0 Май 10 17:02:44 endless cupsd[566]: Report: jobs-active=0 Май 10 17:02:44 endless cupsd[566]: Report: printers=0 Май 10 17:02:44 endless cupsd[566]: Report: stringpool-string-count=223 Май 10 17:02:44 endless cupsd[566]: Report: stringpool-alloc-bytes=3016 Май 10 17:02:44 endless cupsd[566]: Report: stringpool-total-bytes=3296 Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: [Client 13] POST / HTTP/1.1 Май 10 17:02:44 endless cupsd[566]: cupsdSetBusyState: newbusy="Active clients", busy="Not busy" Май 10 17:02:44 endless cupsd[566]: [Client 13] No authentication data provided. Май 10 17:02:44 endless cupsd[566]: [Client 13] 2.0 CUPS-Get-Printers 1 Май 10 17:02:44 endless cupsd[566]: CUPS-Get-Printers Май 10 17:02:44 endless cupsd[566]: CUPS-Get-Printers client-error-not-found: No destinations added. Май 10 17:02:44 endless cupsd[566]: [Client 13] Returning IPP client-error-not-found for CUPS-Get-Printers (no URI) from localhost Май 10 17:02:44 endless cupsd[566]: [Client 13] Content-Length: 113 Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: [Client 13] cupsdWriteClient error=0, used=0, state=HTTP_STATE_POST_SEND, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=113, response=0x55fb83cfd1a0(IPP_IDLE), pipe_pid=0, file=-1 Май 10 17:02:44 endless cupsd[566]: [Client 13] Writing IPP response, ipp_state=DATA, old wused=0, new wused=0 Май 10 17:02:44 endless cupsd[566]: [Client 13] bytes=0, http_state=0, data_remaining=0 Май 10 17:02:44 endless cupsd[566]: [Client 13] Waiting for request. Май 10 17:02:44 endless cupsd[566]: cupsdSetBusyState: newbusy="Not busy", busy="Active clients" Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: [Client 14] Accepted from localhost (Domain) Май 10 17:02:44 endless cupsd[566]: [Client 14] Waiting for request. Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: [Client 13] POST / HTTP/1.1 Май 10 17:02:44 endless cupsd[566]: cupsdSetBusyState: newbusy="Active clients", busy="Not busy" Май 10 17:02:44 endless cupsd[566]: [Client 13] No authentication data provided. Май 10 17:02:44 endless cupsd[566]: [Client 13] 2.0 CUPS-Get-Classes 2 Май 10 17:02:44 endless cupsd[566]: CUPS-Get-Classes Май 10 17:02:44 endless cupsd[566]: CUPS-Get-Classes client-error-not-found: No destinations added. Май 10 17:02:44 endless cupsd[566]: [Client 13] Returning IPP client-error-not-found for CUPS-Get-Classes (no URI) from localhost Май 10 17:02:44 endless cupsd[566]: [Client 13] Content-Length: 113 Май 10 17:02:44 endless cupsd[566]: [Client 14] HTTP_STATE_WAITING Closing on EOF Май 10 17:02:44 endless cupsd[566]: [Client 14] Closing connection. Май 10 17:02:44 endless cupsd[566]: cupsdSetBusyState: newbusy="Active clients", busy="Active clients" Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: [Client 13] cupsdWriteClient error=0, used=0, state=HTTP_STATE_POST_SEND, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=113, response=0x55fb83d01550(IPP_IDLE), pipe_pid=0, file=-1 Май 10 17:02:44 endless cupsd[566]: [Client 13] Writing IPP response, ipp_state=DATA, old wused=0, new wused=0 Май 10 17:02:44 endless cupsd[566]: [Client 13] bytes=0, http_state=0, data_remaining=0 Май 10 17:02:44 endless cupsd[566]: [Client 13] Waiting for request. Май 10 17:02:44 endless cupsd[566]: cupsdSetBusyState: newbusy="Not busy", busy="Active clients" Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: [Client 13] POST / HTTP/1.1 Май 10 17:02:44 endless cupsd[566]: cupsdSetBusyState: newbusy="Active clients", busy="Not busy" Май 10 17:02:44 endless cupsd[566]: [Client 13] No authentication data provided. Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: [Client 13] 2.0 CUPS-Get-Printers 3 Май 10 17:02:44 endless cupsd[566]: CUPS-Get-Printers Май 10 17:02:44 endless cupsd[566]: CUPS-Get-Printers client-error-not-found: No destinations added. Май 10 17:02:44 endless cupsd[566]: [Client 13] Returning IPP client-error-not-found for CUPS-Get-Printers (no URI) from localhost Май 10 17:02:44 endless cupsd[566]: [Client 13] Content-Length: 113 Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: [Client 13] cupsdWriteClient error=0, used=0, state=HTTP_STATE_POST_SEND, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=113, response=0x55fb83cfd1a0(IPP_IDLE), pipe_pid=0, file=-1 Май 10 17:02:44 endless cupsd[566]: [Client 13] Writing IPP response, ipp_state=DATA, old wused=0, new wused=0 Май 10 17:02:44 endless cupsd[566]: [Client 13] bytes=0, http_state=0, data_remaining=0 Май 10 17:02:44 endless cupsd[566]: [Client 13] Waiting for request. Май 10 17:02:44 endless cupsd[566]: cupsdSetBusyState: newbusy="Not busy", busy="Active clients" Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: [Client 13] POST / HTTP/1.1 Май 10 17:02:44 endless cupsd[566]: cupsdSetBusyState: newbusy="Active clients", busy="Not busy" Май 10 17:02:44 endless cupsd[566]: [Client 13] No authentication data provided. Май 10 17:02:44 endless cupsd[566]: [Client 13] 2.0 CUPS-Get-Printers 4 Май 10 17:02:44 endless cupsd[566]: CUPS-Get-Printers Май 10 17:02:44 endless cupsd[566]: CUPS-Get-Printers client-error-not-found: No destinations added. Май 10 17:02:44 endless cupsd[566]: [Client 13] Returning IPP client-error-not-found for CUPS-Get-Printers (no URI) from localhost Май 10 17:02:44 endless cupsd[566]: [Client 13] Content-Length: 113 Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: [Client 13] cupsdWriteClient error=0, used=0, state=HTTP_STATE_POST_SEND, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=113, response=0x55fb83cfd1a0(IPP_IDLE), pipe_pid=0, file=-1 Май 10 17:02:44 endless cupsd[566]: [Client 13] Writing IPP response, ipp_state=DATA, old wused=0, new wused=0 Май 10 17:02:44 endless cupsd[566]: [Client 13] bytes=0, http_state=0, data_remaining=0 Май 10 17:02:44 endless cupsd[566]: [Client 13] Waiting for request. Май 10 17:02:44 endless cupsd[566]: cupsdSetBusyState: newbusy="Not busy", busy="Active clients" Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: [Client 13] POST / HTTP/1.1 Май 10 17:02:44 endless cupsd[566]: cupsdSetBusyState: newbusy="Active clients", busy="Not busy" Май 10 17:02:44 endless cupsd[566]: [Client 13] No authentication data provided. Май 10 17:02:44 endless cupsd[566]: [Client 13] 2.0 CUPS-Get-Printers 5 Май 10 17:02:44 endless cupsd[566]: CUPS-Get-Printers Май 10 17:02:44 endless cupsd[566]: CUPS-Get-Printers client-error-not-found: No destinations added. Май 10 17:02:44 endless cupsd[566]: [Client 13] Returning IPP client-error-not-found for CUPS-Get-Printers (no URI) from localhost Май 10 17:02:44 endless cupsd[566]: [Client 13] Content-Length: 113 Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: [Client 13] cupsdWriteClient error=0, used=0, state=HTTP_STATE_POST_SEND, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=113, response=0x55fb83cfd1a0(IPP_IDLE), pipe_pid=0, file=-1 Май 10 17:02:44 endless cupsd[566]: [Client 13] Writing IPP response, ipp_state=DATA, old wused=0, new wused=0 Май 10 17:02:44 endless cupsd[566]: [Client 13] bytes=0, http_state=0, data_remaining=0 Май 10 17:02:44 endless cupsd[566]: [Client 13] Waiting for request. Май 10 17:02:44 endless cupsd[566]: cupsdSetBusyState: newbusy="Not busy", busy="Active clients" Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: [Client 13] POST / HTTP/1.1 Май 10 17:02:44 endless cupsd[566]: cupsdSetBusyState: newbusy="Active clients", busy="Not busy" Май 10 17:02:44 endless cupsd[566]: [Client 13] No authentication data provided. Май 10 17:02:44 endless cupsd[566]: [Client 13] 2.0 Get-Jobs 6 Май 10 17:02:44 endless cupsd[566]: Get-Jobs ipp://localhost/ Май 10 17:02:44 endless cupsd[566]: [Client 13] Returning IPP successful-ok for Get-Jobs (ipp://localhost/) from localhost Май 10 17:02:44 endless cupsd[566]: [Client 13] Content-Length: 72 Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: [Client 13] cupsdWriteClient error=0, used=0, state=HTTP_STATE_POST_SEND, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=72, response=0x55fb83cfd1a0(IPP_IDLE), pipe_pid=0, file=-1 Май 10 17:02:44 endless cupsd[566]: [Client 13] Writing IPP response, ipp_state=DATA, old wused=0, new wused=0 Май 10 17:02:44 endless cupsd[566]: [Client 13] bytes=0, http_state=0, data_remaining=0 Май 10 17:02:44 endless cupsd[566]: [Client 13] Waiting for request. Май 10 17:02:44 endless cupsd[566]: cupsdSetBusyState: newbusy="Not busy", busy="Active clients" Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown. Май 10 17:02:44 endless cupsd[566]: [Client 13] HTTP_STATE_WAITING Closing on EOF Май 10 17:02:44 endless cupsd[566]: [Client 13] Closing connection. Май 10 17:02:44 endless cupsd[566]: cupsdSetBusyState: newbusy="Not busy", busy="Not busy" Май 10 17:02:44 endless cupsd[566]: cupsd is not idle any more, canceling shutdown.