===================== = EndlessOS version = ===================== NAME="Endless" VERSION="3.8.1" ID="endless" ID_LIKE="ubuntu debian" PRETTY_NAME="Endless 3.8.1" VERSION_ID="3.8.1" HOME_URL="http://www.endlessm.com/" BUILD_ID="200518-152214" ========== = Kernel = ========== Linux endless 5.4.0-19-generic #23+dev177.1a56fd1beos3.8.2 SMP Tue May 5 22:42:53 UTC 2020 x86_64 GNU/Linux cmdline: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-94c993d319cdf01ff15a7624dd6855cc9ebe14d7b40f3077a1e965a0de360d8e/vmlinuz-5.4.0-19-generic root=UUID=05c7cd5b-40f9-47d7-a032-e98150535435 rw splash plymouth.ignore-serial-consoles quiet loglevel=2 ostree=/ostree/boot.1/eos/94c993d319cdf01ff15a7624dd6855cc9ebe14d7b40f3077a1e965a0de360d8e/0 Module Size Used by rfcomm 81920 2 ccm 20480 9 intel_rapl_msr 20480 0 intel_rapl_common 24576 1 intel_rapl_msr x86_pkg_temp_thermal 20480 0 intel_powerclamp 20480 0 coretemp 20480 0 kvm_intel 262144 0 kvm 659456 1 kvm_intel crct10dif_pclmul 16384 1 ghash_clmulni_intel 16384 0 aesni_intel 372736 6 crypto_simd 16384 1 aesni_intel cryptd 24576 2 crypto_simd,ghash_clmulni_intel glue_helper 16384 1 aesni_intel intel_cstate 20480 0 snd_hda_codec_hdmi 61440 1 intel_rapl_perf 20480 0 snd_hda_codec_realtek 122880 1 snd_hda_codec_generic 81920 1 snd_hda_codec_realtek ledtrig_audio 16384 2 snd_hda_codec_generic,snd_hda_codec_realtek snd_hda_intel 53248 3 snd_intel_nhlt 20480 1 snd_hda_intel snd_hda_codec 131072 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek ath10k_pci 49152 0 ath10k_core 471040 1 ath10k_pci uvcvideo 98304 0 ath 36864 1 ath10k_core mac80211 839680 1 ath10k_core snd_hda_core 90112 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_hwdep 20480 1 snd_hda_codec snd_pcm 102400 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core snd_timer 36864 1 snd_pcm r8169 90112 0 cfg80211 704512 3 ath,mac80211,ath10k_core snd 86016 14 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm videobuf2_vmalloc 20480 1 uvcvideo videobuf2_memops 20480 1 videobuf2_vmalloc videobuf2_v4l2 24576 1 uvcvideo videobuf2_common 53248 2 videobuf2_v4l2,uvcvideo videodev 221184 3 videobuf2_v4l2,uvcvideo,videobuf2_common cmac 16384 2 bnep 24576 2 btusb 57344 0 btrtl 20480 1 btusb joydev 24576 0 hid_multitouch 28672 0 hid_generic 16384 0 mc 53248 4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common intel_lpss_pci 20480 0 intel_lpss 16384 1 intel_lpss_pci idma64 20480 0 btbcm 16384 1 btusb btintel 24576 1 btusb bluetooth 577536 31 btrtl,btintel,btbcm,bnep,btusb,rfcomm mei_hdcp 24576 0 zram 32768 1 acer_wmi 24576 0 input_leds 16384 0 sparse_keymap 16384 1 acer_wmi rtsx_pci_ms 24576 0 mei_me 40960 1 intel_wmi_thunderbolt 20480 0 ecdh_generic 16384 2 bluetooth mei 106496 3 mei_hdcp,mei_me memstick 20480 1 rtsx_pci_ms virt_dma 20480 1 idma64 soundcore 16384 1 snd libarc4 16384 1 mac80211 ecc 32768 1 ecdh_generic realtek 24576 1 intel_xhci_usb_role_switch 16384 0 wmi_bmof 16384 0 roles 16384 1 intel_xhci_usb_role_switch bfq 69632 9 acpi_pad 184320 0 acer_wireless 20480 0 mac_hid 16384 0 binfmt_misc 24576 1 ip_tables 28672 0 x_tables 40960 1 ip_tables rtsx_pci_sdmmc 28672 0 i915 1978368 18 crc32_pclmul 16384 0 serio_raw 20480 0 rtsx_pci 69632 2 rtsx_pci_sdmmc,rtsx_pci_ms ahci 40960 1 libahci 32768 1 ahci i2c_hid 28672 0 i2c_algo_bit 16384 1 i915 hid 131072 3 i2c_hid,hid_multitouch,hid_generic wmi 32768 3 intel_wmi_thunderbolt,acer_wmi,wmi_bmof video 49152 2 acer_wmi,i915 vmwgfx 299008 0 drm_kms_helper 184320 2 vmwgfx,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 ttm 102400 1 vmwgfx drm 487424 10 vmwgfx,drm_kms_helper,i915,ttm =================== = EndlessOS image = =================== eosoem-eos3.3-amd64-nexthw.180410-084859.sea ========== = Uptime = ========== 14:16:41 up 30 min, 1 user, load average: 0,57, 0,77, 1,26 ================= = OSTree status = ================= * eos 17d99c0a4107b0fe05569ee5906fe30b2c672e8457de8de4a1db729d7af290dd.0 Version: 3.8.1 origin refspec: eos:os/eos/amd64/eos3a GPG: Signature made seg 18 mai 2020 14:22:16 -03 using RSA key ID 9E08D8DABA02FC46 GPG: Good signature from "EOS OSTree Signing Key 1 " GPG: Key expires sáb 30 jun 2029 13:18:11 -03 GPG: Signature made seg 18 mai 2020 14:22:19 -03 using RSA key ID FCF17B17F1F8E157 GPG: Good signature from "EOS Flatpak Signing Key 1 " GPG: Key expires ter 09 jun 2026 14:47:38 -03 eos 51610f7af0cc1d2e0880024e634d00883a0f61bbdf00656f384aa7fb647f5789.0 (rollback) Version: 3.8.0 origin refspec: eos:os/eos/amd64/eos3a GPG: Signature made seg 27 abr 2020 15:01:55 -03 using RSA key ID 9E08D8DABA02FC46 GPG: Good signature from "EOS OSTree Signing Key 1 " GPG: Key expires sáb 30 jun 2029 13:18:11 -03 GPG: Signature made seg 27 abr 2020 15:01:57 -03 using RSA key ID FCF17B17F1F8E157 GPG: Good signature from "EOS Flatpak Signing Key 1 " GPG: Key expires ter 09 jun 2026 14:47:38 -03 =============== = OSTree refs = =============== deploy/app/au.edu.uq.esys.escript/x86_64/stable deploy/app/br.gov.cti.invesalius/x86_64/stable deploy/app/ca._0ldsk00l.Nestopia/x86_64/stable deploy/app/cc.arduino.arduinoide/x86_64/stable deploy/app/ch.openboard.OpenBoard/x86_64/stable deploy/app/chat.rocket.RocketChat/x86_64/stable deploy/app/com.adobe.Flash-Player-Projector/x86_64/stable deploy/app/com.airtame.Client/x86_64/stable deploy/app/com.albiononline.AlbionOnline/x86_64/stable deploy/app/com.alientrap.nexuiz-classic/x86_64/stable deploy/app/com.anydesk.Anydesk/x86_64/stable deploy/app/com.beakerbrowser.Beaker/x86_64/stable deploy/app/com.bitwarden.desktop/x86_64/stable deploy/app/com.bladecoder.adventure-editor/x86_64/stable deploy/app/com.bluejeans.BlueJeans/x86_64/stable deploy/app/com.brosix.Brosix/x86_64/stable deploy/app/com.chez.GrafX2/x86_64/stable deploy/app/com.dhsdevelopments.Climaxima/x86_64/stable deploy/app/com.discordapp.Discord/x86_64/stable deploy/app/com.dosbox.DOSBox/x86_64/stable deploy/app/com.dropbox.Client/x86_64/stable deploy/app/com.eduke32.EDuke32/x86_64/stable deploy/app/com.endlessm.EknServicesMultiplexer/x86_64/stable deploy/app/com.endlessm.HatchPreviewer/x86_64/stable deploy/app/com.endlessm.animals.pt/x86_64/eos3 deploy/app/com.endlessm.astronomy.pt/x86_64/eos3 deploy/app/com.endlessm.bibliotecas_embrapa.pt_BR/x86_64/eos3 deploy/app/com.endlessm.biology.pt/x86_64/eos3 deploy/app/com.endlessm.celebrities.pt/x86_64/eos3 deploy/app/com.endlessm.dinosaurs.pt/x86_64/eos3 deploy/app/com.endlessm.encyclopedia.pt/x86_64/eos3 deploy/app/com.endlessm.extra.pt_BR/x86_64/eos3 deploy/app/com.endlessm.farming.pt/x86_64/eos3 deploy/app/com.endlessm.finance/x86_64/eos3 deploy/app/com.endlessm.geography.pt/x86_64/eos3 deploy/app/com.endlessm.history.pt/x86_64/eos3 deploy/app/com.endlessm.library.pt/x86_64/eos3 deploy/app/com.endlessm.math.pt/x86_64/eos3 deploy/app/com.endlessm.myths.pt/x86_64/eos3 deploy/app/com.endlessm.physics.pt/x86_64/eos3 deploy/app/com.endlessm.programming/x86_64/eos3 deploy/app/com.endlessm.quote_of_the_day.en/x86_64/eos3 deploy/app/com.endlessm.socialsciences.pt/x86_64/eos3 deploy/app/com.endlessm.translation/x86_64/eos3 deploy/app/com.endlessm.ubongo_kids_demo/x86_64/eos3 deploy/app/com.endlessm.video_animations/x86_64/eos3 deploy/app/com.endlessm.word_of_the_day.en/x86_64/eos3 deploy/app/com.endlessm.your_health.pt_BR/x86_64/eos3 deploy/app/com.endlessnetwork.MidnightmareTeddy/x86_64/stable deploy/app/com.endlessnetwork.aqueducts/x86_64/stable deploy/app/com.endlessnetwork.arduinoprojects/x86_64/eos3 deploy/app/com.endlessnetwork.blendertutorials/x86_64/eos3 deploy/app/com.endlessnetwork.csstutorials/x86_64/eos3 deploy/app/com.endlessnetwork.dragonsapprentice/x86_64/stable deploy/app/com.endlessnetwork.fablemaker/x86_64/stable deploy/app/com.endlessnetwork.frogsquash/x86_64/stable deploy/app/com.endlessnetwork.guitartutorials/x86_64/eos3 deploy/app/com.endlessnetwork.htmltutorials/x86_64/eos3 deploy/app/com.endlessnetwork.missilemath/x86_64/stable deploy/app/com.endlessnetwork.passage/x86_64/stable deploy/app/com.endlessnetwork.raspberrypiprojects/x86_64/eos3 deploy/app/com.endlessnetwork.sciencesnacks/x86_64/eos3 deploy/app/com.endlessnetwork.shortfilms/x86_64/eos3 deploy/app/com.endlessnetwork.tankwarriors/x86_64/stable deploy/app/com.endlessnetwork.videogamestutorials/x86_64/eos3 deploy/app/com.endlessnetwork.whitehouse/x86_64/stable deploy/app/com.flashforge.FlashPrint/x86_64/stable deploy/app/com.getferdi.Ferdi/x86_64/stable deploy/app/com.getpostman.Postman/x86_64/stable deploy/app/com.github.IsmaelMartinez.teams_for_linux/x86_64/stable deploy/app/com.github.JannikHv.Gydl/x86_64/stable deploy/app/com.github.Johnn3y.Forklift/x86_64/stable deploy/app/com.github.PintaProject.Pinta/x86_64/stable deploy/app/com.github.alecaddd.sequeler/x86_64/stable deploy/app/com.github.artemanufrij.graphui/x86_64/stable deploy/app/com.github.artemanufrij.playmyvideos/x86_64/stable deploy/app/com.github.bcedu.valasimplehttpserver/x86_64/stable deploy/app/com.github.bvschaik.julius/x86_64/stable deploy/app/com.github.coslyk.MoonPlayer/x86_64/stable deploy/app/com.github.dariasteam.cowsrevenge/x86_64/stable deploy/app/com.github.geigi.cozy/x86_64/stable deploy/app/com.github.hopsan.Hopsan/x86_64/stable deploy/app/com.github.lainsce.coin/x86_64/stable deploy/app/com.github.lainsce.notejot/x86_64/stable deploy/app/com.github.matfantinel.moneta/x86_64/stable deploy/app/com.github.mdh34.hackup/x86_64/stable deploy/app/com.github.micahflee.torbrowser-launcher/x86_64/stable deploy/app/com.github.muriloventuroso.easyssh/x86_64/stable deploy/app/com.github.paolostivanin.OTPClient/x86_64/stable deploy/app/com.github.philip_scott.spice-up/x86_64/stable deploy/app/com.github.quaternion/x86_64/stable deploy/app/com.github.robertsanseries.ciano/x86_64/stable deploy/app/com.github.rssguard/x86_64/stable deploy/app/com.github.tchx84.Flatseal/x86_64/stable deploy/app/com.github.unrud.VideoDownloader/x86_64/stable deploy/app/com.github.wwmm.pulseeffects/x86_64/stable deploy/app/com.github.z.Cumulonimbus/x86_64/stable deploy/app/com.gitlab.azymohliad.Qwertone/x86_64/stable deploy/app/com.gitlab.bitseater.meteo/x86_64/stable deploy/app/com.google.AndroidStudio/x86_64/stable deploy/app/com.google.Chrome/x86_64/eos3 deploy/app/com.grangerhub.Tremulous/x86_64/stable deploy/app/com.hack_computer.Clubhouse/x86_64/eos3 deploy/app/com.hack_computer.OperatingSystemApp/x86_64/eos3 deploy/app/com.hack_computer.ProjectLibrary/x86_64/eos3 deploy/app/com.hack_computer.Sidetrack/x86_64/eos3 deploy/app/com.inform7.IDE/x86_64/stable deploy/app/com.jagex.RuneScape/x86_64/stable deploy/app/com.jetbrains.DataGrip/x86_64/stable deploy/app/com.jetbrains.IntelliJ-IDEA-Community/x86_64/stable deploy/app/com.jetbrains.IntelliJ-IDEA-Ultimate/x86_64/stable deploy/app/com.jetbrains.PhpStorm/x86_64/stable deploy/app/com.jetbrains.PyCharm-Community/x86_64/stable deploy/app/com.jetbrains.PyCharm-Professional/x86_64/stable deploy/app/com.jetbrains.Rider/x86_64/stable deploy/app/com.jetbrains.WebStorm/x86_64/stable deploy/app/com.jgraph.drawio.desktop/x86_64/stable deploy/app/com.jvieira.tpt.Metronome/x86_64/stable deploy/app/com.katawa_shoujo.KatawaShoujo/x86_64/stable deploy/app/com.mattermost.Desktop/x86_64/stable deploy/app/com.microsoft.Teams/x86_64/stable deploy/app/com.moddb.TotalChaos/x86_64/stable deploy/app/com.mojang.Minecraft/x86_64/stable deploy/app/com.moonlight_stream.Moonlight/x86_64/stable deploy/app/com.notepadqq.Notepadqq/x86_64/stable deploy/app/com.obsproject.Studio/x86_64/stable deploy/app/com.ozmartians.VidCutter/x86_64/stable deploy/app/com.play0ad.zeroad/x86_64/stable deploy/app/com.prusa3d.PrusaSlicer/x86_64/stable deploy/app/com.rawtherapee.RawTherapee/x86_64/stable deploy/app/com.realm667.WolfenDoom_Blade_of_Agony/x86_64/stable deploy/app/com.retrodev.blastem/x86_64/stable deploy/app/com.scoutshonour.Digital/x86_64/stable deploy/app/com.scoutshonour.dtipbijays/i386/stable deploy/app/com.shatteredpixel.shatteredpixeldungeon/x86_64/stable deploy/app/com.sigmyne.crush/x86_64/stable deploy/app/com.skype.Client/x86_64/stable deploy/app/com.snes9x.Snes9x/x86_64/stable deploy/app/com.spotify.Client/x86_64/stable deploy/app/com.sublimemerge.App/x86_64/stable deploy/app/com.sublimetext.three/x86_64/stable deploy/app/com.sweethome3d.Sweethome3d/x86_64/stable deploy/app/com.syntevo.SmartGit/x86_64/stable deploy/app/com.tux4kids.tuxmath/x86_64/stable deploy/app/com.unity.UnityHub/x86_64/stable deploy/app/com.valvesoftware.Steam/x86_64/stable deploy/app/com.viber.Viber/x86_64/stable deploy/app/com.viewizard.AstroMenace/x86_64/stable deploy/app/com.visualstudio.code.oss/x86_64/stable deploy/app/com.visualstudio.code/x86_64/stable deploy/app/com.wire.WireDesktop/x86_64/stable deploy/app/com.wps.Office/x86_64/stable deploy/app/de.billardgl.Billardgl/x86_64/stable deploy/app/de.create3000.titania/x86_64/stable deploy/app/de.haeckerfelix.Fragments/x86_64/stable deploy/app/de.haeckerfelix.gradio/x86_64/stable deploy/app/de.rwth_aachen.ient.RDPlot/x86_64/stable deploy/app/de.willuhn.Jameica/x86_64/stable deploy/app/edu.mit.Scratch/x86_64/stable deploy/app/eu.planete_kraus.Tarot/x86_64/stable deploy/app/fr.free.Homebank/x86_64/stable deploy/app/fr.natron.Natron/x86_64/stable deploy/app/im.pidgin.Pidgin/x86_64/stable deploy/app/info.bibletime.BibleTime/x86_64/stable deploy/app/info.colobot.Colobot/x86_64/stable deploy/app/io.atom.Atom/x86_64/stable deploy/app/io.brackets.Brackets/x86_64/stable deploy/app/io.dbeaver.DBeaverCommunity/x86_64/stable deploy/app/io.designer.GravitDesigner/x86_64/stable deploy/app/io.exodus.Exodus/x86_64/stable deploy/app/io.freetubeapp.FreeTube/x86_64/stable deploy/app/io.github.OpenToonz/x86_64/stable deploy/app/io.github.RodZill4.Material-Maker/x86_64/stable deploy/app/io.github.endless_sky.endless_sky/x86_64/stable deploy/app/io.github.freedoom.FreeDM/x86_64/stable deploy/app/io.github.gillesdegottex.FMIT/x86_64/stable deploy/app/io.github.guillaumechereau.Goxel/x86_64/stable deploy/app/io.github.hakuneko.HakuNeko/x86_64/stable deploy/app/io.github.jliljebl.Flowblade/x86_64/stable deploy/app/io.github.markummitchell.Engauge_Digitizer/x86_64/stable deploy/app/io.github.maurycyliebner.enve/x86_64/stable deploy/app/io.github.mki1967.mki3dgame/x86_64/stable deploy/app/io.github.rinigus.PureMaps/x86_64/stable deploy/app/io.github.sharkwouter.Minigalaxy/x86_64/stable deploy/app/io.github.technic.e2designer/x86_64/stable deploy/app/io.github.wereturtle.ghostwriter/x86_64/stable deploy/app/io.gitlab.o20.word/x86_64/stable deploy/app/io.gitlab.osslugaru.Lugaru/x86_64/stable deploy/app/io.lbry.lbry-app/x86_64/stable deploy/app/io.lmms.LMMS/x86_64/stable deploy/app/io.webtorrent.WebTorrent/x86_64/stable deploy/app/jp.yvt.OpenSpades/x86_64/stable deploy/app/net.ankiweb.Anki/x86_64/stable deploy/app/net.bartkessels.getit/x86_64/stable deploy/app/net.blockout.BlockOutII/x86_64/stable deploy/app/net.codeindustry.MasterPDFEditor/x86_64/stable deploy/app/net.dengine.Doomsday/x86_64/stable deploy/app/net.gwyddion.Gwyddion/x86_64/stable deploy/app/net.mancubus.SLADE/x86_64/stable deploy/app/net.mediaarea.MediaInfo/x86_64/stable deploy/app/net.meijn.onvifviewer/x86_64/stable deploy/app/net.minetest.Minetest/x86_64/stable deploy/app/net.openra.OpenRA/x86_64/stable deploy/app/net.oz9aec.Gpredict/x86_64/stable deploy/app/net.pcsx2.PCSX2/i386/stable deploy/app/net.pioneerspacesim.Pioneer/x86_64/stable deploy/app/net.purrdata.PurrData/x86_64/stable deploy/app/net.redeclipse.RedEclipse/x86_64/stable deploy/app/net.runelite.RuneLite/x86_64/stable deploy/app/net.scribus.Scribus/x86_64/stable deploy/app/net.sf.nootka/x86_64/stable deploy/app/net.sourceforge.Chessx/x86_64/stable deploy/app/net.sourceforge.ExtremeTuxRacer/x86_64/stable deploy/app/net.sourceforge.TuxFootball/x86_64/stable deploy/app/net.sourceforge.VMPK/x86_64/stable deploy/app/net.sourceforge.chromium-bsu/x86_64/stable deploy/app/net.sourceforge.fretsonfire/x86_64/stable deploy/app/net.sourceforge.projectM/x86_64/stable deploy/app/net.sourceforge.qtpfsgui.LuminanceHDR/x86_64/stable deploy/app/net.sourceforge.torcs/x86_64/stable deploy/app/net.supertuxkart.SuperTuxKart/x86_64/stable deploy/app/net.veloren.veloren/x86_64/stable deploy/app/net.wz2100.wz2100/x86_64/stable deploy/app/nl.g4d.Girens/x86_64/stable deploy/app/nl.openoffice.bluefish/x86_64/stable deploy/app/org.DolphinEmu.dolphin-emu/x86_64/stable deploy/app/org.apache.netbeans/x86_64/stable deploy/app/org.atheme.audacious/x86_64/stable deploy/app/org.audacityteam.Audacity/x86_64/stable deploy/app/org.bitcoincore.bitcoin-qt/x86_64/stable deploy/app/org.blender.Blender/x86_64/stable deploy/app/org.bluej.BlueJ/x86_64/stable deploy/app/org.bunkus.mkvtoolnix-gui/x86_64/stable deploy/app/org.bzflag.BZFlag/x86_64/stable deploy/app/org.codeblocks.codeblocks/x86_64/stable deploy/app/org.cvfosammmm.Porto/x86_64/stable deploy/app/org.darktable.Darktable/x86_64/stable deploy/app/org.eclipse.Committers/x86_64/stable deploy/app/org.eclipse.Java/x86_64/stable deploy/app/org.eclipse.iot.fourdiac.Ide/x86_64/stable deploy/app/org.entangle_photo.Manager/x86_64/stable deploy/app/org.fedoraproject.MediaWriter/x86_64/stable deploy/app/org.filezillaproject.Filezilla/x86_64/stable deploy/app/org.flarerpg.Flare/x86_64/stable deploy/app/org.flatpak.qtdemo/x86_64/stable deploy/app/org.flightgear.FlightGear/x86_64/stable deploy/app/org.fontforge.FontForge/x86_64/stable deploy/app/org.free_astro.siril/x86_64/stable deploy/app/org.freecadweb.FreeCAD/x86_64/stable deploy/app/org.freecol.FreeCol/x86_64/stable deploy/app/org.freedesktop.Bustle/x86_64/stable deploy/app/org.freedesktop.GstDebugViewer/x86_64/stable deploy/app/org.freefilesync.FreeFileSync/x86_64/stable deploy/app/org.fritzing.Fritzing/x86_64/stable deploy/app/org.gabmus.whatip/x86_64/stable deploy/app/org.geany.Geany/x86_64/stable deploy/app/org.geeqie.Geeqie/x86_64/stable deploy/app/org.geogebra.GeoGebra/x86_64/stable deploy/app/org.gimp.GIMP/x86_64/stable deploy/app/org.glimpse_editor.Glimpse/x86_64/stable deploy/app/org.gnode.NixView/x86_64/stable deploy/app/org.gnome.Books/x86_64/stable deploy/app/org.gnome.Boxes/x86_64/stable deploy/app/org.gnome.Builder/x86_64/stable deploy/app/org.gnome.Calendar/x86_64/stable deploy/app/org.gnome.Cheese/x86_64/stable deploy/app/org.gnome.Chess/x86_64/stable deploy/app/org.gnome.Devhelp/x86_64/stable deploy/app/org.gnome.Dictionary/x86_64/stable deploy/app/org.gnome.Eolie/x86_64/stable deploy/app/org.gnome.Epiphany/x86_64/stable deploy/app/org.gnome.Fractal/x86_64/stable deploy/app/org.gnome.GHex/x86_64/stable deploy/app/org.gnome.Genius/x86_64/stable deploy/app/org.gnome.Glade/x86_64/stable deploy/app/org.gnome.HexGL/x86_64/stable deploy/app/org.gnome.Lollypop/x86_64/stable deploy/app/org.gnome.Maps/x86_64/stable deploy/app/org.gnome.Nibbles/x86_64/stable deploy/app/org.gnome.Quadrapassel/x86_64/stable deploy/app/org.gnome.Reversi/x86_64/stable deploy/app/org.gnome.SoundRecorder/x86_64/stable deploy/app/org.gnome.Tetravex/x86_64/stable deploy/app/org.gnome.TwentyFortyEight/x86_64/stable deploy/app/org.gnome.dfeet/x86_64/stable deploy/app/org.gnome.gbrainy/x86_64/stable deploy/app/org.gnome.gitg/x86_64/stable deploy/app/org.gnome.gitlab.Cowsay/x86_64/stable deploy/app/org.gnome.glabels-3/x86_64/stable deploy/app/org.gnome.meld/x86_64/stable deploy/app/org.gnucash.GnuCash/x86_64/stable deploy/app/org.godotengine.Godot/x86_64/stable deploy/app/org.gottcode.Kapow/x86_64/stable deploy/app/org.horizon_eda.HorizonEDA/x86_64/stable deploy/app/org.hydrogenmusic.Hydrogen/x86_64/stable deploy/app/org.inkscape.Inkscape/x86_64/stable deploy/app/org.jamovi.jamovi/x86_64/stable deploy/app/org.jdownloader.JDownloader/x86_64/stable deploy/app/org.kde.dolphin/x86_64/stable deploy/app/org.kde.kalzium/x86_64/stable deploy/app/org.kde.katomic/x86_64/stable deploy/app/org.kde.kbruch/x86_64/stable deploy/app/org.kde.kdenlive/x86_64/stable deploy/app/org.kde.kgeography/x86_64/stable deploy/app/org.kde.khangman/x86_64/stable deploy/app/org.kde.knavalbattle/x86_64/stable deploy/app/org.kde.knetwalk/x86_64/stable deploy/app/org.kde.kolourpaint/x86_64/stable deploy/app/org.kde.kpat/x86_64/stable deploy/app/org.kde.krita/x86_64/stable deploy/app/org.kde.ksudoku/x86_64/stable deploy/app/org.kde.ktouch/x86_64/stable deploy/app/org.kde.kubrick/x86_64/stable deploy/app/org.kde.kxstitch/x86_64/stable deploy/app/org.kde.okular/x86_64/stable deploy/app/org.kde.palapeli/x86_64/stable deploy/app/org.kde.skrooge/x86_64/stable deploy/app/org.kicad_pcb.KiCad/x86_64/stable deploy/app/org.kiwix.desktop/x86_64/stable deploy/app/org.laptop.TurtleArtActivity/x86_64/stable deploy/app/org.learningequality.Kolibri/x86_64/stable deploy/app/org.leocad.LeoCAD/x86_64/stable deploy/app/org.libreoffice.LibreOffice/x86_64/stable deploy/app/org.librepcb.LibrePCB/x86_64/stable deploy/app/org.libretro.RetroArch/x86_64/stable deploy/app/org.linux_hardware.hw-probe/x86_64/stable deploy/app/org.midori_browser.Midori/x86_64/stable deploy/app/org.mixxx.Mixxx/x86_64/stable deploy/app/org.mobsya.ThymioSuite/x86_64/stable deploy/app/org.mozilla.Firefox/x86_64/eos3 deploy/app/org.musescore.MuseScore/x86_64/stable deploy/app/org.musesequencer.Muse3/x86_64/stable deploy/app/org.mypaint.MyPaint/x86_64/stable deploy/app/org.nextcloud.Nextcloud/x86_64/stable deploy/app/org.octave.Octave/x86_64/stable deploy/app/org.olivevideoeditor.Olive/x86_64/stable deploy/app/org.onlyoffice.desktopeditors/x86_64/stable deploy/app/org.openmw.OpenMW/x86_64/stable deploy/app/org.openscad.OpenSCAD/x86_64/stable deploy/app/org.openshot.OpenShot/x86_64/stable deploy/app/org.openstreetmap.josm/x86_64/stable deploy/app/org.opensurge2d.OpenSurge/x86_64/stable deploy/app/org.openttd.OpenTTD/x86_64/stable deploy/app/org.pegasus_frontend.Pegasus/x86_64/stable deploy/app/org.phoenicis.playonlinux/x86_64/stable deploy/app/org.pitivi.Pitivi/x86_64/stable deploy/app/org.pjbroad.EternallandsClient/x86_64/stable deploy/app/org.ppsspp.PPSSPP/x86_64/stable deploy/app/org.pulseaudio.pavucontrol/x86_64/stable deploy/app/org.pyzo.pyzo/x86_64/stable deploy/app/org.qbittorrent.qBittorrent/x86_64/stable deploy/app/org.qgis.qgis/x86_64/stable deploy/app/org.qutebrowser.qutebrowser/x86_64/stable deploy/app/org.remmina.Remmina/x86_64/stable deploy/app/org.robocode.Robocode/x86_64/stable deploy/app/org.sauerbraten.Sauerbraten/x86_64/stable deploy/app/org.shadered.SHADERed/x86_64/stable deploy/app/org.shotcut.Shotcut/x86_64/stable deploy/app/org.signal.Signal/x86_64/stable deploy/app/org.snap4arduino.App/x86_64/eos3 deploy/app/org.speed_dreams.SpeedDreams/x86_64/stable deploy/app/org.speedcrunch.SpeedCrunch/x86_64/stable deploy/app/org.squeakland.Etoys/x86_64/stable deploy/app/org.srb2.SRB2/x86_64/stable deploy/app/org.srb2.SRB2Kart/x86_64/stable deploy/app/org.stellarium.Stellarium/x86_64/stable deploy/app/org.subsurface_divelog.Subsurface/x86_64/stable deploy/app/org.sugarlabs.AbacusActivity/x86_64/stable deploy/app/org.sugarlabs.FotoToon/x86_64/stable deploy/app/org.sugarlabs.FractionBounce/x86_64/stable deploy/app/org.sugarlabs.Measure/x86_64/stable deploy/app/org.sugarlabs.MusicKeyboard/x86_64/stable deploy/app/org.sugarlabs.Physics/x86_64/stable deploy/app/org.sugarlabs.Pippy/x86_64/stable deploy/app/org.sugarlabs.Sliderule/x86_64/stable deploy/app/org.sugarlabs.Speak/x86_64/stable deploy/app/org.sugarlabs.StoryActivity/x86_64/stable deploy/app/org.sugarlabs.Words/x86_64/stable deploy/app/org.synfig.SynfigStudio/x86_64/stable deploy/app/org.telegram.desktop/x86_64/stable deploy/app/org.tuxfamily.StuntRally/x86_64/stable deploy/app/org.tuxfamily.XMoto/x86_64/stable deploy/app/org.vergecurrency.verge-qt/x86_64/stable deploy/app/org.videolan.VLC/x86_64/stable deploy/app/org.wesnoth.Wesnoth/x86_64/stable deploy/app/org.widelands.Widelands/x86_64/stable deploy/app/org.wireshark.Wireshark/x86_64/stable deploy/app/org.xonotic.Xonotic/x86_64/stable deploy/app/org.zdoom.GZDoom/x86_64/stable deploy/app/re.sonny.Tangram/x86_64/stable deploy/app/space.fips.Fips/x86_64/stable deploy/app/tv.kodi.Kodi/x86_64/stable deploy/app/uk.jnthn.backgammony/x86_64/stable deploy/app/us.zoom.Zoom/x86_64/stable deploy/app/website.i2pd.i2pd/x86_64/stable deploy/app/ws.openarena.OpenArena/x86_64/stable deploy/app/xyz.z3ntu.razergenie/x86_64/stable deploy/runtime/com.adobe.Flash_Player_Projector.Locale/x86_64/stable deploy/runtime/com.airtame.Client.Locale/x86_64/stable deploy/runtime/com.endlessm.Platform/x86_64/eos3.2 deploy/runtime/com.endlessm.animals.pt.Content/x86_64/eos3 deploy/runtime/com.endlessm.apps.Platform.Locale/x86_64/1 deploy/runtime/com.endlessm.apps.Platform.Locale/x86_64/3 deploy/runtime/com.endlessm.apps.Platform.Locale/x86_64/5 deploy/runtime/com.endlessm.apps.Platform/x86_64/5 deploy/runtime/com.endlessm.astronomy.pt.Content/x86_64/eos3 deploy/runtime/com.endlessm.biology.pt.Content/x86_64/eos3 deploy/runtime/com.endlessm.celebrities.pt.Content/x86_64/eos3 deploy/runtime/com.endlessm.encyclopedia.pt.Content/x86_64/eos3 deploy/runtime/com.endlessm.extra.pt_BR.Content/x86_64/eos3 deploy/runtime/com.endlessm.farming.pt.Content/x86_64/eos3 deploy/runtime/com.endlessm.geography.pt.Content/x86_64/eos3 deploy/runtime/com.endlessm.history.pt.Content/x86_64/eos3 deploy/runtime/com.endlessm.library.pt.Content/x86_64/eos3 deploy/runtime/com.endlessm.math.pt.Content/x86_64/eos3 deploy/runtime/com.endlessm.myths.pt.Content/x86_64/eos3 deploy/runtime/com.endlessm.physics.pt.Content/x86_64/eos3 deploy/runtime/com.endlessm.programming.Locale/x86_64/eos3 deploy/runtime/com.endlessm.quote_of_the_day.en.Content/x86_64/eos3 deploy/runtime/com.endlessm.socialsciences.pt.Content/x86_64/eos3 deploy/runtime/com.endlessm.translation.Locale/x86_64/eos3 deploy/runtime/com.endlessm.ubongo_kids_demo.Content/x86_64/eos3 deploy/runtime/com.endlessm.word_of_the_day.en.Content/x86_64/eos3 deploy/runtime/com.endlessm.your_health.pt_BR.Content/x86_64/eos3 deploy/runtime/com.github.JannikHv.Gydl.Locale/x86_64/stable deploy/runtime/com.github.PintaProject.Pinta.Locale/x86_64/stable deploy/runtime/com.github.alecaddd.sequeler.Locale/x86_64/stable deploy/runtime/com.github.artemanufrij.graphui.Locale/x86_64/stable deploy/runtime/com.github.artemanufrij.playmyvideos.Locale/x86_64/stable deploy/runtime/com.github.bcedu.valasimplehttpserver.Locale/x86_64/stable deploy/runtime/com.github.coslyk.MoonPlayer.Locale/x86_64/stable deploy/runtime/com.github.geigi.cozy.Locale/x86_64/stable deploy/runtime/com.github.lainsce.coin.Locale/x86_64/stable deploy/runtime/com.github.lainsce.notejot.Locale/x86_64/stable deploy/runtime/com.github.matfantinel.moneta.Locale/x86_64/stable deploy/runtime/com.github.mdh34.hackup.Locale/x86_64/stable deploy/runtime/com.github.muriloventuroso.easyssh.Locale/x86_64/stable deploy/runtime/com.github.philip_scott.spice_up.Locale/x86_64/stable deploy/runtime/com.github.robertsanseries.ciano.Locale/x86_64/stable deploy/runtime/com.github.unrud.VideoDownloader.Locale/x86_64/stable deploy/runtime/com.github.wwmm.pulseeffects.Locale/x86_64/stable deploy/runtime/com.gitlab.bitseater.meteo.Locale/x86_64/stable deploy/runtime/com.google.AndroidStudio.Locale/x86_64/stable deploy/runtime/com.hack_computer.Clippy.Extension/x86_64/eos3 deploy/runtime/com.hack_computer.Clubhouse.Locale/x86_64/eos3 deploy/runtime/com.hack_computer.ProjectLibrary.Content/x86_64/eos3 deploy/runtime/com.inform7.IDE.Locale/x86_64/stable deploy/runtime/com.obsproject.Studio.Locale/x86_64/stable deploy/runtime/com.prusa3d.PrusaSlicer.Locale/x86_64/stable deploy/runtime/com.rawtherapee.RawTherapee.Locale/x86_64/stable deploy/runtime/com.snes9x.Snes9x.Locale/x86_64/stable deploy/runtime/com.tux4kids.tuxmath.Locale/x86_64/stable deploy/runtime/de.create3000.titania.Locale/x86_64/stable deploy/runtime/de.haeckerfelix.Fragments.Locale/x86_64/stable deploy/runtime/de.haeckerfelix.gradio.Locale/x86_64/stable deploy/runtime/eu.planete_kraus.Tarot.Locale/x86_64/stable deploy/runtime/fr.free.Homebank.Locale/x86_64/stable deploy/runtime/fr.natron.Natron.Locale/x86_64/stable deploy/runtime/im.pidgin.Pidgin.Locale/x86_64/stable deploy/runtime/info.colobot.Colobot.Locale/x86_64/stable deploy/runtime/io.github.OpenToonz.Locale/x86_64/stable deploy/runtime/io.github.jliljebl.Flowblade.Locale/x86_64/stable deploy/runtime/io.github.maurycyliebner.enve.Locale/x86_64/stable deploy/runtime/io.github.sharkwouter.Minigalaxy.Locale/x86_64/stable deploy/runtime/io.lbry.lbry_app.Locale/x86_64/stable deploy/runtime/net.bartkessels.getit.Locale/x86_64/stable deploy/runtime/net.codeindustry.MasterPDFEditor.Locale/x86_64/stable deploy/runtime/net.gwyddion.Gwyddion.Locale/x86_64/stable deploy/runtime/net.mancubus.SLADE.Locale/x86_64/stable deploy/runtime/net.meijn.onvifviewer.Locale/x86_64/stable deploy/runtime/net.minetest.Minetest.Locale/x86_64/stable deploy/runtime/net.oz9aec.Gpredict.Locale/x86_64/stable deploy/runtime/net.pcsx2.PCSX2.Locale/i386/stable deploy/runtime/net.sourceforge.TuxFootball.Locale/x86_64/stable deploy/runtime/net.sourceforge.chromium_bsu.Locale/x86_64/stable deploy/runtime/net.sourceforge.fretsonfire.Locale/x86_64/stable deploy/runtime/nl.g4d.Girens.Locale/x86_64/stable deploy/runtime/nl.openoffice.bluefish.Locale/x86_64/stable deploy/runtime/org.DolphinEmu.dolphin_emu.Locale/x86_64/stable deploy/runtime/org.atheme.audacious.Locale/x86_64/stable deploy/runtime/org.audacityteam.Audacity.Codecs/x86_64/stable deploy/runtime/org.audacityteam.Audacity.Locale/x86_64/stable deploy/runtime/org.blender.Blender.Codecs/x86_64/stable deploy/runtime/org.bunkus.mkvtoolnix_gui.Locale/x86_64/stable deploy/runtime/org.codeblocks.codeblocks.Locale/x86_64/stable deploy/runtime/org.cvfosammmm.Porto.Locale/x86_64/stable deploy/runtime/org.darktable.Darktable.Locale/x86_64/stable deploy/runtime/org.entangle_photo.Manager.Locale/x86_64/stable deploy/runtime/org.filezillaproject.Filezilla.Locale/x86_64/stable deploy/runtime/org.fontforge.FontForge.Locale/x86_64/stable deploy/runtime/org.free_astro.siril.Locale/x86_64/stable deploy/runtime/org.freedesktop.Platform.Compat.i386/x86_64/18.08 deploy/runtime/org.freedesktop.Platform.Compat.i386/x86_64/19.08 deploy/runtime/org.freedesktop.Platform.GL.default/x86_64/19.08 deploy/runtime/org.freedesktop.Platform.GL32.default/x86_64/19.08 deploy/runtime/org.freedesktop.Platform.Icontheme.EndlessOS/x86_64/1.0 deploy/runtime/org.freedesktop.Platform.Locale/i386/18.08 deploy/runtime/org.freedesktop.Platform.Locale/x86_64/1.6 deploy/runtime/org.freedesktop.Platform.Locale/x86_64/18.08 deploy/runtime/org.freedesktop.Platform.Locale/x86_64/19.08 deploy/runtime/org.freedesktop.Platform.VAAPI.Intel/i386/18.08 deploy/runtime/org.freedesktop.Platform.VAAPI.Intel/x86_64/1.6 deploy/runtime/org.freedesktop.Platform.VAAPI.Intel/x86_64/18.08 deploy/runtime/org.freedesktop.Platform.VAAPI.Intel/x86_64/19.08 deploy/runtime/org.freedesktop.Platform.ffmpeg-full/x86_64/19.08 deploy/runtime/org.freedesktop.Platform.ffmpeg/x86_64/1.6 deploy/runtime/org.freedesktop.Platform.html5-codecs/i386/18.08 deploy/runtime/org.freedesktop.Platform.html5-codecs/x86_64/18.08 deploy/runtime/org.freedesktop.Platform.openh264/x86_64/2.0 deploy/runtime/org.freedesktop.Platform/i386/18.08 deploy/runtime/org.freedesktop.Platform/x86_64/1.6 deploy/runtime/org.freedesktop.Platform/x86_64/18.08 deploy/runtime/org.freedesktop.Platform/x86_64/19.08 deploy/runtime/org.freedesktop.Sdk.Locale/x86_64/1.6 deploy/runtime/org.freedesktop.Sdk.Locale/x86_64/18.08 deploy/runtime/org.freedesktop.Sdk.Locale/x86_64/19.08 deploy/runtime/org.freedesktop.Sdk/x86_64/1.6 deploy/runtime/org.freedesktop.Sdk/x86_64/18.08 deploy/runtime/org.freedesktop.Sdk/x86_64/19.08 deploy/runtime/org.freefilesync.FreeFileSync.Locale/x86_64/stable deploy/runtime/org.gabmus.whatip.Locale/x86_64/stable deploy/runtime/org.geany.Geany.Locale/x86_64/stable deploy/runtime/org.geeqie.Geeqie.Locale/x86_64/stable deploy/runtime/org.geogebra.GeoGebra.Locale/x86_64/stable deploy/runtime/org.glimpse_editor.Glimpse.Locale/x86_64/stable deploy/runtime/org.gnome.Books.Locale/x86_64/stable deploy/runtime/org.gnome.Boxes.Locale/x86_64/stable deploy/runtime/org.gnome.Builder.Locale/x86_64/stable deploy/runtime/org.gnome.Calendar.Locale/x86_64/stable deploy/runtime/org.gnome.Cheese.Locale/x86_64/stable deploy/runtime/org.gnome.Chess.Locale/x86_64/stable deploy/runtime/org.gnome.Devhelp.Locale/x86_64/stable deploy/runtime/org.gnome.Dictionary.Locale/x86_64/stable deploy/runtime/org.gnome.Eolie.Locale/x86_64/stable deploy/runtime/org.gnome.Epiphany.Locale/x86_64/stable deploy/runtime/org.gnome.Fractal.Locale/x86_64/stable deploy/runtime/org.gnome.GHex.Locale/x86_64/stable deploy/runtime/org.gnome.Genius.Locale/x86_64/stable deploy/runtime/org.gnome.Glade.Locale/x86_64/stable deploy/runtime/org.gnome.Lollypop.Locale/x86_64/stable deploy/runtime/org.gnome.Maps.Locale/x86_64/stable deploy/runtime/org.gnome.Nibbles.Locale/x86_64/stable deploy/runtime/org.gnome.Platform.Compat.i386/x86_64/3.36 deploy/runtime/org.gnome.Platform.Locale/x86_64/3.26 deploy/runtime/org.gnome.Platform.Locale/x86_64/3.28 deploy/runtime/org.gnome.Platform.Locale/x86_64/3.32 deploy/runtime/org.gnome.Platform.Locale/x86_64/3.34 deploy/runtime/org.gnome.Platform.Locale/x86_64/3.36 deploy/runtime/org.gnome.Platform/x86_64/3.26 deploy/runtime/org.gnome.Platform/x86_64/3.28 deploy/runtime/org.gnome.Platform/x86_64/3.32 deploy/runtime/org.gnome.Platform/x86_64/3.34 deploy/runtime/org.gnome.Platform/x86_64/3.36 deploy/runtime/org.gnome.Quadrapassel.Locale/x86_64/stable deploy/runtime/org.gnome.Reversi.Locale/x86_64/stable deploy/runtime/org.gnome.Sdk.Locale/x86_64/3.28 deploy/runtime/org.gnome.Sdk.Locale/x86_64/3.32 deploy/runtime/org.gnome.Sdk.Locale/x86_64/3.34 deploy/runtime/org.gnome.Sdk.Locale/x86_64/3.36 deploy/runtime/org.gnome.Sdk/x86_64/3.28 deploy/runtime/org.gnome.Sdk/x86_64/3.32 deploy/runtime/org.gnome.Sdk/x86_64/3.34 deploy/runtime/org.gnome.Sdk/x86_64/3.36 deploy/runtime/org.gnome.SoundRecorder.Locale/x86_64/stable deploy/runtime/org.gnome.Tetravex.Locale/x86_64/stable deploy/runtime/org.gnome.TwentyFortyEight.Locale/x86_64/stable deploy/runtime/org.gnome.dfeet.Locale/x86_64/stable deploy/runtime/org.gnome.gbrainy.Locale/x86_64/stable deploy/runtime/org.gnome.gitg.Locale/x86_64/stable deploy/runtime/org.gnome.glabels_3.Locale/x86_64/stable deploy/runtime/org.gnome.meld.Locale/x86_64/stable deploy/runtime/org.gnucash.GnuCash.Locale/x86_64/stable deploy/runtime/org.gtk.Gtk3theme.elementary/x86_64/3.22 deploy/runtime/org.inkscape.Inkscape.Locale/x86_64/stable deploy/runtime/org.kde.KStyle.Adwaita/x86_64/5.11 deploy/runtime/org.kde.KStyle.Adwaita/x86_64/5.12 deploy/runtime/org.kde.KStyle.Adwaita/x86_64/5.13 deploy/runtime/org.kde.KStyle.Adwaita/x86_64/5.14 deploy/runtime/org.kde.KStyle.HighContrast/x86_64/5.11 deploy/runtime/org.kde.KStyle.HighContrast/x86_64/5.12 deploy/runtime/org.kde.KStyle.HighContrast/x86_64/5.13 deploy/runtime/org.kde.KStyle.HighContrast/x86_64/5.14 deploy/runtime/org.kde.Platform.Locale/x86_64/5.11 deploy/runtime/org.kde.Platform.Locale/x86_64/5.12 deploy/runtime/org.kde.Platform.Locale/x86_64/5.13 deploy/runtime/org.kde.Platform.Locale/x86_64/5.14 deploy/runtime/org.kde.Platform/x86_64/5.11 deploy/runtime/org.kde.Platform/x86_64/5.12 deploy/runtime/org.kde.Platform/x86_64/5.13 deploy/runtime/org.kde.Platform/x86_64/5.14 deploy/runtime/org.kde.PlatformTheme.QGnomePlatform.Sources/x86_64/5.11 deploy/runtime/org.kde.PlatformTheme.QGnomePlatform.Sources/x86_64/5.12 deploy/runtime/org.kde.PlatformTheme.QGnomePlatform.Sources/x86_64/5.13 deploy/runtime/org.kde.PlatformTheme.QGnomePlatform.Sources/x86_64/5.14 deploy/runtime/org.kde.PlatformTheme.QGnomePlatform/x86_64/5.11 deploy/runtime/org.kde.PlatformTheme.QGnomePlatform/x86_64/5.12 deploy/runtime/org.kde.PlatformTheme.QGnomePlatform/x86_64/5.13 deploy/runtime/org.kde.PlatformTheme.QGnomePlatform/x86_64/5.14 deploy/runtime/org.kde.Sdk.Locale/x86_64/5.14 deploy/runtime/org.kde.Sdk/x86_64/5.14 deploy/runtime/org.kde.WaylandDecoration.QGnomePlatform-decoration/x86_64/5.12 deploy/runtime/org.kde.WaylandDecoration.QGnomePlatform-decoration/x86_64/5.13 deploy/runtime/org.kde.WaylandDecoration.QGnomePlatform-decoration/x86_64/5.14 deploy/runtime/org.kde.WaylandDecoration.QGnomePlatform_decoration.Sources/x86_64/5.12 deploy/runtime/org.kde.WaylandDecoration.QGnomePlatform_decoration.Sources/x86_64/5.13 deploy/runtime/org.kde.WaylandDecoration.QGnomePlatform_decoration.Sources/x86_64/5.14 deploy/runtime/org.kde.dolphin.Locale/x86_64/stable deploy/runtime/org.kde.kalzium.Locale/x86_64/stable deploy/runtime/org.kde.katomic.Locale/x86_64/stable deploy/runtime/org.kde.kbruch.Locale/x86_64/stable deploy/runtime/org.kde.kdenlive.Locale/x86_64/stable deploy/runtime/org.kde.kgeography.Locale/x86_64/stable deploy/runtime/org.kde.khangman.Locale/x86_64/stable deploy/runtime/org.kde.knavalbattle.Locale/x86_64/stable deploy/runtime/org.kde.knetwalk.Locale/x86_64/stable deploy/runtime/org.kde.kolourpaint.Locale/x86_64/stable deploy/runtime/org.kde.kpat.Locale/x86_64/stable deploy/runtime/org.kde.krita.Locale/x86_64/stable deploy/runtime/org.kde.ksudoku.Locale/x86_64/stable deploy/runtime/org.kde.ktouch.Locale/x86_64/stable deploy/runtime/org.kde.kubrick.Locale/x86_64/stable deploy/runtime/org.kde.kxstitch.Locale/x86_64/stable deploy/runtime/org.kde.okular.Locale/x86_64/stable deploy/runtime/org.kde.palapeli.Locale/x86_64/stable deploy/runtime/org.kde.skrooge.Locale/x86_64/stable deploy/runtime/org.kicad_pcb.KiCad.Locale/x86_64/stable deploy/runtime/org.kiwix.desktop.Locale/x86_64/stable deploy/runtime/org.laptop.TurtleArtActivity.Locale/x86_64/stable deploy/runtime/org.libreoffice.LibreOffice.Locale/x86_64/stable deploy/runtime/org.libretro.RetroArch.Locale/x86_64/stable deploy/runtime/org.midori_browser.Midori.Locale/x86_64/stable deploy/runtime/org.mixxx.Mixxx.Locale/x86_64/stable deploy/runtime/org.mobsya.ThymioSuite.Locale/x86_64/stable deploy/runtime/org.musesequencer.Muse3.Locale/x86_64/stable deploy/runtime/org.mypaint.MyPaint.Locale/x86_64/stable deploy/runtime/org.nextcloud.Nextcloud.Locale/x86_64/stable deploy/runtime/org.opensurge2d.OpenSurge.Locale/x86_64/stable deploy/runtime/org.pitivi.Pitivi.Codecs/x86_64/stable deploy/runtime/org.pitivi.Pitivi.Locale/x86_64/stable deploy/runtime/org.pulseaudio.pavucontrol.Locale/x86_64/stable deploy/runtime/org.remmina.Remmina.Locale/x86_64/stable deploy/runtime/org.snap4arduino.App.Locale/x86_64/eos3 deploy/runtime/org.squeakland.Etoys.Locale/x86_64/stable deploy/runtime/org.synfig.SynfigStudio.Locale/x86_64/stable deploy/runtime/org.tuxfamily.XMoto.Locale/x86_64/stable deploy/runtime/org.videolan.VLC.Locale/x86_64/stable eos-apps:app/com.endlessm.animals.pt/x86_64/eos3 eos-apps:app/com.endlessm.astronomy.pt/x86_64/eos3 eos-apps:app/com.endlessm.bibliotecas_embrapa.pt_BR/x86_64/eos3 eos-apps:app/com.endlessm.biology.pt/x86_64/eos3 eos-apps:app/com.endlessm.celebrities.pt/x86_64/eos3 eos-apps:app/com.endlessm.dinosaurs.pt/x86_64/eos3 eos-apps:app/com.endlessm.encyclopedia.pt/x86_64/eos3 eos-apps:app/com.endlessm.extra.pt_BR/x86_64/eos3 eos-apps:app/com.endlessm.farming.pt/x86_64/eos3 eos-apps:app/com.endlessm.finance/x86_64/eos3 eos-apps:app/com.endlessm.geography.pt/x86_64/eos3 eos-apps:app/com.endlessm.history.pt/x86_64/eos3 eos-apps:app/com.endlessm.library.pt/x86_64/eos3 eos-apps:app/com.endlessm.math.pt/x86_64/eos3 eos-apps:app/com.endlessm.myths.pt/x86_64/eos3 eos-apps:app/com.endlessm.physics.pt/x86_64/eos3 eos-apps:app/com.endlessm.programming/x86_64/eos3 eos-apps:app/com.endlessm.quote_of_the_day.en/x86_64/eos3 eos-apps:app/com.endlessm.socialsciences.pt/x86_64/eos3 eos-apps:app/com.endlessm.translation/x86_64/eos3 eos-apps:app/com.endlessm.ubongo_kids_demo/x86_64/eos3 eos-apps:app/com.endlessm.video_animations/x86_64/eos3 eos-apps:app/com.endlessm.word_of_the_day.en/x86_64/eos3 eos-apps:app/com.endlessm.your_health.pt_BR/x86_64/eos3 eos-apps:app/com.endlessnetwork.arduinoprojects/x86_64/eos3 eos-apps:app/com.endlessnetwork.blendertutorials/x86_64/eos3 eos-apps:app/com.endlessnetwork.csstutorials/x86_64/eos3 eos-apps:app/com.endlessnetwork.guitartutorials/x86_64/eos3 eos-apps:app/com.endlessnetwork.htmltutorials/x86_64/eos3 eos-apps:app/com.endlessnetwork.raspberrypiprojects/x86_64/eos3 eos-apps:app/com.endlessnetwork.sciencesnacks/x86_64/eos3 eos-apps:app/com.endlessnetwork.shortfilms/x86_64/eos3 eos-apps:app/com.endlessnetwork.videogamestutorials/x86_64/eos3 eos-apps:app/com.google.Chrome/x86_64/eos3 eos-apps:app/com.hack_computer.Clubhouse/x86_64/eos3 eos-apps:app/com.hack_computer.OperatingSystemApp/x86_64/eos3 eos-apps:app/com.hack_computer.ProjectLibrary/x86_64/eos3 eos-apps:app/com.hack_computer.Sidetrack/x86_64/eos3 eos-apps:app/org.mozilla.Firefox/x86_64/eos3 eos-apps:app/org.snap4arduino.App/x86_64/eos3 eos-apps:appstream/x86_64 eos-apps:appstream2/x86_64 eos-apps:ostree-metadata eos-apps:runtime/com.endlessm.animals.pt.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.astronomy.pt.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.biology.pt.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.celebrities.pt.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.encyclopedia.pt.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.extra.pt_BR.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.farming.pt.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.geography.pt.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.history.pt.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.library.pt.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.math.pt.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.myths.pt.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.physics.pt.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.programming.Locale/x86_64/eos3 eos-apps:runtime/com.endlessm.quote_of_the_day.en.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.socialsciences.pt.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.translation.Locale/x86_64/eos3 eos-apps:runtime/com.endlessm.ubongo_kids_demo.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.word_of_the_day.en.Content/x86_64/eos3 eos-apps:runtime/com.endlessm.your_health.pt_BR.Content/x86_64/eos3 eos-apps:runtime/com.hack_computer.Clippy.Extension/x86_64/eos3 eos-apps:runtime/com.hack_computer.Clubhouse.Locale/x86_64/eos3 eos-apps:runtime/com.hack_computer.ProjectLibrary.Content/x86_64/eos3 eos-apps:runtime/org.snap4arduino.App.Locale/x86_64/eos3 eos-runtimes:appstream/x86_64 eos-runtimes:appstream2/x86_64 eos-runtimes:runtime/com.endlessm.Platform/x86_64/eos3.2 eos-sdk:app/com.endlessm.EknServicesMultiplexer/x86_64/stable eos-sdk:appstream/x86_64 eos-sdk:appstream2/x86_64 eos-sdk:ostree-metadata eos-sdk:runtime/com.endlessm.apps.Platform.Locale/x86_64/1 eos-sdk:runtime/com.endlessm.apps.Platform.Locale/x86_64/3 eos-sdk:runtime/com.endlessm.apps.Platform.Locale/x86_64/5 eos-sdk:runtime/com.endlessm.apps.Platform/x86_64/1 eos-sdk:runtime/com.endlessm.apps.Platform/x86_64/3 eos-sdk:runtime/com.endlessm.apps.Platform/x86_64/5 eos-sdk:runtime/org.freedesktop.Platform.Icontheme.EndlessOS/x86_64/1.0 eos:os/eos/amd64/eos3a eos:os/eos/nexthw/eos3.3 flathub:app/au.edu.uq.esys.escript/x86_64/stable flathub:app/br.gov.cti.invesalius/x86_64/stable flathub:app/ca._0ldsk00l.Nestopia/x86_64/stable flathub:app/cc.arduino.arduinoide/x86_64/stable flathub:app/ch.openboard.OpenBoard/x86_64/stable flathub:app/chat.rocket.RocketChat/x86_64/stable flathub:app/com.adobe.Flash-Player-Projector/x86_64/stable flathub:app/com.airtame.Client/x86_64/stable flathub:app/com.albiononline.AlbionOnline/x86_64/stable flathub:app/com.alientrap.nexuiz-classic/x86_64/stable flathub:app/com.anydesk.Anydesk/x86_64/stable flathub:app/com.beakerbrowser.Beaker/x86_64/stable flathub:app/com.bitwarden.desktop/x86_64/stable flathub:app/com.bladecoder.adventure-editor/x86_64/stable flathub:app/com.bluejeans.BlueJeans/x86_64/stable flathub:app/com.brosix.Brosix/x86_64/stable flathub:app/com.chez.GrafX2/x86_64/stable flathub:app/com.dhsdevelopments.Climaxima/x86_64/stable flathub:app/com.discordapp.Discord/x86_64/stable flathub:app/com.dosbox.DOSBox/x86_64/stable flathub:app/com.dropbox.Client/x86_64/stable flathub:app/com.eduke32.EDuke32/x86_64/stable flathub:app/com.endlessm.HatchPreviewer/x86_64/stable flathub:app/com.endlessnetwork.MidnightmareTeddy/x86_64/stable flathub:app/com.endlessnetwork.aqueducts/x86_64/stable flathub:app/com.endlessnetwork.dragonsapprentice/x86_64/stable flathub:app/com.endlessnetwork.fablemaker/x86_64/stable flathub:app/com.endlessnetwork.frogsquash/x86_64/stable flathub:app/com.endlessnetwork.missilemath/x86_64/stable flathub:app/com.endlessnetwork.passage/x86_64/stable flathub:app/com.endlessnetwork.tankwarriors/x86_64/stable flathub:app/com.endlessnetwork.whitehouse/x86_64/stable flathub:app/com.flashforge.FlashPrint/x86_64/stable flathub:app/com.getferdi.Ferdi/x86_64/stable flathub:app/com.getpostman.Postman/x86_64/stable flathub:app/com.github.IsmaelMartinez.teams_for_linux/x86_64/stable flathub:app/com.github.JannikHv.Gydl/x86_64/stable flathub:app/com.github.Johnn3y.Forklift/x86_64/stable flathub:app/com.github.PintaProject.Pinta/x86_64/stable flathub:app/com.github.alecaddd.sequeler/x86_64/stable flathub:app/com.github.artemanufrij.graphui/x86_64/stable flathub:app/com.github.artemanufrij.playmyvideos/x86_64/stable flathub:app/com.github.bcedu.valasimplehttpserver/x86_64/stable flathub:app/com.github.bvschaik.julius/x86_64/stable flathub:app/com.github.coslyk.MoonPlayer/x86_64/stable flathub:app/com.github.dariasteam.cowsrevenge/x86_64/stable flathub:app/com.github.geigi.cozy/x86_64/stable flathub:app/com.github.hopsan.Hopsan/x86_64/stable flathub:app/com.github.lainsce.coin/x86_64/stable flathub:app/com.github.lainsce.notejot/x86_64/stable flathub:app/com.github.matfantinel.moneta/x86_64/stable flathub:app/com.github.mdh34.hackup/x86_64/stable flathub:app/com.github.micahflee.torbrowser-launcher/x86_64/stable flathub:app/com.github.muriloventuroso.easyssh/x86_64/stable flathub:app/com.github.paolostivanin.OTPClient/x86_64/stable flathub:app/com.github.philip_scott.spice-up/x86_64/stable flathub:app/com.github.quaternion/x86_64/stable flathub:app/com.github.robertsanseries.ciano/x86_64/stable flathub:app/com.github.rssguard/x86_64/stable flathub:app/com.github.tchx84.Flatseal/x86_64/stable flathub:app/com.github.unrud.VideoDownloader/x86_64/stable flathub:app/com.github.wwmm.pulseeffects/x86_64/stable flathub:app/com.github.z.Cumulonimbus/x86_64/stable flathub:app/com.gitlab.azymohliad.Qwertone/x86_64/stable flathub:app/com.gitlab.bitseater.meteo/x86_64/stable flathub:app/com.google.AndroidStudio/x86_64/stable flathub:app/com.grangerhub.Tremulous/x86_64/stable flathub:app/com.inform7.IDE/x86_64/stable flathub:app/com.jagex.RuneScape/x86_64/stable flathub:app/com.jetbrains.DataGrip/x86_64/stable flathub:app/com.jetbrains.IntelliJ-IDEA-Community/x86_64/stable flathub:app/com.jetbrains.IntelliJ-IDEA-Ultimate/x86_64/stable flathub:app/com.jetbrains.PhpStorm/x86_64/stable flathub:app/com.jetbrains.PyCharm-Community/x86_64/stable flathub:app/com.jetbrains.PyCharm-Professional/x86_64/stable flathub:app/com.jetbrains.Rider/x86_64/stable flathub:app/com.jetbrains.WebStorm/x86_64/stable flathub:app/com.jgraph.drawio.desktop/x86_64/stable flathub:app/com.jvieira.tpt.Metronome/x86_64/stable flathub:app/com.katawa_shoujo.KatawaShoujo/x86_64/stable flathub:app/com.mattermost.Desktop/x86_64/stable flathub:app/com.microsoft.Teams/x86_64/stable flathub:app/com.moddb.TotalChaos/x86_64/stable flathub:app/com.mojang.Minecraft/x86_64/stable flathub:app/com.moonlight_stream.Moonlight/x86_64/stable flathub:app/com.notepadqq.Notepadqq/x86_64/stable flathub:app/com.obsproject.Studio/x86_64/stable flathub:app/com.ozmartians.VidCutter/x86_64/stable flathub:app/com.play0ad.zeroad/x86_64/stable flathub:app/com.prusa3d.PrusaSlicer/x86_64/stable flathub:app/com.rawtherapee.RawTherapee/x86_64/stable flathub:app/com.realm667.WolfenDoom_Blade_of_Agony/x86_64/stable flathub:app/com.retrodev.blastem/x86_64/stable flathub:app/com.scoutshonour.Digital/x86_64/stable flathub:app/com.scoutshonour.dtipbijays/i386/stable flathub:app/com.shatteredpixel.shatteredpixeldungeon/x86_64/stable flathub:app/com.sigmyne.crush/x86_64/stable flathub:app/com.skype.Client/x86_64/stable flathub:app/com.snes9x.Snes9x/x86_64/stable flathub:app/com.spotify.Client/x86_64/stable flathub:app/com.sublimemerge.App/x86_64/stable flathub:app/com.sublimetext.three/x86_64/stable flathub:app/com.sweethome3d.Sweethome3d/x86_64/stable flathub:app/com.syntevo.SmartGit/x86_64/stable flathub:app/com.tux4kids.tuxmath/x86_64/stable flathub:app/com.unity.UnityHub/x86_64/stable flathub:app/com.valvesoftware.Steam/x86_64/stable flathub:app/com.viber.Viber/x86_64/stable flathub:app/com.viewizard.AstroMenace/x86_64/stable flathub:app/com.visualstudio.code.oss/x86_64/stable flathub:app/com.visualstudio.code/x86_64/stable flathub:app/com.wire.WireDesktop/x86_64/stable flathub:app/com.wps.Office/x86_64/stable flathub:app/de.billardgl.Billardgl/x86_64/stable flathub:app/de.create3000.titania/x86_64/stable flathub:app/de.haeckerfelix.Fragments/x86_64/stable flathub:app/de.haeckerfelix.gradio/x86_64/stable flathub:app/de.rwth_aachen.ient.RDPlot/x86_64/stable flathub:app/de.willuhn.Jameica/x86_64/stable flathub:app/edu.mit.Scratch/x86_64/stable flathub:app/eu.planete_kraus.Tarot/x86_64/stable flathub:app/fr.free.Homebank/x86_64/stable flathub:app/fr.natron.Natron/x86_64/stable flathub:app/im.pidgin.Pidgin/x86_64/stable flathub:app/info.bibletime.BibleTime/x86_64/stable flathub:app/info.colobot.Colobot/x86_64/stable flathub:app/io.atom.Atom/x86_64/stable flathub:app/io.brackets.Brackets/x86_64/stable flathub:app/io.dbeaver.DBeaverCommunity/x86_64/stable flathub:app/io.designer.GravitDesigner/x86_64/stable flathub:app/io.exodus.Exodus/x86_64/stable flathub:app/io.freetubeapp.FreeTube/x86_64/stable flathub:app/io.github.OpenToonz/x86_64/stable flathub:app/io.github.RodZill4.Material-Maker/x86_64/stable flathub:app/io.github.endless_sky.endless_sky/x86_64/stable flathub:app/io.github.freedoom.FreeDM/x86_64/stable flathub:app/io.github.gillesdegottex.FMIT/x86_64/stable flathub:app/io.github.guillaumechereau.Goxel/x86_64/stable flathub:app/io.github.hakuneko.HakuNeko/x86_64/stable flathub:app/io.github.jliljebl.Flowblade/x86_64/stable flathub:app/io.github.markummitchell.Engauge_Digitizer/x86_64/stable flathub:app/io.github.maurycyliebner.enve/x86_64/stable flathub:app/io.github.mki1967.mki3dgame/x86_64/stable flathub:app/io.github.rinigus.PureMaps/x86_64/stable flathub:app/io.github.sharkwouter.Minigalaxy/x86_64/stable flathub:app/io.github.technic.e2designer/x86_64/stable flathub:app/io.github.wereturtle.ghostwriter/x86_64/stable flathub:app/io.gitlab.o20.word/x86_64/stable flathub:app/io.gitlab.osslugaru.Lugaru/x86_64/stable flathub:app/io.lbry.lbry-app/x86_64/stable flathub:app/io.lmms.LMMS/x86_64/stable flathub:app/io.webtorrent.WebTorrent/x86_64/stable flathub:app/jp.yvt.OpenSpades/x86_64/stable flathub:app/net.ankiweb.Anki/x86_64/stable flathub:app/net.bartkessels.getit/x86_64/stable flathub:app/net.blockout.BlockOutII/x86_64/stable flathub:app/net.codeindustry.MasterPDFEditor/x86_64/stable flathub:app/net.dengine.Doomsday/x86_64/stable flathub:app/net.gwyddion.Gwyddion/x86_64/stable flathub:app/net.mancubus.SLADE/x86_64/stable flathub:app/net.mediaarea.MediaInfo/x86_64/stable flathub:app/net.meijn.onvifviewer/x86_64/stable flathub:app/net.minetest.Minetest/x86_64/stable flathub:app/net.openra.OpenRA/x86_64/stable flathub:app/net.oz9aec.Gpredict/x86_64/stable flathub:app/net.pcsx2.PCSX2/i386/stable flathub:app/net.pioneerspacesim.Pioneer/x86_64/stable flathub:app/net.purrdata.PurrData/x86_64/stable flathub:app/net.redeclipse.RedEclipse/x86_64/stable flathub:app/net.runelite.RuneLite/x86_64/stable flathub:app/net.scribus.Scribus/x86_64/stable flathub:app/net.sf.nootka/x86_64/stable flathub:app/net.sourceforge.Chessx/x86_64/stable flathub:app/net.sourceforge.ExtremeTuxRacer/x86_64/stable flathub:app/net.sourceforge.TuxFootball/x86_64/stable flathub:app/net.sourceforge.VMPK/x86_64/stable flathub:app/net.sourceforge.chromium-bsu/x86_64/stable flathub:app/net.sourceforge.fretsonfire/x86_64/stable flathub:app/net.sourceforge.projectM/x86_64/stable flathub:app/net.sourceforge.qtpfsgui.LuminanceHDR/x86_64/stable flathub:app/net.sourceforge.torcs/x86_64/stable flathub:app/net.supertuxkart.SuperTuxKart/x86_64/stable flathub:app/net.veloren.veloren/x86_64/stable flathub:app/net.wz2100.wz2100/x86_64/stable flathub:app/nl.g4d.Girens/x86_64/stable flathub:app/nl.openoffice.bluefish/x86_64/stable flathub:app/org.DolphinEmu.dolphin-emu/x86_64/stable flathub:app/org.apache.netbeans/x86_64/stable flathub:app/org.atheme.audacious/x86_64/stable flathub:app/org.audacityteam.Audacity/x86_64/stable flathub:app/org.bitcoincore.bitcoin-qt/x86_64/stable flathub:app/org.blender.Blender/x86_64/stable flathub:app/org.bluej.BlueJ/x86_64/stable flathub:app/org.bunkus.mkvtoolnix-gui/x86_64/stable flathub:app/org.bzflag.BZFlag/x86_64/stable flathub:app/org.codeblocks.codeblocks/x86_64/stable flathub:app/org.cvfosammmm.Porto/x86_64/stable flathub:app/org.darktable.Darktable/x86_64/stable flathub:app/org.eclipse.Committers/x86_64/stable flathub:app/org.eclipse.Java/x86_64/stable flathub:app/org.eclipse.iot.fourdiac.Ide/x86_64/stable flathub:app/org.entangle_photo.Manager/x86_64/stable flathub:app/org.fedoraproject.MediaWriter/x86_64/stable flathub:app/org.filezillaproject.Filezilla/x86_64/stable flathub:app/org.flarerpg.Flare/x86_64/stable flathub:app/org.flatpak.qtdemo/x86_64/stable flathub:app/org.flightgear.FlightGear/x86_64/stable flathub:app/org.fontforge.FontForge/x86_64/stable flathub:app/org.free_astro.siril/x86_64/stable flathub:app/org.freecadweb.FreeCAD/x86_64/stable flathub:app/org.freecol.FreeCol/x86_64/stable flathub:app/org.freedesktop.Bustle/x86_64/stable flathub:app/org.freedesktop.GstDebugViewer/x86_64/stable flathub:app/org.freefilesync.FreeFileSync/x86_64/stable flathub:app/org.fritzing.Fritzing/x86_64/stable flathub:app/org.gabmus.whatip/x86_64/stable flathub:app/org.geany.Geany/x86_64/stable flathub:app/org.geeqie.Geeqie/x86_64/stable flathub:app/org.geogebra.GeoGebra/x86_64/stable flathub:app/org.gimp.GIMP/x86_64/stable flathub:app/org.glimpse_editor.Glimpse/x86_64/stable flathub:app/org.gnode.NixView/x86_64/stable flathub:app/org.gnome.Books/x86_64/stable flathub:app/org.gnome.Boxes/x86_64/stable flathub:app/org.gnome.Builder/x86_64/stable flathub:app/org.gnome.Calendar/x86_64/stable flathub:app/org.gnome.Cheese/x86_64/stable flathub:app/org.gnome.Chess/x86_64/stable flathub:app/org.gnome.Devhelp/x86_64/stable flathub:app/org.gnome.Dictionary/x86_64/stable flathub:app/org.gnome.Eolie/x86_64/stable flathub:app/org.gnome.Epiphany/x86_64/stable flathub:app/org.gnome.Fractal/x86_64/stable flathub:app/org.gnome.GHex/x86_64/stable flathub:app/org.gnome.Genius/x86_64/stable flathub:app/org.gnome.Glade/x86_64/stable flathub:app/org.gnome.HexGL/x86_64/stable flathub:app/org.gnome.Lollypop/x86_64/stable flathub:app/org.gnome.Maps/x86_64/stable flathub:app/org.gnome.Nibbles/x86_64/stable flathub:app/org.gnome.Quadrapassel/x86_64/stable flathub:app/org.gnome.Reversi/x86_64/stable flathub:app/org.gnome.SoundRecorder/x86_64/stable flathub:app/org.gnome.Tetravex/x86_64/stable flathub:app/org.gnome.TwentyFortyEight/x86_64/stable flathub:app/org.gnome.dfeet/x86_64/stable flathub:app/org.gnome.gbrainy/x86_64/stable flathub:app/org.gnome.gitg/x86_64/stable flathub:app/org.gnome.gitlab.Cowsay/x86_64/stable flathub:app/org.gnome.glabels-3/x86_64/stable flathub:app/org.gnome.meld/x86_64/stable flathub:app/org.gnucash.GnuCash/x86_64/stable flathub:app/org.godotengine.Godot/x86_64/stable flathub:app/org.gottcode.Kapow/x86_64/stable flathub:app/org.horizon_eda.HorizonEDA/x86_64/stable flathub:app/org.hydrogenmusic.Hydrogen/x86_64/stable flathub:app/org.inkscape.Inkscape/x86_64/stable flathub:app/org.jamovi.jamovi/x86_64/stable flathub:app/org.jdownloader.JDownloader/x86_64/stable flathub:app/org.kde.dolphin/x86_64/stable flathub:app/org.kde.kalzium/x86_64/stable flathub:app/org.kde.katomic/x86_64/stable flathub:app/org.kde.kbruch/x86_64/stable flathub:app/org.kde.kdenlive/x86_64/stable flathub:app/org.kde.kgeography/x86_64/stable flathub:app/org.kde.khangman/x86_64/stable flathub:app/org.kde.knavalbattle/x86_64/stable flathub:app/org.kde.knetwalk/x86_64/stable flathub:app/org.kde.kolourpaint/x86_64/stable flathub:app/org.kde.kpat/x86_64/stable flathub:app/org.kde.krita/x86_64/stable flathub:app/org.kde.ksudoku/x86_64/stable flathub:app/org.kde.ktouch/x86_64/stable flathub:app/org.kde.kubrick/x86_64/stable flathub:app/org.kde.kxstitch/x86_64/stable flathub:app/org.kde.okular/x86_64/stable flathub:app/org.kde.palapeli/x86_64/stable flathub:app/org.kde.skrooge/x86_64/stable flathub:app/org.kicad_pcb.KiCad/x86_64/stable flathub:app/org.kiwix.desktop/x86_64/stable flathub:app/org.laptop.TurtleArtActivity/x86_64/stable flathub:app/org.learningequality.Kolibri/x86_64/stable flathub:app/org.leocad.LeoCAD/x86_64/stable flathub:app/org.libreoffice.LibreOffice/x86_64/stable flathub:app/org.librepcb.LibrePCB/x86_64/stable flathub:app/org.libretro.RetroArch/x86_64/stable flathub:app/org.linux_hardware.hw-probe/x86_64/stable flathub:app/org.midori_browser.Midori/x86_64/stable flathub:app/org.mixxx.Mixxx/x86_64/stable flathub:app/org.mobsya.ThymioSuite/x86_64/stable flathub:app/org.musescore.MuseScore/x86_64/stable flathub:app/org.musesequencer.Muse3/x86_64/stable flathub:app/org.mypaint.MyPaint/x86_64/stable flathub:app/org.nextcloud.Nextcloud/x86_64/stable flathub:app/org.octave.Octave/x86_64/stable flathub:app/org.olivevideoeditor.Olive/x86_64/stable flathub:app/org.onlyoffice.desktopeditors/x86_64/stable flathub:app/org.openmw.OpenMW/x86_64/stable flathub:app/org.openscad.OpenSCAD/x86_64/stable flathub:app/org.openshot.OpenShot/x86_64/stable flathub:app/org.openstreetmap.josm/x86_64/stable flathub:app/org.opensurge2d.OpenSurge/x86_64/stable flathub:app/org.openttd.OpenTTD/x86_64/stable flathub:app/org.pegasus_frontend.Pegasus/x86_64/stable flathub:app/org.phoenicis.playonlinux/x86_64/stable flathub:app/org.pitivi.Pitivi/x86_64/stable flathub:app/org.pjbroad.EternallandsClient/x86_64/stable flathub:app/org.ppsspp.PPSSPP/x86_64/stable flathub:app/org.pulseaudio.pavucontrol/x86_64/stable flathub:app/org.pyzo.pyzo/x86_64/stable flathub:app/org.qbittorrent.qBittorrent/x86_64/stable flathub:app/org.qgis.qgis/x86_64/stable flathub:app/org.qutebrowser.qutebrowser/x86_64/stable flathub:app/org.remmina.Remmina/x86_64/stable flathub:app/org.robocode.Robocode/x86_64/stable flathub:app/org.sauerbraten.Sauerbraten/x86_64/stable flathub:app/org.shadered.SHADERed/x86_64/stable flathub:app/org.shotcut.Shotcut/x86_64/stable flathub:app/org.signal.Signal/x86_64/stable flathub:app/org.speed_dreams.SpeedDreams/x86_64/stable flathub:app/org.speedcrunch.SpeedCrunch/x86_64/stable flathub:app/org.squeakland.Etoys/x86_64/stable flathub:app/org.srb2.SRB2/x86_64/stable flathub:app/org.srb2.SRB2Kart/x86_64/stable flathub:app/org.stellarium.Stellarium/x86_64/stable flathub:app/org.subsurface_divelog.Subsurface/x86_64/stable flathub:app/org.sugarlabs.AbacusActivity/x86_64/stable flathub:app/org.sugarlabs.FotoToon/x86_64/stable flathub:app/org.sugarlabs.FractionBounce/x86_64/stable flathub:app/org.sugarlabs.Measure/x86_64/stable flathub:app/org.sugarlabs.MusicKeyboard/x86_64/stable flathub:app/org.sugarlabs.Physics/x86_64/stable flathub:app/org.sugarlabs.Pippy/x86_64/stable flathub:app/org.sugarlabs.Sliderule/x86_64/stable flathub:app/org.sugarlabs.Speak/x86_64/stable flathub:app/org.sugarlabs.StoryActivity/x86_64/stable flathub:app/org.sugarlabs.Words/x86_64/stable flathub:app/org.synfig.SynfigStudio/x86_64/stable flathub:app/org.telegram.desktop/x86_64/stable flathub:app/org.tuxfamily.StuntRally/x86_64/stable flathub:app/org.tuxfamily.XMoto/x86_64/stable flathub:app/org.vergecurrency.verge-qt/x86_64/stable flathub:app/org.videolan.VLC/x86_64/stable flathub:app/org.wesnoth.Wesnoth/x86_64/stable flathub:app/org.widelands.Widelands/x86_64/stable flathub:app/org.wireshark.Wireshark/x86_64/stable flathub:app/org.xonotic.Xonotic/x86_64/stable flathub:app/org.zdoom.GZDoom/x86_64/stable flathub:app/re.sonny.Tangram/x86_64/stable flathub:app/space.fips.Fips/x86_64/stable flathub:app/tv.kodi.Kodi/x86_64/stable flathub:app/uk.jnthn.backgammony/x86_64/stable flathub:app/us.zoom.Zoom/x86_64/stable flathub:app/website.i2pd.i2pd/x86_64/stable flathub:app/ws.openarena.OpenArena/x86_64/stable flathub:app/xyz.z3ntu.razergenie/x86_64/stable flathub:appstream/x86_64 flathub:appstream2/x86_64 flathub:runtime/com.adobe.Flash_Player_Projector.Locale/x86_64/stable flathub:runtime/com.airtame.Client.Locale/x86_64/stable flathub:runtime/com.github.JannikHv.Gydl.Locale/x86_64/stable flathub:runtime/com.github.PintaProject.Pinta.Locale/x86_64/stable flathub:runtime/com.github.alecaddd.sequeler.Locale/x86_64/stable flathub:runtime/com.github.artemanufrij.graphui.Locale/x86_64/stable flathub:runtime/com.github.artemanufrij.playmyvideos.Locale/x86_64/stable flathub:runtime/com.github.bcedu.valasimplehttpserver.Locale/x86_64/stable flathub:runtime/com.github.coslyk.MoonPlayer.Locale/x86_64/stable flathub:runtime/com.github.geigi.cozy.Locale/x86_64/stable flathub:runtime/com.github.lainsce.coin.Locale/x86_64/stable flathub:runtime/com.github.lainsce.notejot.Locale/x86_64/stable flathub:runtime/com.github.matfantinel.moneta.Locale/x86_64/stable flathub:runtime/com.github.mdh34.hackup.Locale/x86_64/stable flathub:runtime/com.github.muriloventuroso.easyssh.Locale/x86_64/stable flathub:runtime/com.github.philip_scott.spice_up.Locale/x86_64/stable flathub:runtime/com.github.robertsanseries.ciano.Locale/x86_64/stable flathub:runtime/com.github.unrud.VideoDownloader.Locale/x86_64/stable flathub:runtime/com.github.wwmm.pulseeffects.Locale/x86_64/stable flathub:runtime/com.gitlab.bitseater.meteo.Locale/x86_64/stable flathub:runtime/com.google.AndroidStudio.Locale/x86_64/stable flathub:runtime/com.inform7.IDE.Locale/x86_64/stable flathub:runtime/com.obsproject.Studio.Locale/x86_64/stable flathub:runtime/com.prusa3d.PrusaSlicer.Locale/x86_64/stable flathub:runtime/com.rawtherapee.RawTherapee.Locale/x86_64/stable flathub:runtime/com.snes9x.Snes9x.Locale/x86_64/stable flathub:runtime/com.tux4kids.tuxmath.Locale/x86_64/stable flathub:runtime/de.create3000.titania.Locale/x86_64/stable flathub:runtime/de.haeckerfelix.Fragments.Locale/x86_64/stable flathub:runtime/de.haeckerfelix.gradio.Locale/x86_64/stable flathub:runtime/eu.planete_kraus.Tarot.Locale/x86_64/stable flathub:runtime/fr.free.Homebank.Locale/x86_64/stable flathub:runtime/fr.natron.Natron.Locale/x86_64/stable flathub:runtime/im.pidgin.Pidgin.Locale/x86_64/stable flathub:runtime/info.colobot.Colobot.Locale/x86_64/stable flathub:runtime/io.github.OpenToonz.Locale/x86_64/stable flathub:runtime/io.github.jliljebl.Flowblade.Locale/x86_64/stable flathub:runtime/io.github.maurycyliebner.enve.Locale/x86_64/stable flathub:runtime/io.github.sharkwouter.Minigalaxy.Locale/x86_64/stable flathub:runtime/io.lbry.lbry_app.Locale/x86_64/stable flathub:runtime/net.bartkessels.getit.Locale/x86_64/stable flathub:runtime/net.codeindustry.MasterPDFEditor.Locale/x86_64/stable flathub:runtime/net.gwyddion.Gwyddion.Locale/x86_64/stable flathub:runtime/net.mancubus.SLADE.Locale/x86_64/stable flathub:runtime/net.meijn.onvifviewer.Locale/x86_64/stable flathub:runtime/net.minetest.Minetest.Locale/x86_64/stable flathub:runtime/net.oz9aec.Gpredict.Locale/x86_64/stable flathub:runtime/net.pcsx2.PCSX2.Locale/i386/stable flathub:runtime/net.sourceforge.TuxFootball.Locale/x86_64/stable flathub:runtime/net.sourceforge.chromium_bsu.Locale/x86_64/stable flathub:runtime/net.sourceforge.fretsonfire.Locale/x86_64/stable flathub:runtime/nl.g4d.Girens.Locale/x86_64/stable flathub:runtime/nl.openoffice.bluefish.Locale/x86_64/stable flathub:runtime/org.DolphinEmu.dolphin_emu.Locale/x86_64/stable flathub:runtime/org.atheme.audacious.Locale/x86_64/stable flathub:runtime/org.audacityteam.Audacity.Codecs/x86_64/stable flathub:runtime/org.audacityteam.Audacity.Locale/x86_64/stable flathub:runtime/org.blender.Blender.Codecs/x86_64/stable flathub:runtime/org.bunkus.mkvtoolnix_gui.Locale/x86_64/stable flathub:runtime/org.codeblocks.codeblocks.Locale/x86_64/stable flathub:runtime/org.cvfosammmm.Porto.Locale/x86_64/stable flathub:runtime/org.darktable.Darktable.Locale/x86_64/stable flathub:runtime/org.entangle_photo.Manager.Locale/x86_64/stable flathub:runtime/org.filezillaproject.Filezilla.Locale/x86_64/stable flathub:runtime/org.fontforge.FontForge.Locale/x86_64/stable flathub:runtime/org.free_astro.siril.Locale/x86_64/stable flathub:runtime/org.freedesktop.Platform.Compat.i386/x86_64/18.08 flathub:runtime/org.freedesktop.Platform.Compat.i386/x86_64/19.08 flathub:runtime/org.freedesktop.Platform.GL.default/x86_64/19.08 flathub:runtime/org.freedesktop.Platform.GL32.default/x86_64/19.08 flathub:runtime/org.freedesktop.Platform.Locale/i386/18.08 flathub:runtime/org.freedesktop.Platform.Locale/x86_64/1.6 flathub:runtime/org.freedesktop.Platform.Locale/x86_64/18.08 flathub:runtime/org.freedesktop.Platform.Locale/x86_64/19.08 flathub:runtime/org.freedesktop.Platform.VAAPI.Intel/i386/18.08 flathub:runtime/org.freedesktop.Platform.VAAPI.Intel/x86_64/1.6 flathub:runtime/org.freedesktop.Platform.VAAPI.Intel/x86_64/18.08 flathub:runtime/org.freedesktop.Platform.VAAPI.Intel/x86_64/19.08 flathub:runtime/org.freedesktop.Platform.ffmpeg-full/x86_64/19.08 flathub:runtime/org.freedesktop.Platform.ffmpeg/x86_64/1.6 flathub:runtime/org.freedesktop.Platform.html5-codecs/i386/18.08 flathub:runtime/org.freedesktop.Platform.html5-codecs/x86_64/18.08 flathub:runtime/org.freedesktop.Platform.openh264/x86_64/2.0 flathub:runtime/org.freedesktop.Platform/i386/18.08 flathub:runtime/org.freedesktop.Platform/x86_64/1.6 flathub:runtime/org.freedesktop.Platform/x86_64/18.08 flathub:runtime/org.freedesktop.Platform/x86_64/19.08 flathub:runtime/org.freedesktop.Sdk.Locale/x86_64/1.6 flathub:runtime/org.freedesktop.Sdk.Locale/x86_64/18.08 flathub:runtime/org.freedesktop.Sdk.Locale/x86_64/19.08 flathub:runtime/org.freedesktop.Sdk/x86_64/1.6 flathub:runtime/org.freedesktop.Sdk/x86_64/18.08 flathub:runtime/org.freedesktop.Sdk/x86_64/19.08 flathub:runtime/org.freefilesync.FreeFileSync.Locale/x86_64/stable flathub:runtime/org.gabmus.whatip.Locale/x86_64/stable flathub:runtime/org.geany.Geany.Locale/x86_64/stable flathub:runtime/org.geeqie.Geeqie.Locale/x86_64/stable flathub:runtime/org.geogebra.GeoGebra.Locale/x86_64/stable flathub:runtime/org.glimpse_editor.Glimpse.Locale/x86_64/stable flathub:runtime/org.gnome.Books.Locale/x86_64/stable flathub:runtime/org.gnome.Boxes.Locale/x86_64/stable flathub:runtime/org.gnome.Builder.Locale/x86_64/stable flathub:runtime/org.gnome.Calendar.Locale/x86_64/stable flathub:runtime/org.gnome.Cheese.Locale/x86_64/stable flathub:runtime/org.gnome.Chess.Locale/x86_64/stable flathub:runtime/org.gnome.Devhelp.Locale/x86_64/stable flathub:runtime/org.gnome.Dictionary.Locale/x86_64/stable flathub:runtime/org.gnome.Eolie.Locale/x86_64/stable flathub:runtime/org.gnome.Epiphany.Locale/x86_64/stable flathub:runtime/org.gnome.Fractal.Locale/x86_64/stable flathub:runtime/org.gnome.GHex.Locale/x86_64/stable flathub:runtime/org.gnome.Genius.Locale/x86_64/stable flathub:runtime/org.gnome.Glade.Locale/x86_64/stable flathub:runtime/org.gnome.Lollypop.Locale/x86_64/stable flathub:runtime/org.gnome.Maps.Locale/x86_64/stable flathub:runtime/org.gnome.Nibbles.Locale/x86_64/stable flathub:runtime/org.gnome.Platform.Compat.i386/x86_64/3.36 flathub:runtime/org.gnome.Platform.Locale/x86_64/3.26 flathub:runtime/org.gnome.Platform.Locale/x86_64/3.28 flathub:runtime/org.gnome.Platform.Locale/x86_64/3.32 flathub:runtime/org.gnome.Platform.Locale/x86_64/3.34 flathub:runtime/org.gnome.Platform.Locale/x86_64/3.36 flathub:runtime/org.gnome.Platform/x86_64/3.26 flathub:runtime/org.gnome.Platform/x86_64/3.28 flathub:runtime/org.gnome.Platform/x86_64/3.32 flathub:runtime/org.gnome.Platform/x86_64/3.34 flathub:runtime/org.gnome.Platform/x86_64/3.36 flathub:runtime/org.gnome.Quadrapassel.Locale/x86_64/stable flathub:runtime/org.gnome.Reversi.Locale/x86_64/stable flathub:runtime/org.gnome.Sdk.Locale/x86_64/3.28 flathub:runtime/org.gnome.Sdk.Locale/x86_64/3.32 flathub:runtime/org.gnome.Sdk.Locale/x86_64/3.34 flathub:runtime/org.gnome.Sdk.Locale/x86_64/3.36 flathub:runtime/org.gnome.Sdk/x86_64/3.28 flathub:runtime/org.gnome.Sdk/x86_64/3.32 flathub:runtime/org.gnome.Sdk/x86_64/3.34 flathub:runtime/org.gnome.Sdk/x86_64/3.36 flathub:runtime/org.gnome.SoundRecorder.Locale/x86_64/stable flathub:runtime/org.gnome.Tetravex.Locale/x86_64/stable flathub:runtime/org.gnome.TwentyFortyEight.Locale/x86_64/stable flathub:runtime/org.gnome.dfeet.Locale/x86_64/stable flathub:runtime/org.gnome.gbrainy.Locale/x86_64/stable flathub:runtime/org.gnome.gitg.Locale/x86_64/stable flathub:runtime/org.gnome.glabels_3.Locale/x86_64/stable flathub:runtime/org.gnome.meld.Locale/x86_64/stable flathub:runtime/org.gnucash.GnuCash.Locale/x86_64/stable flathub:runtime/org.gtk.Gtk3theme.elementary/x86_64/3.22 flathub:runtime/org.inkscape.Inkscape.Locale/x86_64/stable flathub:runtime/org.kde.KStyle.Adwaita/x86_64/5.11 flathub:runtime/org.kde.KStyle.Adwaita/x86_64/5.12 flathub:runtime/org.kde.KStyle.Adwaita/x86_64/5.13 flathub:runtime/org.kde.KStyle.Adwaita/x86_64/5.14 flathub:runtime/org.kde.KStyle.HighContrast/x86_64/5.11 flathub:runtime/org.kde.KStyle.HighContrast/x86_64/5.12 flathub:runtime/org.kde.KStyle.HighContrast/x86_64/5.13 flathub:runtime/org.kde.KStyle.HighContrast/x86_64/5.14 flathub:runtime/org.kde.Platform.Locale/x86_64/5.11 flathub:runtime/org.kde.Platform.Locale/x86_64/5.12 flathub:runtime/org.kde.Platform.Locale/x86_64/5.13 flathub:runtime/org.kde.Platform.Locale/x86_64/5.14 flathub:runtime/org.kde.Platform/x86_64/5.11 flathub:runtime/org.kde.Platform/x86_64/5.12 flathub:runtime/org.kde.Platform/x86_64/5.13 flathub:runtime/org.kde.Platform/x86_64/5.14 flathub:runtime/org.kde.PlatformTheme.QGnomePlatform.Sources/x86_64/5.11 flathub:runtime/org.kde.PlatformTheme.QGnomePlatform.Sources/x86_64/5.12 flathub:runtime/org.kde.PlatformTheme.QGnomePlatform.Sources/x86_64/5.13 flathub:runtime/org.kde.PlatformTheme.QGnomePlatform.Sources/x86_64/5.14 flathub:runtime/org.kde.PlatformTheme.QGnomePlatform/x86_64/5.11 flathub:runtime/org.kde.PlatformTheme.QGnomePlatform/x86_64/5.12 flathub:runtime/org.kde.PlatformTheme.QGnomePlatform/x86_64/5.13 flathub:runtime/org.kde.PlatformTheme.QGnomePlatform/x86_64/5.14 flathub:runtime/org.kde.Sdk.Locale/x86_64/5.14 flathub:runtime/org.kde.Sdk/x86_64/5.14 flathub:runtime/org.kde.WaylandDecoration.QGnomePlatform-decoration/x86_64/5.12 flathub:runtime/org.kde.WaylandDecoration.QGnomePlatform-decoration/x86_64/5.13 flathub:runtime/org.kde.WaylandDecoration.QGnomePlatform-decoration/x86_64/5.14 flathub:runtime/org.kde.WaylandDecoration.QGnomePlatform_decoration.Sources/x86_64/5.12 flathub:runtime/org.kde.WaylandDecoration.QGnomePlatform_decoration.Sources/x86_64/5.13 flathub:runtime/org.kde.WaylandDecoration.QGnomePlatform_decoration.Sources/x86_64/5.14 flathub:runtime/org.kde.dolphin.Locale/x86_64/stable flathub:runtime/org.kde.kalzium.Locale/x86_64/stable flathub:runtime/org.kde.katomic.Locale/x86_64/stable flathub:runtime/org.kde.kbruch.Locale/x86_64/stable flathub:runtime/org.kde.kdenlive.Locale/x86_64/stable flathub:runtime/org.kde.kgeography.Locale/x86_64/stable flathub:runtime/org.kde.khangman.Locale/x86_64/stable flathub:runtime/org.kde.knavalbattle.Locale/x86_64/stable flathub:runtime/org.kde.knetwalk.Locale/x86_64/stable flathub:runtime/org.kde.kolourpaint.Locale/x86_64/stable flathub:runtime/org.kde.kpat.Locale/x86_64/stable flathub:runtime/org.kde.krita.Locale/x86_64/stable flathub:runtime/org.kde.ksudoku.Locale/x86_64/stable flathub:runtime/org.kde.ktouch.Locale/x86_64/stable flathub:runtime/org.kde.kubrick.Locale/x86_64/stable flathub:runtime/org.kde.kxstitch.Locale/x86_64/stable flathub:runtime/org.kde.okular.Locale/x86_64/stable flathub:runtime/org.kde.palapeli.Locale/x86_64/stable flathub:runtime/org.kde.skrooge.Locale/x86_64/stable flathub:runtime/org.kicad_pcb.KiCad.Locale/x86_64/stable flathub:runtime/org.kiwix.desktop.Locale/x86_64/stable flathub:runtime/org.laptop.TurtleArtActivity.Locale/x86_64/stable flathub:runtime/org.libreoffice.LibreOffice.Locale/x86_64/stable flathub:runtime/org.libretro.RetroArch.Locale/x86_64/stable flathub:runtime/org.midori_browser.Midori.Locale/x86_64/stable flathub:runtime/org.mixxx.Mixxx.Locale/x86_64/stable flathub:runtime/org.mobsya.ThymioSuite.Locale/x86_64/stable flathub:runtime/org.musesequencer.Muse3.Locale/x86_64/stable flathub:runtime/org.mypaint.MyPaint.Locale/x86_64/stable flathub:runtime/org.nextcloud.Nextcloud.Locale/x86_64/stable flathub:runtime/org.opensurge2d.OpenSurge.Locale/x86_64/stable flathub:runtime/org.pitivi.Pitivi.Codecs/x86_64/stable flathub:runtime/org.pitivi.Pitivi.Locale/x86_64/stable flathub:runtime/org.pulseaudio.pavucontrol.Locale/x86_64/stable flathub:runtime/org.remmina.Remmina.Locale/x86_64/stable flathub:runtime/org.squeakland.Etoys.Locale/x86_64/stable flathub:runtime/org.synfig.SynfigStudio.Locale/x86_64/stable flathub:runtime/org.tuxfamily.XMoto.Locale/x86_64/stable flathub:runtime/org.videolan.VLC.Locale/x86_64/stable ostree/1/1/0 ostree/1/1/1 =================================== = OSTree repository configuration = =================================== [core] repo_version=1 mode=bare add-remotes-config-dir=false min-free-space-size=500MB [remote "eos"] url=https://ostree.endlessm.com/ostree/eos-amd64 branches=os/eos/amd64/eos3a; xa.disable=true collection-id=com.endlessm.Os [remote "eos-runtimes"] url=https://ostree.endlessm.com/ostree/eos-amd64 gpg-verify=true gpg-verify-summary=true xa.title=Endless OS and Runtimes [remote "flathub"] url=https://dl.flathub.org/repo/ xa.title=Flathub gpg-verify=true gpg-verify-summary=true [remote "eos-apps"] url=https://ostree.endlessm.com/ostree/eos-apps xa.default-branch=eos3 gpg-verify=true gpg-verify-summary=false xa.title=Endless Applications collection-id=com.endlessm.Apps [remote "eos-sdk"] url=https://ostree.endlessm.com/ostree/eos-sdk gpg-verify=true gpg-verify-summary=false xa.title=Endless Runtime and SDK xa.default-branch=stable collection-id=com.endlessm.Sdk ============================================== = OSTree repository configuration (extra SD) = ============================================== not a split system (or SD card missing) ========================== = Product identification = ========================== sys_vendor: Acer product_name: Aspire A515-51 product_uuid: b65a8354-6646-e911-b016-9829a6e74308 product_version: V2.02 board_asset_tag: Type2 - Board Serial Number board_name: Charmander_KL board_vendor: KBL board_version: V2.02 bios_date: 01/03/2019 bios_vendor: Insyde Corp. bios_version: V2.02 chassis_asset_tag: chassis_type: 10 chassis_vendor: Acer chassis_version: V2.02 ======= = CPU = ======= processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 142 model name : Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz stepping : 9 microcode : 0xca cpu MHz : 2700.080 cache size : 4096 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 22 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 cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips : 5799.77 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 : 142 model name : Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz stepping : 9 microcode : 0xca cpu MHz : 2700.753 cache size : 4096 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 22 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 cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips : 5799.77 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 : 142 model name : Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz stepping : 9 microcode : 0xca cpu MHz : 2700.061 cache size : 4096 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 22 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 cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips : 5799.77 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 : 142 model name : Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz stepping : 9 microcode : 0xca cpu MHz : 2700.023 cache size : 4096 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 22 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 cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips : 5799.77 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: ========== = Memory = ========== total used free shared buff/cache available Mem: 7,7Gi 1,5Gi 2,1Gi 321Mi 4,1Gi 5,8Gi Swap: 11Gi 1,0Mi 11Gi MemTotal: 8025280 kB MemFree: 2157620 kB MemAvailable: 6035748 kB Buffers: 412508 kB Cached: 3732172 kB SwapCached: 72 kB Active: 4649772 kB Inactive: 618356 kB Active(anon): 1297928 kB Inactive(anon): 155024 kB Active(file): 3351844 kB Inactive(file): 463332 kB Unevictable: 172244 kB Mlocked: 80 kB SwapTotal: 12037916 kB SwapFree: 12036892 kB Dirty: 396 kB Writeback: 0 kB AnonPages: 1295600 kB Mapped: 454520 kB Shmem: 329496 kB KReclaimable: 167292 kB Slab: 258528 kB SReclaimable: 167292 kB SUnreclaim: 91236 kB KernelStack: 10976 kB PageTables: 27616 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 16050556 kB Committed_AS: 7821792 kB VmallocTotal: 34359738367 kB VmallocUsed: 97572 kB VmallocChunk: 0 kB Percpu: 2480 kB HardwareCorrupted: 0 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB Hugetlb: 0 kB DirectMap4k: 231412 kB DirectMap2M: 6981632 kB DirectMap1G: 1048576 kB NAME DISKSIZE DATA COMPR ALGORITHM STREAMS ZERO-PAGES TOTAL MEM-LIMIT MEM-USED MIGRATED MOUNTPOINT /dev/zram0 11,5G 648K 24,8K lzo-rle 4 110 236K 0B 2,7M 0B [SWAP] ========= = Disks = ========= /org/freedesktop/UDisks2/Manager: org.freedesktop.UDisks2.Manager: DefaultEncryptionType: luks1 SupportedEncryptionTypes: luks1 luks2 SupportedFilesystems: ext2 ext3 ext4 vfat ntfs exfat xfs reiserfs nilfs2 btrfs minix udf f2fs swap Version: 2.8.4 /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: UserspaceMountOptions: 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: UserspaceMountOptions: 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: UserspaceMountOptions: 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: UserspaceMountOptions: 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: UserspaceMountOptions: 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: UserspaceMountOptions: 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: UserspaceMountOptions: 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: UserspaceMountOptions: org.freedesktop.UDisks2.Loop: Autoclear: false BackingFile: SetupByUID: 0 /org/freedesktop/UDisks2/block_devices/sda: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/sda DeviceNumber: 2048 Drive: '/org/freedesktop/UDisks2/drives/ST2000LM007_1R8174_WDZFXS27' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-ST2000LM007-1R8174_WDZFXS27 IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sda ReadOnly: false Size: 2000398934016 Symlinks: /dev/disk/by-id/ata-ST2000LM007-1R8174_WDZFXS27 /dev/disk/by-id/wwn-0x5000c500bd99cad5 /dev/disk/by-path/pci-0000:00:17.0-ata-1 UserspaceMountOptions: org.freedesktop.UDisks2.PartitionTable: Partitions: ['/org/freedesktop/UDisks2/block_devices/sda3', '/org/freedesktop/UDisks2/block_devices/sda5', '/org/freedesktop/UDisks2/block_devices/sda2', '/org/freedesktop/UDisks2/block_devices/sda1'] Type: gpt /org/freedesktop/UDisks2/block_devices/sda1: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/sda1 DeviceNumber: 2049 Drive: '/org/freedesktop/UDisks2/drives/ST2000LM007_1R8174_WDZFXS27' HintAuto: false HintIconName: HintIgnore: true HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-ST2000LM007-1R8174_WDZFXS27-part1 IdLabel: IdType: vfat IdUUID: E271-4A8F IdUsage: filesystem IdVersion: FAT16 MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sda1 ReadOnly: false Size: 65011712 Symlinks: /dev/disk/by-id/ata-ST2000LM007-1R8174_WDZFXS27-part1 /dev/disk/by-id/wwn-0x5000c500bd99cad5-part1 /dev/disk/by-partuuid/e206065c-ed0e-4e38-9d1c-2cc6ea9b69c3 /dev/disk/by-path/pci-0000:00:17.0-ata-1-part1 /dev/disk/by-uuid/E271-4A8F UserspaceMountOptions: org.freedesktop.UDisks2.Filesystem: MountPoints: Size: 0 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: e206065c-ed0e-4e38-9d1c-2cc6ea9b69c3 /org/freedesktop/UDisks2/block_devices/sda2: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/sda2 DeviceNumber: 2050 Drive: '/org/freedesktop/UDisks2/drives/ST2000LM007_1R8174_WDZFXS27' HintAuto: false HintIconName: HintIgnore: true HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-ST2000LM007-1R8174_WDZFXS27-part2 IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sda2 ReadOnly: false Size: 1048576 Symlinks: /dev/disk/by-id/ata-ST2000LM007-1R8174_WDZFXS27-part2 /dev/disk/by-id/wwn-0x5000c500bd99cad5-part2 /dev/disk/by-partuuid/8f36717a-af7a-4ab5-b6ae-d5204437166c /dev/disk/by-path/pci-0000:00:17.0-ata-1-part2 UserspaceMountOptions: 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: 8f36717a-af7a-4ab5-b6ae-d5204437166c /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/ST2000LM007_1R8174_WDZFXS27' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-ST2000LM007-1R8174_WDZFXS27-part3 IdLabel: ostree IdType: ext4 IdUUID: 05c7cd5b-40f9-47d7-a032-e98150535435 IdUsage: filesystem IdVersion: 1.0 MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sda3 ReadOnly: false Size: 1994565615616 Symlinks: /dev/disk/by-id/ata-ST2000LM007-1R8174_WDZFXS27-part3 /dev/disk/by-id/wwn-0x5000c500bd99cad5-part3 /dev/disk/by-label/ostree /dev/disk/by-partuuid/4f316229-26c0-47cc-8a5a-5787dd2d332e /dev/disk/by-path/pci-0000:00:17.0-ata-1-part3 /dev/disk/by-uuid/05c7cd5b-40f9-47d7-a032-e98150535435 UserspaceMountOptions: org.freedesktop.UDisks2.Filesystem: MountPoints: / /boot /sysroot /usr /var Size: 1994565615616 org.freedesktop.UDisks2.Partition: Flags: 0 IsContained: false IsContainer: false Name: Number: 3 Offset: 67108864 Size: 1994565615616 Table: '/org/freedesktop/UDisks2/block_devices/sda' Type: 4f68bce3-e8cd-4db1-96e7-fbcaf984b709 UUID: 4f316229-26c0-47cc-8a5a-5787dd2d332e /org/freedesktop/UDisks2/block_devices/sda5: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/sda5 DeviceNumber: 2053 Drive: '/org/freedesktop/UDisks2/drives/ST2000LM007_1R8174_WDZFXS27' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: by-id-ata-ST2000LM007-1R8174_WDZFXS27-part5 IdLabel: WINDRIVER IdType: ntfs IdUUID: F4725CF0725CB956 IdUsage: filesystem IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sda5 ReadOnly: false Size: 5766119424 Symlinks: /dev/disk/by-id/ata-ST2000LM007-1R8174_WDZFXS27-part5 /dev/disk/by-id/wwn-0x5000c500bd99cad5-part5 /dev/disk/by-label/WINDRIVER /dev/disk/by-partlabel/Basic\x20data\x20partition /dev/disk/by-partuuid/156f4e1f-cf4a-47e4-9166-7f3e092e2f79 /dev/disk/by-path/pci-0000:00:17.0-ata-1-part5 /dev/disk/by-uuid/F4725CF0725CB956 UserspaceMountOptions: org.freedesktop.UDisks2.Filesystem: MountPoints: Size: 0 org.freedesktop.UDisks2.Partition: Flags: 0 IsContained: false IsContainer: false Name: Basic data partition Number: 5 Offset: 1994632724480 Size: 5766119424 Table: '/org/freedesktop/UDisks2/block_devices/sda' Type: ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 UUID: 156f4e1f-cf4a-47e4-9166-7f3e092e2f79 /org/freedesktop/UDisks2/block_devices/zram0: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/zram0 DeviceNumber: 64512 Drive: '/' HintAuto: false HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: true Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/zram0 ReadOnly: false Size: 12326830080 Symlinks: UserspaceMountOptions: org.freedesktop.UDisks2.Swapspace: Active: true /org/freedesktop/UDisks2/drives/ST2000LM007_1R8174_WDZFXS27: org.freedesktop.UDisks2.Drive: CanPowerOff: false Configuration: {} ConnectionBus: Ejectable: false Id: ST2000LM007-1R8174-WDZFXS27 Media: MediaAvailable: true MediaChangeDetected: true MediaCompatibility: MediaRemovable: false Model: ST2000LM007-1R8174 Optical: false OpticalBlank: false OpticalNumAudioTracks: 0 OpticalNumDataTracks: 0 OpticalNumSessions: 0 OpticalNumTracks: 0 Removable: false Revision: ACM1 RotationRate: 5400 Seat: seat0 Serial: WDZFXS27 SiblingId: Size: 2000398934016 SortKey: 00coldplug/00fixed/sd____a TimeDetected: 1590252371180529 TimeMediaDetected: 1590252371180529 Vendor: WWN: 0x5000c500bd99cad5 org.freedesktop.UDisks2.Drive.Ata: AamEnabled: false AamSupported: false AamVendorRecommendedValue: 0 ApmEnabled: true ApmSupported: true PmEnabled: true PmSupported: true ReadLookaheadEnabled: true ReadLookaheadSupported: true SecurityEnhancedEraseUnitMinutes: 336 SecurityEraseUnitMinutes: 336 SecurityFrozen: true SmartEnabled: true SmartFailing: false SmartNumAttributesFailedInThePast: 0 SmartNumAttributesFailing: 0 SmartNumBadSectors: 88 SmartPowerOnSeconds: 3178800 SmartSelftestPercentRemaining: 0 SmartSelftestStatus: success SmartSupported: true SmartTemperature: 311.15000000000003 SmartUpdated: 1590254180 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=3985460k,nr_inodes=996365,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) cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,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) none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700) 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) 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/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/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime) /dev/sda3 on /sysroot type ext4 (rw,relatime,errors=remount-ro) /dev/sda3 on / type ext4 (rw,relatime,errors=remount-ro) /dev/sda3 on /boot type ext4 (rw,relatime,errors=remount-ro) /dev/sda3 on /usr type ext4 (ro,relatime,errors=remount-ro) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=1634) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /tmp type tmpfs (rw,nosuid,nodev) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) /dev/sda3 on /var type ext4 (rw,relatime,errors=remount-ro) fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) tmpfs on /run/user/1001 type tmpfs (rw,nosuid,nodev,relatime,size=802528k,mode=700,uid=1001,gid=1001) gvfsd-fuse on /run/user/1001/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1001,group_id=1001) /dev/fuse on /run/user/1001/doc type fuse (rw,nosuid,nodev,relatime,user_id=1001,group_id=1001) Sist. Arq. Tam. Usado Disp. Uso% Montado em devtmpfs 3,9G 0 3,9G 0% /dev tmpfs 3,9G 120M 3,8G 4% /dev/shm tmpfs 3,9G 1,8M 3,9G 1% /run tmpfs 5,0M 4,0K 5,0M 1% /run/lock tmpfs 3,9G 0 3,9G 0% /sys/fs/cgroup /dev/sda3 1,8T 452G 1,4T 25% /sysroot tmpfs 3,9G 4,0K 3,9G 1% /tmp tmpfs 784M 72K 784M 1% /run/user/1001 ====================== = Network interfaces = ====================== enp1s0f1: flags=4099 mtu 1500 ether 98:29:a6:e7:43:08 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Loopback Local) RX packets 55 bytes 4196 (4.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 55 bytes 4196 (4.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp2s0: flags=4163 mtu 1500 inet 192.168.0.34 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::c6c7:3fc7:b338:a37b prefixlen 64 scopeid 0x20 inet6 2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e prefixlen 64 scopeid 0x0 inet6 2804:14d:5ce6:9e6b::1001 prefixlen 128 scopeid 0x0 ether 5c:c9:d3:dd:a0:cd txqueuelen 1000 (Ethernet) RX packets 9999 bytes 8556245 (8.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 6116 bytes 1208427 (1.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ================== = rfkill devices = ================== rfkill0 name: acer-wireless type: wlan hard: 0 soft: 0 persistent: 0 state: 1 rfkill1 name: acer-bluetooth type: bluetooth hard: 0 soft: 0 persistent: 0 state: 1 rfkill2 name: hci0 type: bluetooth hard: 0 soft: 0 persistent: 0 state: 1 driver: btusb rfkill3 name: phy0 type: wlan hard: 0 soft: 0 persistent: 0 state: 1 driver: ath10k_pci ============ = Graphics = ============ Renderer: ============================ = Direct Rendering devices = ============================ renderD128 driver: i915 firmware_path: \_SB_.PCI0.GFX0 card0 driver: i915 firmware_path: \_SB_.PCI0.GFX0 card0-eDP-1 (enabled) status: connected dpms: On card0-HDMI-A-1 (disabled) status: disconnected dpms: Off =========== = Display = =========== Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (0x45) normal (normal left inverted right x axis y axis) 344mm x 193mm Identifier: 0x42 Timestamp: 362301 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: EDID: 00ffffffffffff000daedc1500000000 2d1901049522137802c3f59155549429 25505400000001010101010101010101 010101010101da1d56e250002030442d 470058c110000018000000fe004e3135 364247412d4542320a20000000fe0043 4d4e0a202020202020202020000000fe 004e3135364247412d4542320a2000f1 scaling mode: Full aspect supported: Full, Center, Full aspect max bpc: 12 range: (6, 12) Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 link-status: Good supported: Good, Bad CONNECTOR_ID: 86 supported: 86 non-desktop: 0 range: (0, 1) 1366x768 (0x45) 76.420MHz -HSync -VSync *current +preferred h: width 1366 start 1434 end 1479 total 1592 skew 0 clock 48.00KHz v: height 768 start 772 end 779 total 800 clock 60.00Hz 1360x768 (0x46) 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 (0x47) 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 1280x720 (0x48) 156.125MHz -HSync +VSync DoubleScan h: width 1280 start 1376 end 1512 total 1744 skew 0 clock 89.52KHz v: height 720 start 721 end 724 total 746 clock 60.00Hz 1280x720 (0x49) 120.750MHz +HSync -VSync DoubleScan h: width 1280 start 1304 end 1320 total 1360 skew 0 clock 88.79KHz v: height 720 start 721 end 724 total 740 clock 59.99Hz 1280x720 (0x4a) 74.500MHz -HSync +VSync h: width 1280 start 1344 end 1472 total 1664 skew 0 clock 44.77KHz v: height 720 start 723 end 728 total 748 clock 59.86Hz 1280x720 (0x4b) 63.750MHz +HSync -VSync h: width 1280 start 1328 end 1360 total 1440 skew 0 clock 44.27KHz v: height 720 start 723 end 728 total 741 clock 59.74Hz 1024x768 (0x4c) 133.475MHz -HSync +VSync DoubleScan h: width 1024 start 1100 end 1212 total 1400 skew 0 clock 95.34KHz v: height 768 start 768 end 770 total 794 clock 60.04Hz 1024x768 (0x4d) 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 960x720 (0x4e) 117.000MHz -HSync +VSync DoubleScan h: width 960 start 1024 end 1128 total 1300 skew 0 clock 90.00KHz v: height 720 start 720 end 722 total 750 clock 60.00Hz 928x696 (0x4f) 109.150MHz -HSync +VSync DoubleScan h: width 928 start 976 end 1088 total 1264 skew 0 clock 86.35KHz v: height 696 start 696 end 698 total 719 clock 60.05Hz 896x672 (0x50) 102.400MHz -HSync +VSync DoubleScan h: width 896 start 960 end 1060 total 1224 skew 0 clock 83.66KHz v: height 672 start 672 end 674 total 697 clock 60.01Hz 1024x576 (0x51) 98.500MHz -HSync +VSync DoubleScan h: width 1024 start 1092 end 1200 total 1376 skew 0 clock 71.58KHz v: height 576 start 577 end 580 total 597 clock 59.95Hz 1024x576 (0x52) 78.375MHz +HSync -VSync DoubleScan h: width 1024 start 1048 end 1064 total 1104 skew 0 clock 70.99KHz v: height 576 start 577 end 580 total 592 clock 59.96Hz 1024x576 (0x53) 46.500MHz -HSync +VSync h: width 1024 start 1064 end 1160 total 1296 skew 0 clock 35.88KHz v: height 576 start 579 end 584 total 599 clock 59.90Hz 1024x576 (0x54) 42.000MHz +HSync -VSync h: width 1024 start 1072 end 1104 total 1184 skew 0 clock 35.47KHz v: height 576 start 579 end 584 total 593 clock 59.82Hz 960x600 (0x55) 96.625MHz -HSync +VSync DoubleScan h: width 960 start 1028 end 1128 total 1296 skew 0 clock 74.56KHz v: height 600 start 601 end 604 total 622 clock 59.93Hz 960x600 (0x56) 77.000MHz +HSync -VSync DoubleScan h: width 960 start 984 end 1000 total 1040 skew 0 clock 74.04KHz v: height 600 start 601 end 604 total 617 clock 60.00Hz 960x540 (0x57) 86.500MHz -HSync +VSync DoubleScan h: width 960 start 1024 end 1124 total 1288 skew 0 clock 67.16KHz v: height 540 start 541 end 544 total 560 clock 59.96Hz 960x540 (0x58) 69.250MHz +HSync -VSync DoubleScan h: width 960 start 984 end 1000 total 1040 skew 0 clock 66.59KHz v: height 540 start 541 end 544 total 555 clock 59.99Hz 960x540 (0x59) 40.750MHz -HSync +VSync h: width 960 start 992 end 1088 total 1216 skew 0 clock 33.51KHz v: height 540 start 543 end 548 total 562 clock 59.63Hz 960x540 (0x5a) 37.250MHz +HSync -VSync h: width 960 start 1008 end 1040 total 1120 skew 0 clock 33.26KHz v: height 540 start 543 end 548 total 556 clock 59.82Hz 800x600 (0x5b) 81.000MHz +HSync +VSync DoubleScan h: width 800 start 832 end 928 total 1080 skew 0 clock 75.00KHz v: height 600 start 600 end 602 total 625 clock 60.00Hz 800x600 (0x5c) 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 (0x5d) 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 840x525 (0x5e) 73.125MHz -HSync +VSync DoubleScan h: width 840 start 892 end 980 total 1120 skew 0 clock 65.29KHz v: height 525 start 526 end 529 total 544 clock 60.01Hz 840x525 (0x5f) 59.500MHz +HSync -VSync DoubleScan h: width 840 start 864 end 880 total 920 skew 0 clock 64.67KHz v: height 525 start 526 end 529 total 540 clock 59.88Hz 864x486 (0x60) 32.500MHz -HSync +VSync h: width 864 start 888 end 968 total 1072 skew 0 clock 30.32KHz v: height 486 start 489 end 494 total 506 clock 59.92Hz 864x486 (0x61) 30.500MHz +HSync -VSync h: width 864 start 912 end 944 total 1024 skew 0 clock 29.79KHz v: height 486 start 489 end 494 total 500 clock 59.57Hz 800x512 (0x62) 51.562MHz +HSync +VSync DoubleScan h: width 800 start 800 end 828 total 832 skew 0 clock 61.97KHz v: height 512 start 512 end 514 total 515 clock 60.17Hz 700x525 (0x63) 61.000MHz +HSync +VSync DoubleScan h: width 700 start 744 end 820 total 940 skew 0 clock 64.89KHz v: height 525 start 526 end 532 total 541 clock 59.98Hz 800x450 (0x64) 59.125MHz -HSync +VSync DoubleScan h: width 800 start 848 end 928 total 1056 skew 0 clock 55.99KHz v: height 450 start 451 end 454 total 467 clock 59.95Hz 800x450 (0x65) 48.750MHz +HSync -VSync DoubleScan h: width 800 start 824 end 840 total 880 skew 0 clock 55.40KHz v: height 450 start 451 end 454 total 463 clock 59.82Hz 640x512 (0x66) 54.000MHz +HSync +VSync DoubleScan h: width 640 start 664 end 720 total 844 skew 0 clock 63.98KHz v: height 512 start 512 end 514 total 533 clock 60.02Hz 720x450 (0x67) 53.250MHz -HSync +VSync DoubleScan h: width 720 start 760 end 836 total 952 skew 0 clock 55.93KHz v: height 450 start 451 end 454 total 467 clock 59.89Hz 700x450 (0x68) 51.750MHz -HSync +VSync DoubleScan h: width 700 start 740 end 812 total 924 skew 0 clock 56.01KHz v: height 450 start 451 end 456 total 467 clock 59.96Hz 700x450 (0x69) 43.250MHz +HSync -VSync DoubleScan h: width 700 start 724 end 740 total 780 skew 0 clock 55.45KHz v: height 450 start 451 end 456 total 463 clock 59.88Hz 640x480 (0x6a) 54.000MHz +HSync +VSync DoubleScan h: width 640 start 688 end 744 total 900 skew 0 clock 60.00KHz v: height 480 start 480 end 482 total 500 clock 60.00Hz 640x480 (0x6b) 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 (0x6c) 22.500MHz -HSync +VSync h: width 720 start 744 end 808 total 896 skew 0 clock 25.11KHz v: height 405 start 408 end 413 total 422 clock 59.51Hz 720x405 (0x6d) 21.750MHz +HSync -VSync h: width 720 start 768 end 800 total 880 skew 0 clock 24.72KHz v: height 405 start 408 end 413 total 419 clock 58.99Hz 684x384 (0x6e) 42.625MHz -HSync +VSync DoubleScan h: width 684 start 720 end 788 total 892 skew 0 clock 47.79KHz v: height 384 start 385 end 390 total 399 clock 59.88Hz 684x384 (0x6f) 36.125MHz +HSync -VSync DoubleScan h: width 684 start 708 end 724 total 764 skew 0 clock 47.28KHz v: height 384 start 385 end 390 total 395 clock 59.85Hz 680x384 (0x70) 42.375MHz -HSync +VSync DoubleScan h: width 680 start 716 end 784 total 888 skew 0 clock 47.72KHz v: height 384 start 385 end 390 total 399 clock 59.80Hz 680x384 (0x71) 36.000MHz +HSync -VSync DoubleScan h: width 680 start 704 end 720 total 760 skew 0 clock 47.37KHz v: height 384 start 385 end 390 total 395 clock 59.96Hz 640x400 (0x72) 41.750MHz -HSync +VSync DoubleScan h: width 640 start 676 end 740 total 840 skew 0 clock 49.70KHz v: height 400 start 401 end 404 total 415 clock 59.88Hz 640x400 (0x73) 35.500MHz +HSync -VSync DoubleScan h: width 640 start 664 end 680 total 720 skew 0 clock 49.31KHz v: height 400 start 401 end 404 total 411 clock 59.98Hz 576x432 (0x74) 40.810MHz -HSync +VSync DoubleScan h: width 576 start 608 end 668 total 760 skew 0 clock 53.70KHz v: height 432 start 432 end 434 total 447 clock 60.06Hz 640x360 (0x75) 37.250MHz -HSync +VSync DoubleScan h: width 640 start 672 end 736 total 832 skew 0 clock 44.77KHz v: height 360 start 361 end 364 total 374 clock 59.86Hz 640x360 (0x76) 31.875MHz +HSync -VSync DoubleScan h: width 640 start 664 end 680 total 720 skew 0 clock 44.27KHz v: height 360 start 361 end 364 total 370 clock 59.83Hz 640x360 (0x77) 18.000MHz -HSync +VSync h: width 640 start 664 end 720 total 800 skew 0 clock 22.50KHz v: height 360 start 363 end 368 total 376 clock 59.84Hz 640x360 (0x78) 17.750MHz +HSync -VSync h: width 640 start 688 end 720 total 800 skew 0 clock 22.19KHz v: height 360 start 363 end 368 total 374 clock 59.32Hz 512x384 (0x79) 32.500MHz -HSync -VSync DoubleScan h: width 512 start 524 end 592 total 672 skew 0 clock 48.36KHz v: height 384 start 385 end 388 total 403 clock 60.00Hz 512x288 (0x7a) 23.250MHz -HSync +VSync DoubleScan h: width 512 start 532 end 580 total 648 skew 0 clock 35.88KHz v: height 288 start 289 end 292 total 299 clock 60.00Hz 512x288 (0x7b) 21.000MHz +HSync -VSync DoubleScan h: width 512 start 536 end 552 total 592 skew 0 clock 35.47KHz v: height 288 start 289 end 292 total 296 clock 59.92Hz 480x270 (0x7c) 20.375MHz -HSync +VSync DoubleScan h: width 480 start 496 end 544 total 608 skew 0 clock 33.51KHz v: height 270 start 271 end 274 total 281 clock 59.63Hz 480x270 (0x7d) 18.625MHz +HSync -VSync DoubleScan h: width 480 start 504 end 520 total 560 skew 0 clock 33.26KHz v: height 270 start 271 end 274 total 278 clock 59.82Hz 400x300 (0x7e) 20.000MHz +HSync +VSync DoubleScan h: width 400 start 420 end 484 total 528 skew 0 clock 37.88KHz v: height 300 start 300 end 302 total 314 clock 60.32Hz 400x300 (0x7f) 18.000MHz +HSync +VSync DoubleScan h: width 400 start 412 end 448 total 512 skew 0 clock 35.16KHz v: height 300 start 300 end 301 total 312 clock 56.34Hz 432x243 (0x80) 16.250MHz -HSync +VSync DoubleScan h: width 432 start 444 end 484 total 536 skew 0 clock 30.32KHz v: height 243 start 244 end 247 total 253 clock 59.92Hz 432x243 (0x81) 15.250MHz +HSync -VSync DoubleScan h: width 432 start 456 end 472 total 512 skew 0 clock 29.79KHz v: height 243 start 244 end 247 total 250 clock 59.57Hz 320x240 (0x82) 12.587MHz -HSync -VSync DoubleScan h: width 320 start 328 end 376 total 400 skew 0 clock 31.47KHz v: height 240 start 245 end 246 total 262 clock 60.05Hz 360x202 (0x83) 11.250MHz -HSync +VSync DoubleScan h: width 360 start 372 end 404 total 448 skew 0 clock 25.11KHz v: height 202 start 204 end 206 total 211 clock 59.51Hz 360x202 (0x84) 10.875MHz +HSync -VSync DoubleScan h: width 360 start 384 end 400 total 440 skew 0 clock 24.72KHz v: height 202 start 204 end 206 total 209 clock 59.13Hz 320x180 (0x85) 9.000MHz -HSync +VSync DoubleScan h: width 320 start 332 end 360 total 400 skew 0 clock 22.50KHz v: height 180 start 181 end 184 total 188 clock 59.84Hz 320x180 (0x86) 8.875MHz +HSync -VSync DoubleScan h: width 320 start 344 end 360 total 400 skew 0 clock 22.19KHz v: height 180 start 181 end 184 total 187 clock 59.32Hz HDMI-1 disconnected (normal left inverted right x axis y axis) Identifier: 0x43 Timestamp: 362301 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: HDCP Content Type: HDCP Type0 supported: HDCP Type0, HDCP Type1 Content Protection: Undesired supported: Undesired, Desired, Enabled max bpc: 12 range: (8, 12) content type: No Data supported: No Data, Graphics, Photo, Cinema, Game Colorspace: Default supported: Default, SMPTE_170M_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, DCI-P3_RGB_D65, DCI-P3_RGB_Theater aspect ratio: Automatic supported: Automatic, 4:3, 16:9 Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on link-status: Good supported: Good, Bad CONNECTOR_ID: 92 supported: 92 non-desktop: 0 range: (0, 1) ============== = Pulseaudio = ============== Placa #0 Nome: alsa_card.pci-0000_00_1f.3 Driver: module-alsa-card.c Módulo proprietário: 7 Propriedades: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xb1320000 irq 132" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:1f.3" sysfs.path = "/devices/pci0000:00/0000:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "9d71" device.product.name = "Sunrise Point-LP HD Audio" device.form_factor = "internal" device.string = "0" device.description = "Áudio interno" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Perfis: input:analog-stereo: Entrada de Estéreo analógico (destino: 0, fontes: 1, prioridade: 65, disponível: sim) output:analog-stereo: Saída de Estéreo analógico (destino: 1, fontes: 0, prioridade: 6500, disponível: sim) output:analog-stereo+input:analog-stereo: Duplex estéreo analógico (destino: 1, fontes: 1, prioridade: 6565, disponível: sim) output:hdmi-stereo: Saída de Digital Stereo (HDMI) (destino: 1, fontes: 0, prioridade: 5900, disponível: não) output:hdmi-stereo+input:analog-stereo: Saída de Digital Stereo (HDMI) + Entrada de Estéreo analógico (destino: 1, fontes: 1, prioridade: 5965, disponível: não) output:hdmi-stereo-extra1: Saída de Digital Stereo (HDMI 2) (destino: 1, fontes: 0, prioridade: 5700, disponível: não) output:hdmi-stereo-extra1+input:analog-stereo: Saída de Digital Stereo (HDMI 2) + Entrada de Estéreo analógico (destino: 1, fontes: 1, prioridade: 5765, disponível: não) output:hdmi-stereo-extra2: Saída de Digital Stereo (HDMI 3) (destino: 1, fontes: 0, prioridade: 5700, disponível: não) output:hdmi-stereo-extra2+input:analog-stereo: Saída de Digital Stereo (HDMI 3) + Entrada de Estéreo analógico (destino: 1, fontes: 1, prioridade: 5765, disponível: não) output:hdmi-stereo-extra3: Saída de Digital Stereo (HDMI 4) (destino: 1, fontes: 0, prioridade: 5700, disponível: não) output:hdmi-stereo-extra3+input:analog-stereo: Saída de Digital Stereo (HDMI 4) + Entrada de Estéreo analógico (destino: 1, fontes: 1, prioridade: 5765, disponível: não) output:hdmi-stereo-extra4: Saída de Digital Stereo (HDMI 5) (destino: 1, fontes: 0, prioridade: 5700, disponível: não) output:hdmi-stereo-extra4+input:analog-stereo: Saída de Digital Stereo (HDMI 5) + Entrada de Estéreo analógico (destino: 1, fontes: 1, prioridade: 5765, disponível: não) off: Desligado (destino: 0, fontes: 0, prioridade: 0, disponível: sim) Perfil ativo: output:analog-stereo+input:analog-stereo Portas: analog-input-internal-mic: Microfone interno (priority: 8900, latency offset: 0 usec) Propriedades: device.icon_name = "audio-input-microphone" Parte de perfil/perfis: input:analog-stereo, output:analog-stereo+input:analog-stereo, output:hdmi-stereo+input:analog-stereo, output:hdmi-stereo-extra1+input:analog-stereo, output:hdmi-stereo-extra2+input:analog-stereo, output:hdmi-stereo-extra3+input:analog-stereo, output:hdmi-stereo-extra4+input:analog-stereo analog-input-headset-mic: Microfone de headset (priority: 8800, latency offset: 0 usec, not available) Propriedades: device.icon_name = "audio-input-microphone" Parte de perfil/perfis: input:analog-stereo, output:analog-stereo+input:analog-stereo, output:hdmi-stereo+input:analog-stereo, output:hdmi-stereo-extra1+input:analog-stereo, output:hdmi-stereo-extra2+input:analog-stereo, output:hdmi-stereo-extra3+input:analog-stereo, output:hdmi-stereo-extra4+input:analog-stereo analog-output-speaker: Alto-falantes (priority: 7900, latency offset: 0 usec) Propriedades: device.icon_name = "audio-speakers" Parte de perfil/perfis: output:analog-stereo, output:analog-stereo+input:analog-stereo analog-output-headphones: Fones de ouvido (priority: 9900, latency offset: 0 usec, not available) Propriedades: device.icon_name = "audio-headphones" Parte de perfil/perfis: output:analog-stereo, output:analog-stereo+input:analog-stereo hdmi-output-0: HDMI / DisplayPort (priority: 8900, latency offset: 0 usec, not available) Propriedades: device.icon_name = "video-display" Parte de perfil/perfis: output:hdmi-stereo, output:hdmi-stereo+input:analog-stereo hdmi-output-1: HDMI / DisplayPort 2 (priority: 8800, latency offset: 0 usec, not available) Propriedades: device.icon_name = "video-display" Parte de perfil/perfis: output:hdmi-stereo-extra1, output:hdmi-stereo-extra1+input:analog-stereo hdmi-output-2: HDMI / DisplayPort 3 (priority: 8700, latency offset: 0 usec, not available) Propriedades: device.icon_name = "video-display" Parte de perfil/perfis: output:hdmi-stereo-extra2, output:hdmi-stereo-extra2+input:analog-stereo hdmi-output-3: HDMI / DisplayPort 4 (priority: 8600, latency offset: 0 usec, not available) Propriedades: device.icon_name = "video-display" Parte de perfil/perfis: output:hdmi-stereo-extra3, output:hdmi-stereo-extra3+input:analog-stereo hdmi-output-4: HDMI / DisplayPort 5 (priority: 8500, latency offset: 0 usec, not available) Propriedades: device.icon_name = "video-display" Parte de perfil/perfis: output:hdmi-stereo-extra4, output:hdmi-stereo-extra4+input:analog-stereo Fonte #0 Estado: SUSPENDED Nome: alsa_output.pci-0000_00_1f.3.analog-stereo.monitor Descrição: Monitor of Áudio interno Estéreo analógico Driver: module-alsa-card.c Especificação da amostragem: s16le 2ch 44100Hz Mapa dos canais: front-left,front-right Módulo proprietário: 7 Mudo: não Volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB balanço 0,00 Volume base: 65536 / 100% / 0,00 dB Monitor do destino: alsa_output.pci-0000_00_1f.3.analog-stereo Latência: 0 useg, 0 useg configurado Sinalizadores: DECIBEL_VOLUME LATENCY Propriedades: device.description = "Monitor of Áudio interno Estéreo analógico" device.class = "monitor" alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xb1320000 irq 132" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:1f.3" sysfs.path = "/devices/pci0000:00/0000:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "9d71" device.product.name = "Sunrise Point-LP HD Audio" device.form_factor = "internal" device.string = "0" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Formatos: pcm Fonte #1 Estado: SUSPENDED Nome: alsa_input.pci-0000_00_1f.3.analog-stereo Descrição: Áudio interno Estéreo analógico Driver: module-alsa-card.c Especificação da amostragem: s16le 2ch 44100Hz Mapa dos canais: front-left,front-right Módulo proprietário: 7 Mudo: não Volume: front-left: 10387 / 16% / -48,00 dB, front-right: 10387 / 16% / -48,00 dB balanço 0,00 Volume base: 6554 / 10% / -60,00 dB Monitor do destino: n/d Latência: 0 useg, 0 useg configurado Sinalizadores: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Propriedades: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC255 Analog" alsa.id = "ALC255 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 0xb1320000 irq 132" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:1f.3" sysfs.path = "/devices/pci0000:00/0000:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "9d71" device.product.name = "Sunrise Point-LP HD Audio" 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 = "Estéreo analógico" device.description = "Áudio interno Estéreo analógico" alsa.mixer_name = "Realtek ALC255" alsa.components = "HDA:10ec0255,10251193,00100002 HDA:8086280b,80860101,00100000" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Portas: analog-input-internal-mic: Microfone interno (priority: 8900) analog-input-headset-mic: Microfone de headset (priority: 8800, not available) Porta ativa: analog-input-internal-mic Formatos: pcm Destino #0 Estado: SUSPENDED Nome: alsa_output.pci-0000_00_1f.3.analog-stereo Descrição: Áudio interno Estéreo analógico Driver: module-alsa-card.c Especificação da amostragem: s16le 2ch 44100Hz Mapa dos canais: front-left,front-right Módulo proprietário: 7 Mudo: não Volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB balanço 0,00 Volume base: 65536 / 100% / 0,00 dB Fonte de monitoração: alsa_output.pci-0000_00_1f.3.analog-stereo.monitor Latência: 0 useg, 0 useg configurado Sinalizadores: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Propriedades: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC255 Analog" alsa.id = "ALC255 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 0xb1320000 irq 132" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:1f.3" sysfs.path = "/devices/pci0000:00/0000:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "9d71" device.product.name = "Sunrise Point-LP HD Audio" 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 = "Estéreo analógico" device.description = "Áudio interno Estéreo analógico" alsa.mixer_name = "Realtek ALC255" alsa.components = "HDA:10ec0255,10251193,00100002 HDA:8086280b,80860101,00100000" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Portas: analog-output-speaker: Alto-falantes (priority: 7900) analog-output-headphones: Fones de ouvido (priority: 9900, not available) Porta ativa: analog-output-speaker Formatos: pcm ================= = Input devices = ================= I: Bus=0019 Vendor=0000 Product=0005 Version=0000 N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:19/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 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/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor=0000 Product=0001 Version=0000 N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10000000000000 0 I: Bus=0019 Vendor=0000 Product=0001 Version=0000 N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10000000000000 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=10000 c020000000000 0 0 700f02000003 3802078f870f401 febfffdfffefffff fffffffffffffffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor=0000 Product=0006 Version=0000 N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b00000000 0 0 0 I: Bus=0019 Vendor=1025 Product=1229 Version=0000 N: Name="Acer Wireless Radio Control" P: Phys=acer-wireless/input0 S: Sysfs=/devices/LNXSYSTM:00/10251229:00/input/input6 U: Uniq= H: Handlers=rfkill kbd event6 B: PROP=0 B: EV=3 B: KEY=80000000000000 0 0 0 I: Bus=0019 Vendor=0000 Product=0000 Version=0000 N: Name="Acer WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input7 U: Uniq= H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=13 B: KEY=1c0000 0 0 0 0 1600800000c00 300000 10000000000000 0 B: MSC=10 I: Bus=0018 Vendor=06cb Product=7db7 Version=0100 N: Name="SYNA7DB5:01 06CB:7DB7 Mouse" P: Phys=i2c-SYNA7DB5:01 S: Sysfs=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-SYNA7DB5:01/0018:06CB:7DB7.0001/input/input11 U: Uniq= H: Handlers=mouse0 event8 B: PROP=0 B: EV=17 B: KEY=30000 0 0 0 0 B: REL=3 B: MSC=10 I: Bus=0018 Vendor=06cb Product=7db7 Version=0100 N: Name="SYNA7DB5:01 06CB:7DB7 Touchpad" P: Phys=i2c-SYNA7DB5:01 S: Sysfs=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-SYNA7DB5:01/0018:06CB:7DB7.0001/input/input12 U: Uniq= H: Handlers=mouse1 event9 B: PROP=5 B: EV=1b B: KEY=e520 10000 0 0 0 0 B: ABS=2e0800000000003 B: MSC=20 I: Bus=0003 Vendor=0408 Product=a061 Version=0004 N: Name="HD User Facing: HD User Facing" P: Phys=usb-0000:00:14.0-7/button S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/input/input14 U: Uniq= H: Handlers=kbd event10 B: PROP=0 B: EV=3 B: KEY=100000 0 0 0 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel PCH Front Headphone" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input15 U: Uniq= H: Handlers=event11 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:1f.3/sound/card0/input16 U: Uniq= H: Handlers=event12 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:1f.3/sound/card0/input17 U: Uniq= H: Handlers=event13 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:1f.3/sound/card0/input18 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input19 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input20 U: Uniq= H: Handlers=event16 B: PROP=0 B: EV=21 B: SW=140 =============== = PCI devices = =============== 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5904] (rev 02) Subsystem: Acer Incorporated [ALI] Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1025:1193] Flags: bus master, fast devsel, latency 0 Capabilities: Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1193] Flags: bus master, fast devsel, latency 0, IRQ 127 Memory at b0000000 (64-bit, non-prefetchable) [size=16M] Memory at a0000000 (64-bit, prefetchable) [size=256M] I/O ports at 4000 [size=64] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Acer Incorporated [ALI] Sunrise Point-LP USB 3.0 xHCI Controller [1025:1193] Flags: medium devsel, IRQ 124 Memory at b1310000 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: xhci_hcd 00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 [8086:9d60] (rev 21) Subsystem: Acer Incorporated [ALI] Sunrise Point-LP Serial IO I2C Controller [1025:1193] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at b132a000 (64-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 [8086:9d61] (rev 21) Subsystem: Acer Incorporated [ALI] Sunrise Point-LP Serial IO I2C Controller [1025:1193] Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at b132b000 (64-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Acer Incorporated [ALI] Sunrise Point-LP CSME HECI [1025:1193] Flags: bus master, fast devsel, latency 0, IRQ 128 Memory at b132c000 (64-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: mei_me Kernel modules: mei_me 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] [8086:9d03] (rev 21) (prog-if 01 [AHCI 1.0]) Subsystem: Acer Incorporated [ALI] Sunrise Point-LP SATA Controller [AHCI mode] [1025:1193] Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 125 Memory at b1328000 (32-bit, non-prefetchable) [size=8K] Memory at b132f000 (32-bit, non-prefetchable) [size=256] I/O ports at 4080 [size=8] I/O ports at 4088 [size=4] I/O ports at 4060 [size=32] Memory at b132d000 (32-bit, non-prefetchable) [size=2K] Capabilities: Kernel driver in use: ahci Kernel modules: ahci 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 [8086:9d14] (rev f1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 122 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 00003000-00003fff Memory behind bridge: b1200000-b12fffff Capabilities: Kernel driver in use: pcieport 00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 [8086:9d15] (rev f1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 123 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 Memory behind bridge: b1000000-b11fffff Capabilities: Kernel driver in use: pcieport 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point LPC Controller/eSPI Controller [8086:9d4e] (rev 21) Subsystem: Acer Incorporated [ALI] Sunrise Point LPC Controller/eSPI Controller [1025:1193] Flags: bus master, medium devsel, latency 0 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) Subsystem: Acer Incorporated [ALI] Sunrise Point-LP PMC [1025:1193] Flags: bus master, fast devsel, latency 0 Memory at b1324000 (32-bit, non-prefetchable) [size=16K] 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) (prog-if 80) Subsystem: Acer Incorporated [ALI] Sunrise Point-LP HD Audio [1025:1193] Flags: bus master, fast devsel, latency 32, IRQ 132 Memory at b1320000 (64-bit, non-prefetchable) [size=16K] Memory at b1300000 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21) Subsystem: Acer Incorporated [ALI] Sunrise Point-LP SMBus [1025:1193] Flags: medium devsel, IRQ 255 Memory at b132e000 (64-bit, non-prefetchable) [size=256] I/O ports at 4040 [size=32] Kernel modules: i2c_i801 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader [10ec:5287] (rev 01) Subsystem: Acer Incorporated [ALI] RTL8411B PCI Express Card Reader [1025:1193] Flags: bus master, fast devsel, latency 0, IRQ 126 Memory at b1205000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at b1210000 [disabled] [size=64K] Capabilities: Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci 01:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: Acer Incorporated [ALI] RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1025:1193] Flags: bus master, fast devsel, latency 0, IRQ 16 I/O ports at 3000 [size=256] Memory at b1204000 (64-bit, non-prefetchable) [size=4K] Memory at b1200000 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: r8169 Kernel modules: r8169 02:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 31) Subsystem: Lite-On Communications Inc QCA9377 802.11ac Wireless Network Adapter [11ad:08a6] Flags: bus master, fast devsel, latency 0, IRQ 131 Memory at b1000000 (64-bit, non-prefetchable) [size=2M] Capabilities: Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci =============== = USB devices = =============== Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:a061 Quanta Computer, Inc. Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub =============== = MMC devices = =============== mmc0 firmware_path: \_SB_.PCI0.RP05.PXSX driver: rtsx_pci_sdmmc =============== = I2C devices = =============== i2c-0 name: i915 gmbus dpc driver: i915 i2c-1 name: i915 gmbus dpb driver: i915 i2c-2 name: i915 gmbus dpd driver: i915 i2c-3 name: DPDDC-A i2c-4 name: Synopsys DesignWare I2C adapter firmware_path: \_SB_.PCI0.I2C0 driver: i2c_designware i2c-5 name: Synopsys DesignWare I2C adapter firmware_path: \_SB_.PCI0.I2C1 driver: i2c_designware i2c-SYNA7DB5:01 name: SYNA7DB5:01 firmware_path: \_SB_.PCI0.I2C1.TPAD driver: i2c_hid ================ = ALSA devices = ================ 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xb1320000 irq 132 ============= = Intel HDA = ============= card0 codec#0: Codec: Realtek ALC255 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0255 Subsystem Id: 0x10251193 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="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: [0x57 0x57] Converter: stream=0, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC255 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x57, nsteps=0x57, stepsize=0x02, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=0, channel=0 PCM: rates [0x60]: 44100 48000 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=D0, actual=D0 Node 0x07 [Vendor Defined Widget] wcaps 0xf00000: Mono 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 Device: name="ALC255 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=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=D0, actual=D0 Connection: 1 0x22 Node 0x0a [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x0b [Audio Mixer] wcaps 0x20010b: Stereo Amp-In Control: name="Headset Mic Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=1, ofs=0 Control: name="Headset Mic Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=In, idx=1, ofs=0 Control: name="Beep Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=4, ofs=0 Control: name="Beep Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=In, idx=4, ofs=0 Amp-In caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1 Amp-In vals: [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] Connection: 5 0x18 0x19 0x1a 0x1b 0x1d Node 0x0c [Audio Mixer] wcaps 0x20010b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] [0x80 0x80] Connection: 2 0x02 0x0b Node 0x0d [Audio Mixer] wcaps 0x20010b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] [0x80 0x80] Connection: 2 0x03 0x0b Node 0x0e [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x0f [Audio Mixer] wcaps 0x20010a: Mono Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] Connection: 1 0x0d Node 0x10 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x11 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In Control: name="Internal Mic Boost Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-In vals: [0x00 0x00] Pincap 0x00000020: IN Pin Default 0x90a60140: [Fixed] Mic at Int N/A Conn = Digital, Color = Unknown DefAssociation = 0x4, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x20: IN Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x13 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x14 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Control: name="Speaker Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x00010014: OUT EAPD Detect EAPD 0x2: EAPD Pin Default 0x90171120: [Fixed] Speaker at Int N/A Conn = Analog, Color = Black DefAssociation = 0x2, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 1 0x0c Node 0x15 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x16 [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x17 [Pin Complex] wcaps 0x40050c: Mono Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x80] Pincap 0x00000010: OUT Pin Default 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=D0, actual=D0 Connection: 1 0x0f 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=D0, actual=D0 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=D0, actual=D0 Node 0x1a [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: 0x00: VREF_HIZ 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 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: [0x80 0x80] Pincap 0x0001373c: IN OUT HP EAPD Detect Vref caps: HIZ 50 GRD 80 100 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: 0x20: IN VREF_HIZ Unsolicited: tag=00, enabled=0 Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 2 0x0c* 0x0d Node 0x1c [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x1d [Pin Complex] wcaps 0x400400: Mono Pincap 0x00000020: IN Pin Default 0x40700001: [N/A] Modem Hand at Ext N/A Conn = Unknown, Color = Unknown DefAssociation = 0x0, Sequence = 0x1 Pin-ctls: 0x20: IN Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 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=D0, actual=D0 Connection: 1 0x06 Node 0x1f [Vendor Defined Widget] wcaps 0xf00000: Mono Node 0x20 [Vendor Defined Widget] wcaps 0xf00040: Mono Processing caps: benign=0, ncoeff=76 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 0x02211030: [Jack] HP Out at Ext Front Conn = 1/8, Color = Black DefAssociation = 0x3, Sequence = 0x0 Pin-ctls: 0xc0: OUT HP Unsolicited: tag=01, enabled=1 Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 2 0x0c 0x0d* Node 0x22 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] Connection: 6 0x18 0x19 0x1a 0x1b 0x1d 0x0b Node 0x23 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x00 0x00] Connection: 7 0x18 0x19 0x1a 0x1b 0x1d 0x0b 0x12 card0 codec#2: Codec: Intel Kabylake HDMI Address: 2 AFG Function Id: 0x1 (unsol 0) Vendor Id: 0x8086280b 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 Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x0b000094: OUT Detect HBR HDMI DP Pin Default 0x18560010: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0x1, Sequence = 0x0 Pin-ctls: 0x00: Unsolicited: tag=00, enabled=0 Power states: D0 D3 EPSS Power: setting=D0, actual=D0 Devices: 0 Connection: 0 In-driver Connection: 3 0x02 0x03 0x04 Node 0x06 [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x0b000094: OUT Detect HBR HDMI DP Pin Default 0x18560010: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0x1, Sequence = 0x0 Pin-ctls: 0x00: Unsolicited: tag=00, enabled=0 Power states: D0 D3 EPSS Power: setting=D0, actual=D0 Devices: 0 Connection: 0 In-driver Connection: 3 0x02 0x03 0x04 Node 0x07 [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x0b000094: OUT Detect HBR HDMI DP Pin Default 0x18560010: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0x1, Sequence = 0x0 Pin-ctls: 0x00: Unsolicited: tag=00, enabled=0 Power states: D0 D3 EPSS Power: setting=D0, actual=D0 Devices: 0 Connection: 0 In-driver Connection: 3 0x02 0x03 0x04 Node 0x08 [Vendor Defined Widget] wcaps 0xf00000: Mono hwC0D0: vendor: 0x10ec0255 subsystem: 0x10251193 init_pin_configs: 0x12 0x90a60140 0x14 0x90171120 0x17 0x40000000 0x18 0x411111f0 0x19 0x411111f0 0x1a 0x411111f0 0x1b 0x411111f0 0x1d 0x40700001 0x1e 0x411111f0 0x21 0x02211030 driver_pin_configs: 0x19 0x01a1913c hwC0D2: vendor: 0x8086280b subsystem: 0x80860101 init_pin_configs: 0x05 0x18560010 0x06 0x18560010 0x07 0x18560010 ============ = Printers = ============ CUPS status: ------------ scheduler is running no system default destination device for L565: dnssd://EPSON%20L565%20Series._ipp._tcp.local/?uuid=cfe92100-67c4-11d4-a45f-44d2444ba540 L565 accepting requests since Sat Jan 18 21:22:31 2020 printer L565 is idle. enabled since Sat Jan 18 21:22:31 2020 Contents for /etc/cups/ppd/L565.ppd: ------------------------------------ not available =============== = Temperature = =============== +27.8°C ==================== = Chromium plugins = ==================== Flash Version: 32.0.0.371 Widevine Version: 4.10.1582.2 ========== = 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.15.0.1 License LGPL Source module gst-libav Binary package GStreamer libav Plugins (unknown Debian derivative) Origin URL http://packages.qa.debian.org/gst-libav1.0 avenc_ac3: libav ATSC A/52A (AC-3) encoder avenc_mp2: libav MP2 (MPEG audio layer 2) encoder avdec_ac3: libav ATSC A/52A (AC-3) decoder avdec_mp3: libav MP3 (MPEG audio layer 3) decoder avdec_vp3: libav On2 VP3 decoder avdec_vp8: libav On2 VP8 decoder avdec_vp9: libav Google VP9 decoder avdeinterlace: libav Deinterlace element 8 features: +-- 8 elements Arquivos colocados na lista negra: Contagem total: 0 arquivo na lista negra =================== = Flatpak remotes = =================== eos-apps Endless Applications https://ostree.endlessm.com/ostree/eos-apps com.endlessm.Apps - 1 system - - - - eos-runtimes Endless OS and Runtimes https://ostree.endlessm.com/ostree/eos-amd64 - - 1 system - - - - eos-sdk Endless Runtime and SDK https://ostree.endlessm.com/ostree/eos-sdk com.endlessm.Sdk - 1 system - - - - flathub Flathub https://dl.flathub.org/repo/ - - 1 system - - - - ==================== = Flatpak runtimes = ==================== Locale com.adobe.Flash_Player_Projector.Locale stable x86_64 flathub system com.adobe.Flash_Player_Projector.Locale/x86_64/stable 01d0ab2882ef - 14,1 MB system,partial (/pt) Locale com.airtame.Client.Locale stable x86_64 flathub system com.airtame.Client.Locale/x86_64/stable 0a042787c652 - 1,8 MB system,partial (/pt) Platform com.endlessm.Platform eos3.2 x86_64 eos-runtimes system com.endlessm.Platform/x86_64/eos3.2 9fac654c1e70 - 2,2 GB system Content com.endlessm.animals.pt.Content eos3 x86_64 eos-apps system com.endlessm.animals.pt.Content/x86_64/eos3 a66302293302 - 81,3 MB system Endless Application Platform version 1 Shared libraries used by Endless applications com.endlessm.apps.Platform 1 x86_64 eos-sdk system com.endlessm.apps.Platform/x86_64/1 0ab903d622f5 - 894,6 MB system Endless Application Platform version 3 Shared libraries used by Endless applications com.endlessm.apps.Platform 3 x86_64 eos-sdk system com.endlessm.apps.Platform/x86_64/3 07046fc5a683 - 905,5 MB system Endless Application Platform version 5 Shared libraries used by Endless applications com.endlessm.apps.Platform 5 x86_64 eos-sdk system com.endlessm.apps.Platform/x86_64/5 351a918886c3 - 1,4 GB system Content com.endlessm.astronomy.pt.Content eos3 x86_64 eos-apps system com.endlessm.astronomy.pt.Content/x86_64/eos3 53e69775f0b9 - 48,7 MB system Content com.endlessm.biology.pt.Content eos3 x86_64 eos-apps system com.endlessm.biology.pt.Content/x86_64/eos3 ce468666f299 - 65,6 MB system Content com.endlessm.celebrities.pt.Content eos3 x86_64 eos-apps system com.endlessm.celebrities.pt.Content/x86_64/eos3 80a2f3c08495 - 146,2 MB system Content com.endlessm.encyclopedia.pt.Content eos3 x86_64 eos-apps system com.endlessm.encyclopedia.pt.Content/x86_64/eos3 cd133f618ee2 - 5,4 GB system Content com.endlessm.extra.pt_BR.Content eos3 x86_64 eos-apps system com.endlessm.extra.pt_BR.Content/x86_64/eos3 84c573c3b7d8 - 111,3 MB system Content com.endlessm.farming.pt.Content eos3 x86_64 eos-apps system com.endlessm.farming.pt.Content/x86_64/eos3 225f0003d7d1 - 60,5 MB system Content com.endlessm.geography.pt.Content eos3 x86_64 eos-apps system com.endlessm.geography.pt.Content/x86_64/eos3 5ec5af738988 - 234,8 MB system Content com.endlessm.history.pt.Content eos3 x86_64 eos-apps system com.endlessm.history.pt.Content/x86_64/eos3 c5cdef1f8ccd - 172,8 MB system Content com.endlessm.library.pt.Content eos3 x86_64 eos-apps system com.endlessm.library.pt.Content/x86_64/eos3 11963d2728b2 - 110,2 MB system Content com.endlessm.math.pt.Content eos3 x86_64 eos-apps system com.endlessm.math.pt.Content/x86_64/eos3 ddf8b2729d2b - 31,5 MB system Content com.endlessm.myths.pt.Content eos3 x86_64 eos-apps system com.endlessm.myths.pt.Content/x86_64/eos3 fd4e1becb143 - 40,6 MB system Content com.endlessm.physics.pt.Content eos3 x86_64 eos-apps system com.endlessm.physics.pt.Content/x86_64/eos3 1418d7856782 - 33,7 MB system Locale com.endlessm.programming.Locale eos3 x86_64 eos-apps system com.endlessm.programming.Locale/x86_64/eos3 fdc066dd19b7 - 833,5 kB system,partial (/pt) Content com.endlessm.quote_of_the_day.en.Content eos3 x86_64 eos-apps system com.endlessm.quote_of_the_day.en.Content/x86_64/eos3 535c9012a9d3 - 8,4 MB system Content com.endlessm.socialsciences.pt.Content eos3 x86_64 eos-apps system com.endlessm.socialsciences.pt.Content/x86_64/eos3 bfd0e123620c - 41,5 MB system Locale com.endlessm.translation.Locale eos3 x86_64 eos-apps system com.endlessm.translation.Locale/x86_64/eos3 618a7a11c76e - 3,6 kB system,partial (/pt) Content com.endlessm.ubongo_kids_demo.Content eos3 x86_64 eos-apps system com.endlessm.ubongo_kids_demo.Content/x86_64/eos3 7b82b711b10a - 130,3 MB system Content com.endlessm.word_of_the_day.en.Content eos3 x86_64 eos-apps system com.endlessm.word_of_the_day.en.Content/x86_64/eos3 9e578db920a8 - 7,0 MB system Content com.endlessm.your_health.pt_BR.Content eos3 x86_64 eos-apps system com.endlessm.your_health.pt_BR.Content/x86_64/eos3 83a24e34f1a4 - 34,6 MB system Locale com.github.JannikHv.Gydl.Locale stable x86_64 flathub system com.github.JannikHv.Gydl.Locale/x86_64/stable b83e2d7ec30d - 512 bytes system,partial (/pt) Locale com.github.PintaProject.Pinta.Locale stable x86_64 flathub system com.github.PintaProject.Pinta.Locale/x86_64/stable d56d5fc2bd02 - 7,8 MB system,partial (/pt) Locale com.github.alecaddd.sequeler.Locale stable x86_64 flathub system com.github.alecaddd.sequeler.Locale/x86_64/stable 0b7c4460cb23 - 444,9 kB system,partial (/pt) Locale com.github.artemanufrij.graphui.Locale stable x86_64 flathub system com.github.artemanufrij.graphui.Locale/x86_64/stable 08961a2fba04 - 24,6 kB system,partial (/pt) Locale com.github.artemanufrij.playmyvideos.Locale stable x86_64 flathub system com.github.artemanufrij.playmyvideos.Locale/x86_64/stable bab458d533ab - 10,8 kB system,partial (/pt) Locale com.github.bcedu.valasimplehttpserver.Locale stable x86_64 flathub system com.github.bcedu.valasimplehttpserver.Locale/x86_64/stable f73c6e527bd4 - 8,7 kB system,partial (/pt) Locale com.github.coslyk.MoonPlayer.Locale stable x86_64 flathub system com.github.coslyk.MoonPlayer.Locale/x86_64/stable 534f3aa35af1 - 40,4 kB system,partial (/pt) Locale com.github.geigi.cozy.Locale stable x86_64 flathub system com.github.geigi.cozy.Locale/x86_64/stable 8ed6f28a5ed1 - 17,9 kB system,partial (/pt) Locale com.github.lainsce.coin.Locale stable x86_64 flathub system com.github.lainsce.coin.Locale/x86_64/stable 727584d1445c - 9,7 kB system,partial (/pt) Locale com.github.lainsce.notejot.Locale stable x86_64 flathub system com.github.lainsce.notejot.Locale/x86_64/stable d2c8b268511c - 24,6 kB system,partial (/pt) Locale com.github.matfantinel.moneta.Locale stable x86_64 flathub system com.github.matfantinel.moneta.Locale/x86_64/stable d92de3d81030 - 10,2 kB system,partial (/pt) Locale com.github.mdh34.hackup.Locale stable x86_64 flathub system com.github.mdh34.hackup.Locale/x86_64/stable 32bde07d4bf1 - 10,8 kB system,partial (/pt) Locale com.github.muriloventuroso.easyssh.Locale stable x86_64 flathub system com.github.muriloventuroso.easyssh.Locale/x86_64/stable eab9d05e12e6 - 20,0 kB system,partial (/pt) Locale com.github.philip_scott.spice_up.Locale stable x86_64 flathub system com.github.philip_scott.spice_up.Locale/x86_64/stable bce55e0cc126 - 18,9 kB system,partial (/pt) Locale com.github.robertsanseries.ciano.Locale stable x86_64 flathub system com.github.robertsanseries.ciano.Locale/x86_64/stable 46859832eb24 - 16,9 kB system,partial (/pt) Locale com.github.unrud.VideoDownloader.Locale stable x86_64 flathub system com.github.unrud.VideoDownloader.Locale/x86_64/stable 16550485c1f8 - 512 bytes system,partial (/pt) Locale com.github.wwmm.pulseeffects.Locale stable x86_64 flathub system com.github.wwmm.pulseeffects.Locale/x86_64/stable 301c5527efec - 19,5 kB system,partial (/pt) Locale com.gitlab.bitseater.meteo.Locale stable x86_64 flathub system com.gitlab.bitseater.meteo.Locale/x86_64/stable 63653f4c37c8 - 17,4 kB system,partial (/pt) Locale com.google.AndroidStudio.Locale stable x86_64 flathub system com.google.AndroidStudio.Locale/x86_64/stable 14a446e9bc57 - 415,2 kB system,partial (/pt) Clippy Component that makes apps hackable com.hack_computer.Clippy.Extension eos3 x86_64 eos-apps system com.hack_computer.Clippy.Extension/x86_64/eos3 37d491810acf - 341,0 kB system Locale com.hack_computer.Clubhouse.Locale eos3 x86_64 eos-apps system com.hack_computer.Clubhouse.Locale/x86_64/eos3 13cce5ff50e0 - 428,0 kB system Content com.hack_computer.ProjectLibrary.Content eos3 x86_64 eos-apps system com.hack_computer.ProjectLibrary.Content/x86_64/eos3 255bc78998ef - 8,1 MB system Locale com.inform7.IDE.Locale stable x86_64 flathub system com.inform7.IDE.Locale/x86_64/stable 8a4d5f7bc73a - 3,0 MB system,partial (/pt) Locale com.obsproject.Studio.Locale stable x86_64 flathub system com.obsproject.Studio.Locale/x86_64/stable a9cd319f1f44 - 40,4 kB system,partial (/pt) Locale com.prusa3d.PrusaSlicer.Locale stable x86_64 flathub system com.prusa3d.PrusaSlicer.Locale/x86_64/stable 52c6f2a87678 - 14,1 MB system,partial (/pt) Locale com.rawtherapee.RawTherapee.Locale stable x86_64 flathub system com.rawtherapee.RawTherapee.Locale/x86_64/stable 2399c7ff3eee - 512 bytes system,partial (/pt) Locale com.snes9x.Snes9x.Locale stable x86_64 flathub system com.snes9x.Snes9x.Locale/x86_64/stable 21ad3c7b55a3 - 17,4 kB system,partial (/pt) Locale com.tux4kids.tuxmath.Locale stable x86_64 flathub system com.tux4kids.tuxmath.Locale/x86_64/stable 2b694f5b6444 - 19,5 kB system,partial (/pt) Locale de.create3000.titania.Locale stable x86_64 flathub system de.create3000.titania.Locale/x86_64/stable 7b5b0cfd7c4a - 97,8 kB system,partial (/pt) Locale de.haeckerfelix.Fragments.Locale stable x86_64 flathub system de.haeckerfelix.Fragments.Locale/x86_64/stable f59679d0173f - 512 bytes system,partial (/pt) Locale de.haeckerfelix.gradio.Locale stable x86_64 flathub system de.haeckerfelix.gradio.Locale/x86_64/stable 7e783b3e6fc6 - 7,7 kB system,partial (/pt) Locale eu.planete_kraus.Tarot.Locale stable x86_64 flathub system eu.planete_kraus.Tarot.Locale/x86_64/stable fbb45a4677e9 - 512 bytes system,partial (/pt) Locale fr.free.Homebank.Locale stable x86_64 flathub system fr.free.Homebank.Locale/x86_64/stable 762f590f8272 - 107,0 kB system,partial (/pt) Locale fr.natron.Natron.Locale stable x86_64 flathub system fr.natron.Natron.Locale/x86_64/stable 8219bda9e46b - 47,6 kB system,partial (/pt) Locale im.pidgin.Pidgin.Locale stable x86_64 flathub system im.pidgin.Pidgin.Locale/x86_64/stable bd780767d6da - 2,1 MB system,partial (/pt) Locale info.colobot.Colobot.Locale stable x86_64 flathub system info.colobot.Colobot.Locale/x86_64/stable 59bacd795b8b - 46,6 kB system,partial (/pt) Locale io.github.OpenToonz.Locale stable x86_64 flathub system io.github.OpenToonz.Locale/x86_64/stable ea2df67df76b - 45,6 kB system,partial (/pt) Locale io.github.jliljebl.Flowblade.Locale stable x86_64 flathub system io.github.jliljebl.Flowblade.Locale/x86_64/stable 0c45ddf20dc2 - 14,1 MB system,partial (/pt) Locale io.github.maurycyliebner.enve.Locale stable x86_64 flathub system io.github.maurycyliebner.enve.Locale/x86_64/stable b80541911a2f - 45,6 kB system,partial (/pt) Locale io.github.sharkwouter.Minigalaxy.Locale stable x86_64 flathub system io.github.sharkwouter.Minigalaxy.Locale/x86_64/stable 1bc9492c26fc - 14,1 MB system,partial (/pt) Locale io.lbry.lbry_app.Locale stable x86_64 flathub system io.lbry.lbry_app.Locale/x86_64/stable 8aa9c5db6432 - 1,7 MB system,partial (/pt) Locale net.bartkessels.getit.Locale stable x86_64 flathub system net.bartkessels.getit.Locale/x86_64/stable 7bc2fd2d091b - 26,6 kB system,partial (/pt) Locale net.codeindustry.MasterPDFEditor.Locale stable x86_64 flathub system net.codeindustry.MasterPDFEditor.Locale/x86_64/stable d0363d71a841 - 20,0 kB system,partial (/pt) Locale net.gwyddion.Gwyddion.Locale stable x86_64 flathub system net.gwyddion.Gwyddion.Locale/x86_64/stable 5d1392697e61 - 14,2 MB system,partial (/pt) Locale net.mancubus.SLADE.Locale stable x86_64 flathub system net.mancubus.SLADE.Locale/x86_64/stable bc039de7cfd8 - 512 bytes system,partial (/pt) Locale net.meijn.onvifviewer.Locale stable x86_64 flathub system net.meijn.onvifviewer.Locale/x86_64/stable bd717ad3f19f - 9,2 kB system,partial (/pt) Locale net.minetest.Minetest.Locale stable x86_64 flathub system net.minetest.Minetest.Locale/x86_64/stable d4eaf9df1b24 - 290,3 kB system,partial (/pt) Locale net.oz9aec.Gpredict.Locale stable x86_64 flathub system net.oz9aec.Gpredict.Locale/x86_64/stable 3157a367ccd7 - 29,7 kB system,partial (/pt) Locale net.pcsx2.PCSX2.Locale stable i386 flathub system net.pcsx2.PCSX2.Locale/i386/stable 3d1f62c23221 - 93,7 kB system,partial (/pt) Locale net.sourceforge.TuxFootball.Locale stable x86_64 flathub system net.sourceforge.TuxFootball.Locale/x86_64/stable ae4a9c961515 - 512 bytes system,partial (/pt) Locale net.sourceforge.chromium_bsu.Locale stable x86_64 flathub system net.sourceforge.chromium_bsu.Locale/x86_64/stable bfeef58286e0 - 512 bytes system,partial (/pt) Locale net.sourceforge.fretsonfire.Locale stable x86_64 flathub system net.sourceforge.fretsonfire.Locale/x86_64/stable adf6d66d3c07 - 512 bytes system,partial (/pt) Locale nl.g4d.Girens.Locale stable x86_64 flathub system nl.g4d.Girens.Locale/x86_64/stable 76c9f74e3f46 - 512 bytes system,partial (/pt) Locale nl.openoffice.bluefish.Locale stable x86_64 flathub system nl.openoffice.bluefish.Locale/x86_64/stable 95a2b92bff0f - 202,8 kB system,partial (/pt) Locale org.DolphinEmu.dolphin_emu.Locale stable x86_64 flathub system org.DolphinEmu.dolphin_emu.Locale/x86_64/stable 8ee1971be91f - 215,6 kB system,partial (/pt) Locale org.atheme.audacious.Locale stable x86_64 flathub system org.atheme.audacious.Locale/x86_64/stable 10da9e20c968 - 192,0 kB system,partial (/pt) Codecs org.audacityteam.Audacity.Codecs stable x86_64 flathub system org.audacityteam.Audacity.Codecs/x86_64/stable 3edcaa5cad87 - 20,5 MB system Locale org.audacityteam.Audacity.Locale stable x86_64 flathub system org.audacityteam.Audacity.Locale/x86_64/stable 6ceafb09c469 - 681,0 kB system,partial (/pt) Codecs org.blender.Blender.Codecs stable x86_64 flathub system org.blender.Blender.Codecs/x86_64/stable 9a5681944c0a - 21,4 MB system Locale org.bunkus.mkvtoolnix_gui.Locale stable x86_64 flathub system org.bunkus.mkvtoolnix_gui.Locale/x86_64/stable 902594220078 - 391,7 kB system,partial (/pt) Locale org.codeblocks.codeblocks.Locale stable x86_64 flathub system org.codeblocks.codeblocks.Locale/x86_64/stable 4c77fb8daa1d - 512 bytes system,partial (/pt) Locale org.cvfosammmm.Porto.Locale stable x86_64 flathub system org.cvfosammmm.Porto.Locale/x86_64/stable 3635d33bafa1 - 15,4 kB system,partial (/pt) Locale org.darktable.Darktable.Locale stable x86_64 flathub system org.darktable.Darktable.Locale/x86_64/stable 297636555283 - 47,6 kB system,partial (/pt) Locale org.entangle_photo.Manager.Locale stable x86_64 flathub system org.entangle_photo.Manager.Locale/x86_64/stable 4b1bd0d11df1 - 21,5 kB system,partial (/pt) Locale org.filezillaproject.Filezilla.Locale stable x86_64 flathub system org.filezillaproject.Filezilla.Locale/x86_64/stable 0219348026c3 - 344,1 kB system,partial (/pt) Locale org.fontforge.FontForge.Locale stable x86_64 flathub system org.fontforge.FontForge.Locale/x86_64/stable 9f0b2c2f0e45 - 22,5 kB system,partial (/pt) Locale org.free_astro.siril.Locale stable x86_64 flathub system org.free_astro.siril.Locale/x86_64/stable 58ac8122739e - 512 bytes system,partial (/pt) Freedesktop Platform Shared libraries org.freedesktop.Platform 18.08.39 18.08 i386 flathub system org.freedesktop.Platform/i386/18.08 92d702fced84 - 847,7 MB system Freedesktop.org Application Platform version 1.6 Shared libraries provided by freedesktop.org org.freedesktop.Platform 1.6 1.6 x86_64 flathub system org.freedesktop.Platform/x86_64/1.6 8ddf3a298dfc - 1,1 GB system Freedesktop Platform Shared libraries org.freedesktop.Platform 18.08.39 18.08 x86_64 flathub system org.freedesktop.Platform/x86_64/18.08 1f7a5575c84c - 822,6 MB system Freedesktop Platform Shared libraries org.freedesktop.Platform 19.08.10 19.08 x86_64 flathub system org.freedesktop.Platform/x86_64/19.08 893ea4aa41e3 - 694,1 MB system i386 org.freedesktop.Platform.Compat.i386 18.08 x86_64 flathub system org.freedesktop.Platform.Compat.i386/x86_64/18.08 613ef1e68a34 - 479,6 MB system i386 org.freedesktop.Platform.Compat.i386 19.08 x86_64 flathub system org.freedesktop.Platform.Compat.i386/x86_64/19.08 75471e583b3e - 344,3 MB system default org.freedesktop.Platform.GL.default 19.08 x86_64 flathub system org.freedesktop.Platform.GL.default/x86_64/19.08 0d51f4a9d159 - 243,1 MB system default org.freedesktop.Platform.GL32.default 19.08 x86_64 flathub system org.freedesktop.Platform.GL32.default/x86_64/19.08 fbb5a87bf417 - 260,7 MB system EndlessOS icon theme EndlessOS icon theme org.freedesktop.Platform.Icontheme.EndlessOS 1.0 x86_64 eos-sdk system org.freedesktop.Platform.Icontheme.EndlessOS/x86_64/1.0 2bd8fccf5f25 - 216,1 kB system Intel org.freedesktop.Platform.VAAPI.Intel 18.08 i386 flathub system org.freedesktop.Platform.VAAPI.Intel/i386/18.08 2d579aa23d43 - 8,4 MB system Intel VAAPI Driver Intel driver for hardware accelerated video decoding and playback org.freedesktop.Platform.VAAPI.Intel 1.6 x86_64 flathub system org.freedesktop.Platform.VAAPI.Intel/x86_64/1.6 82006efc71d3 - 8,7 MB system Intel org.freedesktop.Platform.VAAPI.Intel 18.08 x86_64 flathub system org.freedesktop.Platform.VAAPI.Intel/x86_64/18.08 227f12933709 - 8,2 MB system Intel org.freedesktop.Platform.VAAPI.Intel 19.08 x86_64 flathub system org.freedesktop.Platform.VAAPI.Intel/x86_64/19.08 febe88924fa8 - 37,0 MB system FFmpeg extension Add support for aac, mpeg4 and h264 org.freedesktop.Platform.ffmpeg 1.6 x86_64 flathub system org.freedesktop.Platform.ffmpeg/x86_64/1.6 d757f762489e - 7,7 MB system ffmpeg-full org.freedesktop.Platform.ffmpeg-full 19.08 x86_64 flathub system org.freedesktop.Platform.ffmpeg-full/x86_64/19.08 a16d72eeaf4e - 9,6 MB system html5-codecs org.freedesktop.Platform.html5-codecs 18.08 i386 flathub system org.freedesktop.Platform.html5-codecs/i386/18.08 964e29f63869 - 9,5 MB system html5-codecs org.freedesktop.Platform.html5-codecs 18.08 x86_64 flathub system org.freedesktop.Platform.html5-codecs/x86_64/18.08 b7006caaf6a7 - 8,8 MB system openh264 OpenH264 Video Codec provided by Cisco Systems, Inc. org.freedesktop.Platform.openh264 2.0 x86_64 flathub system org.freedesktop.Platform.openh264/x86_64/2.0 15266352ca75 - 773,6 kB system Freedesktop.org Software Development Kit version 1.6 Tools and headers for developing applications using the freedesktop.org application platform org.freedesktop.Sdk 1.6 1.6 x86_64 flathub system org.freedesktop.Sdk/x86_64/1.6 4bb9279bd097 - 1,9 GB system Freedesktop SDK Tools and headers for developing applications org.freedesktop.Sdk 18.08.39 18.08 x86_64 flathub system org.freedesktop.Sdk/x86_64/18.08 a3e263fab79a - 1,7 GB system Freedesktop SDK Tools and headers for developing applications org.freedesktop.Sdk 19.08.10 19.08 x86_64 flathub system org.freedesktop.Sdk/x86_64/19.08 702dbaf249ef - 1,7 GB system Locale org.freefilesync.FreeFileSync.Locale stable x86_64 flathub system org.freefilesync.FreeFileSync.Locale/x86_64/stable ab6f979efd74 - 14,1 MB system,partial (/pt) Locale org.gabmus.whatip.Locale stable x86_64 flathub system org.gabmus.whatip.Locale/x86_64/stable f3329cb2845d - 512 bytes system,partial (/pt) Locale org.geany.Geany.Locale stable x86_64 flathub system org.geany.Geany.Locale/x86_64/stable 7289d551791f - 217,6 kB system,partial (/pt) Locale org.geeqie.Geeqie.Locale stable x86_64 flathub system org.geeqie.Geeqie.Locale/x86_64/stable 8ea2f21343f9 - 11,0 MB system,partial (/pt) Locale org.geogebra.GeoGebra.Locale stable x86_64 flathub system org.geogebra.GeoGebra.Locale/x86_64/stable e8599e5f33e4 - 3,6 kB system,partial (/pt) Locale org.glimpse_editor.Glimpse.Locale stable x86_64 flathub system org.glimpse_editor.Glimpse.Locale/x86_64/stable 717b577e8f7c - 4,8 MB system,partial (/pt) Locale org.gnome.Books.Locale stable x86_64 flathub system org.gnome.Books.Locale/x86_64/stable 266746ec559e - 284,2 kB system,partial (/pt) Locale org.gnome.Boxes.Locale stable x86_64 flathub system org.gnome.Boxes.Locale/x86_64/stable f1f1a63b862b - 905,2 kB system,partial (/pt) Locale org.gnome.Builder.Locale stable x86_64 flathub system org.gnome.Builder.Locale/x86_64/stable 4e3b495af8cb - 600,1 kB system,partial (/pt) Locale org.gnome.Calendar.Locale stable x86_64 flathub system org.gnome.Calendar.Locale/x86_64/stable 434715dbf083 - 727,0 kB system,partial (/pt) Locale org.gnome.Cheese.Locale stable x86_64 flathub system org.gnome.Cheese.Locale/x86_64/stable 8330f76897c1 - 34,3 kB system,partial (/pt) Locale org.gnome.Chess.Locale stable x86_64 flathub system org.gnome.Chess.Locale/x86_64/stable a1979b8ac49b - 66,0 kB system,partial (/pt) Locale org.gnome.Devhelp.Locale stable x86_64 flathub system org.gnome.Devhelp.Locale/x86_64/stable 7a9599a35aef - 20,0 kB system,partial (/pt) Locale org.gnome.Dictionary.Locale stable x86_64 flathub system org.gnome.Dictionary.Locale/x86_64/stable bb3b462ef2f8 - 28,2 kB system,partial (/pt) Locale org.gnome.Eolie.Locale stable x86_64 flathub system org.gnome.Eolie.Locale/x86_64/stable 5bd95c57451e - 497,7 kB system Locale org.gnome.Epiphany.Locale stable x86_64 flathub system org.gnome.Epiphany.Locale/x86_64/stable 6c1a39b9ad0a - 135,7 kB system,partial (/pt) Locale org.gnome.Fractal.Locale stable x86_64 flathub system org.gnome.Fractal.Locale/x86_64/stable 3253dbbd5b1e - 58,4 kB system,partial (/pt) Locale org.gnome.GHex.Locale stable x86_64 flathub system org.gnome.GHex.Locale/x86_64/stable e39225d89acd - 38,9 kB system,partial (/pt) Locale org.gnome.Genius.Locale stable x86_64 flathub system org.gnome.Genius.Locale/x86_64/stable fc9b5b1477d0 - 312,3 kB system,partial (/pt) Locale org.gnome.Glade.Locale stable x86_64 flathub system org.gnome.Glade.Locale/x86_64/stable 6b6738c6e81b - 259,1 kB system,partial (/pt) Locale org.gnome.Lollypop.Locale stable x86_64 flathub system org.gnome.Lollypop.Locale/x86_64/stable e04578b5adcb - 59,9 kB system,partial (/pt) Locale org.gnome.Maps.Locale stable x86_64 flathub system org.gnome.Maps.Locale/x86_64/stable 50f795eda827 - 785,9 kB system,partial (/pt) Locale org.gnome.Nibbles.Locale stable x86_64 flathub system org.gnome.Nibbles.Locale/x86_64/stable e70d7d17dce0 - 21,5 kB system,partial (/pt) GNOME Application Platform version 3.26 Shared libraries used by GNOME applications org.gnome.Platform 3.26 x86_64 flathub system org.gnome.Platform/x86_64/3.26 d01b14e467c2 - 1,3 GB system GNOME Application Platform version 3.28 Shared libraries used by GNOME applications org.gnome.Platform 3.28 x86_64 flathub system org.gnome.Platform/x86_64/3.28 6d1d0ebbd724 - 1,3 GB system GNOME Application Platform version 3.32 Shared libraries used by GNOME applications org.gnome.Platform 3.32 x86_64 flathub system org.gnome.Platform/x86_64/3.32 24da23761540 - 1,0 GB system,eol=The GNOME 3.32 runtime is no longer supported as of 11th March 2020. Please ask your application developer to migrate to a supported platform. GNOME Application Platform version 3.34 Shared libraries used by GNOME applications org.gnome.Platform 3.34 x86_64 flathub system org.gnome.Platform/x86_64/3.34 e937e1d81343 - 918,2 MB system GNOME Application Platform version 3.36 Shared libraries used by GNOME applications org.gnome.Platform 3.36 x86_64 flathub system org.gnome.Platform/x86_64/3.36 ad7f022f9489 - 934,5 MB system i386 org.gnome.Platform.Compat.i386 3.36 x86_64 flathub system org.gnome.Platform.Compat.i386/x86_64/3.36 dbe0820c1095 - 463,5 MB system Locale org.gnome.Quadrapassel.Locale stable x86_64 flathub system org.gnome.Quadrapassel.Locale/x86_64/stable 9edbd6b29089 - 579,1 kB system Locale org.gnome.Reversi.Locale stable x86_64 flathub system org.gnome.Reversi.Locale/x86_64/stable 0d34b498151c - 603,1 kB system GNOME Software Development Kit version 3.28 Tools and headers for developing applications using the GNOME application platform org.gnome.Sdk 3.28 x86_64 flathub system org.gnome.Sdk/x86_64/3.28 31af0c10f8e4 - 2,2 GB system GNOME Software Development Kit version 3.32 Tools and headers for developing applications using the GNOME application platform org.gnome.Sdk 3.32 x86_64 flathub system org.gnome.Sdk/x86_64/3.32 430bf7a53690 - 2,0 GB system,eol=The GNOME 3.32 runtime is no longer supported as of 11th March 2020. Please ask your application developer to migrate to a supported platform. GNOME Software Development Kit version 3.34 Tools and headers for developing applications using the GNOME application platform org.gnome.Sdk 3.34 x86_64 flathub system org.gnome.Sdk/x86_64/3.34 3983fe181e26 - 1,9 GB system GNOME Software Development Kit version 3.36 Tools and headers for developing applications using the GNOME application platform org.gnome.Sdk 3.36 x86_64 flathub system org.gnome.Sdk/x86_64/3.36 93e447785a0e - 1,9 GB system Locale org.gnome.SoundRecorder.Locale stable x86_64 flathub system org.gnome.SoundRecorder.Locale/x86_64/stable 80c437bff173 - 13,8 kB system,partial (/pt) Locale org.gnome.Tetravex.Locale stable x86_64 flathub system org.gnome.Tetravex.Locale/x86_64/stable 112723a6b33e - 572,9 kB system Locale org.gnome.TwentyFortyEight.Locale stable x86_64 flathub system org.gnome.TwentyFortyEight.Locale/x86_64/stable 485b3a7870d2 - 16,4 kB system,partial (/pt) Locale org.gnome.dfeet.Locale stable x86_64 flathub system org.gnome.dfeet.Locale/x86_64/stable ed0980b0dc0e - 7,2 kB system,partial (/pt) Locale org.gnome.gbrainy.Locale stable x86_64 flathub system org.gnome.gbrainy.Locale/x86_64/stable 62a31ecee617 - 263,7 kB system,partial (/pt) Locale org.gnome.gitg.Locale stable x86_64 flathub system org.gnome.gitg.Locale/x86_64/stable 4058d7224d48 - 110,1 kB system,partial (/pt) Locale org.gnome.glabels_3.Locale stable x86_64 flathub system org.gnome.glabels_3.Locale/x86_64/stable 4ccae7a63b49 - 125,4 kB system,partial (/pt) Locale org.gnome.meld.Locale stable x86_64 flathub system org.gnome.meld.Locale/x86_64/stable e59ec6fad652 - 119,3 kB system,partial (/pt) Locale org.gnucash.GnuCash.Locale stable x86_64 flathub system org.gnucash.GnuCash.Locale/x86_64/stable 18ed42fe4bc3 - 935,9 kB system,partial (/pt) elementary stylesheet The Gtk+ Stylesheet for elementary OS. org.gtk.Gtk3theme.elementary 3.22 x86_64 flathub system org.gtk.Gtk3theme.elementary/x86_64/3.22 a884bbfa236b - 16,7 MB system Locale org.inkscape.Inkscape.Locale stable x86_64 flathub system org.inkscape.Inkscape.Locale/x86_64/stable a90c92dc68a7 - 1,2 MB system,partial (/pt) Adwaita theme Adwaita widget theme matching the GNOME adwaita theme org.kde.KStyle.Adwaita 5.11 x86_64 flathub system org.kde.KStyle.Adwaita/x86_64/5.11 9f45dabd8317 - 1,3 MB system Adwaita theme Adwaita widget theme matching the GNOME adwaita theme org.kde.KStyle.Adwaita 5.12 x86_64 flathub system org.kde.KStyle.Adwaita/x86_64/5.12 e5f0a6fe78b3 - 16,3 MB system Adwaita theme Adwaita widget theme matching the GNOME adwaita theme org.kde.KStyle.Adwaita 5.13 x86_64 flathub system org.kde.KStyle.Adwaita/x86_64/5.13 fdd4bcb419e8 - 17,6 MB system Adwaita theme Adwaita widget theme matching the GNOME adwaita theme org.kde.KStyle.Adwaita 5.14 x86_64 flathub system org.kde.KStyle.Adwaita/x86_64/5.14 7e8f3e52c779 - 18,0 MB system HighContrast Theme HighContrast widget theme matching the GNOME highcontrast theme org.kde.KStyle.HighContrast 5.11 x86_64 flathub system org.kde.KStyle.HighContrast/x86_64/5.11 50cedd08065e - 1,3 MB system HighContrast Theme HighContrast widget theme matching the GNOME highcontrast theme org.kde.KStyle.HighContrast 5.12 x86_64 flathub system org.kde.KStyle.HighContrast/x86_64/5.12 ffbb069de612 - 14,0 MB system HighContrast Theme HighContrast widget theme matching the GNOME highcontrast theme org.kde.KStyle.HighContrast 5.13 x86_64 flathub system org.kde.KStyle.HighContrast/x86_64/5.13 06d624deaa36 - 15,4 MB system HighContrast Theme HighContrast widget theme matching the GNOME highcontrast theme org.kde.KStyle.HighContrast 5.14 x86_64 flathub system org.kde.KStyle.HighContrast/x86_64/5.14 858837db2c6a - 17,8 MB system KDE Application Platform version master Shared libraries used by KDE applications org.kde.Platform 5.11 x86_64 flathub system org.kde.Platform/x86_64/5.11 02ede84d3591 - 1,4 GB system KDE Application Platform Shared libraries used by KDE applications org.kde.Platform 5.12 x86_64 flathub system org.kde.Platform/x86_64/5.12 800a51d3562a - 1,2 GB system KDE Application Platform Shared libraries used by KDE applications org.kde.Platform 5.13 x86_64 flathub system org.kde.Platform/x86_64/5.13 f9477196a7b6 - 920,3 MB system KDE Application Platform Shared libraries used by KDE applications org.kde.Platform 5.14 x86_64 flathub system org.kde.Platform/x86_64/5.14 710b312bd61b - 925,8 MB system QGnomePlatform Qt Platform Theme aimed to accommodate GNOME settings org.kde.PlatformTheme.QGnomePlatform 5.11 x86_64 flathub system org.kde.PlatformTheme.QGnomePlatform/x86_64/5.11 819a74457c03 - 343,0 kB system QGnomePlatform Qt Platform Theme aimed to accommodate GNOME settings org.kde.PlatformTheme.QGnomePlatform 5.12 x86_64 flathub system org.kde.PlatformTheme.QGnomePlatform/x86_64/5.12 ed5faeeb20f2 - 416,8 kB system QGnomePlatform Qt Platform Theme aimed to accommodate GNOME settings org.kde.PlatformTheme.QGnomePlatform 5.13 x86_64 flathub system org.kde.PlatformTheme.QGnomePlatform/x86_64/5.13 46f02cd21f64 - 416,8 kB system QGnomePlatform Qt Platform Theme aimed to accommodate GNOME settings org.kde.PlatformTheme.QGnomePlatform 5.14 x86_64 flathub system org.kde.PlatformTheme.QGnomePlatform/x86_64/5.14 fd87fb78f096 - 420,9 kB system KDE Software Development Kit Tools and headers for developing applications using the KDE application platform org.kde.Sdk 5.14 x86_64 flathub system org.kde.Sdk/x86_64/5.14 df2303f5dbfd - 2,2 GB system QGnomePlatform-decoration Qt Platform Theme aimed to accommodate GNOME settings org.kde.WaylandDecoration.QGnomePlatform-decoration 5.12 x86_64 flathub system org.kde.WaylandDecoration.QGnomePlatform-decoration/x86_64/5.12 bbba5a892f54 - 164,9 kB system QGnomePlatform-decoration Qt Platform Theme aimed to accommodate GNOME settings org.kde.WaylandDecoration.QGnomePlatform-decoration 5.13 x86_64 flathub system org.kde.WaylandDecoration.QGnomePlatform-decoration/x86_64/5.13 1bf7ab26092c - 169,0 kB system QGnomePlatform-decoration Qt Platform Theme aimed to accommodate GNOME settings org.kde.WaylandDecoration.QGnomePlatform-decoration 5.14 x86_64 flathub system org.kde.WaylandDecoration.QGnomePlatform-decoration/x86_64/5.14 212f272885a0 - 169,0 kB system Locale org.kde.dolphin.Locale stable x86_64 flathub system org.kde.dolphin.Locale/x86_64/stable 57b62ecb7cba - 452,6 kB system,partial (/pt) Locale org.kde.kalzium.Locale stable x86_64 flathub system org.kde.kalzium.Locale/x86_64/stable 216dd63fa7b1 - 403,5 kB system,partial (/pt) Locale org.kde.katomic.Locale stable x86_64 flathub system org.kde.katomic.Locale/x86_64/stable 9c1b3d897225 - 29,7 kB system,partial (/pt) Locale org.kde.kbruch.Locale stable x86_64 flathub system org.kde.kbruch.Locale/x86_64/stable 82bdf99ce72d - 45,6 kB system,partial (/pt) Locale org.kde.kdenlive.Locale stable x86_64 flathub system org.kde.kdenlive.Locale/x86_64/stable c1ef4b6a4811 - 440,8 kB system,partial (/pt) Locale org.kde.kgeography.Locale stable x86_64 flathub system org.kde.kgeography.Locale/x86_64/stable 0a1c220ee3ef - 872,4 kB system,partial (/pt) Locale org.kde.khangman.Locale stable x86_64 flathub system org.kde.khangman.Locale/x86_64/stable cff211585280 - 35,3 kB system,partial (/pt) Locale org.kde.knavalbattle.Locale stable x86_64 flathub system org.kde.knavalbattle.Locale/x86_64/stable 9bbdc28c5147 - 36,9 kB system,partial (/pt) Locale org.kde.knetwalk.Locale stable x86_64 flathub system org.kde.knetwalk.Locale/x86_64/stable 3c8876d75b20 - 29,7 kB system,partial (/pt) Locale org.kde.kolourpaint.Locale stable x86_64 flathub system org.kde.kolourpaint.Locale/x86_64/stable 3e3e3deca828 - 97,8 kB system,partial (/pt) Locale org.kde.kpat.Locale stable x86_64 flathub system org.kde.kpat.Locale/x86_64/stable 2c7dfcd94fbd - 42,0 kB system,partial (/pt) Locale org.kde.krita.Locale stable x86_64 flathub system org.kde.krita.Locale/x86_64/stable b01605ce7dbb - 1,2 MB system,partial (/pt) Locale org.kde.ksudoku.Locale stable x86_64 flathub system org.kde.ksudoku.Locale/x86_64/stable ded535d9ecb7 - 71,7 kB system,partial (/pt) Locale org.kde.ktouch.Locale stable x86_64 flathub system org.kde.ktouch.Locale/x86_64/stable 9e5e44cdc773 - 41,5 kB system,partial (/pt) Locale org.kde.kubrick.Locale stable x86_64 flathub system org.kde.kubrick.Locale/x86_64/stable edfd78463049 - 59,4 kB system,partial (/pt) Locale org.kde.kxstitch.Locale stable x86_64 flathub system org.kde.kxstitch.Locale/x86_64/stable f4f6ac36f01f - 84,5 kB system,partial (/pt) Locale org.kde.okular.Locale stable x86_64 flathub system org.kde.okular.Locale/x86_64/stable b1d0a1183844 - 293,4 kB system,partial (/pt) Locale org.kde.palapeli.Locale stable x86_64 flathub system org.kde.palapeli.Locale/x86_64/stable fbcb5faa8354 - 72,7 kB system,partial (/pt) Locale org.kde.skrooge.Locale stable x86_64 flathub system org.kde.skrooge.Locale/x86_64/stable ef356268a211 - 504,8 kB system,partial (/pt) Locale org.kicad_pcb.KiCad.Locale stable x86_64 flathub system org.kicad_pcb.KiCad.Locale/x86_64/stable d1414b917e6b - 475,1 kB system,partial (/pt) Locale org.kiwix.desktop.Locale stable x86_64 flathub system org.kiwix.desktop.Locale/x86_64/stable 9ba88c4b7e46 - 183,8 kB system,partial (/pt) Locale org.laptop.TurtleArtActivity.Locale stable x86_64 flathub system org.laptop.TurtleArtActivity.Locale/x86_64/stable 0603b6cb4f3d - 68,6 kB system,partial (/pt) Locale org.libreoffice.LibreOffice.Locale stable x86_64 flathub system org.libreoffice.LibreOffice.Locale/x86_64/stable b59b7634d6da - 5,9 MB system,partial (/pt) Locale org.libretro.RetroArch.Locale stable x86_64 flathub system org.libretro.RetroArch.Locale/x86_64/stable 8620c72cae3b - 24,6 kB system,partial (/pt) Locale org.midori_browser.Midori.Locale stable x86_64 flathub system org.midori_browser.Midori.Locale/x86_64/stable 78eadbd1c237 - 140,8 kB system,partial (/pt) Locale org.mixxx.Mixxx.Locale stable x86_64 flathub system org.mixxx.Mixxx.Locale/x86_64/stable ce8c9238410e - 512 bytes system,partial (/pt) Locale org.mobsya.ThymioSuite.Locale stable x86_64 flathub system org.mobsya.ThymioSuite.Locale/x86_64/stable cd9905a0e3ed - 17,9 kB system,partial (/pt) Locale org.musesequencer.Muse3.Locale stable x86_64 flathub system org.musesequencer.Muse3.Locale/x86_64/stable 37f346e8d45f - 14,1 MB system,partial (/pt) Locale org.mypaint.MyPaint.Locale stable x86_64 flathub system org.mypaint.MyPaint.Locale/x86_64/stable 7f297e537f03 - 238,1 kB system,partial (/pt) Locale org.nextcloud.Nextcloud.Locale stable x86_64 flathub system org.nextcloud.Nextcloud.Locale/x86_64/stable f098e4785813 - 4,6 kB system,partial (/pt) Locale org.opensurge2d.OpenSurge.Locale stable x86_64 flathub system org.opensurge2d.OpenSurge.Locale/x86_64/stable 76cfbde2ab70 - 14,1 MB system,partial (/pt) Codecs org.pitivi.Pitivi.Codecs stable x86_64 flathub system org.pitivi.Pitivi.Codecs/x86_64/stable 53cd99c9811e - 21,9 MB system Locale org.pitivi.Pitivi.Locale stable x86_64 flathub system org.pitivi.Pitivi.Locale/x86_64/stable 3254c2666b41 - 150,0 kB system,partial (/pt) Locale org.pulseaudio.pavucontrol.Locale stable x86_64 flathub system org.pulseaudio.pavucontrol.Locale/x86_64/stable 0c816c90d346 - 16,9 kB system,partial (/pt) Locale org.remmina.Remmina.Locale stable x86_64 flathub system org.remmina.Remmina.Locale/x86_64/stable 688d5942d88f - 126,0 kB system,partial (/pt) Locale org.snap4arduino.App.Locale eos3 x86_64 eos-apps system org.snap4arduino.App.Locale/x86_64/eos3 d34f40e82430 - 1,9 MB system,partial (/pt) Locale org.squeakland.Etoys.Locale stable x86_64 flathub system org.squeakland.Etoys.Locale/x86_64/stable 9786aa740dec - 5,2 MB system,partial (/pt) Locale org.synfig.SynfigStudio.Locale stable x86_64 flathub system org.synfig.SynfigStudio.Locale/x86_64/stable 7be3f535cd79 - 431,6 kB system,partial (/pt) Locale org.tuxfamily.XMoto.Locale stable x86_64 flathub system org.tuxfamily.XMoto.Locale/x86_64/stable 85f313546694 - 135,7 kB system,partial (/pt) Locale org.videolan.VLC.Locale stable x86_64 flathub system org.videolan.VLC.Locale/x86_64/stable 1779fc2c0db1 - 1,2 MB system,partial (/pt) ======================== = Flatpak applications = ======================== esys-escript esys-escript is a python module for implementing mathematical models using the finite element method au.edu.uq.esys.escript 5.5 stable x86_64 flathub system au.edu.uq.esys.escript/x86_64/stable 15040ef3076b - 607,1 MB system,current InVesalius 3D medical imaging reconstruction software br.gov.cti.invesalius 3.1.99994 stable x86_64 flathub system br.gov.cti.invesalius/x86_64/stable 788dc89a0498 - 562,7 MB system,current Nestopia A Nintendo Entertainment System emulator ca._0ldsk00l.Nestopia 1.49.0 stable x86_64 flathub system ca._0ldsk00l.Nestopia/x86_64/stable 7c8991a8cf00 - 4,7 MB system,current Arduino IDE Open-source electronics prototyping platform cc.arduino.arduinoide 1.8.12 stable x86_64 flathub system cc.arduino.arduinoide/x86_64/stable 84056e5462fa - 538,8 MB system,current OpenBoard Quadro branco interativo para escolas e universidades ch.openboard.OpenBoard 1.5.4 stable x86_64 flathub system ch.openboard.OpenBoard/x86_64/stable 78308731a6af - 136,9 MB system,current Rocket.Chat Open Source Team Communication chat.rocket.RocketChat 2.17.9 stable x86_64 flathub system chat.rocket.RocketChat/x86_64/stable eff96daa7ff2 - 205,0 MB system,current Adobe Flash Player Player for content created using Adobe Flash com.adobe.Flash-Player-Projector 32.0.0.371 stable x86_64 flathub system com.adobe.Flash-Player-Projector/x86_64/stable d9fcffd73de9 - 7,1 MB system,current Airtame Airtame is a wireless streaming solution com.airtame.Client 3.5.0 stable x86_64 flathub system com.airtame.Client/x86_64/stable 7c82e1653bd3 - 9,8 MB system,current Albion Online MMORPG open medieval fantasy game com.albiononline.AlbionOnline 1.0.34.184 stable x86_64 flathub system com.albiononline.AlbionOnline/x86_64/stable ab656a896255 - 466,4 kB system,current Nexuiz Classic A multiplayer first-person shooter com.alientrap.nexuiz-classic 2.5.2 stable x86_64 flathub system com.alientrap.nexuiz-classic/x86_64/stable 2ff1c460d4e7 - 895,6 MB system,current AnyDesk Conectar com um computador remotamente com.anydesk.Anydesk 5.5.6 stable x86_64 flathub system com.anydesk.Anydesk/x86_64/stable a2ebd818b9de - 6,0 MB system,current Beaker A browser for the next-generation P2P web com.beakerbrowser.Beaker 0.8.10 stable x86_64 flathub system com.beakerbrowser.Beaker/x86_64/stable 3616baf584b0 - 326,5 MB system,current Bitwarden A secure and free password manager for all of your devices com.bitwarden.desktop 1.17.2 stable x86_64 flathub system com.bitwarden.desktop/x86_64/stable f3641770efdc - 175,1 MB system,current adventure-editor Classic point and click adventure game engine and editor com.bladecoder.adventure-editor 4.0.0 stable x86_64 flathub system com.bladecoder.adventure-editor/x86_64/stable a5a719735e24 - 593,2 MB system,current BlueJeans BlueJeans Desktop App com.bluejeans.BlueJeans 1.37.22 stable x86_64 flathub system com.bluejeans.BlueJeans/x86_64/stable adb19c6ec85d - 34,8 MB system,current Brosix An all-in-one, secure instant messenger com.brosix.Brosix 4.5 Build 200326.12251 stable x86_64 flathub system com.brosix.Brosix/x86_64/stable cc401264397c - 517,9 MB system,current GrafX2 A bitmap paint program specialized in 256 color drawing com.chez.GrafX2 stable x86_64 flathub system com.chez.GrafX2/x86_64/stable a9e1031ed7d2 - 4,8 MB system,current Climaxima Frontend for Maxima CAS com.dhsdevelopments.Climaxima release-2020-03-03_01 stable x86_64 flathub system com.dhsdevelopments.Climaxima/x86_64/stable 6866d3f999bf - 276,1 MB system,current Discord Chat client com.discordapp.Discord 0.0.10 stable x86_64 flathub system com.discordapp.Discord/x86_64/stable 26490b6a744f - 181,8 MB system,current DOSBox x86/DOS emulator with sound and graphics com.dosbox.DOSBox 0.74-3 stable x86_64 flathub system com.dosbox.DOSBox/x86_64/stable 0ad3f3f57593 - 3,9 MB system,current Dropbox Acesse seus arquivos à partir de qualquer computador com.dropbox.Client 97.4.467 stable x86_64 flathub system com.dropbox.Client/x86_64/stable bd668bed831e - 1,5 MB system,current EDuke32 EDuke32 is an awesome, free homebrew game engine com.eduke32.EDuke32 r8904 stable x86_64 flathub system com.eduke32.EDuke32/x86_64/stable 5be261b8afdc - 5,6 MB system,current Endless Desktop Search Desktop search provider for Endless applications com.endlessm.EknServicesMultiplexer stable x86_64 eos-sdk system com.endlessm.EknServicesMultiplexer/x86_64/stable e250946375c4 - 2,5 MB system,current Hatch Previewer Developer tool for packaged websites com.endlessm.HatchPreviewer 0.0.6 stable x86_64 flathub system com.endlessm.HatchPreviewer/x86_64/stable 99ac7e39c4ef - 213,3 MB system,current Animais Aprenda mais sobre todas as criaturas da Terra. com.endlessm.animals.pt eos3 x86_64 eos-apps system com.endlessm.animals.pt/x86_64/eos3 c3fe3eac2967 - 11,1 MB system,current Astronomia Aprenda sobre o universo e tudo que contém nele com.endlessm.astronomy.pt eos3 x86_64 eos-apps system com.endlessm.astronomy.pt/x86_64/eos3 c1ef5cc50ef1 - 2,2 MB system,current Bibliotecas Embrapa Publicações da Embrapa com.endlessm.bibliotecas_embrapa.pt_BR eos3 x86_64 eos-apps system com.endlessm.bibliotecas_embrapa.pt_BR/x86_64/eos3 7987069da3ff - 818,0 MB system,current Biologia Aprenda tudo sobre o mundo vivo ao seu redor com.endlessm.biology.pt eos3 x86_64 eos-apps system com.endlessm.biology.pt/x86_64/eos3 bdbb50dee18b - 6,9 MB system,current Celebridades Saiba mais sobre suas celebridades favoritas com.endlessm.celebrities.pt eos3 x86_64 eos-apps system com.endlessm.celebrities.pt/x86_64/eos3 5971a671412f - 6,7 MB system,current Dinossauros Trazendo a pré-história de volta à vida para você descobrir de novo com.endlessm.dinosaurs.pt eos3 x86_64 eos-apps system com.endlessm.dinosaurs.pt/x86_64/eos3 ab2892917d24 - 45,5 MB system,current Enciclopédia A enciclopédia livre editável por todos com.endlessm.encyclopedia.pt eos3 x86_64 eos-apps system com.endlessm.encyclopedia.pt/x86_64/eos3 9697f8f67986 - 6,2 MB system,current Extra Globo Notícias que afetam o seu dia a dia com.endlessm.extra.pt_BR eos3 x86_64 eos-apps system com.endlessm.extra.pt_BR/x86_64/eos3 65d8f265b0b2 - 3,2 MB system,current Agricultura Saiba mais sobre lavouras e criação de animais com.endlessm.farming.pt eos3 x86_64 eos-apps system com.endlessm.farming.pt/x86_64/eos3 d92bade2d4a6 - 2,9 MB system,current Meu Orçamento Aprenda a criar seu próprio orçamento e a economizar com.endlessm.finance eos3 x86_64 eos-apps system com.endlessm.finance/x86_64/eos3 f087ac09917f - 47,8 MB system,current Geografia Saiba mais sobre todos os países do mundo com.endlessm.geography.pt eos3 x86_64 eos-apps system com.endlessm.geography.pt/x86_64/eos3 42b41a8a2622 - 7,8 MB system,current História Saiba mais sobre acontecimentos e civilizações do mundo com.endlessm.history.pt eos3 x86_64 eos-apps system com.endlessm.history.pt/x86_64/eos3 303b7f7eb302 - 2,5 MB system,current Biblioteca Clássicos da literatura para todas as idades com.endlessm.library.pt eos3 x86_64 eos-apps system com.endlessm.library.pt/x86_64/eos3 343645627957 - 3,5 MB system,current Matemática Matemática do ensino médio de forma simples e acessível com.endlessm.math.pt eos3 x86_64 eos-apps system com.endlessm.math.pt/x86_64/eos3 f80391540d9f - 3,2 MB system,current Mitos e Lendas Mitos e lendas de todo o mundo com.endlessm.myths.pt eos3 x86_64 eos-apps system com.endlessm.myths.pt/x86_64/eos3 61a87ed90654 - 4,3 MB system,current Física Saiba mais sobre os mistérios do mundo da física com.endlessm.physics.pt eos3 x86_64 eos-apps system com.endlessm.physics.pt/x86_64/eos3 0beca80d71b9 - 2,8 MB system,current Código Divertido Aprende a programar computadores criando os seus próprios jogos com.endlessm.programming eos3 x86_64 eos-apps system com.endlessm.programming/x86_64/eos3 ef5f6692dac0 - 93,0 MB system,current Quote of the Day Inspiring quotes from some of history's most influential thinkers. com.endlessm.quote_of_the_day.en eos3 x86_64 eos-apps system com.endlessm.quote_of_the_day.en/x86_64/eos3 a0e2cd4b40b1 - 4,6 MB system,current Ciências Sociais Temas que exploram sobre o indivíduo e a sociedade com.endlessm.socialsciences.pt eos3 x86_64 eos-apps system com.endlessm.socialsciences.pt/x86_64/eos3 5ce80502c6cf - 6,2 MB system,current Tradutor Traduz rapidamente textos em várias línguas com.endlessm.translation eos3 x86_64 eos-apps system com.endlessm.translation/x86_64/eos3 01a81f9a9279 - 2,0 MB system,current Ubongo Kids Lite Ubongo Kids Lite com.endlessm.ubongo_kids_demo eos3 x86_64 eos-apps system com.endlessm.ubongo_kids_demo/x86_64/eos3 c08d77803a04 - 840,7 kB system,current Animações Imagens valem mais do que palavras com.endlessm.video_animations eos3 x86_64 eos-apps system com.endlessm.video_animations/x86_64/eos3 5b18c5499f68 - 183,9 MB system,current Word of the Day A new word and its definition each day. com.endlessm.word_of_the_day.en eos3 x86_64 eos-apps system com.endlessm.word_of_the_day.en/x86_64/eos3 6abb5d51b7f9 - 2,1 MB system,current Sua Saúde Saúde, alimentação e bem-estar em um clique com.endlessm.your_health.pt_BR eos3 x86_64 eos-apps system com.endlessm.your_health.pt_BR/x86_64/eos3 f540c45e06df - 3,9 MB system,current Midnightmare Teddy Shoot and survive com.endlessnetwork.MidnightmareTeddy 1.0 stable x86_64 flathub system com.endlessnetwork.MidnightmareTeddy/x86_64/stable 1e902e95e9b5 - 138,6 MB system,current Aqueducts An immersive puzzle adventure game where you hack your way to saving the day! com.endlessnetwork.aqueducts 1.2.2 stable x86_64 flathub system com.endlessnetwork.aqueducts/x86_64/stable 53f9bc945b1f - 469,5 MB system,current Arduino Projects Control the world around you with Arduino! com.endlessnetwork.arduinoprojects 1.0.0 eos3 x86_64 eos-apps system com.endlessnetwork.arduinoprojects/x86_64/eos3 2681c0f9d910 - 82,5 MB system,current Blender Tutorials Get a glimpse of the most fundamental tools and concepts in Blender. com.endlessnetwork.blendertutorials 1.0.0 eos3 x86_64 eos-apps system com.endlessnetwork.blendertutorials/x86_64/eos3 80b3cc268fc8 - 867,2 MB system,current CSS Tutorials CSS is about styling a webpage. Give your webpage a colorful life! com.endlessnetwork.csstutorials eos3 x86_64 eos-apps system com.endlessnetwork.csstutorials/x86_64/eos3 57393e73d694 - 11,1 MB system,current Dragon’s Apprentice An RPG like puzzle solving dungeon crawling game, and more! com.endlessnetwork.dragonsapprentice 1.1 stable x86_64 flathub system com.endlessnetwork.dragonsapprentice/x86_64/stable 776239a4c18c - 2,3 GB system,current Fablemaker Enter the world of Aesop's fables like never before! Interactive stories where you can customize characters, texts and sounds, hacking into its code in this absorbing and educational app. com.endlessnetwork.fablemaker 1.2 stable x86_64 flathub system com.endlessnetwork.fablemaker/x86_64/stable 004ccff24a94 - 885,1 MB system,current Frog Squash An addictive crossy roads game with a twist com.endlessnetwork.frogsquash 1.2 stable x86_64 flathub system com.endlessnetwork.frogsquash/x86_64/stable e4df08280447 - 92,9 MB system,current Guitar Tutorials Pick up your guitar and start making your own music! com.endlessnetwork.guitartutorials eos3 x86_64 eos-apps system com.endlessnetwork.guitartutorials/x86_64/eos3 76292d22b767 - 709,8 MB system,current HTML Tutorials Learn how to write rich and stunning webpages com.endlessnetwork.htmltutorials eos3 x86_64 eos-apps system com.endlessnetwork.htmltutorials/x86_64/eos3 8f8ac0d3ced6 - 4,0 MB system,current Missile Math A plane flying shooter game com.endlessnetwork.missilemath 1.0 stable x86_64 flathub system com.endlessnetwork.missilemath/x86_64/stable 44ac33d43d7e - 152,2 MB system,current The Passage Hack your way through this side scrolling action adventure shooting game com.endlessnetwork.passage 1.34 stable x86_64 flathub system com.endlessnetwork.passage/x86_64/stable 24cb54796b91 - 476,3 MB system,current Raspberry Pi Projects Learn how to create great projects using Raspberry Pi products com.endlessnetwork.raspberrypiprojects 1.0.0 eos3 x86_64 eos-apps system com.endlessnetwork.raspberrypiprojects/x86_64/eos3 a01f6ebb94ca - 356,4 MB system,current Science Snacks Hands-on science activities with easy-to-follow instructions, advice, and helpful hints. com.endlessnetwork.sciencesnacks 1.0.0 eos3 x86_64 eos-apps system com.endlessnetwork.sciencesnacks/x86_64/eos3 901fb0da614c - 60,3 MB system,current Short Films Animated and live action shorts films from around the world. com.endlessnetwork.shortfilms eos3 x86_64 eos-apps system com.endlessnetwork.shortfilms/x86_64/eos3 8375f64ffdb8 - 681,9 MB system,current Tank Warriors Driving, shooting, explosions, and programming - all in one game com.endlessnetwork.tankwarriors 1.3 stable x86_64 flathub system com.endlessnetwork.tankwarriors/x86_64/stable c5d2c0dab2bf - 495,5 MB system,current Video Games Unity tutorials with easy to follow steps on how to create enjoyable video games from scratch. com.endlessnetwork.videogamestutorials eos3 x86_64 eos-apps system com.endlessnetwork.videogamestutorials/x86_64/eos3 9d57c06050af - 565,9 MB system,current White House Using the magic of CSS, hack your world into a unique burst of color and light revealing hidden objects and clues. com.endlessnetwork.whitehouse 1.175 stable x86_64 flathub system com.endlessnetwork.whitehouse/x86_64/stable ff4d83324357 - 1,1 GB system,current FlashPrint Slicer for the FlashForge 3D printers com.flashforge.FlashPrint 4.1.0 stable x86_64 flathub system com.flashforge.FlashPrint/x86_64/stable 944bbcf9bc1c - 11,1 MB system,current Ferdi Messenger for the desktop com.getferdi.Ferdi 5.5.0 stable x86_64 flathub system com.getferdi.Ferdi/x86_64/stable 61705410ed40 - 369,0 MB system,current Postman Postman is a complete API development environment. com.getpostman.Postman 7.22.1 stable x86_64 flathub system com.getpostman.Postman/x86_64/stable 37f8c089f0b7 - 1,7 MB system,current teams-for-linux Unofficial Microsoft Teams client for Linux using Electron com.github.IsmaelMartinez.teams_for_linux 1.0.0 stable x86_64 flathub system com.github.IsmaelMartinez.teams_for_linux/x86_64/stable c79b9bb9b992 - 166,8 MB system,current Gydl Download content from sites like YouTube com.github.JannikHv.Gydl 0.1.1 stable x86_64 flathub system com.github.JannikHv.Gydl/x86_64/stable 2a57569b8d7c - 66,0 MB system,current Forklift Video and audio download application com.github.Johnn3y.Forklift 1.0.0 stable x86_64 flathub system com.github.Johnn3y.Forklift/x86_64/stable d3c4adeadc2b - 34,2 MB system,current Pinta Edit images and paint digitally com.github.PintaProject.Pinta 1.6 stable x86_64 flathub system com.github.PintaProject.Pinta/x86_64/stable baac6770e2e9 - 85,4 MB system,current Sequeler Friendly SQL Client com.github.alecaddd.sequeler 0.7.5 stable x86_64 flathub system com.github.alecaddd.sequeler/x86_64/stable cb598c1d2705 - 152,4 MB system,current GraphUI Graph Visualization com.github.artemanufrij.graphui 1.1.1 stable x86_64 flathub system com.github.artemanufrij.graphui/x86_64/stable e33897c2d0e2 - 97,5 MB system,current Cinema A video player for watching local video files com.github.artemanufrij.playmyvideos 1.1.2 stable x86_64 flathub system com.github.artemanufrij.playmyvideos/x86_64/stable 2b6d6b0d1e02 - 95,0 MB system,current VServer Acces to your files from any device in the same network com.github.bcedu.valasimplehttpserver 1.3.5 stable x86_64 flathub system com.github.bcedu.valasimplehttpserver/x86_64/stable b8b236cb61d1 - 97,6 MB system,current Julius Julius is an open source re-implementation of Caesar III com.github.bvschaik.julius 1.4.0 stable x86_64 flathub system com.github.bvschaik.julius/x86_64/stable 32cbd8039f44 - 3,3 MB system,current MoonPlayer Video player for playing and downloading online videos from YouTube, Youku etc. com.github.coslyk.MoonPlayer 3.1 stable x86_64 flathub system com.github.coslyk.MoonPlayer/x86_64/stable a151e3874f78 - 35,1 MB system,current Cow's Revenge Indie Platformer Pixel Art Game com.github.dariasteam.cowsrevenge 1.3 stable x86_64 flathub system com.github.dariasteam.cowsrevenge/x86_64/stable bc314a4502fe - 39,4 MB system,current Cozy A modern audio book player com.github.geigi.cozy 0.6.16 stable x86_64 flathub system com.github.geigi.cozy/x86_64/stable 836f1b2a4df2 - 7,4 MB system,current Hopsan A modelling and simulation tool for fluid power and mechatronic systems com.github.hopsan.Hopsan 2.14.2 stable x86_64 flathub system com.github.hopsan.Hopsan/x86_64/stable 5d0d5bf310f4 - 66,1 MB system,current Coin Never miss out on the monetary value of a virtual currency with this handy applet com.github.lainsce.coin 1.2.5 stable x86_64 flathub system com.github.lainsce.coin/x86_64/stable 5782c0569405 - 94,3 MB system,current Notejot Anote suas ideias com.github.lainsce.notejot 1.5.6 stable x86_64 flathub system com.github.lainsce.notejot/x86_64/stable 7cb55716833f - 97,6 MB system,current Moneta Monitor the exchange rates of real-world currencies on your desktop com.github.matfantinel.moneta 2.1.0 stable x86_64 flathub system com.github.matfantinel.moneta/x86_64/stable c6c13ce5b8e4 - 89,4 MB system,current HackUp Leia o Hacker News pelo desktop com.github.mdh34.hackup 1.1.8 stable x86_64 flathub system com.github.mdh34.hackup/x86_64/stable 2b905a3a67da - 94,9 MB system,current Tor Browser Launcher A program to help you download, keep updated, and run the Tor Browser Bundle com.github.micahflee.torbrowser-launcher 0.3.2 stable x86_64 flathub system com.github.micahflee.torbrowser-launcher/x86_64/stable 683f23f798d9 - 32,7 MB system,current EasySSH Gerenciador de Conexões SSH com.github.muriloventuroso.easyssh 1.6.6 stable x86_64 flathub system com.github.muriloventuroso.easyssh/x86_64/stable e38c2835f765 - 94,8 MB system,current OTPClient GTK+ application for managing TOTP and HOTP tokens with built-in encryption. com.github.paolostivanin.OTPClient 2.3.0 stable x86_64 flathub system com.github.paolostivanin.OTPClient/x86_64/stable a365dfa467d4 - 2,8 MB system,current Spice-Up Create simple and beautiful presentations com.github.philip_scott.spice-up 1.8.2 stable x86_64 flathub system com.github.philip_scott.spice-up/x86_64/stable d1ca5a6f5f53 - 98,0 MB system,current Quaternion Qt5-based client for Matrix networks com.github.quaternion 0.0.9.4 stable x86_64 flathub system com.github.quaternion/x86_64/stable c0e63417547c - 2,5 MB system,current Ciano Um conversor de arquivos multimídia com.github.robertsanseries.ciano 0.1.8 stable x86_64 flathub system com.github.robertsanseries.ciano/x86_64/stable 27725a60661a - 120,3 MB system,current RSS Guard Simple (yet powerful) feed reader com.github.rssguard 3.6.1 stable x86_64 flathub system com.github.rssguard/x86_64/stable b7defd52743d - 5,7 MB system,current Flatseal Um gerenciador de permissões para Flatpak com.github.tchx84.Flatseal 1.5.3 stable x86_64 flathub system com.github.tchx84.Flatseal/x86_64/stable cfb03e1a070a - 970,2 kB system,current Video Downloader Download videos from websites like YouTube and many others com.github.unrud.VideoDownloader 0.2.9 stable x86_64 flathub system com.github.unrud.VideoDownloader/x86_64/stable 38b9a0f0302c - 31,2 MB system,current PulseEffects Efeitos de Áudio para Programas que Utilizam Pulseaudio com.github.wwmm.pulseeffects 4.6.8 stable x86_64 flathub system com.github.wwmm.pulseeffects/x86_64/stable 0069ef34aaa1 - 38,4 MB system,current Cumulonimbus A simple, beautiful podcast app com.github.z.Cumulonimbus 1.9.6 stable x86_64 flathub system com.github.z.Cumulonimbus/x86_64/stable 100e7531234c - 193,0 MB system,current Qwertone Turns your PC into musical instrument com.gitlab.azymohliad.Qwertone 0.2.0 stable x86_64 flathub system com.gitlab.azymohliad.Qwertone/x86_64/stable 424648434b63 - 707,1 kB system,current Meteo Saber a previsão para as próximas horas e dias, com dados e mapas com.gitlab.bitseater.meteo 0.9.8 stable x86_64 flathub system com.gitlab.bitseater.meteo/x86_64/stable 5947a955a0f1 - 1,6 MB system,current Android Studio Integrated development environment for Google's Android platform com.google.AndroidStudio 3.6.3.0 stable x86_64 flathub system com.google.AndroidStudio/x86_64/stable eea532981344 - 46,2 MB system,current Google Chrome Navegador popular do Google com.google.Chrome 83.0.4103.61-1 eos3 x86_64 eos-apps system com.google.Chrome/x86_64/eos3 b64e9ec5fb51 - 2,1 MB system,current Tremulous Aliens vs Humans, First Person Shooter game with elements of Real Time Strategy com.grangerhub.Tremulous 1.3.0-alpha.0.14 stable x86_64 flathub system com.grangerhub.Tremulous/x86_64/stable ffd79b71a75a - 112,0 MB system,current Hack The destination for kids to learn how to code com.hack_computer.Clubhouse 0.0.99 eos3 x86_64 eos-apps system com.hack_computer.Clubhouse/x86_64/eos3 a884a99b79ca - 225,0 MB system,current System System lets you be part of the magic that keeps your computer humming! com.hack_computer.OperatingSystemApp 1.1 eos3 x86_64 eos-apps system com.hack_computer.OperatingSystemApp/x86_64/eos3 2d767e9a46fe - 14,7 MB system,current Project Library This app is part of the overall Hack experience. com.hack_computer.ProjectLibrary eos3 x86_64 eos-apps system com.hack_computer.ProjectLibrary/x86_64/eos3 21cda5cce6a8 - 14,1 MB system,current Sidetrack Escape the maze of pits and robots! com.hack_computer.Sidetrack 1.1 eos3 x86_64 eos-apps system com.hack_computer.Sidetrack/x86_64/eos3 bfedf1a0f805 - 7,8 MB system,current Inform 7 Write interactive fiction com.inform7.IDE 6M62 stable x86_64 flathub system com.inform7.IDE/x86_64/stable aab3c906b576 - 88,7 MB system,current RuneScape A free-to-play fantasy MMORPG com.jagex.RuneScape 2.2.7 stable x86_64 flathub system com.jagex.RuneScape/x86_64/stable f2ccffcdec84 - 27,9 MB system,current DataGrip IntelliJ-based IDE for databases and SQL com.jetbrains.DataGrip 2020.1.3 stable x86_64 flathub system com.jetbrains.DataGrip/x86_64/stable c4348318529d - 560,6 kB system,current IntelliJ IDEA Community Capable and Ergonomic Java IDE com.jetbrains.IntelliJ-IDEA-Community 2020.1.1 stable x86_64 flathub system com.jetbrains.IntelliJ-IDEA-Community/x86_64/stable 08658fcac1d1 - 1,1 GB system,current IntelliJ IDEA Ultimate Capable and Ergonomic Java IDE for Enterprise, Web and Mobile Development com.jetbrains.IntelliJ-IDEA-Ultimate 2020.1.1 stable x86_64 flathub system com.jetbrains.IntelliJ-IDEA-Ultimate/x86_64/stable 1a0c7791493d - 562,2 kB system,current PhpStorm PHP IDE for Professional Development com.jetbrains.PhpStorm 2020.1.1 stable x86_64 flathub system com.jetbrains.PhpStorm/x86_64/stable 2cf59d626242 - 559,1 kB system,current PyCharm-Community The most intelligent Python IDE com.jetbrains.PyCharm-Community 2020.1.1 stable x86_64 flathub system com.jetbrains.PyCharm-Community/x86_64/stable 72d2be4d3012 - 803,5 MB system,current PyCharm-Professional The most intelligent Python IDE com.jetbrains.PyCharm-Professional 2020.1.1 stable x86_64 flathub system com.jetbrains.PyCharm-Professional/x86_64/stable d95b69dabc2e - 24,9 MB system,current Rider Fast & powerful, cross platform .NET IDE com.jetbrains.Rider 2020.1.3 stable x86_64 flathub system com.jetbrains.Rider/x86_64/stable 7360076849c1 - 27,1 kB system,current WebStorm The smartest JavaScript IDE com.jetbrains.WebStorm 2020.1.1 stable x86_64 flathub system com.jetbrains.WebStorm/x86_64/stable 52bbce51cfea - 24,8 MB system,current draw.io Crie e compartilhe diagramas com.jgraph.drawio.desktop 12.9.3 stable x86_64 flathub system com.jgraph.drawio.desktop/x86_64/stable 459a5043599e - 269,8 MB system,current Metronome A simple Metronome application for the GNOME desktop com.jvieira.tpt.Metronome 0.1.0 stable x86_64 flathub system com.jvieira.tpt.Metronome/x86_64/stable 7fa5a66d60d1 - 913,9 kB system,current Katawa Shoujo A bishoujo-style visual novel com.katawa_shoujo.KatawaShoujo 1.3.1 stable x86_64 flathub system com.katawa_shoujo.KatawaShoujo/x86_64/stable 11d5083fe684 - 598,0 MB system,current Mattermost Opensource team chat com.mattermost.Desktop 4.4.1 stable x86_64 flathub system com.mattermost.Desktop/x86_64/stable 2b060ee5b017 - 283,5 MB system,current Microsoft Teams O Microsoft Teams é o hub de trabalho em equipe do Office 365 com.microsoft.Teams 1.3.00.5153 stable x86_64 flathub system com.microsoft.Teams/x86_64/stable ce82ecd883c6 - 3,9 MB system,current Total Chaos Survival horror set on a remote island known as Fort Oasis com.moddb.TotalChaos 1.0 stable x86_64 flathub system com.moddb.TotalChaos/x86_64/stable cd83445aefc0 - 1,6 GB system,current Minecraft Crie seu próprio mundo em um dos videogames mais populares com.mojang.Minecraft 2.1.14403 stable x86_64 flathub system com.mojang.Minecraft/x86_64/stable 67537c054fb2 - 201,5 MB system,current Moonlight Play games remotely from your NVIDIA GameStream-enabled PC com.moonlight_stream.Moonlight 2.1.0 stable x86_64 flathub system com.moonlight_stream.Moonlight/x86_64/stable 500d2017c973 - 5,6 MB system,current Notepadqq An advanced text editor com.notepadqq.Notepadqq 1.4.8 stable x86_64 flathub system com.notepadqq.Notepadqq/x86_64/stable a5c8fc6de090 - 97,0 MB system,current OBS Studio Live streaming and video recording software com.obsproject.Studio 25.0.8 stable x86_64 flathub system com.obsproject.Studio/x86_64/stable ee065632ecba - 45,2 MB system,current VidCutter Media Cutter + Joiner com.ozmartians.VidCutter 6.0.0.7 stable x86_64 flathub system com.ozmartians.VidCutter/x86_64/stable 82d4e08ecbe6 - 102,4 MB system,current 0 A.D. Real-Time Strategy Game of Ancient Warfare com.play0ad.zeroad 0.0.23 stable x86_64 flathub system com.play0ad.zeroad/x86_64/stable 3b9ff00b8893 - 2,2 GB system,current PrusaSlicer Powerful 3D printing slicer optimized for Prusa printers com.prusa3d.PrusaSlicer 2.2.0-1 stable x86_64 flathub system com.prusa3d.PrusaSlicer/x86_64/stable a5f2567f8f64 - 168,6 MB system,current RawTherapee An advanced raw photo development program com.rawtherapee.RawTherapee 5.8 stable x86_64 flathub system com.rawtherapee.RawTherapee/x86_64/stable a1eee180b7c6 - 122,5 MB system,current WolfenDoom: Blade of Agony Story-driven FPS inspired by WWII shooters from the 90's and early 2000's com.realm667.WolfenDoom_Blade_of_Agony 2.0 stable x86_64 flathub system com.realm667.WolfenDoom_Blade_of_Agony/x86_64/stable e99b246bdad0 - 459,9 MB system,current Blastem A Sega Mega Drive/Genesis, and Master System emulator com.retrodev.blastem 0.6.2 stable x86_64 flathub system com.retrodev.blastem/x86_64/stable 98e9160d3b87 - 2,4 MB system,current Digital: A Love Story A computer mystery/romance set five minutes into the future of 1988 com.scoutshonour.Digital stable x86_64 flathub system com.scoutshonour.Digital/x86_64/stable cd2c0e81ef1f - 152,6 MB system,current don't take it personally, babe, it just ain't your story A spiritual sequel of sorts to Digital: A Love Story, set in a prestigious private high school, and on the social networks of 2027 com.scoutshonour.dtipbijays stable i386 flathub system com.scoutshonour.dtipbijays/i386/stable b80f1857b922 - 52,6 MB system,current Shattered Pixel Dungeon Roguelike RPG, with pixel art graphics and lots of variety and replayability com.shatteredpixel.shatteredpixeldungeon 0.8.0b stable x86_64 flathub system com.shatteredpixel.shatteredpixeldungeon/x86_64/stable 91912dcca15a - 188,2 MB system,current crush com.sigmyne.crush stable x86_64 flathub system com.sigmyne.crush/x86_64/stable 34c027cb119b - 192,6 MB system,current Skype Call and message skype users, with video chat support com.skype.Client 8.60.0.76 stable x86_64 flathub system com.skype.Client/x86_64/stable 18f8d005ce4d - 4,0 MB system,current Snes9x A Super Nintendo emulator com.snes9x.Snes9x 1.60 stable x86_64 flathub system com.snes9x.Snes9x/x86_64/stable d5af57ee543c - 9,2 MB system,current Spotify Online music streaming service com.spotify.Client 1.1.26.501 stable x86_64 flathub system com.spotify.Client/x86_64/stable f4d7a1bbc93a - 33,8 MB system,current Sublime Merge Sublime Merge is a Git client, from the makers of Sublime Text com.sublimemerge.App 0.1119 stable x86_64 flathub system com.sublimemerge.App/x86_64/stable b86ff1b14543 - 10,6 MB system,current Sublime Text Sophisticated text editor for code, markup and prose com.sublimetext.three 3.2.2 stable x86_64 flathub system com.sublimetext.three/x86_64/stable 3b95453ad5df - 66,6 kB system,current Sweet Home 3D Sweet Home 3D Interior Design Application com.sweethome3d.Sweethome3d 6.3 stable x86_64 flathub system com.sweethome3d.Sweethome3d/x86_64/stable 0ad39e1a98d2 - 141,6 MB system,current SmartGit Get your commit done com.syntevo.SmartGit 20.1.2 stable x86_64 flathub system com.syntevo.SmartGit/x86_64/stable cedb0a6312c4 - 47,7 MB system,current Tux, of Math Command TuxMath is an arcade game that helps kids practice their math facts com.tux4kids.tuxmath 2.0.3 stable x86_64 flathub system com.tux4kids.tuxmath/x86_64/stable c2b07896e5a1 - 16,4 MB system,current Unity Hub Real-time game engine com.unity.UnityHub 2.3.1 stable x86_64 flathub system com.unity.UnityHub/x86_64/stable 9ad41240d24d - 3,6 MB system,current Steam Jogue jogos populares e os últimos lançamentos com.valvesoftware.Steam 1.0.0.62 stable x86_64 flathub system com.valvesoftware.Steam/x86_64/stable a2f3d2042084 - 81,0 MB system,current Viber We connect people, no matter who they are or where they are from. com.viber.Viber 11.9 stable x86_64 flathub system com.viber.Viber/x86_64/stable 2185a362376d - 35,1 MB system,current AstroMenace Hardcore 3D space scroll-shooter with spaceship upgrade possibilities com.viewizard.AstroMenace 1.4.1 stable x86_64 flathub system com.viewizard.AstroMenace/x86_64/stable b5382b4d995f - 118,3 MB system,current Visual Studio Code Visual Studio Code. Code editing. Redefined. com.visualstudio.code 1.45.1-1589445302 stable x86_64 flathub system com.visualstudio.code/x86_64/stable c141719f7eaa - 3,8 MB system,current Visual Studio Code - OSS Visual Studio Code. Code editing. Redefined. com.visualstudio.code.oss 1.41.1 stable x86_64 flathub system com.visualstudio.code.oss/x86_64/stable 34a80c5ed83a - 231,7 MB system,current Wire The most secure collaboration platform com.wire.WireDesktop 3.17.2924 stable x86_64 flathub system com.wire.WireDesktop/x86_64/stable 97f7204238bb - 180,9 MB system,current WPS Office WPS Office Suite com.wps.Office 11.1.0.9505 stable x86_64 flathub system com.wps.Office/x86_64/stable 9f75cb1126fd - 281,9 MB system,current Sinuca Divertido jogo de sinuca em 3D de.billardgl.Billardgl 1.75 stable x86_64 flathub system de.billardgl.Billardgl/x86_64/stable 433a9ec571d7 - 8,9 MB system,current Titania X3D Editor Edit, view, and navigate in X3D and VRML worlds de.create3000.titania 4.6.9 stable x86_64 flathub system de.create3000.titania/x86_64/stable b2c5c0469e4d - 314,7 MB system,current Fragments A BitTorrent Client de.haeckerfelix.Fragments 1.4 stable x86_64 flathub system de.haeckerfelix.Fragments/x86_64/stable 8c1d8c1dd12f - 2,3 MB system,current Gradio Find and listen to internet radio stations de.haeckerfelix.gradio 7.3 stable x86_64 flathub system de.haeckerfelix.gradio/x86_64/stable 8b3f1a2e082f - 1,1 MB system,current RDPlot RDPlot is a tool for plotting rate distortion curves de.rwth_aachen.ient.RDPlot 1.3.1 stable x86_64 flathub system de.rwth_aachen.ient.RDPlot/x86_64/stable 0022b9b1a166 - 203,8 MB system,current Jameica Application-Platform similar to OSGI de.willuhn.Jameica 2.8.6 stable x86_64 flathub system de.willuhn.Jameica/x86_64/stable 12debe9e6667 - 199,0 MB system,current Scratch Create stories, games, and animations, share with others around the world edu.mit.Scratch 3.6.0 stable x86_64 flathub system edu.mit.Scratch/x86_64/stable 123e220a8e83 - 512,6 MB system,current The Amazing Rules Of TAROT Play a game of Tarot against the artificial intelligence eu.planete_kraus.Tarot 1.5.2 stable x86_64 flathub system eu.planete_kraus.Tarot/x86_64/stable da27909a9a23 - 21,6 MB system,current HomeBank Contabilidade pessoal fácil e gratuita para todos fr.free.Homebank stable x86_64 flathub system fr.free.Homebank/x86_64/stable 7e836d8380ba - 40,7 MB system,current Natron Open-source video compositing software fr.natron.Natron 2.3.14 stable x86_64 flathub system fr.natron.Natron/x86_64/stable 1ac5981d830e - 500,5 MB system,current Pidgin Cliente de mensagens instantâneas im.pidgin.Pidgin 2.13.0 stable x86_64 flathub system im.pidgin.Pidgin/x86_64/stable 52b3fcfd2766 - 19,9 MB system,current BibleTime Bible Study Program info.bibletime.BibleTime 3.0.0_rc1 stable x86_64 flathub system info.bibletime.BibleTime/x86_64/stable 2864a7442f11 - 87,5 MB system,current Colobot Colonize with bots info.colobot.Colobot 0.1.12 stable x86_64 flathub system info.colobot.Colobot/x86_64/stable 2238fd098be9 - 155,3 MB system,current Atom A hackable text editor for the 21st Century io.atom.Atom 1.45.0 stable x86_64 flathub system io.atom.Atom/x86_64/stable 03453d16b0fd - 589,0 MB system,current Brackets An open source code editor for the web io.brackets.Brackets 1.14 stable x86_64 flathub system io.brackets.Brackets/x86_64/stable 30faa3a67f99 - 353,5 MB system,current DBeaver Community Universal Database Manager. io.dbeaver.DBeaverCommunity 7.0.5 stable x86_64 flathub system io.dbeaver.DBeaverCommunity/x86_64/stable c183293d6507 - 234,2 MB system,current Gravit Designer Vector design app io.designer.GravitDesigner 2020-1.2.1 stable x86_64 flathub system io.designer.GravitDesigner/x86_64/stable 19f31e19c210 - 1,7 MB system,current Exodus All-in-one app to secure, manage, and exchange blockchain assets io.exodus.Exodus 20.5.22 stable x86_64 flathub system io.exodus.Exodus/x86_64/stable c334d20b365d - 1,7 MB system,current FreeTube An Open Source YouTube app for privacy io.freetubeapp.FreeTube 0.7.2 Beta stable x86_64 flathub system io.freetubeapp.FreeTube/x86_64/stable 4b789148d9d0 - 382,9 MB system,current OpenToonz 2D animation io.github.OpenToonz 1.4.0 stable x86_64 flathub system io.github.OpenToonz/x86_64/stable 77547ab27a83 - 84,8 MB system,current Material Maker Procedural texture generation tool io.github.RodZill4.Material-Maker 0.9 stable x86_64 flathub system io.github.RodZill4.Material-Maker/x86_64/stable 87f970a845d5 - 52,9 MB system,current Endless Sky Space exploration and combat game io.github.endless_sky.endless_sky 0.9.12 stable x86_64 flathub system io.github.endless_sky.endless_sky/x86_64/stable 66d20b844475 - 339,0 MB system,current FreeDM Deathmatch game based on the Doom engine io.github.freedoom.FreeDM 0.12.1 stable x86_64 flathub system io.github.freedoom.FreeDM/x86_64/stable 433a83430bea - 45,4 MB system,current FMIT Afinador de Instrumentos Musicais Livre (FMIT), uma ferramenta para afinar instrumentos musicais io.github.gillesdegottex.FMIT 1.2.13 stable x86_64 flathub system io.github.gillesdegottex.FMIT/x86_64/stable 80930178ef98 - 1,1 MB system,current Goxel Open Source 3D voxel editor io.github.guillaumechereau.Goxel v0.7.3 stable x86_64 flathub system io.github.guillaumechereau.Goxel/x86_64/stable 2a43cae634c7 - 1,5 MB system,current HakuNeko A cross-platform downloader for manga and anime from various websites io.github.hakuneko.HakuNeko v6.1.7 stable x86_64 flathub system io.github.hakuneko.HakuNeko/x86_64/stable b130a8b28867 - 185,2 MB system,current Flowblade Video Editor - Fast, Precise, Stable io.github.jliljebl.Flowblade 2.4 stable x86_64 flathub system io.github.jliljebl.Flowblade/x86_64/stable fdfc29b12d52 - 124,6 MB system,current Engauge Digitizer interactively convert a bitmap graph or map into numbers io.github.markummitchell.Engauge_Digitizer 12.1 stable x86_64 flathub system io.github.markummitchell.Engauge_Digitizer/x86_64/stable b90ba249bd39 - 25,6 MB system,current enve 2D animation io.github.maurycyliebner.enve 0.0.0c-1be1483 stable x86_64 flathub system io.github.maurycyliebner.enve/x86_64/stable fb11ca57b50f - 213,2 MB system,current MKI3D Game A simple OpenGL game of searching for tokens in 3D stages io.github.mki1967.mki3dgame 2.05 stable x86_64 flathub system io.github.mki1967.mki3dgame/x86_64/stable db8a80c3f320 - 10,4 MB system,current Pure Maps Maps and navigation io.github.rinigus.PureMaps 1.26.2 stable x86_64 flathub system io.github.rinigus.PureMaps/x86_64/stable ad4bc774a1cc - 144,2 MB system,current Minigalaxy A simple GOG client for Linux io.github.sharkwouter.Minigalaxy 0.9.1 stable x86_64 flathub system io.github.sharkwouter.Minigalaxy/x86_64/stable 708d5280022c - 25,3 MB system,current e2designer Skin editor for enigma2 written with Qt5 io.github.technic.e2designer 0.2 stable x86_64 flathub system io.github.technic.e2designer/x86_64/stable 435048e01262 - 1,9 MB system,current ghostwriter Distraction-free text editor for Markdown io.github.wereturtle.ghostwriter 1.8.0 stable x86_64 flathub system io.github.wereturtle.ghostwriter/x86_64/stable 70147e994bc5 - 136,6 MB system,current O20.Word Open Source MS Word 2019 clone... for Linux io.gitlab.o20.word 20.1.3 stable x86_64 flathub system io.gitlab.o20.word/x86_64/stable cb84752bb9d2 - 20,5 MB system,current Lugaru HD Third person ninja rabbit fighting game io.gitlab.osslugaru.Lugaru stable x86_64 flathub system io.gitlab.osslugaru.Lugaru/x86_64/stable deca70255ace - 39,1 MB system,current LBRY A browser and wallet for LBRY, the decentralized, user-controlled content marketplace. io.lbry.lbry-app 0.45.2 stable x86_64 flathub system io.lbry.lbry-app/x86_64/stable 94d23366b319 - 364,3 MB system,current LMMS A music production application io.lmms.LMMS 1.2.1 stable x86_64 flathub system io.lmms.LMMS/x86_64/stable db0272374297 - 140,1 MB system,current WebTorrent Streaming torrent app io.webtorrent.WebTorrent 0.2.1 stable x86_64 flathub system io.webtorrent.WebTorrent/x86_64/stable f931447adb84 - 227,2 MB system,current OpenSpades Open Source voxel shooter jp.yvt.OpenSpades 0.1.3 stable x86_64 flathub system jp.yvt.OpenSpades/x86_64/stable b29d7c26314b - 15,8 MB system,current Anki Powerful, intelligent flash cards net.ankiweb.Anki 2.1.15 stable x86_64 flathub system net.ankiweb.Anki/x86_64/stable c25c86b1d720 - 34,8 MB system,current GetIt Send HTTP requests to API endpoints net.bartkessels.getit 4.0.9 stable x86_64 flathub system net.bartkessels.getit/x86_64/stable e22b5d5f9253 - 4,5 MB system,current BlockOut II A free adaptation of the original BlockOut game net.blockout.BlockOutII 2.5 stable x86_64 flathub system net.blockout.BlockOutII/x86_64/stable 315280a82c57 - 6,1 MB system,current Master PDF Editor View, create, modify, sign, scan, OCR and print PDF documents net.codeindustry.MasterPDFEditor 5.4.38 stable x86_64 flathub system net.codeindustry.MasterPDFEditor/x86_64/stable 224b19f9a26b - 15,0 MB system,current Doomsday Engine Enhanced source port of Doom, Heretic, and Hexen net.dengine.Doomsday 2.2.2 stable x86_64 flathub system net.dengine.Doomsday/x86_64/stable 2a30f224b41c - 172,6 MB system,current Gwyddion Program for SPM (scanning probe microscopy) data visualization and analysis net.gwyddion.Gwyddion 2.55 stable x86_64 flathub system net.gwyddion.Gwyddion/x86_64/stable 0a508dc69d2e - 25,9 MB system,current SLADE It's a Doom editor net.mancubus.SLADE 3.1.11 stable x86_64 flathub system net.mancubus.SLADE/x86_64/stable ca7f77d3da75 - 297,6 MB system,current MediaInfo Convenient unified display of the most relevant technical and tag data for video and audio files net.mediaarea.MediaInfo 20.03 stable x86_64 flathub system net.mediaarea.MediaInfo/x86_64/stable 327458d59132 - 33,1 MB system,current ONVIFViewer Ver e controlar câmeras de rede usando o protocolo ONVIF net.meijn.onvifviewer 0.12 stable x86_64 flathub system net.meijn.onvifviewer/x86_64/stable 5fefdb12815c - 6,7 MB system,current Minetest Multiplayer infinite-world block sandbox game net.minetest.Minetest 5.2.0 stable x86_64 flathub system net.minetest.Minetest/x86_64/stable cd4226cd553b - 34,2 MB system,current OpenRA Reimagining of early Westwood real-time strategy games net.openra.OpenRA release-20200503 stable x86_64 flathub system net.openra.OpenRA/x86_64/stable 3a93ef3996ce - 117,6 MB system,current Gpredict Real-time satellite tracking and orbit prediction program net.oz9aec.Gpredict 2.2.1 stable x86_64 flathub system net.oz9aec.Gpredict/x86_64/stable 666e4265cc45 - 27,6 MB system,current PCSX2 A Playstation 2 emulator net.pcsx2.PCSX2 1.5.0-dev stable i386 flathub system net.pcsx2.PCSX2/i386/stable cd36b344f672 - 36,3 MB system,current Pioneer A game of lonely space adventure net.pioneerspacesim.Pioneer 20200203 stable x86_64 flathub system net.pioneerspacesim.Pioneer/x86_64/stable 35a984ca75f9 - 673,9 MB system,current Purr Data An open source visual programming language for multimedia, based on Pure Data net.purrdata.PurrData 2.10.1 stable x86_64 flathub system net.purrdata.PurrData/x86_64/stable 8e7b934121d7 - 295,0 MB system,current Red Eclipse First-person shooter with agile gameplay and built-in editor net.redeclipse.RedEclipse 2.0.0 stable x86_64 flathub system net.redeclipse.RedEclipse/x86_64/stable 4a0a1030b906 - 1,1 GB system,current RuneLite RuneLite OSRS Client net.runelite.RuneLite 2.1.0 stable x86_64 flathub system net.runelite.RuneLite/x86_64/stable 801508924c7d - 169,8 MB system,current Scribus Open Source Page Layout and Desktop Publishing (DTP) net.scribus.Scribus 1.5.6.svn stable x86_64 flathub system net.scribus.Scribus/x86_64/stable 79bf6ccd761d - 239,3 MB system,current Nootka Application to learn classical score notation net.sf.nootka 1.4.7 stable x86_64 flathub system net.sf.nootka/x86_64/stable 28c41d9afe97 - 15,6 MB system,current ChessX Free Chess Database net.sourceforge.Chessx 1.5.0 stable x86_64 flathub system net.sourceforge.Chessx/x86_64/stable 225e7fb612b7 - 6,3 MB system,current Extreme Tuxracer High speed arctic racing game based on Tux Racer net.sourceforge.ExtremeTuxRacer 0.8.0 stable x86_64 flathub system net.sourceforge.ExtremeTuxRacer/x86_64/stable 0588cb7a02c0 - 45,7 MB system,current Tux Futebol Um divertido jogo de futebol - estrelando Tux, o pinguim net.sourceforge.TuxFootball 0.3.1 stable x86_64 flathub system net.sourceforge.TuxFootball/x86_64/stable 5fe630d17033 - 20,4 MB system,current VMPK Virtual MIDI Piano Keyboard: a MIDI events generator and receiver net.sourceforge.VMPK 0.7.2 stable x86_64 flathub system net.sourceforge.VMPK/x86_64/stable a6d0074d9496 - 3,4 MB system,current Chromium B.S.U. Fast paced, arcade-style, top-scrolling space shooter net.sourceforge.chromium-bsu 0.9.16.1 stable x86_64 flathub system net.sourceforge.chromium-bsu/x86_64/stable 46b83d417202 - 2,7 MB system,current Frets On Fire Frets on Fire is a game of musical skill and fast fingers. The aim of the game is to play guitar with the keyboard as accurately as possible. net.sourceforge.fretsonfire 1.3.110 stable x86_64 flathub system net.sourceforge.fretsonfire/x86_64/stable 1138bd56a253 - 122,8 MB system,current projectM Music visualizer which uses 3D accelerated iterative image based rendering net.sourceforge.projectM 3.1.1-rc4 stable x86_64 flathub system net.sourceforge.projectM/x86_64/stable ae98d07a636f - 17,4 MB system,current Luminance HDR Create HDR images net.sourceforge.qtpfsgui.LuminanceHDR 2.6.0 stable x86_64 flathub system net.sourceforge.qtpfsgui.LuminanceHDR/x86_64/stable 0dd46d63bed7 - 39,5 MB system,current TORCS The Open Racing Car Simulator net.sourceforge.torcs 1.3.7 stable x86_64 flathub system net.sourceforge.torcs/x86_64/stable 4cc8ebd2b998 - 611,3 MB system,current SuperTuxKart A 3D arcade racer with a variety of characters, tracks, and modes to play. net.supertuxkart.SuperTuxKart 1.1 stable x86_64 flathub system net.supertuxkart.SuperTuxKart/x86_64/stable 0377ef37cc7a - 683,3 MB system,current Veloren Veloren is a multiplayer voxel RPG written in Rust. It is inspired by games such as Cube World, Legend of Zelda: Breath of the Wild, Dwarf Fortress and Minecraft. net.veloren.veloren 0.6.0-2f89b86 stable x86_64 flathub system net.veloren.veloren/x86_64/stable a43125e83ffd - 172,0 MB system,current Warzone2100 In Warzone 2100, you command the forces of The Project in a battle to rebuild the world after mankind has almost been destroyed by nuclear missiles. net.wz2100.wz2100 3.3.0 stable x86_64 flathub system net.wz2100.wz2100/x86_64/stable ae9742cd45ad - 1,1 GB system,current Girens for Plex Girens is a Plex GTK client for playing movies, TV shows and music from your Plex library. nl.g4d.Girens 1.1.6 stable x86_64 flathub system nl.g4d.Girens/x86_64/stable a7c5005484eb - 26,2 MB system,current Bluefish Text editor with many web and software development extras nl.openoffice.bluefish 2.2.10 stable x86_64 flathub system nl.openoffice.bluefish/x86_64/stable f21a6013966d - 7,4 MB system,current Dolphin Emulator GameCube / Wii / Triforce Emulator org.DolphinEmu.dolphin-emu 5.0-11991 stable x86_64 flathub system org.DolphinEmu.dolphin-emu/x86_64/stable c447a15b3c7d - 28,2 MB system,current NetBeans NetBeans - Apache Java IDE. Fits the Pieces Together org.apache.netbeans 11.3 stable x86_64 flathub system org.apache.netbeans/x86_64/stable e89de096ccfe - 1,3 GB system,current Audacious Lightweight audio player org.atheme.audacious 4.0.2 stable x86_64 flathub system org.atheme.audacious/x86_64/stable b42c84a03c49 - 25,4 MB system,current Audacity Record and edit audio files org.audacityteam.Audacity 2.4.1 stable x86_64 flathub system org.audacityteam.Audacity/x86_64/stable 649bacef62f4 - 84,5 MB system,current Bitcoin Core Connect to the Bitcoin P2P network org.bitcoincore.bitcoin-qt 0.19.1 stable x86_64 flathub system org.bitcoincore.bitcoin-qt/x86_64/stable c9b1f0d52404 - 65,5 MB system,current Blender Free and open source 3D creation suite org.blender.Blender 2.82a stable x86_64 flathub system org.blender.Blender/x86_64/stable 550c7b982022 - 273,2 MB system,current BlueJ Java IDE for beginners org.bluej.BlueJ 4.2.2 stable x86_64 flathub system org.bluej.BlueJ/x86_64/stable d245bcd7a416 - 279,7 MB system,current MKVToolNix Matroska files creator and tools org.bunkus.mkvtoolnix-gui 46.0.0 stable x86_64 flathub system org.bunkus.mkvtoolnix-gui/x86_64/stable 65c1182d1e4c - 26,5 MB system,current BZFlag A 3D first person tank battle game org.bzflag.BZFlag 2.4.20 stable x86_64 flathub system org.bzflag.BZFlag/x86_64/stable 734c492a8fa4 - 21,0 MB system,current Code::Blocks IDE IDE for C, C++ and Fortran org.codeblocks.codeblocks 17.12 stable x86_64 flathub system org.codeblocks.codeblocks/x86_64/stable 15cab82e9ebd - 48,9 MB system,current Porto Edit Jupyter notebooks on the desktop org.cvfosammmm.Porto 0.0.2 stable x86_64 flathub system org.cvfosammmm.Porto/x86_64/stable 96819cfadc77 - 48,5 MB system,current darktable Organize and develop images from digital cameras org.darktable.Darktable 3.0.2 stable x86_64 flathub system org.darktable.Darktable/x86_64/stable 1574abd91832 - 51,5 MB system,current Eclipse IDE for Eclipse Committers Package suited for development of Eclipse itself at Eclipse.org; based on the Eclipse Platform adding PDE, Git, Marketplace Client, source code and developer documentation org.eclipse.Committers 4.15 stable x86_64 flathub system org.eclipse.Committers/x86_64/stable 4ecd92d57315 - 1,1 GB system,current Eclipse IDE for Java Developers The essential tools for any Java developer, including a Java IDE, a Git client, XML Editor, Mylyn, Maven and Gradle integration org.eclipse.Java 4.15 stable x86_64 flathub system org.eclipse.Java/x86_64/stable bcbbca8e33bc - 835,0 MB system,current Eclipse 4DIAC IDE An OpenSource IEC 61499 compatible PLC IDE org.eclipse.iot.fourdiac.Ide 1.12.1 stable x86_64 flathub system org.eclipse.iot.fourdiac.Ide/x86_64/stable 6cc128caa348 - 384,2 MB system,current Entangle Tethered Camera Control & Capture org.entangle_photo.Manager 2.0 stable x86_64 flathub system org.entangle_photo.Manager/x86_64/stable 4e44e138007f - 10,2 MB system,current Fedora Media Writer A tool to create a live USB drive with an edition of Fedora org.fedoraproject.MediaWriter 4.1.4 stable x86_64 flathub system org.fedoraproject.MediaWriter/x86_64/stable 90f0eded8744 - 6,0 MB system,current FileZilla FileZilla Client is a fast and reliable cross-platform FTP, FTPS and SFTP client with lots of useful features and an intuitive graphical user interface org.filezillaproject.Filezilla 3.48.1 stable x86_64 flathub system org.filezillaproject.Filezilla/x86_64/stable 5c241d2c2532 - 32,1 MB system,current Flare: Empyrean Campaign A single player, 2D-isometric, action Role-Playing Game org.flarerpg.Flare 1.0 stable x86_64 flathub system org.flarerpg.Flare/x86_64/stable e94ffff58fd3 - 149,6 MB system,current Flatpak Developer Demo Flatpak Developer Demo org.flatpak.qtdemo 1.1.3 stable x86_64 flathub system org.flatpak.qtdemo/x86_64/stable 599363484b9d - 257,5 kB system,current FlightGear Um simulador de voo gratuito e altamente sofisticado org.flightgear.FlightGear 2018.3.2 stable x86_64 flathub system org.flightgear.FlightGear/x86_64/stable 36d918505f0c - 2,8 GB system,current FontForge Um editor de fontes org.fontforge.FontForge 20200314 stable x86_64 flathub system org.fontforge.FontForge/x86_64/stable e0d17abb1636 - 61,7 MB system,current Siril Astronomical image (pre-)processing program org.free_astro.siril 0.9.12 stable x86_64 flathub system org.free_astro.siril/x86_64/stable bb9804931b7a - 42,5 MB system,current FreeCAD An open source parametric 3D CAD modeler org.freecadweb.FreeCAD 0.18.4 stable x86_64 flathub system org.freecadweb.FreeCAD/x86_64/stable fc02da35593e - 740,5 MB system,current FreeCol A free Colonization clone org.freecol.FreeCol stable x86_64 flathub system org.freecol.FreeCol/x86_64/stable c5aaebbf2738 - 212,1 MB system,current Bustle Draw sequence diagrams of D-Bus activity org.freedesktop.Bustle 0.7.5 stable x86_64 flathub system org.freedesktop.Bustle/x86_64/stable 7bc7b122f126 - 12,4 MB system,current GStreamer Debug Viewer Examine GStreamer debug log information org.freedesktop.GstDebugViewer stable x86_64 flathub system org.freedesktop.GstDebugViewer/x86_64/stable 2491d9b19ce4 - 2,0 MB system,current FreeFileSync Visual folder comparison and synchronization org.freefilesync.FreeFileSync 10.24 stable x86_64 flathub system org.freefilesync.FreeFileSync/x86_64/stable a9f74570e8a1 - 55,7 MB system,current Fritzing Electronic Design Tool org.fritzing.Fritzing 0.9.4b stable x86_64 flathub system org.fritzing.Fritzing/x86_64/stable c595162a1d06 - 186,2 MB system,current What IP Info on your IP org.gabmus.whatip 0.1.2 stable x86_64 flathub system org.gabmus.whatip/x86_64/stable 443e753b938d - 13,6 MB system,current Geany A fast and lightweight IDE org.geany.Geany 1.36 stable x86_64 flathub system org.geany.Geany/x86_64/stable 168e928f9177 - 9,8 MB system,current Geeqie A lightweight image viewer org.geeqie.Geeqie v1.5.1 stable x86_64 flathub system org.geeqie.Geeqie/x86_64/stable 2c69732b74c7 - 30,1 MB system,current GeoGebra Um aplicativo de matemática dinâmica org.geogebra.GeoGebra 6.0.581.0 stable x86_64 flathub system org.geogebra.GeoGebra/x86_64/stable 9327b5ed8161 - 1,5 MB system,current Programa de manipulação de imagem do GNU Crie e edite imagens ou fotografias org.gimp.GIMP 2.10.18 stable x86_64 flathub system org.gimp.GIMP/x86_64/stable c01ca44fb07f - 313,9 MB system,current Glimpse Create images and edit photographs org.glimpse_editor.Glimpse 0.1.2 stable x86_64 flathub system org.glimpse_editor.Glimpse/x86_64/stable 770f7a3e2df5 - 231,4 MB system,current NixView Viewer for nix datafiles org.gnode.NixView 0.1 stable x86_64 flathub system org.gnode.NixView/x86_64/stable 032ad490f60b - 43,7 MB system,current Livros Um aplicativo para gerenciamento de e-book para o GNOME org.gnome.Books 3.34.0 stable x86_64 flathub system org.gnome.Books/x86_64/stable 818ad2b88733 - 19,9 MB system,current Caixas GNOME Máquinas virtuais e remotas simples org.gnome.Boxes 3.36.3 stable x86_64 flathub system org.gnome.Boxes/x86_64/stable 34f4ff9f0016 - 679,9 MB system,current Construtor Uma IDE para o GNOME org.gnome.Builder 3.36.0 stable x86_64 flathub system org.gnome.Builder/x86_64/stable 5249fd4662fb - 123,6 MB system,current Calendário Calendário do GNOME org.gnome.Calendar 3.36.1 stable x86_64 flathub system org.gnome.Calendar/x86_64/stable 1bc488546d3c - 17,6 MB system,current Cheese Tire fotos e vídeos com sua webcam, com efeitos gráficos divertidos org.gnome.Cheese 3.34.0 stable x86_64 flathub system org.gnome.Cheese/x86_64/stable 0c054721ac13 - 5,0 MB system,current GNOME Xadrez Jogue o clássico jogo de tabuleiro de xadrez para dois jogadores org.gnome.Chess 3.36.0 stable x86_64 flathub system org.gnome.Chess/x86_64/stable 84e0cf810e8f - 2,4 MB system,current Devhelp Uma ferramenta de desenvolvimento para navegar e pesquisar documentação de API org.gnome.Devhelp 3.36.2 stable x86_64 flathub system org.gnome.Devhelp/x86_64/stable db775ae741b9 - 1,4 MB system,current Dicionário do GNOME Verificar definição e ortografia das palavras em um dicionário on-line org.gnome.Dictionary 3.26.0 stable x86_64 flathub system org.gnome.Dictionary/x86_64/stable 26e520337183 - 2,1 MB system,current Eolie Web browser org.gnome.Eolie 0.9.63 stable x86_64 flathub system org.gnome.Eolie/x86_64/stable 7181480e6c3b - 37,9 MB system,current GNOME Web Navegador da web para o GNOME org.gnome.Epiphany 3.36.1 stable x86_64 flathub system org.gnome.Epiphany/x86_64/stable 81b6d3294196 - 11,0 MB system,current Fractal Aplicativo de mensageria de grupo Matrix org.gnome.Fractal 4.2.2 stable x86_64 flathub system org.gnome.Fractal/x86_64/stable 023ac71e1c3b - 12,7 MB system,current Editor hexadecimal do GNOME Inspecione e edite arquivos binários org.gnome.GHex 3.18.4 stable x86_64 flathub system org.gnome.GHex/x86_64/stable 1287608b14b8 - 2,8 MB system,current Genius Genius is a general purpose calculator program org.gnome.Genius 1.0.25 stable x86_64 flathub system org.gnome.Genius/x86_64/stable cdcf4b7a0c1c - 23,2 MB system,current Glade Crie ou abra projetos de interface com o usuário para aplicativos GTK+ org.gnome.Glade 3.36.0 stable x86_64 flathub system org.gnome.Glade/x86_64/stable 8209cdbecd1f - 4,7 MB system,current HexGL Space racing game org.gnome.HexGL 0.2.0 stable x86_64 flathub system org.gnome.HexGL/x86_64/stable 29c73dbb40f4 - 13,9 MB system,current Player Lollypop Toca e organiza sua coleção de músicas org.gnome.Lollypop 1.2.35 stable x86_64 flathub system org.gnome.Lollypop/x86_64/stable 2e02d1f5713f - 36,5 MB system,current GNOME Mapas Encontrar lugares ao redor do mundo org.gnome.Maps 3.36.2 stable x86_64 flathub system org.gnome.Maps/x86_64/stable aef3834f37b3 - 27,8 MB system,current GNOME Nibbles Guie uma minhoca por um labirinto org.gnome.Nibbles 3.36.0 stable x86_64 flathub system org.gnome.Nibbles/x86_64/stable 7234cbe25ac9 - 1,5 MB system,current Quadrapassel Encaixe blocos que estão caindo org.gnome.Quadrapassel 3.35.92 stable x86_64 flathub system org.gnome.Quadrapassel/x86_64/stable 838e0c4ab501 - 1,1 MB system,current GNOME Reversi Domine o tabuleiro em uma versão clássica do Reversi, ou jogo a variante inversa org.gnome.Reversi 3.36.0 stable x86_64 flathub system org.gnome.Reversi/x86_64/stable e229e5796c75 - 12,3 MB system,current Gravador de som Um gravador de som moderno e simples para o GNOME org.gnome.SoundRecorder 3.34.0 stable x86_64 flathub system org.gnome.SoundRecorder/x86_64/stable 34596ab4880c - 221,2 kB system,current GNOME Tetravex Arranje as peças para encaixarem no quadrado org.gnome.Tetravex 3.36.0 stable x86_64 flathub system org.gnome.Tetravex/x86_64/stable fb187b76d268 - 1,5 MB system,current GNOME 2048 Obtenha o bloco 2048 org.gnome.TwentyFortyEight 3.36.0 stable x86_64 flathub system org.gnome.TwentyFortyEight/x86_64/stable 91ec2ef5d053 - 402,4 kB system,current D-Feet Depure aplicativos D-Bus org.gnome.dfeet 0.3.15 stable x86_64 flathub system org.gnome.dfeet/x86_64/stable de4fbdb3ee48 - 1,8 MB system,current gbrainy O gbrainy é um jogo para você treinar suas habilidades de memória, aritmética e lógica com vários tipos de exercícios de diferentes níveis de dificuldades org.gnome.gbrainy stable x86_64 flathub system org.gnome.gbrainy/x86_64/stable b9d55c4d24e2 - 77,1 MB system,current gitg gui for git org.gnome.gitg 3.32.1 stable x86_64 flathub system org.gnome.gitg/x86_64/stable 1b18f83f116a - 12,1 MB system,current Cowsay Cowsay, a state of the art Cowsay generator using GNOME conventions org.gnome.gitlab.Cowsay 1.7.2 stable x86_64 flathub system org.gnome.gitlab.Cowsay/x86_64/stable a1d833f87581 - 171,5 kB system,current Etiquetas Crie etiquetas, cartões de visita e capas para mídias org.gnome.glabels-3 3.4.1 stable x86_64 flathub system org.gnome.glabels-3/x86_64/stable a10157d82512 - 17,7 MB system,current Meld Compare e mescle seus arquivos org.gnome.meld 3.20.2 stable x86_64 flathub system org.gnome.meld/x86_64/stable d43efc3317eb - 8,3 MB system,current GnuCash Gerencie suas finanças, contas e investimentos org.gnucash.GnuCash 3.10-1 stable x86_64 flathub system org.gnucash.GnuCash/x86_64/stable ba7d206027d8 - 310,6 MB system,current Godot Godot game engine editor org.godotengine.Godot 3.2.1 stable x86_64 flathub system org.godotengine.Godot/x86_64/stable aec4b67fc19a - 64,6 MB system,current Relógio de ponto Kapow Mantenha o registro do tempo gasto em projetos org.gottcode.Kapow 1.5.10 stable x86_64 flathub system org.gottcode.Kapow/x86_64/stable 6d9f48b6af10 - 906,8 kB system,current Horizon EDA A free EDA package org.horizon_eda.HorizonEDA 1.1.0 stable x86_64 flathub system org.horizon_eda.HorizonEDA/x86_64/stable 31994394c529 - 125,5 MB system,current Hydrogen Hydrogen Drum Machine org.hydrogenmusic.Hydrogen 1.0.0-beta2 stable x86_64 flathub system org.hydrogenmusic.Hydrogen/x86_64/stable 69d3aae913ed - 44,3 MB system,current Inkscape Editor de Imagens Vetoriais org.inkscape.Inkscape 1.0 stable x86_64 flathub system org.inkscape.Inkscape/x86_64/stable 90ed46765f25 - 231,9 MB system,current jamovi Real-time statistical spreadsheet org.jamovi.jamovi 1.2.19 stable x86_64 flathub system org.jamovi.jamovi/x86_64/stable b53b0c02c541 - 826,0 MB system,current JDownloader Ferramenta de gerenciamento de download org.jdownloader.JDownloader 2.0 stable x86_64 flathub system org.jdownloader.JDownloader/x86_64/stable b73679768b6a - 189,5 MB system,current Dolphin Gestor de Ficheiros org.kde.dolphin 20.04.1 stable x86_64 flathub system org.kde.dolphin/x86_64/stable c4e14e4092f0 - 17,1 MB system,current Kalzium Tabela Periódica dos Elementos org.kde.kalzium 20.04.1 stable x86_64 flathub system org.kde.kalzium/x86_64/stable 4fc4a4179d68 - 34,8 MB system,current KAtomic Jogo de Lógica Semelhante ao Sokoban org.kde.katomic 20.04.1 stable x86_64 flathub system org.kde.katomic/x86_64/stable 0bf50bd48edb - 34,4 MB system,current KBruch Exercitar Fracções org.kde.kbruch 20.04.1 stable x86_64 flathub system org.kde.kbruch/x86_64/stable 27d0b126f514 - 4,9 MB system,current Kdenlive Editor de Vídeo org.kde.kdenlive 20.04.1 stable x86_64 flathub system org.kde.kdenlive/x86_64/stable e18cde5b489c - 137,3 MB system,current KGeography Ferramenta de aprendizagem de geografia org.kde.kgeography 20.04.1 stable x86_64 flathub system org.kde.kgeography/x86_64/stable dee88be6a10b - 10,2 MB system,current KHangMan Jogo do Enforcado org.kde.khangman 20.04.1 stable x86_64 flathub system org.kde.khangman/x86_64/stable 5aff2662920d - 13,9 MB system,current Batalha Naval Jogo de Batalha Naval org.kde.knavalbattle 2.1.20041 stable x86_64 flathub system org.kde.knavalbattle/x86_64/stable ec7844ad0704 - 34,4 MB system,current KNetWalk O KNetWalk é um jogo para administradores de sistemas org.kde.knetwalk 3.3.20041 stable x86_64 flathub system org.kde.knetwalk/x86_64/stable 0aa9caf50748 - 34,0 MB system,current KolourPaint Programa de Pintura org.kde.kolourpaint 20.04.1 stable x86_64 flathub system org.kde.kolourpaint/x86_64/stable d6031087928e - 8,0 MB system,current Paciência Jogo de cartas do solitário org.kde.kpat 20.04.1 stable x86_64 flathub system org.kde.kpat/x86_64/stable 95e20130c81b - 42,1 MB system,current Krita Pintura Digital, Liberdade Criativa org.kde.krita 4.2.9.0 stable x86_64 flathub system org.kde.krita/x86_64/stable dfaefc1958d8 - 270,2 MB system,current KSudoku Completar um 'puzzle' numérico com os números de um a nove org.kde.ksudoku 1.4.20041 stable x86_64 flathub system org.kde.ksudoku/x86_64/stable 988039516401 - 36,6 MB system,current KTouch Professor de Dactilografia org.kde.ktouch 20.04.1 stable x86_64 flathub system org.kde.ktouch/x86_64/stable 4c041c9069eb - 8,8 MB system,current kubrick Jogo 3-D baseado no Cubo de Rubik org.kde.kubrick 1.1.20041 stable x86_64 flathub system org.kde.kubrick/x86_64/stable 6f8ae84f4a8a - 34,0 MB system,current KXStitch Um criador de padrões de ponto de cruz org.kde.kxstitch 2.2.0 stable x86_64 flathub system org.kde.kxstitch/x86_64/stable 7062bbe5bae2 - 11,4 MB system,current Okular Visualizador do Documento org.kde.okular 1.10.1 stable x86_64 flathub system org.kde.okular/x86_64/stable df5e106e6b53 - 92,5 MB system,current Palapeli Jogo de 'puzzles' org.kde.palapeli 2.1.20041 stable x86_64 flathub system org.kde.palapeli/x86_64/stable d99cd53a292d - 36,4 MB system,current Skrooge Finanças Pessoais org.kde.skrooge 2.22.1 stable x86_64 flathub system org.kde.skrooge/x86_64/stable 46fc822606be - 113,1 MB system,current KiCad EDA Suite org.kicad_pcb.KiCad 5.1.6 stable x86_64 flathub system org.kicad_pcb.KiCad/x86_64/stable 6599ea89f55e - 6,2 GB system,current Kiwix View offline content org.kiwix.desktop 2.0.1 stable x86_64 flathub system org.kiwix.desktop/x86_64/stable 6ec996a336b7 - 20,1 MB system,current TurtleBlocks A Logo-inspired turtle that draws colorful pictures with snap-together visual programming blocks org.laptop.TurtleArtActivity 220 stable x86_64 flathub system org.laptop.TurtleArtActivity/x86_64/stable f399bc4a0562 - 11,4 MB system,current Kolibri Offline education technology platform org.learningequality.Kolibri 0.12.8.1 stable x86_64 flathub system org.learningequality.Kolibri/x86_64/stable 04538c7d1bfa - 286,8 MB system,current LeoCAD Design virtual models you can build with LEGO bricks org.leocad.LeoCAD 19.07.1 stable x86_64 flathub system org.leocad.LeoCAD/x86_64/stable 55f284494040 - 46,6 MB system,current LibreOffice The LibreOffice productivity suite org.libreoffice.LibreOffice 6.4.4.2 stable x86_64 flathub system org.libreoffice.LibreOffice/x86_64/stable a43765652ce9 - 686,9 MB system,current LibrePCB Design Schematics and PCBs org.librepcb.LibrePCB 0.1.4 stable x86_64 flathub system org.librepcb.LibrePCB/x86_64/stable f7461f659b26 - 12,6 MB system,current RetroArch Frontend for emulators, game engines and media players org.libretro.RetroArch 1.8.7 stable x86_64 flathub system org.libretro.RetroArch/x86_64/stable 0c57bc4e9894 - 434,0 MB system,current Hardware Probe Check operability of computer hardware and find drivers org.linux_hardware.hw-probe 1.5 stable x86_64 flathub system org.linux_hardware.hw-probe/x86_64/stable 74e5faefe023 - 17,3 MB system,current Navegador Web Midori A fast and lightweight web browser org.midori_browser.Midori 0.5.11 stable x86_64 flathub system org.midori_browser.Midori/x86_64/stable 56ee4221e805 - 2,0 MB system,current Mixxx DJ Software Everything you need to perform live DJ mixes org.mixxx.Mixxx 2.2.4 stable x86_64 flathub system org.mixxx.Mixxx/x86_64/stable 073efc540b5f - 104,9 MB system,current Thymio Suite Accessing Thymio's programming interfaces easily org.mobsya.ThymioSuite 2.0.2 stable x86_64 flathub system org.mobsya.ThymioSuite/x86_64/stable 0e8c85fc49eb - 173,2 MB system,current Firefox O famoso navegador da Mozilla org.mozilla.Firefox 75.0 eos3 x86_64 eos-apps system org.mozilla.Firefox/x86_64/eos3 43d9d997ce55 - 54,8 MB system,current MuseScore Create, playback, and print sheet music for free org.musescore.MuseScore 3.4.2 stable x86_64 flathub system org.musescore.MuseScore/x86_64/stable e5a106e17fda - 239,3 MB system,current MusE The open source sequencer org.musesequencer.Muse3 3.1.0 stable x86_64 flathub system org.musesequencer.Muse3/x86_64/stable 42daed3343ee - 53,3 MB system,current MyPaint Painting program for digital artists org.mypaint.MyPaint 2.0.0 stable x86_64 flathub system org.mypaint.MyPaint/x86_64/stable 2674a4516a12 - 32,7 MB system,current Nextcloud Nextcloud sync client org.nextcloud.Nextcloud 2.6.4 stable x86_64 flathub system org.nextcloud.Nextcloud/x86_64/stable 4755c241adb7 - 12,1 MB system,current GNU Octave Ambiente de programação interativo para computação numérica org.octave.Octave 5.2.0 stable x86_64 flathub system org.octave.Octave/x86_64/stable 7c4fbf39525f - 397,5 MB system,current Olive Editor de vídeo não-linear org.olivevideoeditor.Olive 0.1.2 stable x86_64 flathub system org.olivevideoeditor.Olive/x86_64/stable 1f583225cd5d - 51,2 MB system,current ONLYOFFICE Desktop Editors Office productivity suite org.onlyoffice.desktopeditors 5.5.1 stable x86_64 flathub system org.onlyoffice.desktopeditors/x86_64/stable d44e9a6495fe - 750,1 MB system,current OpenMW Unofficial open source engine re-implementation of the game Morrowind org.openmw.OpenMW 0.45.0 stable x86_64 flathub system org.openmw.OpenMW/x86_64/stable 9549de131c87 - 58,4 MB system,current OpenSCAD The Programmers Solid 3D CAD Modeller org.openscad.OpenSCAD 2019.05 stable x86_64 flathub system org.openscad.OpenSCAD/x86_64/stable 686d24e2ebce - 28,3 MB system,current OpenShot Video Editor An easy to use, quick to learn, and surprisingly powerful video editor org.openshot.OpenShot 2.5.1 stable x86_64 flathub system org.openshot.OpenShot/x86_64/stable 3c6134ad6ec1 - 241,8 MB system,current JOSM Java OpenStreetMap Editor org.openstreetmap.josm 16238 stable x86_64 flathub system org.openstreetmap.josm/x86_64/stable 067d9ef2b33a - 182,2 MB system,current Open Surge A fun 2D retro platformer inspired by Sonic games and a game creation system org.opensurge2d.OpenSurge 0.5.1.2 stable x86_64 flathub system org.opensurge2d.OpenSurge/x86_64/stable 376de1e10ed2 - 44,6 MB system,current OpenTTD Open source simulation game based upon Transport Tycoon Deluxe org.openttd.OpenTTD 1.10.1 stable x86_64 flathub system org.openttd.OpenTTD/x86_64/stable ce04c683f8c1 - 253,8 MB system,current Pegasus Cross platform, customizable graphical frontend for launching emulators org.pegasus_frontend.Pegasus 0.13 Alpha 13 stable x86_64 flathub system org.pegasus_frontend.Pegasus/x86_64/stable 386770c108cf - 3,5 MB system,current Phoenicis PlayOnLinux Install and run Windows software on Linux org.phoenicis.playonlinux 5.0-alpha-2 stable x86_64 flathub system org.phoenicis.playonlinux/x86_64/stable a24dad589fa1 - 223,8 MB system,current Pitivi Crie e edite os seus próprios filmes org.pitivi.Pitivi 0.999 stable x86_64 flathub system org.pitivi.Pitivi/x86_64/stable 3dfe842f1329 - 129,4 MB system,current Eternal Lands Eternal Lands is a free to play, graphical MMORPG org.pjbroad.EternallandsClient 1.9.5p8 stable x86_64 flathub system org.pjbroad.EternallandsClient/x86_64/stable 48f122735d4a - 229,2 MB system,current PPSSPP A PlayStation Portable emulator org.ppsspp.PPSSPP 1.9.4 stable x86_64 flathub system org.ppsspp.PPSSPP/x86_64/stable b25b0cf4697b - 29,9 MB system,current PulseAudio Volume Control Adjust the volume level of hardware devices and applications org.pulseaudio.pavucontrol 4.0 stable x86_64 flathub system org.pulseaudio.pavucontrol/x86_64/stable ae2131c33143 - 10,9 MB system,current Pyzo A Python IDE aimed at simplicity and interactivity org.pyzo.pyzo 4.9.0 stable x86_64 flathub system org.pyzo.pyzo/x86_64/stable f9027c6316d4 - 35,8 MB system,current qBittorrent An open-source Bittorrent client org.qbittorrent.qBittorrent 4.2.5 stable x86_64 flathub system org.qbittorrent.qBittorrent/x86_64/stable 0e62a597884f - 17,1 MB system,current QGIS Desktop Um Sistema de Informação Geográfica livre e aberto org.qgis.qgis 3.12.3 stable x86_64 flathub system org.qgis.qgis/x86_64/stable d928840c7510 - 1,5 GB system,current qutebrowser A keyboard-driven web browser org.qutebrowser.qutebrowser 1.7.0 stable x86_64 flathub system org.qutebrowser.qutebrowser/x86_64/stable ce1942078211 - 40,6 MB system,current Remmina Remote Desktop Client org.remmina.Remmina 1.4.3 stable x86_64 flathub system org.remmina.Remmina/x86_64/stable 654391089105 - 14,4 MB system,current Robocode Build the best - destroy the rest! org.robocode.Robocode 1.9.3.3 stable x86_64 flathub system org.robocode.Robocode/x86_64/stable e818bf65ab07 - 244,5 MB system,current Sauerbraten Free multiplayer & singleplayer first person shooter, the successor of the Cube FPS org.sauerbraten.Sauerbraten 2013_04_04 stable x86_64 flathub system org.sauerbraten.Sauerbraten/x86_64/stable e611d07e2e24 - 658,1 MB system,current SHADERed Tool for creating and testing HLSL and GLSL shaders org.shadered.SHADERed 1.3.2 stable x86_64 flathub system org.shadered.SHADERed/x86_64/stable aaf0435cb903 - 22,9 MB system,current Shotcut Video editor org.shotcut.Shotcut 20.04.12 stable x86_64 flathub system org.shotcut.Shotcut/x86_64/stable 3d78046a480c - 109,8 MB system,current Signal Desktop Private messenger org.signal.Signal 1.34.1 stable x86_64 flathub system org.signal.Signal/x86_64/stable 12a0ed7f41e0 - 329,6 MB system,current Snap4Arduino Snap! visual programming language for Arduino org.snap4arduino.App eos3 x86_64 eos-apps system org.snap4arduino.App/x86_64/eos3 ef85993906fa - 403,9 MB system,current Speed Dreams Speed Dreams is a 3d cross-platform, open source motorsport simulation and racing game org.speed_dreams.SpeedDreams 2.2.2 stable x86_64 flathub system org.speed_dreams.SpeedDreams/x86_64/stable a07429b5e479 - 1,9 GB system,current SpeedCrunch Calculadora científica de alta precisão org.speedcrunch.SpeedCrunch 0.12 stable x86_64 flathub system org.speedcrunch.SpeedCrunch/x86_64/stable 76389b6aae4c - 3,3 MB system,current Etoys Aprenda com programação virtual org.squeakland.Etoys 5.0.2408 stable x86_64 flathub system org.squeakland.Etoys/x86_64/stable b80a04a442bc - 31,2 MB system,current Sonic Robo Blast 2 A 3D Sonic the Hedgehog fangame based on a modified version of Doom Legacy org.srb2.SRB2 2.2.4 stable x86_64 flathub system org.srb2.SRB2/x86_64/stable 26ed537d8041 - 13,6 MB system,current Sonic Robo Blast 2 Kart A kart racing mod based on the 3D Sonic the Hedgehog fangame Sonic Robo Blast 2 org.srb2.SRB2Kart 1.2 stable x86_64 flathub system org.srb2.SRB2Kart/x86_64/stable 623ea230aa51 - 12,0 MB system,current Stellarium Planetário de Ambiente de Trabalho org.stellarium.Stellarium 0.20.1 stable x86_64 flathub system org.stellarium.Stellarium/x86_64/stable c9252cc20eed - 258,0 MB system,current Subsurface Manage and display dive computer data org.subsurface_divelog.Subsurface v4.9.0 stable x86_64 flathub system org.subsurface_divelog.Subsurface/x86_64/stable 5062feae5686 - 79,0 MB system,current Abacus A tool for simple arithmetic calculations org.sugarlabs.AbacusActivity 61 stable x86_64 flathub system org.sugarlabs.AbacusActivity/x86_64/stable 7f5396cba177 - 13,3 MB system,current FotoToon Create your own comic org.sugarlabs.FotoToon 25 stable x86_64 flathub system org.sugarlabs.FotoToon/x86_64/stable 82d9b025ab10 - 13,4 MB system,current FractionBounce A game about fractions org.sugarlabs.FractionBounce 28.1 stable x86_64 flathub system org.sugarlabs.FractionBounce/x86_64/stable fbdaa6cf398b - 13,9 MB system,current Measure Oscilloscope program for visualizing microphone input org.sugarlabs.Measure 103 stable x86_64 flathub system org.sugarlabs.Measure/x86_64/stable 873fbb8fdeee - 40,2 MB system,current Music Keyboard Play music with this piano keyboard org.sugarlabs.MusicKeyboard 12.1 stable x86_64 flathub system org.sugarlabs.MusicKeyboard/x86_64/stable cef26f62f236 - 44,8 MB system,current Physics Prove Sir Isaac Newton correct org.sugarlabs.Physics 34.1 stable x86_64 flathub system org.sugarlabs.Physics/x86_64/stable cc5229d3c032 - 36,3 MB system,current Pippy Talk to your computer in Python org.sugarlabs.Pippy 75 stable x86_64 flathub system org.sugarlabs.Pippy/x86_64/stable 887e8f860afb - 44,9 MB system,current Sliderule A mechanical calculator org.sugarlabs.Sliderule 35 stable x86_64 flathub system org.sugarlabs.Sliderule/x86_64/stable a124e33ff81e - 13,0 MB system,current Speak An animated face that speaks whatever you type org.sugarlabs.Speak 58 stable x86_64 flathub system org.sugarlabs.Speak/x86_64/stable 67f5b2d90a1a - 62,3 MB system,current Story Tell a story org.sugarlabs.StoryActivity 19.1 stable x86_64 flathub system org.sugarlabs.StoryActivity/x86_64/stable 3cfa36d7e73b - 67,8 MB system,current Words A multilingual offline dictionary org.sugarlabs.Words 24 stable x86_64 flathub system org.sugarlabs.Words/x86_64/stable 96f6e46f71a6 - 101,6 MB system,current Synfig Studio Create and edit 2D animations and compositions org.synfig.SynfigStudio 1.2.2 stable x86_64 flathub system org.synfig.SynfigStudio/x86_64/stable ec94e756def2 - 108,8 MB system,current Telegram Desktop Telegram Desktop messenger org.telegram.desktop 2.1.6 stable x86_64 flathub system org.telegram.desktop/x86_64/stable 04dca004fd89 - 48,9 MB system,current Stunt Rally Racing game with rally style of driving org.tuxfamily.StuntRally 2.6.1 stable x86_64 flathub system org.tuxfamily.StuntRally/x86_64/stable 7a5b454b8fbd - 1,3 GB system,current XMoto 2D motocross platform game org.tuxfamily.XMoto stable x86_64 flathub system org.tuxfamily.XMoto/x86_64/stable 795e77025f51 - 72,1 MB system,current VergeCurrency VergeCurrency, A secure and user-friendly digital currency. org.vergecurrency.verge-qt 6.0.2 stable x86_64 flathub system org.vergecurrency.verge-qt/x86_64/stable a23b3e9f2b54 - 77,2 MB system,current VLC VLC media player, the open-source multimedia player org.videolan.VLC 3.0.10 stable x86_64 flathub system org.videolan.VLC/x86_64/stable 6139e86ee1f8 - 78,2 MB system,current Battle for Wesnoth A turn-based strategy game with a high fantasy theme org.wesnoth.Wesnoth 1.14.12 stable x86_64 flathub system org.wesnoth.Wesnoth/x86_64/stable fcff1e2df38f - 573,1 MB system,current Widelands Um jogo em tempo real de estratégia e evolução org.widelands.Widelands Build 20 stable x86_64 flathub system org.widelands.Widelands/x86_64/stable b9c056a555e3 - 308,4 MB system,current Wireshark Wireshark is the world's foremost protocol analyzer org.wireshark.Wireshark 3.2.2 stable x86_64 flathub system org.wireshark.Wireshark/x86_64/stable 81541ff630dc - 122,8 MB system,current Xonotic Multiplayer, deathmatch oriented first person shooter org.xonotic.Xonotic 0.8.2 stable x86_64 flathub system org.xonotic.Xonotic/x86_64/stable 23d61fc8bf08 - 944,3 MB system,current GZDoom Classic first-person-shooter engine for all classical Id games org.zdoom.GZDoom 4.3.3 stable x86_64 flathub system org.zdoom.GZDoom/x86_64/stable 9d0027e37529 - 22,7 MB system,current Tangram Run web apps on your desktop re.sonny.Tangram 1.2.0 stable x86_64 flathub system re.sonny.Tangram/x86_64/stable 17d0d64b921b - 141,8 kB system,current FIPS OpenGL-based FITS image viewer space.fips.Fips 3.4.0 stable x86_64 flathub system space.fips.Fips/x86_64/stable dcc7a3017f08 - 726,0 kB system,current Kodi Media center tv.kodi.Kodi 18.5-Leia stable x86_64 flathub system tv.kodi.Kodi/x86_64/stable 270aad12949d - 292,2 MB system,current Backgammony A backgammon frontend with multiplayer support uk.jnthn.backgammony 1.0.0 stable x86_64 flathub system uk.jnthn.backgammony/x86_64/stable 6ff608355905 - 14,6 MB system,current Zoom Video Conferencing, Web Conferencing, Webinars, Screen Sharing us.zoom.Zoom 5.0.408598.0517 stable x86_64 flathub system us.zoom.Zoom/x86_64/stable 3099359d3154 - 93,2 kB system,current i2pd Invisible Internet website.i2pd.i2pd 2.30.0 stable x86_64 flathub system website.i2pd.i2pd/x86_64/stable 946d3fb325a8 - 137,7 MB system,current OpenArena Free and open source first-person shooter ws.openarena.OpenArena 0.8.8 stable x86_64 flathub system ws.openarena.OpenArena/x86_64/stable f4c4a9f4005b - 419,2 MB system,current RazerGenie Manage your Razer devices xyz.z3ntu.razergenie 0.8.1 stable x86_64 flathub system xyz.z3ntu.razergenie/x86_64/stable b4e05900b8a2 - 556,0 kB system,current =================== = Flatpak history = =================== mai 23 13:14:00 pull /var/tmp/flatpak-cache-A5OBL0/repo-1dKxgA eos-apps a7908cba8744 a7908cba8744 daniel flatpak 1.6.2 mai 23 13:14:01 pull local system /var/tmp/flatpak-cache-A5OBL0/repo-1dKxgA a7908cba8744 a7908cba8744 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:14:01 pull /var/tmp/flatpak-cache-A5OBL0/repo-BdPXCu eos-runtimes 152606ed8975 152606ed8975 daniel flatpak 1.6.2 mai 23 13:14:02 pull local system /var/tmp/flatpak-cache-A5OBL0/repo-BdPXCu 152606ed8975 152606ed8975 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:14:04 pull /var/tmp/flatpak-cache-A5OBL0/repo-5D7FzC eos-sdk cb34d9876977 cb34d9876977 daniel flatpak 1.6.2 mai 23 13:14:05 pull local system /var/tmp/flatpak-cache-A5OBL0/repo-5D7FzC cb34d9876977 cb34d9876977 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:14:22 pull /var/tmp/flatpak-cache-A5OBL0/repo-p0XQ21 flathub ee5f0a1bcd33 c2ae032972b4 daniel flatpak 1.6.2 mai 23 13:14:24 pull local system /var/tmp/flatpak-cache-A5OBL0/repo-p0XQ21 ee5f0a1bcd33 c2ae032972b4 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:14:38 uninstall ind.ie.Gnomit.Locale x86_64 stable system dd8105130f3b root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:14:39 uninstall io.github.EndlessSky.endless-sky x86_64 stable system 6397a17426f5 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:14:54 pull io.github.maurycyliebner.enve.Locale x86_64 stable /var/tmp/flatpak-cache-A5OBL0/io.github.maurycyliebner.enve.Locale-YMKRK0/repo-qmNTW3 flathub b80541911a2f e43ab2026951 daniel flatpak 1.6.2 mai 23 13:14:59 pull local io.github.maurycyliebner.enve.Locale x86_64 stable system /var/lib/flatpak/repo/tmp/flatpak-cache-TGVAL0/repo-qmNTW3 b80541911a2f e43ab2026951 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:15:00 deploy update io.github.maurycyliebner.enve.Locale x86_64 stable system flathub b80541911a2f e43ab2026951 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:17:14 pull io.exodus.Exodus x86_64 stable /var/tmp/flatpak-cache-A5OBL0/io.exodus.Exodus-W1W4K0/repo-NVfr2z flathub c334d20b365d 19b2dd8fff22 daniel flatpak 1.6.2 mai 23 13:17:22 pull local io.exodus.Exodus x86_64 stable system /var/lib/flatpak/repo/tmp/flatpak-cache-5RZ4K0/repo-NVfr2z c334d20b365d 19b2dd8fff22 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:17:32 deploy update io.exodus.Exodus x86_64 stable system flathub c334d20b365d 19b2dd8fff22 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:17:50 pull com.github.hopsan.Hopsan x86_64 stable /var/tmp/flatpak-cache-A5OBL0/com.github.hopsan.Hopsan-GBYXK0/repo-5IGNFq flathub 5d0d5bf310f4 6e6201232d15 daniel flatpak 1.6.2 mai 23 13:18:11 pull local com.github.hopsan.Hopsan x86_64 stable system /var/lib/flatpak/repo/tmp/flatpak-cache-CJ4WK0/repo-5IGNFq 5d0d5bf310f4 6e6201232d15 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:18:14 deploy update com.github.hopsan.Hopsan x86_64 stable system flathub 5d0d5bf310f4 6e6201232d15 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:18:31 pull io.github.maurycyliebner.enve x86_64 stable /var/tmp/flatpak-cache-A5OBL0/io.github.maurycyliebner.enve-8YMXK0/repo-CSPt5K flathub fb11ca57b50f 93119ff895c1 daniel flatpak 1.6.2 mai 23 13:18:40 pull local io.github.maurycyliebner.enve x86_64 stable system /var/lib/flatpak/repo/tmp/flatpak-cache-K0OXK0/repo-CSPt5K fb11ca57b50f 93119ff895c1 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:18:46 deploy update io.github.maurycyliebner.enve x86_64 stable system flathub fb11ca57b50f 93119ff895c1 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:18:56 pull org.kicad_pcb.KiCad.Locale x86_64 stable /var/tmp/flatpak-cache-A5OBL0/org.kicad_pcb.KiCad.Locale-P0I4K0/repo-9WIVJx flathub d1414b917e6b b2f04b95c2c8 daniel flatpak 1.6.2 mai 23 13:19:00 pull local org.kicad_pcb.KiCad.Locale x86_64 stable system /var/lib/flatpak/repo/tmp/flatpak-cache-QF75K0/repo-9WIVJx d1414b917e6b b2f04b95c2c8 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:19:00 deploy update org.kicad_pcb.KiCad.Locale x86_64 stable system flathub d1414b917e6b b2f04b95c2c8 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:21:16 pull org.kicad_pcb.KiCad x86_64 stable /var/tmp/flatpak-cache-A5OBL0/org.kicad_pcb.KiCad-MLO2K0/repo-lHsVHp flathub 6599ea89f55e 1aed546d7172 daniel flatpak 1.6.2 mai 23 13:22:42 pull local org.kicad_pcb.KiCad x86_64 stable system /var/lib/flatpak/repo/tmp/flatpak-cache-6XL2K0/repo-lHsVHp 6599ea89f55e 1aed546d7172 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:22:52 deploy update org.kicad_pcb.KiCad x86_64 stable system flathub 6599ea89f55e 1aed546d7172 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:23:14 pull org.small_tech.Gnomit.Locale x86_64 stable /var/tmp/flatpak-cache-A5OBL0/org.small_tech.Gnomit.Locale-8591K0/repo-mTimCo flathub ebdb28008c0f daniel flatpak 1.6.2 mai 23 13:23:23 pull local org.small_tech.Gnomit.Locale x86_64 stable system /var/lib/flatpak/repo/tmp/flatpak-cache-JG81K0/repo-mTimCo ebdb28008c0f root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:23:25 deploy install org.small_tech.Gnomit.Locale x86_64 stable system flathub ebdb28008c0f root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:23:44 pull org.wesnoth.Wesnoth.Locale x86_64 stable /var/tmp/flatpak-cache-A5OBL0/org.wesnoth.Wesnoth.Locale-L10UK0/repo-wVnqWc flathub d95095e1f43e d95095e1f43e daniel flatpak 1.6.2 mai 23 13:23:49 pull local org.wesnoth.Wesnoth.Locale x86_64 stable system /var/lib/flatpak/repo/tmp/flatpak-cache-92XUK0/repo-wVnqWc d95095e1f43e d95095e1f43e root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:23:51 deploy update org.wesnoth.Wesnoth.Locale x86_64 stable system flathub d95095e1f43e d95095e1f43e root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:34:55 uninstall com.github.babluboy.bookworm.Locale x86_64 stable system cbb6c0fe3b66 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:34:55 uninstall com.github.naaando.lyrics.Locale x86_64 stable system aff92697d4c1 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:34:56 uninstall com.kristianduske.TrenchBroom.Locale x86_64 stable system 61f5e85f9c21 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:34:56 uninstall org.freedesktop.Platform.openh264 x86_64 19.08 system 416c864f49cf root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:34:56 uninstall org.gnome.OCRFeeder.Locale x86_64 stable system fc4b9fdb965b root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:34:58 uninstall org.gnome.Platform x86_64 3.24 system 6ec840efe68a root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:34:59 uninstall org.gnome.Platform.Locale x86_64 3.24 system 1782298efdcd root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:35:03 uninstall org.gnome.Platform x86_64 3.30 system 540103e81e6d root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:35:10 uninstall org.gnome.Platform.Locale x86_64 3.30 system e390b49e0060 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:35:27 uninstall org.gnome.Sdk x86_64 3.30 system 25cce5916fd8 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:35:32 uninstall org.gnome.Sdk.Locale x86_64 3.30 system 496c36407831 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:35:32 uninstall org.kde.KStyle.Adwaita x86_64 5.9 system 2fbc7ccfecfc root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:35:32 uninstall org.kde.KStyle.HighContrast x86_64 5.9 system 04922bc5a89c root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:35:38 uninstall org.kde.Platform x86_64 5.9 system 1f3f3b021356 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:35:38 uninstall org.kde.Platform.Locale x86_64 5.9 system ec05af508239 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:35:38 uninstall org.kde.PlatformTheme.QGnomePlatform.Sources x86_64 5.9 system 6d6761aa520b root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:35:38 uninstall org.kde.PlatformTheme.QGnomePlatform x86_64 5.9 system 6eda74fee379 root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:35:38 uninstall org.small_tech.Gnomit.Locale x86_64 stable system ebdb28008c0f root (daniel) flatpak-system-helper (flatpak) 1.6.2 mai 23 13:35:38 uninstall org.wesnoth.Wesnoth.Locale x86_64 stable system d95095e1f43e root (daniel) flatpak-system-helper (flatpak) 1.6.2 ============= = Processes = ============= USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.1 167324 11312 ? Ss 13:45 0:01 /lib/systemd/systemd --switched-root --system --deserialize 29 root 2 0.0 0.0 0 0 ? S 13:45 0:00 [kthreadd] root 3 0.0 0.0 0 0 ? I< 13:45 0:00 [rcu_gp] root 4 0.0 0.0 0 0 ? I< 13:45 0:00 [rcu_par_gp] root 6 0.0 0.0 0 0 ? I< 13:45 0:00 [kworker/0:0H-kblockd] root 8 0.0 0.0 0 0 ? I 13:45 0:01 [kworker/u8:0-events_power_efficient] root 9 0.0 0.0 0 0 ? I< 13:45 0:00 [mm_percpu_wq] root 10 0.0 0.0 0 0 ? S 13:45 0:00 [ksoftirqd/0] root 11 0.0 0.0 0 0 ? I 13:45 0:01 [rcu_sched] root 12 0.0 0.0 0 0 ? S 13:45 0:00 [migration/0] root 13 0.0 0.0 0 0 ? S 13:45 0:00 [idle_inject/0] root 14 0.0 0.0 0 0 ? S 13:45 0:00 [cpuhp/0] root 15 0.0 0.0 0 0 ? S 13:45 0:00 [cpuhp/1] root 16 0.0 0.0 0 0 ? S 13:45 0:00 [idle_inject/1] root 17 0.0 0.0 0 0 ? S 13:45 0:00 [migration/1] root 18 0.0 0.0 0 0 ? S 13:45 0:00 [ksoftirqd/1] root 19 0.0 0.0 0 0 ? I 13:45 0:00 [kworker/1:0-events] root 20 0.0 0.0 0 0 ? I< 13:45 0:00 [kworker/1:0H-events_highpri] root 21 0.0 0.0 0 0 ? S 13:45 0:00 [cpuhp/2] root 22 0.0 0.0 0 0 ? S 13:45 0:00 [idle_inject/2] root 23 0.0 0.0 0 0 ? S 13:45 0:00 [migration/2] root 24 0.0 0.0 0 0 ? S 13:45 0:00 [ksoftirqd/2] root 26 0.0 0.0 0 0 ? I< 13:45 0:00 [kworker/2:0H-kblockd] root 27 0.0 0.0 0 0 ? S 13:45 0:00 [cpuhp/3] root 28 0.0 0.0 0 0 ? S 13:45 0:00 [idle_inject/3] root 29 0.0 0.0 0 0 ? S 13:45 0:00 [migration/3] root 30 0.0 0.0 0 0 ? S 13:45 0:00 [ksoftirqd/3] root 32 0.0 0.0 0 0 ? I< 13:45 0:00 [kworker/3:0H-events_highpri] root 33 0.0 0.0 0 0 ? S 13:45 0:00 [kdevtmpfs] root 34 0.0 0.0 0 0 ? I< 13:45 0:00 [netns] root 35 0.0 0.0 0 0 ? S 13:45 0:00 [rcu_tasks_kthre] root 36 0.0 0.0 0 0 ? S 13:45 0:00 [kauditd] root 37 0.0 0.0 0 0 ? S 13:45 0:00 [khungtaskd] root 38 0.0 0.0 0 0 ? S 13:45 0:00 [oom_reaper] root 39 0.0 0.0 0 0 ? I< 13:45 0:00 [writeback] root 40 0.0 0.0 0 0 ? S 13:45 0:00 [kcompactd0] root 41 0.0 0.0 0 0 ? SN 13:45 0:00 [ksmd] root 134 0.0 0.0 0 0 ? I< 13:45 0:00 [kintegrityd] root 135 0.0 0.0 0 0 ? I< 13:45 0:00 [kblockd] root 136 0.0 0.0 0 0 ? I< 13:45 0:00 [blkcg_punt_bio] root 139 0.0 0.0 0 0 ? I< 13:45 0:00 [tpm_dev_wq] root 140 0.0 0.0 0 0 ? I< 13:45 0:00 [ata_sff] root 141 0.0 0.0 0 0 ? I< 13:45 0:00 [md] root 142 0.0 0.0 0 0 ? I< 13:45 0:00 [edac-poller] root 143 0.0 0.0 0 0 ? I< 13:45 0:00 [devfreq_wq] root 144 0.0 0.0 0 0 ? S 13:45 0:00 [watchdogd] root 147 0.0 0.0 0 0 ? S 13:45 0:00 [kswapd0] root 148 0.0 0.0 0 0 ? S 13:45 0:00 [ecryptfs-kthrea] root 151 0.0 0.0 0 0 ? I< 13:45 0:00 [kthrotld] root 152 0.0 0.0 0 0 ? S 13:45 0:00 [irq/122-aerdrv] root 153 0.0 0.0 0 0 ? S 13:45 0:00 [irq/123-aerdrv] root 154 0.0 0.0 0 0 ? I< 13:45 0:00 [acpi_thermal_pm] root 155 0.0 0.0 0 0 ? I< 13:45 0:00 [vfio-irqfd-clea] root 158 0.0 0.0 0 0 ? I< 13:45 0:00 [ipv6_addrconf] root 169 0.0 0.0 0 0 ? I< 13:45 0:00 [kstrp] root 173 0.0 0.0 0 0 ? I< 13:45 0:00 [kworker/u9:0-hci0] root 193 0.0 0.0 0 0 ? I< 13:45 0:00 [charger_manager] root 241 0.0 0.0 0 0 ? I 13:45 0:00 [kworker/3:2-events] root 254 0.0 0.0 0 0 ? S 13:45 0:00 [scsi_eh_0] root 255 0.0 0.0 0 0 ? I< 13:45 0:00 [scsi_tmf_0] root 256 0.0 0.0 0 0 ? S 13:45 0:00 [scsi_eh_1] root 257 0.0 0.0 0 0 ? I< 13:45 0:00 [scsi_tmf_1] root 259 0.0 0.0 0 0 ? I 13:45 0:00 [kworker/u8:3-i915] root 262 0.0 0.0 0 0 ? I< 13:45 0:00 [kworker/2:1H] root 264 0.0 0.0 0 0 ? I< 13:45 0:00 [kworker/3:1H-kblockd] root 265 0.0 0.0 0 0 ? I< 13:45 0:00 [kworker/0:1H-kblockd] root 267 0.0 0.0 0 0 ? I< 13:45 0:00 [kworker/1:1H-kblockd] root 278 0.0 0.0 0 0 ? S 13:45 0:00 [jbd2/sda3-8] root 279 0.0 0.0 0 0 ? I< 13:45 0:00 [ext4-rsv-conver] root 336 0.0 0.1 54768 9848 ? Ss 13:45 0:00 /lib/systemd/systemd-journald root 360 0.2 0.0 24300 8008 ? Ss 13:46 0:05 /lib/systemd/systemd-udevd root 1496 0.0 0.0 0 0 ? I< 13:46 0:00 [kmemstick] root 1532 0.0 0.1 238704 10284 ? Ssl 13:46 0:00 /usr/sbin/ModemManager --filter-policy=strict root 1533 0.0 0.1 451588 9904 ? Ssl 13:46 0:01 /usr/lib/accountsservice/accounts-daemon avahi 1534 0.0 0.0 6272 3788 ? Ss 13:46 0:00 avahi-daemon: running [endless.local] root 1536 0.0 0.1 238284 8976 ? Ss 13:46 0:00 /usr/sbin/cupsd -l message+ 1538 0.2 0.0 8576 5600 ? Ss 13:46 0:04 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only root 1540 0.0 0.2 951828 19944 ? Ssl 13:46 0:01 /usr/sbin/NetworkManager --no-daemon metrics 1542 0.0 0.2 358956 21028 ? Ssl 13:46 0:00 /usr/lib/eos-event-recorder-daemon/eos-metrics-event-recorder root 1594 0.0 0.0 0 0 ? S 13:46 0:00 [irq/128-mei_me] polkitd 1720 0.0 0.3 1676584 25296 ? Ssl 13:46 0:01 /usr/lib/polkit-1/polkitd --no-debug root 1721 0.0 0.0 2272 736 ? Ss 13:46 0:00 /usr/sbin/psi-monitor root 1727 0.0 0.1 336368 9292 ? Ssl 13:46 0:00 /usr/sbin/thermald --no-daemon --dbus-enable root 1728 0.0 0.1 393232 15072 ? Ssl 13:46 0:00 /usr/lib/udisks2/udisksd root 1729 0.0 0.1 463796 10020 ? Ssl 13:46 0:00 /usr/lib/upower/upowerd avahi 1733 0.0 0.0 6148 328 ? S 13:46 0:00 avahi-daemon: chroot helper root 1739 0.0 0.1 173204 11420 ? Ssl 13:46 0:00 /usr/sbin/cups-browsed root 1763 0.0 0.0 0 0 ? I 13:46 0:00 [kworker/2:3-rcu_gp] root 1824 0.0 0.0 16668 7756 ? Ss 13:46 0:00 /lib/systemd/systemd-logind colord 2288 0.0 0.1 455928 14760 ? Ssl 13:46 0:00 /usr/lib/colord/colord root 2289 0.0 0.1 207012 14140 ? Ssl 13:46 0:00 /usr/lib/x86_64-linux-gnu/eos-metrics-instrumentation root 3372 0.0 0.1 526852 9020 ? Ssl 13:46 0:00 /usr/sbin/gdm daniel 3453 0.0 0.1 19156 10400 ? Ss 13:46 0:00 /lib/systemd/systemd --user daniel 3572 0.0 0.0 569772 5236 ? S 13:46 0:00 (sd-pam) root 3628 0.1 0.0 0 0 ? S 13:46 0:02 [irq/129-SYNA7DB] root 3673 0.0 0.1 14140 9392 ? Ss 13:46 0:00 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant root 3737 0.0 0.0 0 0 ? I< 13:46 0:00 [kworker/u9:1-hci0] root 3770 0.0 0.0 11548 5756 ? Ss 13:46 0:00 /usr/lib/bluetooth/bluetoothd rtkit 3835 0.0 0.0 152672 2860 ? SNsl 13:46 0:00 /usr/lib/rtkit/rtkit-daemon root 3909 0.0 0.0 0 0 ? I< 13:46 0:00 [cfg80211] root 3996 0.0 0.0 0 0 ? I< 13:46 0:00 [ath10k_wq] root 3997 0.0 0.0 0 0 ? I< 13:46 0:00 [ath10k_aux_wq] root 4077 0.0 0.0 0 0 ? I< 13:46 0:00 [cryptd] root 4465 0.0 0.0 9484 6112 ? S 13:46 0:00 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/dhclient-wlp2s0.pid -lf /var/lib/NetworkManager/dhclient-6d8338a5-5a59-4474-94ac-04360e95d6df-wlp2s0.lease -cf /var/lib/NetworkManager/dhclient-wlp2s0.conf wlp2s0 ntp 4611 0.0 0.0 74800 3892 ? Ssl 13:46 0:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 112:119 root 4711 0.0 0.0 9484 6260 ? S 13:46 0:00 /sbin/dhclient -d -q -6 -N -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/dhclient6-wlp2s0.pid -lf /var/lib/NetworkManager/dhclient6-6d8338a5-5a59-4474-94ac-04360e95d6df-wlp2s0.lease -cf /var/lib/NetworkManager/dhclient6-wlp2s0.conf wlp2s0 root 4801 0.0 0.0 0 0 ? S< 13:46 0:00 [krfcommd] root 6657 0.0 0.1 496248 14896 ? Ssl 13:49 0:00 /usr/libexec/eos-updater daniel 7175 0.0 0.0 9072 6524 ? Ss 13:51 0:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only root 7222 1.2 0.5 754492 45216 tty1 Ssl+ 13:51 0:19 /usr/lib/xorg/Xorg :0 -background none -noreset -verbose 3 -logfile /dev/null -auth /var/run/gdm3/auth-for-Debian-gdm-JY87K0/database -seat seat0 vt1 root 7458 0.0 0.0 0 0 ? I 13:51 0:00 [kworker/2:0-events] root 7798 0.0 0.1 926600 13772 ? Sl 13:52 0:00 gdm-session-worker [pam/gdm-password] daniel 7859 0.0 0.1 449724 8312 ? SLl 13:52 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login daniel 7906 0.0 0.1 417336 15484 ? Ssl 13:52 0:00 /usr/libexec/gnome-session-binary --systemd --session=gnome daniel 7916 0.0 0.0 448960 7788 ? Ssl 13:52 0:00 /usr/libexec/gvfsd daniel 7932 0.0 0.0 381060 7980 ? Sl 13:52 0:00 /usr/libexec/gvfsd-fuse /run/user/1001/gvfs -f daniel 8018 0.0 0.0 5848 472 ? Ss 13:52 0:00 /usr/bin/ssh-agent /usr/bin/im-launch env GNOME_SHELL_SESSION_MODE=endless /usr/bin/gnome-session --session=gnome daniel 8035 0.1 0.1 524728 10196 ? Ssl 13:52 0:01 /usr/bin/ibus-daemon --daemonize --xim daniel 8042 0.0 0.1 449652 9152 ? Sl 13:52 0:00 /usr/lib/ibus/ibus-dconf daniel 8048 0.0 0.3 499368 31588 ? Sl 13:52 0:00 /usr/lib/ibus/ibus-ui-gtk3 daniel 8052 0.0 0.2 420264 23752 ? Sl 13:52 0:00 /usr/lib/ibus/ibus-x11 --kill-daemon daniel 8053 0.0 0.1 312864 8892 ? Ssl 13:52 0:00 /usr/libexec/at-spi-bus-launcher daniel 8060 0.0 0.1 449460 9256 ? Sl 13:52 0:00 /usr/lib/ibus/ibus-portal daniel 8061 0.0 0.0 6876 4124 ? S 13:52 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 daniel 8071 0.0 0.0 168208 6764 ? Sl 13:52 0:00 /usr/libexec/at-spi2-registryd --use-gnome-session daniel 8075 0.0 0.0 299132 4256 ? Ssl 13:52 0:00 /usr/libexec/gnome-session-ctl --monitor daniel 8076 0.0 0.1 1510664 14200 ? Spriv->actor || !CLUTTER_ACTOR_IN_PAINT (meta->priv->actor)) mai 23 04:37:43 endless gnome-shell[8439]: (../clutter/clutter/clutter-actor-meta.c:109):clutter_actor_meta_real_set_enabled: runtime check failed: (!meta->priv->actor || !CLUTTER_ACTOR_IN_PAINT (meta->priv->actor)) mai 23 04:37:45 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Activating service name='com.endlessm.Speedwagon' requested by ':1.53' (uid=1001 pid=8439 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 04:37:45 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Successfully activated service 'com.endlessm.Speedwagon' mai 23 04:37:45 endless systemd[3868]: Started Application launched by gnome-shell. mai 23 04:37:46 endless google-chrome.desktop[14261]: INFO:root:Found flatpak launcher for Google Chrome: '/var/lib/flatpak/app/com.google.Chrome/x86_64/eos3/b64e9ec5fb516c5d582cd828b5280e806be0814d89d80db7a2dedbc4a60ff4e5/files/bin/eos-google-chrome-app' mai 23 04:37:46 endless google-chrome.desktop[14261]: INFO:root:Flatpak launcher for Chrome found. Launching... mai 23 04:37:46 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[14261]: Found flatpak launcher for Google Chrome: '/var/lib/flatpak/app/com.google.Chrome/x86_64/eos3/b64e9ec5fb516c5d582cd828b5280e806be0814d89d80db7a2dedbc4a60ff4e5/files/bin/eos-google-chrome-app' mai 23 04:37:46 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[14261]: Flatpak launcher for Chrome found. Launching... mai 23 04:37:46 endless google-chrome.desktop[14261]: INFO:root:Running Google Chrome launcher with PID 14280 mai 23 04:37:46 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[14261]: Running Google Chrome launcher with PID 14280 mai 23 04:37:46 endless google-chrome.desktop[14280]: WARNING:root:Could not find Flatpak ref com.google.Chrome in /sysroot/home/daniel/.local/share/flatpak: GLib.Error('App com.google.Chrome not installed', 'flatpak-error-quark', 1) mai 23 04:37:46 endless systemd[3868]: Started flatpak-com.google.Chrome-14283.scope. mai 23 04:37:46 endless google-chrome.desktop[14290]: [14330:14330:0523/043746.501434:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. mai 23 04:37:46 endless gnome-keyring-daemon[8205]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered mai 23 04:37:46 endless gnome-shell[8439]: Error in map accounting. mai 23 04:37:46 endless google-chrome.desktop[14290]: [14332:14342:0523/043746.923826:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018 mai 23 04:37:47 endless gnome-keyring-daemon[8205]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered mai 23 04:38:20 endless NetworkManager[2802]: [1590219500.1420] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:38:20 endless NetworkManager[2802]: [1590219500.1428] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:38:20 endless NetworkManager[2802]: [1590219500.1430] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 04:38:20 endless NetworkManager[2802]: [1590219500.1441] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 04:38:25 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 04:38:25 endless NetworkManager[2802]: [1590219505.7321] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 04:38:25 endless NetworkManager[2802]: [1590219505.7321] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 04:38:25 endless NetworkManager[2802]: [1590219505.7328] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 04:38:25 endless NetworkManager[2802]: [1590219505.7330] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 04:38:25 endless NetworkManager[2802]: [1590219505.7336] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:38:25 endless NetworkManager[2802]: [1590219505.7343] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:38:25 endless NetworkManager[2802]: [1590219505.7344] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 04:38:25 endless NetworkManager[2802]: [1590219505.7349] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 04:38:27 endless google-chrome.desktop[14290]: [14330:14330:0523/043827.214938:ERROR:shared_image_manager.cc(212)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox. mai 23 04:38:27 endless google-chrome.desktop[14290]: [14330:14330:0523/043827.216390:ERROR:shared_image_manager.cc(212)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox. mai 23 04:38:31 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 04:38:31 endless NetworkManager[2802]: [1590219511.1841] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 04:38:31 endless NetworkManager[2802]: [1590219511.1841] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 04:38:31 endless NetworkManager[2802]: [1590219511.1848] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 04:38:31 endless NetworkManager[2802]: [1590219511.1851] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 04:38:31 endless NetworkManager[2802]: [1590219511.1858] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:38:31 endless NetworkManager[2802]: [1590219511.1867] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:38:31 endless NetworkManager[2802]: [1590219511.1868] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 04:38:31 endless NetworkManager[2802]: [1590219511.1872] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 04:38:36 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 04:38:36 endless NetworkManager[2802]: [1590219516.6389] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 04:38:36 endless NetworkManager[2802]: [1590219516.6389] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 04:38:36 endless NetworkManager[2802]: [1590219516.6396] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 04:38:36 endless NetworkManager[2802]: [1590219516.6399] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 04:38:36 endless NetworkManager[2802]: [1590219516.6406] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:38:36 endless NetworkManager[2802]: [1590219516.6414] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:38:36 endless NetworkManager[2802]: [1590219516.6416] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 04:38:36 endless NetworkManager[2802]: [1590219516.6420] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 04:38:37 endless cupsd[2799]: REQUEST localhost - - "POST / HTTP/1.1" 200 185 Renew-Subscription client-error-not-found mai 23 04:38:42 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 04:38:42 endless NetworkManager[2802]: [1590219522.0959] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 04:38:42 endless NetworkManager[2802]: [1590219522.0959] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 04:38:42 endless NetworkManager[2802]: [1590219522.0967] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 04:38:42 endless NetworkManager[2802]: [1590219522.0970] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 04:40:24 endless google-chrome.desktop[14290]: [14710:1:0523/044024.064717:ERROR:batching_media_log.cc(38)] MediaEvent: {"error":"MediaSource endOfStream before demuxer initialization completes (before HAVE_METADATA) is treated as an error. This may also occur as consequence of other MediaSource errors before HAVE_METADATA."} mai 23 04:42:47 endless ntpd[11742]: 188.165.236.162 local addr 192.168.0.34 -> mai 23 04:42:54 endless ntpd[11742]: 192.99.2.8 local addr 192.168.0.34 -> mai 23 04:43:31 endless ntpd[11742]: 200.192.232.8 local addr 192.168.0.34 -> mai 23 04:43:38 endless ntpd[11742]: 192.36.143.130 local addr 192.168.0.34 -> mai 23 04:43:42 endless NetworkManager[2802]: [1590219822.1422] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:43:42 endless NetworkManager[2802]: [1590219822.1428] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:43:42 endless NetworkManager[2802]: [1590219822.1430] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 04:43:42 endless NetworkManager[2802]: [1590219822.1434] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 04:43:47 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 04:43:47 endless NetworkManager[2802]: [1590219827.6348] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 04:43:47 endless NetworkManager[2802]: [1590219827.6349] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 04:43:47 endless NetworkManager[2802]: [1590219827.6356] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 04:43:47 endless NetworkManager[2802]: [1590219827.6359] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 04:43:47 endless NetworkManager[2802]: [1590219827.6365] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:43:47 endless NetworkManager[2802]: [1590219827.6372] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:43:47 endless NetworkManager[2802]: [1590219827.6373] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 04:43:47 endless NetworkManager[2802]: [1590219827.6378] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 04:43:53 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 04:43:53 endless NetworkManager[2802]: [1590219833.0881] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 04:43:53 endless NetworkManager[2802]: [1590219833.0881] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 04:43:53 endless NetworkManager[2802]: [1590219833.0888] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 04:43:53 endless NetworkManager[2802]: [1590219833.0891] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 04:43:53 endless NetworkManager[2802]: [1590219833.0897] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:43:53 endless NetworkManager[2802]: [1590219833.0903] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:43:53 endless NetworkManager[2802]: [1590219833.0904] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 04:43:53 endless NetworkManager[2802]: [1590219833.0909] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 04:43:58 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 04:43:58 endless NetworkManager[2802]: [1590219838.5430] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 04:43:58 endless NetworkManager[2802]: [1590219838.5430] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 04:43:58 endless NetworkManager[2802]: [1590219838.5439] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 04:43:58 endless NetworkManager[2802]: [1590219838.5442] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 04:43:58 endless NetworkManager[2802]: [1590219838.5450] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:43:58 endless NetworkManager[2802]: [1590219838.5458] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:43:58 endless NetworkManager[2802]: [1590219838.5459] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 04:43:58 endless NetworkManager[2802]: [1590219838.5464] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 04:44:03 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 04:44:04 endless NetworkManager[2802]: [1590219844.0000] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 04:44:04 endless NetworkManager[2802]: [1590219844.0000] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 04:44:04 endless NetworkManager[2802]: [1590219844.0008] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 04:44:04 endless NetworkManager[2802]: [1590219844.0011] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 04:46:38 endless google-chrome.desktop[14290]: [14710:1:0523/044638.029111:ERROR:batching_media_log.cc(38)] MediaEvent: {"error":"MediaSource endOfStream before demuxer initialization completes (before HAVE_METADATA) is treated as an error. This may also occur as consequence of other MediaSource errors before HAVE_METADATA."} mai 23 04:49:04 endless NetworkManager[2802]: [1590220144.1463] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:49:04 endless NetworkManager[2802]: [1590220144.1469] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:49:04 endless NetworkManager[2802]: [1590220144.1471] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 04:49:04 endless NetworkManager[2802]: [1590220144.1480] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 04:49:09 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 04:49:09 endless NetworkManager[2802]: [1590220149.5353] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 04:49:09 endless NetworkManager[2802]: [1590220149.5354] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 04:49:09 endless NetworkManager[2802]: [1590220149.5362] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 04:49:09 endless NetworkManager[2802]: [1590220149.5368] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 04:49:09 endless NetworkManager[2802]: [1590220149.5378] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:49:09 endless NetworkManager[2802]: [1590220149.5388] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:49:09 endless NetworkManager[2802]: [1590220149.5395] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 04:49:09 endless NetworkManager[2802]: [1590220149.5409] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 04:49:14 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 04:49:14 endless NetworkManager[2802]: [1590220154.9909] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 04:49:14 endless NetworkManager[2802]: [1590220154.9910] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 04:49:14 endless systemd[1]: Started Endless OS Automatic Updater. mai 23 04:49:14 endless NetworkManager[2802]: [1590220154.9916] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 04:49:14 endless NetworkManager[2802]: [1590220154.9964] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 04:49:14 endless NetworkManager[2802]: [1590220154.9971] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:49:14 endless NetworkManager[2802]: [1590220154.9979] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:49:14 endless NetworkManager[2802]: [1590220154.9981] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 04:49:14 endless NetworkManager[2802]: [1590220154.9986] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 04:49:15 endless systemd[1]: eos-autoupdater.service: Succeeded. mai 23 04:49:20 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 04:49:20 endless NetworkManager[2802]: [1590220160.4520] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 04:49:20 endless NetworkManager[2802]: [1590220160.4520] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 04:49:20 endless NetworkManager[2802]: [1590220160.4526] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 04:49:20 endless NetworkManager[2802]: [1590220160.4529] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 04:49:20 endless NetworkManager[2802]: [1590220160.4535] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:49:20 endless NetworkManager[2802]: [1590220160.4548] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 04:49:20 endless NetworkManager[2802]: [1590220160.4550] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 04:49:20 endless NetworkManager[2802]: [1590220160.4554] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 04:49:25 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 04:49:25 endless NetworkManager[2802]: [1590220165.9038] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 04:49:25 endless NetworkManager[2802]: [1590220165.9039] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 04:49:25 endless NetworkManager[2802]: [1590220165.9046] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 04:49:25 endless NetworkManager[2802]: [1590220165.9049] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 04:50:29 endless google-chrome.desktop[14290]: [0523/045029.240855:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox! mai 23 04:50:29 endless google-chrome.desktop[14290]: Most likely you need to configure your SUID sandbox correctly mai 23 04:50:29 endless systemd[3868]: gnome-launched-google-chrome.desktop-14261.scope: Succeeded. mai 23 04:50:29 endless systemd[3868]: flatpak-com.google.Chrome-14283.scope: Succeeded. mai 23 04:50:30 endless gnome-shell[8439]: (../clutter/clutter/clutter-actor-meta.c:109):clutter_actor_meta_real_set_enabled: runtime check failed: (!meta->priv->actor || !CLUTTER_ACTOR_IN_PAINT (meta->priv->actor)) mai 23 04:50:30 endless gnome-shell[8439]: (../clutter/clutter/clutter-actor-meta.c:109):clutter_actor_meta_real_set_enabled: runtime check failed: (!meta->priv->actor || !CLUTTER_ACTOR_IN_PAINT (meta->priv->actor)) mai 23 04:50:33 endless systemd-logind[3124]: Lid closed. mai 23 04:50:33 endless systemd-logind[3124]: Suspending... mai 23 04:50:33 endless kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 mai 23 04:50:33 endless NetworkManager[2802]: [1590220233.1997] manager: sleep: sleep requested (sleeping: no enabled: yes) mai 23 04:50:33 endless NetworkManager[2802]: [1590220233.1997] device (enp1s0f1): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') mai 23 04:50:33 endless kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 mai 23 04:50:33 endless kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 mai 23 04:50:33 endless NetworkManager[2802]: [1590220233.2191] device (A8:96:75:AE:ED:00): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') mai 23 04:50:33 endless NetworkManager[2802]: [1590220233.2195] manager: NetworkManager state is now ASLEEP mai 23 04:50:33 endless kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 mai 23 04:50:34 endless kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 mai 23 04:50:34 endless systemd[1]: Reached target Sleep. mai 23 04:50:34 endless systemd[1]: Starting Suspend... mai 23 04:50:34 endless upowerd[2942]: cannot write to kbd_backlight as file not open mai 23 04:50:34 endless gsd-power[8797]: failed to turn the kbd backlight off: GDBus.Error:org.freedesktop.UPower.GeneralError: error writing brightness 0 mai 23 04:50:34 endless systemd-sleep[15393]: Suspending system... mai 23 04:50:34 endless kernel: PM: suspend entry (deep) mai 23 12:26:52 endless kernel: Filesystems sync: 0.544 seconds mai 23 12:26:52 endless kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. mai 23 12:26:52 endless kernel: OOM killer disabled. mai 23 12:26:52 endless kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. mai 23 12:26:52 endless kernel: printk: Suspending console(s) (use no_console_suspend to debug) mai 23 12:26:52 endless kernel: wlp2s0: deauthenticating from 80:d0:4a:90:f1:d9 by local choice (Reason: 3=DEAUTH_LEAVING) mai 23 12:26:52 endless kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache mai 23 12:26:52 endless kernel: sd 0:0:0:0: [sda] Stopping disk mai 23 12:26:52 endless kernel: ACPI: EC: interrupt blocked mai 23 12:26:52 endless kernel: ACPI: Preparing to enter system sleep state S3 mai 23 12:26:52 endless kernel: ACPI: EC: event blocked mai 23 12:26:52 endless kernel: ACPI: EC: EC stopped mai 23 12:26:52 endless kernel: PM: Saving platform NVS memory mai 23 12:26:52 endless kernel: Disabling non-boot CPUs ... mai 23 12:26:52 endless kernel: smpboot: CPU 1 is now offline mai 23 12:26:52 endless kernel: smpboot: CPU 2 is now offline mai 23 12:26:52 endless kernel: smpboot: CPU 3 is now offline mai 23 12:26:52 endless kernel: ACPI: Low-level resume complete mai 23 12:26:52 endless kernel: ACPI: EC: EC started mai 23 12:26:52 endless kernel: PM: Restoring platform NVS memory mai 23 12:26:52 endless kernel: Enabling non-boot CPUs ... mai 23 12:26:52 endless kernel: x86: Booting SMP configuration: mai 23 12:26:52 endless kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2 mai 23 12:26:52 endless kernel: microcode: sig=0x806e9, pf=0x80, revision=0x9a mai 23 12:26:52 endless kernel: CPU1 is up mai 23 12:26:52 endless kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1 mai 23 12:26:52 endless kernel: microcode: sig=0x806e9, pf=0x80, revision=0xca mai 23 12:26:52 endless kernel: CPU2 is up mai 23 12:26:52 endless kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3 mai 23 12:26:52 endless kernel: CPU3 is up mai 23 12:26:52 endless kernel: ACPI: Waking up from system sleep state S3 mai 23 12:26:52 endless kernel: ACPI: EC: interrupt unblocked mai 23 12:26:52 endless kernel: ACPI: EC: event unblocked mai 23 12:26:52 endless kernel: sd 0:0:0:0: [sda] Starting disk mai 23 12:26:52 endless kernel: ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536 mai 23 12:26:52 endless kernel: usb 1-7: reset high-speed USB device number 3 using xhci_hcd mai 23 12:26:52 endless kernel: usb 1-5: reset full-speed USB device number 2 using xhci_hcd mai 23 12:26:52 endless kernel: OOM killer enabled. mai 23 12:26:52 endless kernel: Restarting tasks ... mai 23 12:26:52 endless kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) mai 23 12:26:52 endless kernel: Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00000302.bin mai 23 12:26:52 endless kernel: Bluetooth: hci0: QCA: patch rome 0x302 build 0x3e8, firmware rome 0x302 build 0x111 mai 23 12:26:52 endless kernel: done. mai 23 12:26:52 endless kernel: PM: suspend exit mai 23 12:26:52 endless systemd-logind[3124]: Lid opened. mai 23 12:26:52 endless bluetoothd[2947]: Endpoint unregistered: sender=:1.489 path=/MediaEndpoint/A2DPSource/sbc mai 23 12:26:52 endless systemd-sleep[15393]: System resumed. mai 23 12:26:52 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=80:d0:4a:90:f1:d9 reason=3 locally_generated=1 mai 23 12:26:52 endless wpa_supplicant[3353]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3 mai 23 12:26:52 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD mai 23 12:26:52 endless NetworkManager[2802]: [1590247612.6189] bluez5: NAP: removed interface 5C:C9:D3:DD:A0:CE mai 23 12:26:52 endless systemd[1]: Starting Load/Save RF Kill Switch Status... mai 23 12:26:52 endless NetworkManager[2802]: [1590247612.6614] sup-iface[0x558a7a8ed2e0,wlp2s0]: connection disconnected (reason -3) mai 23 12:26:52 endless NetworkManager[2802]: [1590247612.6614] device (wlp2s0): supplicant interface state: completed -> disconnected mai 23 12:26:52 endless kernel: Bluetooth: hci0: using NVM file: qca/nvm_usb_00000302.bin mai 23 12:26:52 endless NetworkManager[2802]: [1590247612.7185] device (wlp2s0): supplicant interface state: disconnected -> scanning mai 23 12:26:52 endless systemd[3868]: Stopped target Bluetooth. mai 23 12:26:52 endless systemd[1]: Stopped target Bluetooth. mai 23 12:26:52 endless systemd[3868]: Reached target Bluetooth. mai 23 12:26:52 endless systemd[1]: Starting Update Bluetooth adapter address... mai 23 12:26:52 endless systemd[1]: Started Load/Save RF Kill Switch Status. mai 23 12:26:52 endless systemd[1]: bluetooth-address-update.service: Succeeded. mai 23 12:26:52 endless systemd[1]: Started Update Bluetooth adapter address. mai 23 12:26:52 endless systemd[1]: Reached target Bluetooth. mai 23 12:26:52 endless gnome-shell[8439]: An active wireless connection, in infrastructure mode, involves no access point? mai 23 12:26:53 endless bluetoothd[2947]: Sap driver initialization failed. mai 23 12:26:53 endless bluetoothd[2947]: sap-server: Operation not permitted (1) mai 23 12:26:53 endless NetworkManager[2802]: [1590247613.1808] bluez5: NAP: added interface 5C:C9:D3:DD:A0:CE mai 23 12:26:53 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN mai 23 12:26:53 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN mai 23 12:26:53 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN mai 23 12:26:53 endless ntpd[11742]: Deleting interface #3 wlp2s0, 192.168.0.34#123, interface stats: received=615, sent=616, dropped=0, active_time=3303 secs mai 23 12:26:53 endless ntpd[11742]: 18.228.195.237 local addr 192.168.0.34 -> mai 23 12:26:53 endless ntpd[11742]: 200.160.7.186 local addr 192.168.0.34 -> mai 23 12:26:53 endless ntpd[11742]: 200.160.0.8 local addr 192.168.0.34 -> mai 23 12:26:53 endless ntpd[11742]: 45.11.105.123 local addr 192.168.0.34 -> mai 23 12:26:53 endless ntpd[11742]: 45.11.105.243 local addr 192.168.0.34 -> mai 23 12:26:53 endless ntpd[11742]: 201.49.148.135 local addr 192.168.0.34 -> mai 23 12:26:53 endless ntpd[11742]: 91.189.89.199 local addr 192.168.0.34 -> mai 23 12:26:53 endless ntpd[11742]: Deleting interface #5 wlp2s0, fe80::c6c7:3fc7:b338:a37b%3#123, interface stats: received=0, sent=0, dropped=0, active_time=3303 secs mai 23 12:26:53 endless ntpd[11742]: Deleting interface #6 wlp2s0, 2804:14d:5ce6:9e6b::1001#123, interface stats: received=0, sent=0, dropped=0, active_time=3223 secs mai 23 12:26:53 endless ntpd[11742]: Deleting interface #7 wlp2s0, 2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e#123, interface stats: received=0, sent=0, dropped=0, active_time=3223 secs mai 23 12:26:54 endless dbus-daemon[2800]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.490' (uid=1001 pid=8439 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 12:26:54 endless systemd[1]: Starting Fingerprint Authentication Daemon... mai 23 12:26:54 endless dbus-daemon[2800]: [system] Successfully activated service 'net.reactivated.Fprint' mai 23 12:26:54 endless systemd[1]: Started Fingerprint Authentication Daemon. mai 23 12:26:54 endless kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) mai 23 12:26:54 endless kernel: ata1.00: configured for UDMA/133 mai 23 12:26:55 endless systemd-sleep[15546]: /dev/sda: mai 23 12:26:55 endless systemd-sleep[15546]: setting Advanced Power Management level to 0xfe (254) mai 23 12:26:55 endless systemd-sleep[15546]: APM_level = 254 mai 23 12:26:55 endless systemd[1]: systemd-suspend.service: Succeeded. mai 23 12:26:55 endless systemd[1]: Started Suspend. mai 23 12:26:55 endless systemd[1]: Stopped target Sleep. mai 23 12:26:55 endless systemd[1]: Reached target Suspend. mai 23 12:26:55 endless systemd[1]: Stopped target Suspend. mai 23 12:26:55 endless systemd-logind[3124]: Operation 'sleep' finished. mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.0893] manager: sleep: wake requested (sleeping: yes enabled: yes) mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.0894] device (wlp2s0): state change: activated -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.1243] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP client pid 11549 mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.1243] dhcp4 (wlp2s0): state changed bound -> done mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.1253] dhcp6 (wlp2s0): canceled DHCP transaction, DHCP client pid 11960 mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.1253] dhcp6 (wlp2s0): state changed bound -> done mai 23 12:26:55 endless avahi-daemon[2791]: Withdrawing address record for 192.168.0.34 on wlp2s0. mai 23 12:26:55 endless avahi-daemon[2791]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.0.34. mai 23 12:26:55 endless avahi-daemon[2791]: Interface wlp2s0.IPv4 no longer relevant for mDNS. mai 23 12:26:55 endless avahi-daemon[2791]: Withdrawing address record for 2804:14d:5ce6:9e6b::1001 on wlp2s0. mai 23 12:26:55 endless avahi-daemon[2791]: Withdrawing address record for 2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e on wlp2s0. mai 23 12:26:55 endless avahi-daemon[2791]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address 2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e. mai 23 12:26:55 endless avahi-daemon[2791]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::c6c7:3fc7:b338:a37b. mai 23 12:26:55 endless avahi-daemon[2791]: Registering new address record for fe80::c6c7:3fc7:b338:a37b on wlp2s0.*. mai 23 12:26:55 endless avahi-daemon[2791]: Withdrawing address record for fe80::c6c7:3fc7:b338:a37b on wlp2s0. mai 23 12:26:55 endless avahi-daemon[2791]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::c6c7:3fc7:b338:a37b. mai 23 12:26:55 endless avahi-daemon[2791]: Interface wlp2s0.IPv6 no longer relevant for mDNS. mai 23 12:26:55 endless bluetoothd[2947]: Loading LTKs timed out for hci0 mai 23 12:26:55 endless bluetoothd[2947]: Endpoint registered: sender=:1.489 path=/MediaEndpoint/A2DPSource/sbc mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.3311] manager: NetworkManager state is now CONNECTED_GLOBAL mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.3330] manager: NetworkManager state is now DISCONNECTED mai 23 12:26:55 endless eos-metrics-ins[3702]: Not recording network ID as it is not required for this image mai 23 12:26:55 endless gnome-shell[8439]: An active wireless connection, in infrastructure mode, involves no access point? mai 23 12:26:55 endless geoclue[6460]: Failed to query location: Error resolving “location.services.mozilla.com”: Nome ou serviço desconhecido mai 23 12:26:55 endless eos-updater[6984]: Changing to state Polling mai 23 12:26:55 endless gnome-software[8873]: Failed to update external appstream file: Failed to download appstream file https://d3lapyynmdp1i9.cloudfront.net/app-info/eos-extra.xml.gz: Cannot resolve hostname mai 23 12:26:55 endless eos-updater[6984]: Using product branch os/eos/amd64/eos3a mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.4289] device (enp1s0f1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed') mai 23 12:26:55 endless kernel: Generic FE-GE Realtek PHY r8169-101:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-101:00, irq=IGNORE) mai 23 12:26:55 endless wpa_supplicant[3353]: nl80211: Failed to open /proc/sys/net/ipv4/conf/p2p-dev-wlp2s0/drop_unicast_in_l2_multicast: No such file or directory mai 23 12:26:55 endless wpa_supplicant[3353]: nl80211: Failed to set IPv4 unicast in multicast filter mai 23 12:26:55 endless gsd-sharing[8803]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded. mai 23 12:26:55 endless dbus-daemon[2800]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.30' (uid=0 pid=2802 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") mai 23 12:26:55 endless gsd-sharing[8803]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded. mai 23 12:26:55 endless systemd[1]: Starting Network Manager Script Dispatcher Service... mai 23 12:26:55 endless gnome-software[8873]: not handling error download-failed for action unknown: Erro ao resolver “dl.flathub.org”: Nome ou serviço desconhecido mai 23 12:26:55 endless dbus-daemon[2800]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' mai 23 12:26:55 endless systemd[1]: Started Network Manager Script Dispatcher Service. mai 23 12:26:55 endless nm-dispatcher[15770]: req:1 'down' [wlp2s0]: new request (5 scripts) mai 23 12:26:55 endless nm-dispatcher[15770]: req:1 'down' [wlp2s0]: start running ordered scripts... mai 23 12:26:55 endless eos-updater[6984]: Using product branch os/eos/amd64/eos3a mai 23 12:26:55 endless eos-updater[6984]: Using product branch os/eos/amd64/eos3a mai 23 12:26:55 endless eos-updater[6984]: Using product branch os/eos/amd64/eos3a mai 23 12:26:55 endless wpa_supplicant[3353]: nl80211: Failed to open /proc/sys/net/ipv4/conf/p2p-dev-wlp2s0/drop_unicast_in_l2_multicast: No such file or directory mai 23 12:26:55 endless wpa_supplicant[3353]: nl80211: Failed to set IPv4 unicast in multicast filter mai 23 12:26:55 endless wpa_supplicant[3353]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 mai 23 12:26:55 endless kernel: r8169 0000:01:00.1 enp1s0f1: Link is Down mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.5454] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed') mai 23 12:26:55 endless gnome-software[8873]: not handling error download-failed for action download: failed to download https://odrs.gnome.org/1.0/reviews/api/ratings: Cannot resolve hostname mai 23 12:26:55 endless eos-updater[6984]: Using product branch os/eos/amd64/eos3a mai 23 12:26:55 endless eos-updater[6984]: Using product branch os/eos/amd64/eos3a mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.5710] bluez: BT device Moto C Plus (A8:96:75:AE:ED:00) added (NAP) mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.5713] manager: (A8:96:75:AE:ED:00): new Bluetooth device (/org/freedesktop/NetworkManager/Devices/6) mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.5753] device (A8:96:75:AE:ED:00): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.5776] device (A8:96:75:AE:ED:00): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.5783] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.5790] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.5792] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.5812] manager: NetworkManager state is now CONNECTING mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.5823] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:26:55 endless eos-updater[6984]: Poll: Couldn’t find any updates mai 23 12:26:55 endless eos-updater[6984]: Using product branch os/eos/amd64/eos3a mai 23 12:26:55 endless eos-updater[6984]: Failed to poll metadata from source main: Erro ao resolver “ostree.endlessm.com”: Nome ou serviço desconhecido mai 23 12:26:55 endless eos-updater[6984]: Changing to state Ready mai 23 12:26:55 endless wpa_supplicant[3353]: nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0 mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.7379] sup-iface[0x558a7a8ed4f0,wlp2s0]: supports 5 scan SSIDs mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.7386] device (wlp2s0): supplicant interface state: starting -> ready mai 23 12:26:55 endless NetworkManager[2802]: [1590247615.7387] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') mai 23 12:26:56 endless dbus-daemon[2800]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.607' (uid=1001 pid=8873 comm="/usr/bin/gnome-software --gapplication-service " label="unconfined") mai 23 12:26:56 endless systemd[1]: Starting Locale Service... mai 23 12:26:56 endless dbus-daemon[2800]: [system] Successfully activated service 'org.freedesktop.locale1' mai 23 12:26:56 endless systemd[1]: Started Locale Service. mai 23 12:26:57 endless ModemManager[2789]: Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.1': not supported by any plugin mai 23 12:26:57 endless ModemManager[2789]: Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0': not supported by any plugin mai 23 12:26:57 endless systemd[1]: systemd-rfkill.service: Succeeded. mai 23 12:26:58 endless gdm-password][15664]: gkr-pam: unlocked login keyring mai 23 12:26:58 endless NetworkManager[2802]: [1590247618.7438] agent-manager: req[0x558a7a99e050, :1.490/org.gnome.Shell.NetworkAgent/1001]: agent registered mai 23 12:26:59 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.3281] policy: auto-activating connection 'BethDaniel' (6d8338a5-5a59-4474-94ac-04360e95d6df) mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.3295] device (wlp2s0): Activation: starting connection 'BethDaniel' (6d8338a5-5a59-4474-94ac-04360e95d6df) mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.3297] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.3306] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.3311] device (wlp2s0): Activation: (wifi) access point 'BethDaniel' has security, but secrets are required. mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.3312] device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.3316] sup-iface[0x558a7a8ed4f0,wlp2s0]: wps: type pbc start... mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.3353] device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.3361] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.3365] device (wlp2s0): Activation: (wifi) connection 'BethDaniel' has security, and secrets exist. No new secrets needed. mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.3367] Config: added 'ssid' value 'BethDaniel' mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.3368] Config: added 'scan_ssid' value '1' mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.3369] Config: added 'bgscan' value 'simple:30:-80:86400' mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.3370] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256' mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.3371] Config: added 'auth_alg' value 'OPEN' mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.3372] Config: added 'psk' value '' mai 23 12:27:00 endless wpa_supplicant[3353]: wlp2s0: SME: Trying to authenticate with 80:d0:4a:90:f1:d9 (SSID='BethDaniel' freq=2412 MHz) mai 23 12:27:00 endless kernel: wlp2s0: authenticate with 80:d0:4a:90:f1:d9 mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.4028] device (wlp2s0): supplicant interface state: ready -> authenticating mai 23 12:27:00 endless kernel: wlp2s0: send auth to 80:d0:4a:90:f1:d9 (try 1/3) mai 23 12:27:00 endless wpa_supplicant[3353]: wlp2s0: Trying to associate with 80:d0:4a:90:f1:d9 (SSID='BethDaniel' freq=2412 MHz) mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.4336] device (wlp2s0): supplicant interface state: authenticating -> associating mai 23 12:27:00 endless kernel: wlp2s0: authenticated mai 23 12:27:00 endless kernel: wlp2s0: associate with 80:d0:4a:90:f1:d9 (try 1/3) mai 23 12:27:00 endless kernel: wlp2s0: RX AssocResp from 80:d0:4a:90:f1:d9 (capab=0x411 status=0 aid=2) mai 23 12:27:00 endless wpa_supplicant[3353]: wlp2s0: Associated with 80:d0:4a:90:f1:d9 mai 23 12:27:00 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 mai 23 12:27:00 endless kernel: wlp2s0: associated mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.4477] device (wlp2s0): supplicant interface state: associating -> associated mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.4915] device (wlp2s0): supplicant interface state: associated -> 4-way handshake mai 23 12:27:00 endless wpa_supplicant[3353]: wlp2s0: WPA: Key negotiation completed with 80:d0:4a:90:f1:d9 [PTK=CCMP GTK=CCMP] mai 23 12:27:00 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 80:d0:4a:90:f1:d9 completed [id=0 id_str=] mai 23 12:27:00 endless kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.5374] device (wlp2s0): supplicant interface state: 4-way handshake -> completed mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.5374] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "BethDaniel" mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.5376] device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.5380] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.5399] dhcp4 (wlp2s0): dhclient started with pid 15920 mai 23 12:27:00 endless avahi-daemon[2791]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::c6c7:3fc7:b338:a37b. mai 23 12:27:00 endless avahi-daemon[2791]: New relevant interface wlp2s0.IPv6 for mDNS. mai 23 12:27:00 endless avahi-daemon[2791]: Registering new address record for fe80::c6c7:3fc7:b338:a37b on wlp2s0.*. mai 23 12:27:00 endless dhclient[15920]: DHCPREQUEST for 192.168.0.34 on wlp2s0 to 255.255.255.255 port 67 mai 23 12:27:00 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.9335] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.9335] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.9343] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.9346] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.9352] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.9358] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.9359] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:27:00 endless NetworkManager[2802]: [1590247620.9363] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:27:01 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-36 noise=-54 txrate=1000 mai 23 12:27:01 endless ntpd[11742]: bind(19) AF_INET6 fe80::c6c7:3fc7:b338:a37b%3#123 flags 0x11 failed: Cannot assign requested address mai 23 12:27:01 endless ntpd[11742]: unable to create socket on wlp2s0 (8) for fe80::c6c7:3fc7:b338:a37b%3#123 mai 23 12:27:01 endless ntpd[11742]: failed to init interface for address fe80::c6c7:3fc7:b338:a37b%3 mai 23 12:27:03 endless ntpd[11742]: Listen normally on 9 wlp2s0 [fe80::c6c7:3fc7:b338:a37b%3]:123 mai 23 12:27:03 endless ntpd[11742]: new interface(s) found: waking up resolver mai 23 12:27:06 endless systemd[1]: NetworkManager-dispatcher.service: Succeeded. mai 23 12:27:06 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:27:06 endless NetworkManager[2802]: [1590247626.4056] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:27:06 endless NetworkManager[2802]: [1590247626.4056] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:27:06 endless NetworkManager[2802]: [1590247626.4064] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:27:06 endless NetworkManager[2802]: [1590247626.4067] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:27:06 endless NetworkManager[2802]: [1590247626.4073] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:27:06 endless NetworkManager[2802]: [1590247626.4080] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:27:06 endless NetworkManager[2802]: [1590247626.4082] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:27:06 endless NetworkManager[2802]: [1590247626.4087] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:27:07 endless dhclient[15920]: DHCPREQUEST for 192.168.0.34 on wlp2s0 to 255.255.255.255 port 67 mai 23 12:27:07 endless dhclient[15920]: DHCPACK of 192.168.0.34 from 192.168.0.1 mai 23 12:27:07 endless NetworkManager[2802]: [1590247627.4995] dhcp4 (wlp2s0): address 192.168.0.34 mai 23 12:27:07 endless NetworkManager[2802]: [1590247627.4996] dhcp4 (wlp2s0): plen 24 (255.255.255.0) mai 23 12:27:07 endless NetworkManager[2802]: [1590247627.4996] dhcp4 (wlp2s0): gateway 192.168.0.1 mai 23 12:27:07 endless NetworkManager[2802]: [1590247627.4996] dhcp4 (wlp2s0): lease time 86400 mai 23 12:27:07 endless NetworkManager[2802]: [1590247627.4996] dhcp4 (wlp2s0): nameserver '181.213.132.5' mai 23 12:27:07 endless NetworkManager[2802]: [1590247627.4996] dhcp4 (wlp2s0): nameserver '181.213.132.4' mai 23 12:27:07 endless avahi-daemon[2791]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.0.34. mai 23 12:27:07 endless NetworkManager[2802]: [1590247627.4996] dhcp4 (wlp2s0): state changed unknown -> bound mai 23 12:27:07 endless avahi-daemon[2791]: New relevant interface wlp2s0.IPv4 for mDNS. mai 23 12:27:07 endless NetworkManager[2802]: [1590247627.5017] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') mai 23 12:27:07 endless avahi-daemon[2791]: Registering new address record for 192.168.0.34 on wlp2s0.IPv4. mai 23 12:27:07 endless NetworkManager[2802]: [1590247627.5025] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') mai 23 12:27:07 endless NetworkManager[2802]: [1590247627.5029] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') mai 23 12:27:07 endless NetworkManager[2802]: [1590247627.7535] manager: NetworkManager state is now CONNECTED_GLOBAL mai 23 12:27:07 endless NetworkManager[2802]: [1590247627.7537] policy: set 'BethDaniel' (wlp2s0) as default for IPv4 routing and DNS mai 23 12:27:07 endless eos-metrics-ins[3702]: Not recording network ID as it is not required for this image mai 23 12:27:07 endless geoclue[6460]: Failed to query location: Error resolving “location.services.mozilla.com”: Nome ou serviço desconhecido mai 23 12:27:07 endless gsd-sharing[8803]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded. mai 23 12:27:07 endless gsd-sharing[8803]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded. mai 23 12:27:07 endless dhclient[15920]: bound to 192.168.0.34 -- renewal in 35722 seconds. mai 23 12:27:07 endless NetworkManager[2802]: [1590247627.9343] device (wlp2s0): Activation: successful, device activated. mai 23 12:27:07 endless dbus-daemon[2800]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.30' (uid=0 pid=2802 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") mai 23 12:27:07 endless systemd[1]: Starting Network Manager Script Dispatcher Service... mai 23 12:27:07 endless dbus-daemon[2800]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' mai 23 12:27:07 endless systemd[1]: Started Network Manager Script Dispatcher Service. mai 23 12:27:07 endless nm-dispatcher[16013]: req:1 'up' [wlp2s0]: new request (5 scripts) mai 23 12:27:07 endless nm-dispatcher[16013]: req:1 'up' [wlp2s0]: start running ordered scripts... mai 23 12:27:08 endless ntpd[11742]: ntpd exiting on signal 15 (Terminated) mai 23 12:27:08 endless systemd[1]: Stopping Network Time Service... mai 23 12:27:08 endless systemd[1]: ntp.service: Succeeded. mai 23 12:27:08 endless ntpd[16111]: ntpd 4.2.8p12@1.3728-o (1): Starting mai 23 12:27:08 endless systemd[1]: Stopped Network Time Service. mai 23 12:27:08 endless ntpd[16111]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 112:119 mai 23 12:27:08 endless systemd[1]: Starting Network Time Service... mai 23 12:27:08 endless ntpd[16131]: proto: precision = 0.131 usec (-23) mai 23 12:27:08 endless systemd[1]: Started Network Time Service. mai 23 12:27:08 endless ntpd[16131]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature mai 23 12:27:08 endless ntpd[16131]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2020-06-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37 mai 23 12:27:08 endless ntpd[16131]: Listen and drop on 0 v6wildcard [::]:123 mai 23 12:27:08 endless ntpd[16131]: Listen and drop on 1 v4wildcard 0.0.0.0:123 mai 23 12:27:08 endless ntpd[16131]: Listen normally on 2 lo 127.0.0.1:123 mai 23 12:27:08 endless ntpd[16131]: Listen normally on 3 wlp2s0 192.168.0.34:123 mai 23 12:27:08 endless ntpd[16131]: Listen normally on 4 lo [::1]:123 mai 23 12:27:08 endless ntpd[16131]: Listen normally on 5 wlp2s0 [fe80::c6c7:3fc7:b338:a37b%3]:123 mai 23 12:27:08 endless ntpd[16131]: Listening on routing socket on fd #22 for interface updates mai 23 12:27:08 endless ntpd[16131]: kernel reports TIME_ERROR: 0x6041: Clock Unsynchronized mai 23 12:27:08 endless ntpd[16131]: kernel reports TIME_ERROR: 0x6041: Clock Unsynchronized mai 23 12:27:09 endless ntpd[16131]: Soliciting pool server 45.11.105.223 mai 23 12:27:10 endless ntpd[16131]: Soliciting pool server 192.36.143.130 mai 23 12:27:10 endless ntpd[16131]: Soliciting pool server 200.160.0.8 mai 23 12:27:10 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-25 noise=-110 txrate=1000 mai 23 12:27:11 endless ntpd[16131]: Soliciting pool server 91.202.42.84 mai 23 12:27:11 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:27:11 endless NetworkManager[2802]: [1590247631.8464] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:27:11 endless NetworkManager[2802]: [1590247631.8464] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:27:11 endless NetworkManager[2802]: [1590247631.8472] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:27:11 endless NetworkManager[2802]: [1590247631.8475] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:27:11 endless NetworkManager[2802]: [1590247631.8481] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:27:11 endless NetworkManager[2802]: [1590247631.8488] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:27:11 endless NetworkManager[2802]: [1590247631.8490] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:27:11 endless NetworkManager[2802]: [1590247631.8495] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:27:12 endless ntpd[16131]: Soliciting pool server 45.11.105.253 mai 23 12:27:12 endless ntpd[16131]: Soliciting pool server 200.160.7.186 mai 23 12:27:15 endless ntpd[16131]: receive: Unexpected origin timestamp 0xe273bf51.3f232efc does not match aorg 0xe273bf53.3f24f6f2 from server@45.11.105.223 xmt 0xe273bf53.c60600e0 mai 23 12:27:15 endless ntpd[16131]: Soliciting pool server 143.107.229.210 mai 23 12:27:15 endless ntpd[16131]: receive: Unexpected origin timestamp 0xe273bf51.3f24c53e does not match aorg 0xe273bf53.3f269a68 from server@91.189.89.198 xmt 0xe273bf53.dbb50b97 mai 23 12:27:16 endless ntpd[16131]: Soliciting pool server 143.107.229.211 mai 23 12:27:16 endless ntpd[16131]: Soliciting pool server 85.254.217.5 mai 23 12:27:16 endless ntpd[16131]: Soliciting pool server 201.49.148.135 mai 23 12:27:17 endless ntpd[16131]: Soliciting pool server 192.99.2.8 mai 23 12:27:17 endless ntpd[16131]: Soliciting pool server 212.129.10.70 mai 23 12:27:17 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:27:17 endless NetworkManager[2802]: [1590247637.3136] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:27:17 endless NetworkManager[2802]: [1590247637.3136] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:27:17 endless NetworkManager[2802]: [1590247637.3144] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:27:17 endless NetworkManager[2802]: [1590247637.3147] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:27:17 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-22 noise=-110 txrate=1000 mai 23 12:27:18 endless systemd[1]: NetworkManager-dispatcher.service: Succeeded. mai 23 12:27:18 endless ntpd[16131]: Soliciting pool server 18.228.195.237 mai 23 12:27:18 endless ntpd[16131]: Soliciting pool server 85.91.1.164 mai 23 12:27:19 endless ntpd[16131]: Soliciting pool server 2001:440:1880:5555::2 mai 23 12:27:19 endless ntpd[16131]: receive: Unexpected origin timestamp 0xe273bf57.3fbdf55a does not match aorg 0000000000.00000000 from server@91.189.89.198 xmt 0xe273bf57.7bac9084 mai 23 12:27:19 endless ntpd[16131]: receive: Unexpected origin timestamp 0xe273bf57.3fbd0651 does not match aorg 0000000000.00000000 from server@85.254.217.5 xmt 0xe273bf57.856349d0 mai 23 12:27:25 endless systemd[1]: fprintd.service: Succeeded. mai 23 12:27:27 endless systemd[1]: systemd-localed.service: Succeeded. mai 23 12:27:32 endless NetworkManager[2802]: [1590247652.6074] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) mai 23 12:27:32 endless NetworkManager[2802]: [1590247652.6090] dhcp6 (wlp2s0): dhclient started with pid 16341 mai 23 12:27:32 endless avahi-daemon[2791]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::c6c7:3fc7:b338:a37b. mai 23 12:27:32 endless avahi-daemon[2791]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address 2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e. mai 23 12:27:32 endless avahi-daemon[2791]: Registering new address record for 2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e on wlp2s0.*. mai 23 12:27:32 endless avahi-daemon[2791]: Withdrawing address record for fe80::c6c7:3fc7:b338:a37b on wlp2s0. mai 23 12:27:32 endless NetworkManager[2802]: [1590247652.6104] policy: set 'BethDaniel' (wlp2s0) as default for IPv6 routing and DNS mai 23 12:27:32 endless kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 mai 23 12:27:33 endless dhclient[16341]: XMT: Confirm on wlp2s0, interval 1090ms. mai 23 12:27:33 endless dhclient[16341]: RCV: Reply message on wlp2s0 from fe80::82d0:4aff:fe90:f1d6. mai 23 12:27:33 endless dhclient[16341]: message status code Success. mai 23 12:27:33 endless NetworkManager[2802]: [1590247653.3825] dhcp6 (wlp2s0): valid_lft 86400 mai 23 12:27:33 endless NetworkManager[2802]: [1590247653.3825] dhcp6 (wlp2s0): preferred_lft 86400 mai 23 12:27:33 endless NetworkManager[2802]: [1590247653.3825] dhcp6 (wlp2s0): address 2804:14d:5ce6:9e6b::1001 mai 23 12:27:33 endless NetworkManager[2802]: [1590247653.3825] dhcp6 (wlp2s0): nameserver '2804:14d:1:0:181:213:132:5' mai 23 12:27:33 endless NetworkManager[2802]: [1590247653.3825] dhcp6 (wlp2s0): nameserver '2804:14d:1:0:181:213:132:4' mai 23 12:27:33 endless NetworkManager[2802]: [1590247653.3825] dhcp6 (wlp2s0): state changed unknown -> bound, event ID="d3:dd:a0:cd|1590190796" mai 23 12:27:33 endless avahi-daemon[2791]: Registering new address record for 2804:14d:5ce6:9e6b::1001 on wlp2s0.*. mai 23 12:27:33 endless dbus-daemon[2800]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.30' (uid=0 pid=2802 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") mai 23 12:27:33 endless systemd[1]: Starting Network Manager Script Dispatcher Service... mai 23 12:27:33 endless dbus-daemon[2800]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' mai 23 12:27:33 endless systemd[1]: Started Network Manager Script Dispatcher Service. mai 23 12:27:33 endless nm-dispatcher[16360]: req:1 'dhcp6-change' [wlp2s0]: new request (5 scripts) mai 23 12:27:33 endless nm-dispatcher[16360]: req:1 'dhcp6-change' [wlp2s0]: start running ordered scripts... mai 23 12:27:33 endless dhclient[16341]: PRC: Renewing lease on wlp2s0. mai 23 12:27:33 endless dhclient[16341]: XMT: Renew on wlp2s0, interval 10930ms. mai 23 12:27:33 endless dhclient[16341]: RCV: Reply message on wlp2s0 from fe80::82d0:4aff:fe90:f1d6. mai 23 12:27:33 endless NetworkManager[2802]: [1590247653.4591] dhcp6 (wlp2s0): valid_lft 86400 mai 23 12:27:33 endless NetworkManager[2802]: [1590247653.4592] dhcp6 (wlp2s0): preferred_lft 86400 mai 23 12:27:33 endless NetworkManager[2802]: [1590247653.4592] dhcp6 (wlp2s0): address 2804:14d:5ce6:9e6b::1001 mai 23 12:27:33 endless NetworkManager[2802]: [1590247653.4592] dhcp6 (wlp2s0): nameserver '2804:14d:1:0:181:213:132:5' mai 23 12:27:33 endless NetworkManager[2802]: [1590247653.4592] dhcp6 (wlp2s0): nameserver '2804:14d:1:0:181:213:132:4' mai 23 12:27:33 endless NetworkManager[2802]: [1590247653.4592] dhcp6 (wlp2s0): state changed bound -> bound, event ID="d3:dd:a0:cd|1590247653" mai 23 12:27:33 endless nm-dispatcher[16360]: req:2 'dhcp6-change' [wlp2s0]: new request (5 scripts) mai 23 12:27:33 endless nm-dispatcher[16360]: req:2 'dhcp6-change' [wlp2s0]: start running ordered scripts... mai 23 12:27:36 endless ntpd[16131]: Listen normally on 6 wlp2s0 [2804:14d:5ce6:9e6b::1001]:123 mai 23 12:27:36 endless ntpd[16131]: Listen normally on 7 wlp2s0 [2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e]:123 mai 23 12:27:36 endless ntpd[16131]: new interface(s) found: waking up resolver mai 23 12:27:36 endless systemd[3868]: Started Application launched by gnome-shell. mai 23 12:27:38 endless gdm-Xorg-:0[7519]: (II) modeset(0): EDID vendor "CMN", prod id 5596 mai 23 12:27:38 endless gdm-Xorg-:0[7519]: (II) modeset(0): Printing DDC gathered Modelines: mai 23 12:27:38 endless gdm-Xorg-:0[7519]: (II) modeset(0): Modeline "1366x768"x0.0 76.42 1366 1434 1479 1592 768 772 779 800 -hsync -vsync (48.0 kHz eP) mai 23 12:27:44 endless systemd[1]: NetworkManager-dispatcher.service: Succeeded. mai 23 12:27:51 endless gnome-shell[8439]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600007 mai 23 12:27:59 endless systemd[3868]: gnome-launched-gnome-control-center.desktop-16439.scope: Succeeded. mai 23 12:28:03 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Activating service name='com.endlessm.Speedwagon' requested by ':1.53' (uid=1001 pid=8439 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 12:28:03 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Successfully activated service 'com.endlessm.Speedwagon' mai 23 12:28:03 endless gnome-shell[8439]: Could not create transient scope for PID 16542: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 16542 does not exist. mai 23 12:28:03 endless eos-link-youtube.desktop[16553]: Found default browser: Google Chrome mai 23 12:28:03 endless eos-link-youtube.desktop[16553]: Chrome set as the default application and available. Selecting... mai 23 12:28:03 endless eos-link-youtube.desktop[16553]: Using eos-google-chrome to launch web application (config dir: /sysroot/home/daniel/.config/chrome-appmode/www.youtube.com)... mai 23 12:28:03 endless eos-link-youtube.desktop[16557]: INFO:root:Found flatpak launcher for Google Chrome: '/var/lib/flatpak/app/com.google.Chrome/x86_64/eos3/b64e9ec5fb516c5d582cd828b5280e806be0814d89d80db7a2dedbc4a60ff4e5/files/bin/eos-google-chrome-app' mai 23 12:28:03 endless eos-link-youtube.desktop[16557]: INFO:root:Flatpak launcher for Chrome found. Launching... mai 23 12:28:03 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[16557]: Found flatpak launcher for Google Chrome: '/var/lib/flatpak/app/com.google.Chrome/x86_64/eos3/b64e9ec5fb516c5d582cd828b5280e806be0814d89d80db7a2dedbc4a60ff4e5/files/bin/eos-google-chrome-app' mai 23 12:28:03 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[16557]: Flatpak launcher for Chrome found. Launching... mai 23 12:28:03 endless eos-link-youtube.desktop[16557]: INFO:root:Running Google Chrome launcher with PID 16569 mai 23 12:28:03 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[16557]: Running Google Chrome launcher with PID 16569 mai 23 12:28:03 endless eos-link-youtube.desktop[16569]: WARNING:root:Could not find Flatpak ref com.google.Chrome in /sysroot/home/daniel/.local/share/flatpak: GLib.Error('App com.google.Chrome not installed', 'flatpak-error-quark', 1) mai 23 12:28:03 endless systemd[3868]: Started flatpak-com.google.Chrome-16572.scope. mai 23 12:28:04 endless eos-link-youtube.desktop[16579]: [16619:16619:0523/122804.538112:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. mai 23 12:28:04 endless gnome-shell[8439]: Error in map accounting. mai 23 12:28:04 endless eos-link-youtube.desktop[16579]: [16621:16635:0523/122804.866521:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018 mai 23 12:28:07 endless gnome-keyring-daemon[8205]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered mai 23 12:28:08 endless eos-link-youtube.desktop[16579]: Fontconfig error: Cannot load default config file: No such file: (null) mai 23 12:32:05 endless eos-link-youtube.desktop[16579]: [16619:16619:0523/123205.307771:ERROR:shared_image_representation.cc(151)] Attempt to read from an uninitialized SharedImage mai 23 12:32:05 endless eos-link-youtube.desktop[16579]: [16619:16619:0523/123205.307961:ERROR:shared_image_representation.cc(151)] Attempt to read from an uninitialized SharedImage mai 23 12:32:11 endless eos-link-youtube.desktop[16579]: [16619:16619:0523/123211.895675:ERROR:shared_image_representation.cc(151)] Attempt to read from an uninitialized SharedImage mai 23 12:32:18 endless NetworkManager[2802]: [1590247938.2007] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:32:18 endless NetworkManager[2802]: [1590247938.2014] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:32:18 endless NetworkManager[2802]: [1590247938.2015] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:32:18 endless NetworkManager[2802]: [1590247938.2018] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:32:23 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:32:23 endless NetworkManager[2802]: [1590247943.7253] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:32:23 endless NetworkManager[2802]: [1590247943.7254] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:32:23 endless NetworkManager[2802]: [1590247943.7260] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:32:23 endless NetworkManager[2802]: [1590247943.7263] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:32:23 endless NetworkManager[2802]: [1590247943.7268] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:32:23 endless NetworkManager[2802]: [1590247943.7275] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:32:23 endless NetworkManager[2802]: [1590247943.7277] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:32:23 endless NetworkManager[2802]: [1590247943.7281] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:32:29 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:32:29 endless NetworkManager[2802]: [1590247949.1784] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:32:29 endless NetworkManager[2802]: [1590247949.1784] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:32:29 endless NetworkManager[2802]: [1590247949.1790] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:32:29 endless NetworkManager[2802]: [1590247949.1793] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:32:29 endless NetworkManager[2802]: [1590247949.1799] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:32:29 endless NetworkManager[2802]: [1590247949.1806] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:32:29 endless NetworkManager[2802]: [1590247949.1807] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:32:29 endless NetworkManager[2802]: [1590247949.1812] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:32:34 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:32:34 endless NetworkManager[2802]: [1590247954.6373] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:32:34 endless NetworkManager[2802]: [1590247954.6373] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:32:34 endless NetworkManager[2802]: [1590247954.6381] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:32:34 endless NetworkManager[2802]: [1590247954.6384] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:32:34 endless NetworkManager[2802]: [1590247954.6390] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:32:34 endless NetworkManager[2802]: [1590247954.6396] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:32:34 endless NetworkManager[2802]: [1590247954.6397] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:32:34 endless NetworkManager[2802]: [1590247954.6401] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:32:40 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:32:40 endless NetworkManager[2802]: [1590247960.1053] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:32:40 endless NetworkManager[2802]: [1590247960.1053] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:32:40 endless NetworkManager[2802]: [1590247960.1059] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:32:40 endless NetworkManager[2802]: [1590247960.1060] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:36:17 endless ntpd[16131]: 143.107.229.210 local addr 192.168.0.34 -> mai 23 12:37:26 endless ntpd[16131]: 143.107.229.211 local addr 192.168.0.34 -> mai 23 12:37:40 endless NetworkManager[2802]: [1590248260.2006] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:37:40 endless NetworkManager[2802]: [1590248260.2012] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:37:40 endless NetworkManager[2802]: [1590248260.2013] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:37:40 endless NetworkManager[2802]: [1590248260.2020] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:37:45 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:37:45 endless NetworkManager[2802]: [1590248265.6251] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:37:45 endless NetworkManager[2802]: [1590248265.6252] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:37:45 endless NetworkManager[2802]: [1590248265.6259] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:37:45 endless NetworkManager[2802]: [1590248265.6262] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:37:45 endless NetworkManager[2802]: [1590248265.6269] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:37:45 endless NetworkManager[2802]: [1590248265.6275] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:37:45 endless NetworkManager[2802]: [1590248265.6277] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:37:45 endless NetworkManager[2802]: [1590248265.6281] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:37:50 endless eos-metrics-eve[2808]: Uploaded 0 events from persistent cache, 7 events from buffer to https://production.metrics.endlessm.com/2/. mai 23 12:37:51 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:37:51 endless NetworkManager[2802]: [1590248271.1060] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:37:51 endless NetworkManager[2802]: [1590248271.1061] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:37:51 endless NetworkManager[2802]: [1590248271.1067] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:37:51 endless NetworkManager[2802]: [1590248271.1070] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:37:51 endless NetworkManager[2802]: [1590248271.1078] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:37:51 endless NetworkManager[2802]: [1590248271.1085] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:37:51 endless NetworkManager[2802]: [1590248271.1087] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:37:51 endless NetworkManager[2802]: [1590248271.1092] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:37:56 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:37:56 endless NetworkManager[2802]: [1590248276.5379] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:37:56 endless NetworkManager[2802]: [1590248276.5379] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:37:56 endless NetworkManager[2802]: [1590248276.5386] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:37:56 endless NetworkManager[2802]: [1590248276.5389] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:37:56 endless NetworkManager[2802]: [1590248276.5393] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:37:56 endless NetworkManager[2802]: [1590248276.5399] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:37:56 endless NetworkManager[2802]: [1590248276.5400] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:37:56 endless NetworkManager[2802]: [1590248276.5405] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:38:01 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:38:01 endless NetworkManager[2802]: [1590248281.9944] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:38:01 endless NetworkManager[2802]: [1590248281.9945] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:38:01 endless NetworkManager[2802]: [1590248281.9953] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:38:01 endless NetworkManager[2802]: [1590248281.9958] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:39:29 endless eos-link-youtube.desktop[16579]: [0523/123929.952889:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox! mai 23 12:39:29 endless eos-link-youtube.desktop[16579]: Most likely you need to configure your SUID sandbox correctly mai 23 12:39:29 endless systemd[3868]: flatpak-com.google.Chrome-16572.scope: Succeeded. mai 23 12:43:02 endless NetworkManager[2802]: [1590248582.2009] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:43:02 endless NetworkManager[2802]: [1590248582.2017] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:43:02 endless NetworkManager[2802]: [1590248582.2018] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:43:02 endless NetworkManager[2802]: [1590248582.2024] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:43:07 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:43:07 endless NetworkManager[2802]: [1590248587.7823] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:43:07 endless NetworkManager[2802]: [1590248587.7824] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:43:07 endless NetworkManager[2802]: [1590248587.7832] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:43:07 endless NetworkManager[2802]: [1590248587.7835] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:43:07 endless NetworkManager[2802]: [1590248587.7841] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:43:07 endless NetworkManager[2802]: [1590248587.7848] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:43:07 endless NetworkManager[2802]: [1590248587.7850] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:43:07 endless NetworkManager[2802]: [1590248587.7854] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:43:13 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:43:13 endless NetworkManager[2802]: [1590248593.2341] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:43:13 endless NetworkManager[2802]: [1590248593.2341] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:43:13 endless NetworkManager[2802]: [1590248593.2349] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:43:13 endless NetworkManager[2802]: [1590248593.2352] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:43:13 endless NetworkManager[2802]: [1590248593.2357] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:43:13 endless NetworkManager[2802]: [1590248593.2362] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:43:13 endless NetworkManager[2802]: [1590248593.2364] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:43:13 endless NetworkManager[2802]: [1590248593.2367] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:43:18 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:43:18 endless NetworkManager[2802]: [1590248598.7026] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:43:18 endless NetworkManager[2802]: [1590248598.7027] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:43:18 endless NetworkManager[2802]: [1590248598.7035] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:43:18 endless NetworkManager[2802]: [1590248598.7038] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:43:18 endless NetworkManager[2802]: [1590248598.7044] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:43:18 endless NetworkManager[2802]: [1590248598.7051] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:43:18 endless NetworkManager[2802]: [1590248598.7052] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:43:18 endless NetworkManager[2802]: [1590248598.7056] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:43:24 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:43:24 endless NetworkManager[2802]: [1590248604.1465] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:43:24 endless NetworkManager[2802]: [1590248604.1465] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:43:24 endless NetworkManager[2802]: [1590248604.1473] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:43:24 endless NetworkManager[2802]: [1590248604.1476] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:48:24 endless NetworkManager[2802]: [1590248904.2058] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:48:24 endless NetworkManager[2802]: [1590248904.2065] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:48:24 endless NetworkManager[2802]: [1590248904.2067] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:48:24 endless NetworkManager[2802]: [1590248904.2072] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:48:29 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:48:29 endless NetworkManager[2802]: [1590248909.6823] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:48:29 endless NetworkManager[2802]: [1590248909.6823] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:48:29 endless NetworkManager[2802]: [1590248909.6831] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:48:29 endless NetworkManager[2802]: [1590248909.6834] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:48:29 endless NetworkManager[2802]: [1590248909.6840] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:48:29 endless NetworkManager[2802]: [1590248909.6848] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:48:29 endless NetworkManager[2802]: [1590248909.6849] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:48:29 endless NetworkManager[2802]: [1590248909.6854] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:48:35 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:48:35 endless NetworkManager[2802]: [1590248915.1543] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:48:35 endless NetworkManager[2802]: [1590248915.1544] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:48:35 endless NetworkManager[2802]: [1590248915.1551] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:48:35 endless NetworkManager[2802]: [1590248915.1555] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:48:35 endless NetworkManager[2802]: [1590248915.1561] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:48:35 endless NetworkManager[2802]: [1590248915.1568] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:48:35 endless NetworkManager[2802]: [1590248915.1569] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:48:35 endless NetworkManager[2802]: [1590248915.1573] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:48:40 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:48:40 endless NetworkManager[2802]: [1590248920.5944] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:48:40 endless NetworkManager[2802]: [1590248920.5944] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:48:40 endless NetworkManager[2802]: [1590248920.5953] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:48:40 endless NetworkManager[2802]: [1590248920.5956] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:48:40 endless NetworkManager[2802]: [1590248920.5962] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:48:40 endless NetworkManager[2802]: [1590248920.5969] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:48:40 endless NetworkManager[2802]: [1590248920.5970] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:48:40 endless NetworkManager[2802]: [1590248920.5975] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:48:46 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:48:46 endless NetworkManager[2802]: [1590248926.0513] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:48:46 endless NetworkManager[2802]: [1590248926.0513] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:48:46 endless NetworkManager[2802]: [1590248926.0523] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:48:46 endless NetworkManager[2802]: [1590248926.0526] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:50:55 endless ntpd[16131]: 85.91.1.164 local addr 192.168.0.34 -> mai 23 12:51:01 endless ntpd[16131]: 91.202.42.84 local addr 192.168.0.34 -> mai 23 12:52:06 endless ntpd[16131]: 192.99.2.8 local addr 192.168.0.34 -> mai 23 12:53:46 endless NetworkManager[2802]: [1590249226.2040] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:53:46 endless NetworkManager[2802]: [1590249226.2048] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:53:46 endless NetworkManager[2802]: [1590249226.2049] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:53:46 endless NetworkManager[2802]: [1590249226.2054] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:53:51 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:53:51 endless NetworkManager[2802]: [1590249231.5867] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:53:51 endless NetworkManager[2802]: [1590249231.5867] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:53:51 endless NetworkManager[2802]: [1590249231.5875] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:53:51 endless NetworkManager[2802]: [1590249231.5878] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:53:51 endless NetworkManager[2802]: [1590249231.5885] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:53:51 endless NetworkManager[2802]: [1590249231.5891] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:53:51 endless NetworkManager[2802]: [1590249231.5893] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:53:51 endless NetworkManager[2802]: [1590249231.5898] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:53:57 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:53:57 endless NetworkManager[2802]: [1590249237.0586] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:53:57 endless NetworkManager[2802]: [1590249237.0587] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:53:57 endless NetworkManager[2802]: [1590249237.0595] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:53:57 endless NetworkManager[2802]: [1590249237.0598] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:53:57 endless NetworkManager[2802]: [1590249237.0605] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:53:57 endless NetworkManager[2802]: [1590249237.0613] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:53:57 endless NetworkManager[2802]: [1590249237.0614] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:53:57 endless NetworkManager[2802]: [1590249237.0619] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:54:02 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:54:02 endless NetworkManager[2802]: [1590249242.4981] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:54:02 endless NetworkManager[2802]: [1590249242.4982] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:54:02 endless NetworkManager[2802]: [1590249242.4990] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:54:02 endless NetworkManager[2802]: [1590249242.4993] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:54:02 endless NetworkManager[2802]: [1590249242.4999] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:54:02 endless NetworkManager[2802]: [1590249242.5006] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:54:02 endless NetworkManager[2802]: [1590249242.5007] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:54:02 endless NetworkManager[2802]: [1590249242.5012] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:54:07 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:54:07 endless NetworkManager[2802]: [1590249247.9667] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:54:07 endless NetworkManager[2802]: [1590249247.9667] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:54:07 endless NetworkManager[2802]: [1590249247.9675] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:54:07 endless NetworkManager[2802]: [1590249247.9678] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:55:51 endless eos-link-user-endlessos.desktop[17102]: This tool has been deprecated, use 'gio open' instead. mai 23 12:55:51 endless eos-link-user-endlessos.desktop[17102]: See 'gio help open' for more info. mai 23 12:55:51 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Activating service name='com.endlessm.Speedwagon' requested by ':1.53' (uid=1001 pid=8439 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 12:55:51 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Successfully activated service 'com.endlessm.Speedwagon' mai 23 12:55:51 endless gnome-shell[8439]: Could not create transient scope for PID 17102: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 17102 does not exist. mai 23 12:55:52 endless eos-link-user-endlessos.desktop[17117]: INFO:root:Found flatpak launcher for Google Chrome: '/var/lib/flatpak/app/com.google.Chrome/x86_64/eos3/b64e9ec5fb516c5d582cd828b5280e806be0814d89d80db7a2dedbc4a60ff4e5/files/bin/eos-google-chrome-app' mai 23 12:55:52 endless eos-link-user-endlessos.desktop[17117]: INFO:root:Flatpak launcher for Chrome found. Launching... mai 23 12:55:52 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[17117]: Found flatpak launcher for Google Chrome: '/var/lib/flatpak/app/com.google.Chrome/x86_64/eos3/b64e9ec5fb516c5d582cd828b5280e806be0814d89d80db7a2dedbc4a60ff4e5/files/bin/eos-google-chrome-app' mai 23 12:55:52 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[17117]: Flatpak launcher for Chrome found. Launching... mai 23 12:55:52 endless eos-link-user-endlessos.desktop[17117]: INFO:root:Running Google Chrome launcher with PID 17130 mai 23 12:55:52 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[17117]: Running Google Chrome launcher with PID 17130 mai 23 12:55:52 endless eos-link-user-endlessos.desktop[17130]: WARNING:root:Could not find Flatpak ref com.google.Chrome in /sysroot/home/daniel/.local/share/flatpak: GLib.Error('App com.google.Chrome not installed', 'flatpak-error-quark', 1) mai 23 12:55:52 endless systemd[3868]: Started flatpak-com.google.Chrome-17133.scope. mai 23 12:55:52 endless eos-link-user-endlessos.desktop[17140]: [17180:17180:0523/125552.510061:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. mai 23 12:55:52 endless gnome-keyring-daemon[8205]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered mai 23 12:55:53 endless gnome-shell[8439]: Error in map accounting. mai 23 12:55:53 endless gnome-keyring-daemon[8205]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered mai 23 12:55:53 endless eos-link-user-endlessos.desktop[17140]: [17183:17268:0523/125553.344267:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018 mai 23 12:59:08 endless NetworkManager[2802]: [1590249548.2006] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:59:08 endless NetworkManager[2802]: [1590249548.2013] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:59:08 endless NetworkManager[2802]: [1590249548.2015] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:59:08 endless NetworkManager[2802]: [1590249548.2021] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:59:13 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:59:13 endless NetworkManager[2802]: [1590249553.7381] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:59:13 endless NetworkManager[2802]: [1590249553.7382] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:59:13 endless NetworkManager[2802]: [1590249553.7391] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:59:13 endless NetworkManager[2802]: [1590249553.7394] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:59:13 endless NetworkManager[2802]: [1590249553.7400] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:59:13 endless NetworkManager[2802]: [1590249553.7407] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:59:13 endless NetworkManager[2802]: [1590249553.7409] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:59:13 endless NetworkManager[2802]: [1590249553.7413] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:59:19 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:59:19 endless NetworkManager[2802]: [1590249559.1929] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:59:19 endless NetworkManager[2802]: [1590249559.1930] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:59:19 endless NetworkManager[2802]: [1590249559.1936] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:59:19 endless NetworkManager[2802]: [1590249559.1940] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:59:19 endless NetworkManager[2802]: [1590249559.1947] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:59:19 endless NetworkManager[2802]: [1590249559.1953] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:59:19 endless NetworkManager[2802]: [1590249559.1954] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:59:19 endless NetworkManager[2802]: [1590249559.1959] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:59:24 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:59:24 endless NetworkManager[2802]: [1590249564.6505] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:59:24 endless NetworkManager[2802]: [1590249564.6505] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:59:24 endless NetworkManager[2802]: [1590249564.6513] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:59:24 endless NetworkManager[2802]: [1590249564.6516] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 12:59:24 endless NetworkManager[2802]: [1590249564.6522] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:59:24 endless NetworkManager[2802]: [1590249564.6529] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 12:59:24 endless NetworkManager[2802]: [1590249564.6531] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 12:59:24 endless NetworkManager[2802]: [1590249564.6535] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 12:59:30 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 12:59:30 endless NetworkManager[2802]: [1590249570.1223] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 12:59:30 endless NetworkManager[2802]: [1590249570.1224] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 12:59:30 endless NetworkManager[2802]: [1590249570.1231] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 12:59:30 endless NetworkManager[2802]: [1590249570.1234] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:02:06 endless ntpd[16131]: 192.36.143.130 local addr 192.168.0.34 -> mai 23 13:04:30 endless NetworkManager[2802]: [1590249870.2006] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:04:30 endless NetworkManager[2802]: [1590249870.2015] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:04:30 endless NetworkManager[2802]: [1590249870.2016] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:04:30 endless NetworkManager[2802]: [1590249870.2020] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:04:35 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:04:35 endless NetworkManager[2802]: [1590249875.6451] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:04:35 endless NetworkManager[2802]: [1590249875.6452] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:04:35 endless NetworkManager[2802]: [1590249875.6459] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:04:35 endless NetworkManager[2802]: [1590249875.6462] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:04:35 endless NetworkManager[2802]: [1590249875.6469] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:04:35 endless NetworkManager[2802]: [1590249875.6476] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:04:35 endless NetworkManager[2802]: [1590249875.6478] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:04:35 endless NetworkManager[2802]: [1590249875.6482] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:04:37 endless ntpd[16131]: 212.129.10.70 local addr 192.168.0.34 -> mai 23 13:04:41 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:04:41 endless NetworkManager[2802]: [1590249881.0983] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:04:41 endless NetworkManager[2802]: [1590249881.0983] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:04:41 endless NetworkManager[2802]: [1590249881.0991] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:04:41 endless NetworkManager[2802]: [1590249881.0994] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:04:41 endless NetworkManager[2802]: [1590249881.1000] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:04:41 endless NetworkManager[2802]: [1590249881.1007] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:04:41 endless NetworkManager[2802]: [1590249881.1008] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:04:41 endless NetworkManager[2802]: [1590249881.1013] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:04:46 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:04:46 endless NetworkManager[2802]: [1590249886.5544] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:04:46 endless NetworkManager[2802]: [1590249886.5544] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:04:46 endless NetworkManager[2802]: [1590249886.5551] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:04:46 endless NetworkManager[2802]: [1590249886.5554] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:04:46 endless NetworkManager[2802]: [1590249886.5559] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:04:46 endless NetworkManager[2802]: [1590249886.5566] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:04:46 endless NetworkManager[2802]: [1590249886.5568] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:04:46 endless NetworkManager[2802]: [1590249886.5574] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:04:52 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:04:52 endless NetworkManager[2802]: [1590249892.0093] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:04:52 endless NetworkManager[2802]: [1590249892.0093] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:04:52 endless NetworkManager[2802]: [1590249892.0101] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:04:52 endless NetworkManager[2802]: [1590249892.0104] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:06:23 endless systemd[3868]: Started Application launched by gnome-shell. mai 23 13:06:23 endless org.gnome.Terminal.desktop[17815]: # _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ mai 23 13:06:23 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.298' (uid=1001 pid=17815 comm="gnome-terminal " label="unconfined") mai 23 13:06:23 endless systemd[3868]: Created slice apps.slice. mai 23 13:06:23 endless systemd[3868]: Created slice apps-org.gnome.Terminal.slice. mai 23 13:06:23 endless systemd[3868]: Starting GNOME Terminal Server... mai 23 13:06:23 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Successfully activated service 'org.gnome.Terminal' mai 23 13:06:23 endless systemd[3868]: Started GNOME Terminal Server. mai 23 13:06:23 endless org.gnome.Terminal.desktop[17815]: # _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ mai 23 13:06:23 endless org.gnome.Terminal.desktop[17815]: # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) mai 23 13:06:23 endless org.gnome.Terminal.desktop[17815]: # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) mai 23 13:06:23 endless org.gnome.Terminal.desktop[17815]: # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) mai 23 13:06:24 endless systemd[3868]: Started VTE child process 17832 launched by gnome-terminal-server process 17823. mai 23 13:06:24 endless systemd[3868]: gnome-launched-org.gnome.Terminal.desktop-17815.scope: Succeeded. mai 23 13:07:07 endless sudo[17841]: daniel : TTY=pts/0 ; PWD=/sysroot/home/daniel ; USER=root ; COMMAND=/usr/bin/bash mai 23 13:07:07 endless sudo[17841]: pam_unix(sudo:session): session opened for user root by (uid=0) mai 23 13:07:44 endless gdm-Xorg-:0[7519]: (II) modeset(0): EDID vendor "CMN", prod id 5596 mai 23 13:07:44 endless gdm-Xorg-:0[7519]: (II) modeset(0): Printing DDC gathered Modelines: mai 23 13:07:44 endless gdm-Xorg-:0[7519]: (II) modeset(0): Modeline "1366x768"x0.0 76.42 1366 1434 1479 1592 768 772 779 800 -hsync -vsync (48.0 kHz eP) mai 23 13:07:45 endless polkitd[2932]: Registered Authentication Agent for unix-process:17926:3942830 (system bus name :1.831 [flatpak remote-list --show-details], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:07:45 endless polkitd[2932]: Unregistered Authentication Agent for unix-process:17926:3942830 (system bus name :1.831, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:07:45 endless polkitd[2932]: Registered Authentication Agent for unix-process:17930:3942836 (system bus name :1.838 [flatpak list --runtime --show-details], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:07:45 endless polkitd[2932]: Unregistered Authentication Agent for unix-process:17930:3942836 (system bus name :1.838, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:07:45 endless polkitd[2932]: Registered Authentication Agent for unix-process:17934:3942860 (system bus name :1.845 [flatpak list --app --show-details], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:07:46 endless polkitd[2932]: Unregistered Authentication Agent for unix-process:17934:3942860 (system bus name :1.845, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:07:46 endless polkitd[2932]: Registered Authentication Agent for unix-process:17938:3942894 (system bus name :1.852 [flatpak history --columns=all], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:07:46 endless polkitd[2932]: Unregistered Authentication Agent for unix-process:17938:3942894 (system bus name :1.852, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:07:47 endless dbus-daemon[17912]: [session uid=0 pid=17910] Activating service name='org.freedesktop.Tracker1' requested by ':1.1' (uid=0 pid=17947 comm="nautilus --new-window --select /root/eos-diagnosti" label="unconfined") mai 23 13:07:47 endless dbus-daemon[17912]: [session uid=0 pid=17910] Activating service name='org.gtk.vfs.Daemon' requested by ':1.2' (uid=0 pid=17955 comm="/usr/libexec/tracker-store " label="unconfined") mai 23 13:07:47 endless dbus-daemon[17912]: [session uid=0 pid=17910] Successfully activated service 'org.gtk.vfs.Daemon' mai 23 13:07:47 endless dbus-daemon[17912]: [session uid=0 pid=17910] Successfully activated service 'org.freedesktop.Tracker1' mai 23 13:07:48 endless dbus-daemon[17912]: [session uid=0 pid=17910] Activating service name='org.freedesktop.portal.Desktop' requested by ':1.1' (uid=0 pid=17947 comm="nautilus --new-window --select /root/eos-diagnosti" label="unconfined") mai 23 13:07:48 endless dbus-daemon[17912]: [session uid=0 pid=17910] Activating service name='org.freedesktop.portal.Documents' requested by ':1.6' (uid=0 pid=18001 comm="/usr/libexec/xdg-desktop-portal " label="unconfined") mai 23 13:07:48 endless dbus-daemon[17912]: [session uid=0 pid=17910] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.7' (uid=0 pid=18006 comm="/usr/libexec/xdg-document-portal " label="unconfined") mai 23 13:07:48 endless dbus-daemon[17912]: [session uid=0 pid=17910] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' mai 23 13:07:48 endless dbus-daemon[17912]: [session uid=0 pid=17910] Successfully activated service 'org.freedesktop.portal.Documents' mai 23 13:07:48 endless dbus-daemon[17912]: [session uid=0 pid=17910] Activating service name='org.freedesktop.impl.portal.desktop.gtk' requested by ':1.6' (uid=0 pid=18001 comm="/usr/libexec/xdg-desktop-portal " label="unconfined") mai 23 13:07:48 endless dbus-daemon[17912]: [session uid=0 pid=17910] Activating service name='ca.desrt.dconf' requested by ':1.10' (uid=0 pid=18022 comm="/usr/libexec/xdg-desktop-portal-gtk " label="unconfined") mai 23 13:07:48 endless dbus-daemon[17912]: [session uid=0 pid=17910] Successfully activated service 'ca.desrt.dconf' mai 23 13:07:48 endless dbus-daemon[17912]: [session uid=0 pid=17910] Successfully activated service 'org.freedesktop.impl.portal.desktop.gtk' mai 23 13:07:48 endless dbus-daemon[17912]: [session uid=0 pid=17910] Activating service name='org.freedesktop.secrets' requested by ':1.6' (uid=0 pid=18001 comm="/usr/libexec/xdg-desktop-portal " label="unconfined") mai 23 13:07:48 endless org.freedesktop.secrets[18036]: GNOME_KEYRING_CONTROL=/root/.cache/keyring-PSY7K0 mai 23 13:07:48 endless dbus-daemon[17912]: [session uid=0 pid=17910] Successfully activated service 'org.freedesktop.secrets' mai 23 13:07:48 endless dbus-daemon[17912]: [session uid=0 pid=17910] Successfully activated service 'org.freedesktop.portal.Desktop' mai 23 13:07:49 endless eos-metrics-eve[2808]: Uploaded 0 events from persistent cache, 1 events from buffer to https://production.metrics.endlessm.com/2/. mai 23 13:08:11 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN mai 23 13:08:17 endless org.freedesktop.Tracker1[17955]: OK mai 23 13:08:18 endless xdg-desktop-por[18001]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list mai 23 13:08:51 endless systemd[1]: Starting Save the current clock... mai 23 13:08:51 endless systemd[1]: fake-hwclock.service: Succeeded. mai 23 13:08:51 endless systemd[1]: Started Save the current clock. mai 23 13:09:52 endless NetworkManager[2802]: [1590250192.2005] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:09:52 endless NetworkManager[2802]: [1590250192.2011] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:09:52 endless NetworkManager[2802]: [1590250192.2012] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:09:52 endless NetworkManager[2802]: [1590250192.2017] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:09:57 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:09:57 endless NetworkManager[2802]: [1590250197.7943] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:09:57 endless NetworkManager[2802]: [1590250197.7944] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:09:57 endless NetworkManager[2802]: [1590250197.7950] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:09:57 endless NetworkManager[2802]: [1590250197.7953] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:09:57 endless NetworkManager[2802]: [1590250197.7959] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:09:57 endless NetworkManager[2802]: [1590250197.7966] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:09:57 endless NetworkManager[2802]: [1590250197.7967] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:09:57 endless NetworkManager[2802]: [1590250197.7972] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:10:03 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:10:03 endless NetworkManager[2802]: [1590250203.2491] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:10:03 endless NetworkManager[2802]: [1590250203.2492] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:10:03 endless NetworkManager[2802]: [1590250203.2499] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:10:03 endless NetworkManager[2802]: [1590250203.2502] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:10:03 endless NetworkManager[2802]: [1590250203.2509] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:10:03 endless NetworkManager[2802]: [1590250203.2516] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:10:03 endless NetworkManager[2802]: [1590250203.2517] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:10:03 endless NetworkManager[2802]: [1590250203.2522] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:10:08 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:10:08 endless NetworkManager[2802]: [1590250208.7214] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:10:08 endless NetworkManager[2802]: [1590250208.7214] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:10:08 endless NetworkManager[2802]: [1590250208.7220] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:10:08 endless NetworkManager[2802]: [1590250208.7223] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:10:08 endless NetworkManager[2802]: [1590250208.7229] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:10:08 endless NetworkManager[2802]: [1590250208.7236] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:10:08 endless NetworkManager[2802]: [1590250208.7236] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:10:08 endless NetworkManager[2802]: [1590250208.7239] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:10:14 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:10:14 endless NetworkManager[2802]: [1590250214.1622] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:10:14 endless NetworkManager[2802]: [1590250214.1623] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:10:14 endless NetworkManager[2802]: [1590250214.1631] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:10:14 endless NetworkManager[2802]: [1590250214.1635] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:10:14 endless gnome-shell[8439]: Object .Gjs_ui_messageTray_Notification (0x55712af90c00), has been already deallocated — impossible to emit any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. mai 23 13:10:14 endless gnome-shell[8439]: Object .Gjs_ui_messageTray_Notification (0x55712af90c00), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. mai 23 13:10:14 endless gnome-shell[8439]: == Stack trace for context 0x5571297396d0 == mai 23 13:10:14 endless gnome-shell[8439]: #0 557131d57640 i resource:///org/gnome/shell/ui/messageTray.js:518 (2c32abb4b880 @ 127) mai 23 13:10:14 endless gnome-shell[8439]: #1 557131d575a0 i resource:///org/gnome/shell/ui/messageTray.js:1517 (2c32abb50178 @ 103) mai 23 13:10:14 endless gnome-shell[8439]: #2 557131d57518 i resource:///org/gnome/shell/ui/messageTray.js:1501 (2c32abb50100 @ 33) mai 23 13:10:14 endless gnome-shell[8439]: #3 557131d57488 i resource:///org/gnome/shell/ui/environment.js:73 (326ac248d5b0 @ 98) mai 23 13:10:14 endless gnome-shell[8439]: #4 557131d573f8 i resource:///org/gnome/shell/ui/environment.js:147 (326ac248d9e8 @ 14) mai 23 13:10:14 endless gnome-shell[8439]: == Stack trace for context 0x5571297396d0 == mai 23 13:10:14 endless gnome-shell[8439]: #0 557131d57640 i resource:///org/gnome/shell/ui/messageTray.js:519 (2c32abb4b880 @ 142) mai 23 13:10:14 endless gnome-shell[8439]: #1 557131d575a0 i resource:///org/gnome/shell/ui/messageTray.js:1517 (2c32abb50178 @ 103) mai 23 13:10:14 endless gnome-shell[8439]: #2 557131d57518 i resource:///org/gnome/shell/ui/messageTray.js:1501 (2c32abb50100 @ 33) mai 23 13:10:14 endless gnome-shell[8439]: #3 557131d57488 i resource:///org/gnome/shell/ui/environment.js:73 (326ac248d5b0 @ 98) mai 23 13:10:14 endless gnome-shell[8439]: #4 557131d573f8 i resource:///org/gnome/shell/ui/environment.js:147 (326ac248d9e8 @ 14) mai 23 13:10:14 endless gnome-shell[8439]: g_object_run_dispose: assertion 'G_IS_OBJECT (object)' failed mai 23 13:10:36 endless wpa_supplicant[3353]: wlp2s0: WPA: Group rekeying completed with 80:d0:4a:90:f1:d9 [GTK=CCMP] mai 23 13:11:12 endless sudo[17841]: pam_unix(sudo:session): session closed for user root mai 23 13:11:19 endless gdm-Xorg-:0[7519]: (II) modeset(0): EDID vendor "CMN", prod id 5596 mai 23 13:11:19 endless gdm-Xorg-:0[7519]: (II) modeset(0): Printing DDC gathered Modelines: mai 23 13:11:19 endless gdm-Xorg-:0[7519]: (II) modeset(0): Modeline "1366x768"x0.0 76.42 1366 1434 1479 1592 768 772 779 800 -hsync -vsync (48.0 kHz eP) mai 23 13:11:19 endless polkitd[2932]: Registered Authentication Agent for unix-process:18300:3964206 (system bus name :1.865 [flatpak remote-list --show-details], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:11:19 endless systemd[1]: Started Send system activation/daily ping messages to Endless. mai 23 13:11:19 endless polkitd[2932]: Unregistered Authentication Agent for unix-process:18300:3964206 (system bus name :1.865, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:11:19 endless polkitd[2932]: Registered Authentication Agent for unix-process:18332:3964212 (system bus name :1.872 [flatpak list --runtime --show-details], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:11:19 endless polkitd[2932]: Unregistered Authentication Agent for unix-process:18332:3964212 (system bus name :1.872, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:11:19 endless polkitd[2932]: Registered Authentication Agent for unix-process:18341:3964232 (system bus name :1.879 [flatpak list --app --show-details], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:11:20 endless polkitd[2932]: Unregistered Authentication Agent for unix-process:18341:3964232 (system bus name :1.879, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:11:20 endless polkitd[2932]: Registered Authentication Agent for unix-process:18346:3964271 (system bus name :1.886 [flatpak history --columns=all], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:11:20 endless polkitd[2932]: Unregistered Authentication Agent for unix-process:18346:3964271 (system bus name :1.886, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:11:21 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.110' (uid=1001 pid=9193 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 13:11:21 endless systemd[3868]: Starting Tracker metadata database store and lookup manager... mai 23 13:11:21 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Successfully activated service 'org.freedesktop.Tracker1' mai 23 13:11:21 endless systemd[3868]: Started Tracker metadata database store and lookup manager. mai 23 13:11:23 endless eos-phone-home[18304]: INFO:__main__:Already activated! mai 23 13:11:23 endless eos-phone-home[18304]: INFO:__main__:Getting variable: live mai 23 13:11:23 endless eos-phone-home[18304]: INFO:__main__:Getting variable: cmdline mai 23 13:11:23 endless eos-phone-home[18304]: INFO:__main__: - Cmdline: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-94c993d319cdf01ff15a7624dd6855cc9ebe14d7b40f3077a1e965a0de360d8e/vmlinuz-5.4.0-19-generic root=UUID=05c7cd5b-40f9-47d7-a032-e98150535435 rw splash plymouth.ignore-serial-consoles quiet loglevel=2 ostree=/ostree/boot.1/eos/94c993d319cdf01ff15a7624dd6855cc9ebe14d7b40f3077a1e965a0de360d8e/0 mai 23 13:11:23 endless eos-phone-home[18304]: INFO:__main__:Count age: 43575.327479839325 mai 23 13:11:23 endless eos-phone-home[18304]: INFO:__main__:Ping not due yet. mai 23 13:11:23 endless systemd[1]: eos-phone-home.service: Succeeded. mai 23 13:11:26 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.110' (uid=1001 pid=9193 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 13:11:26 endless systemd[3868]: Starting Tracker metadata extractor... mai 23 13:11:26 endless tracker-extract[18420]: Set scheduler policy to SCHED_IDLE mai 23 13:11:26 endless tracker-extract[18420]: Setting priority nice level to 19 mai 23 13:11:27 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract' mai 23 13:11:27 endless systemd[3868]: Started Tracker metadata extractor. mai 23 13:11:27 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Activating service name='com.endlessm.Speedwagon' requested by ':1.53' (uid=1001 pid=8439 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:11:27 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Successfully activated service 'com.endlessm.Speedwagon' mai 23 13:11:28 endless gnome-shell[8439]: Error in map accounting. mai 23 13:11:40 endless systemd[3868]: tracker-extract.service: Succeeded. mai 23 13:12:00 endless tracker-store[18377]: OK mai 23 13:12:00 endless systemd[3868]: tracker-store.service: Succeeded. mai 23 13:13:05 endless mogwai-schedule[8813]: Releasing hold on service for D-Bus peer ‘:1.607’ mai 23 13:13:13 endless cupsd[2799]: REQUEST localhost - - "POST / HTTP/1.1" 200 185 Renew-Subscription client-error-not-found mai 23 13:13:35 endless mogwai-schedule[8813]: Exiting due to reaching inactivity timeout mai 23 13:13:35 endless systemd[1]: mogwai-scheduled.service: Succeeded. mai 23 13:13:57 endless polkitd[2932]: Registered Authentication Agent for unix-process:18574:3979959 (system bus name :1.895 [flatpak update --appstream], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:14:00 endless flatpak[18574]: libostree pull from 'eos-apps' for appstream2/x86_64 complete security: GPG: commit http: TLS non-delta: meta: 1 content: 0 transfer: secs: 2 size: 569 bytes mai 23 13:14:00 endless flatpak[18574]: /var/tmp/flatpak-cache-A5OBL0/repo-1dKxgA: Pulled appstream2/x86_64 from eos-apps mai 23 13:14:00 endless dbus-daemon[2800]: [system] Activating via systemd: service name='org.freedesktop.Flatpak.SystemHelper' unit='flatpak-system-helper.service' requested by ':1.895' (uid=1001 pid=18574 comm="flatpak update --appstream " label="unconfined") mai 23 13:14:00 endless systemd[1]: Starting flatpak system helper... mai 23 13:14:00 endless dbus-daemon[2800]: [system] Successfully activated service 'org.freedesktop.Flatpak.SystemHelper' mai 23 13:14:00 endless systemd[1]: Started flatpak system helper. mai 23 13:14:00 endless flatpak-system-helper[18604]: libostree pull from 'eos-apps' for appstream2/x86_64 complete security: GPG: commit non-delta: meta: 1 content: 0 transfer: secs: 0 size: 569 bytes mai 23 13:14:01 endless flatpak-system-helper[18604]: system: Pulled appstream2/x86_64 from /var/tmp/flatpak-cache-A5OBL0/repo-1dKxgA mai 23 13:14:01 endless flatpak[18574]: libostree pull from 'eos-runtimes' for appstream2/x86_64 complete security: GPG: summary+commit http: TLS non-delta: meta: 1 content: 0 transfer: secs: 0 size: 1,1 kB mai 23 13:14:01 endless flatpak[18574]: /var/tmp/flatpak-cache-A5OBL0/repo-BdPXCu: Pulled appstream2/x86_64 from eos-runtimes mai 23 13:14:01 endless flatpak-system-helper[18604]: libostree pull from 'eos-runtimes' for appstream2/x86_64 complete security: GPG: summary+commit non-delta: meta: 1 content: 0 transfer: secs: 0 size: 1,1 kB mai 23 13:14:02 endless flatpak-system-helper[18604]: system: Pulled appstream2/x86_64 from /var/tmp/flatpak-cache-A5OBL0/repo-BdPXCu mai 23 13:14:04 endless flatpak[18574]: libostree pull from 'eos-sdk' for appstream2/x86_64 complete security: GPG: commit http: TLS non-delta: meta: 1 content: 0 transfer: secs: 0 size: 569 bytes mai 23 13:14:04 endless flatpak[18574]: /var/tmp/flatpak-cache-A5OBL0/repo-5D7FzC: Pulled appstream2/x86_64 from eos-sdk mai 23 13:14:04 endless flatpak-system-helper[18604]: libostree pull from 'eos-sdk' for appstream2/x86_64 complete security: GPG: commit non-delta: meta: 1 content: 0 transfer: secs: 0 size: 569 bytes mai 23 13:14:05 endless flatpak-system-helper[18604]: system: Pulled appstream2/x86_64 from /var/tmp/flatpak-cache-A5OBL0/repo-5D7FzC mai 23 13:14:22 endless flatpak[18574]: libostree pull from 'flathub' for appstream2/x86_64 complete security: GPG: summary+commit http: TLS non-delta: meta: 3 content: 1 transfer: secs: 13 size: 2,7 MB mai 23 13:14:22 endless flatpak[18574]: /var/tmp/flatpak-cache-A5OBL0/repo-p0XQ21: Pulled appstream2/x86_64 from flathub mai 23 13:14:24 endless flatpak-system-helper[18604]: system: Pulled appstream2/x86_64 from /var/tmp/flatpak-cache-A5OBL0/repo-p0XQ21 mai 23 13:14:28 endless polkitd[2932]: Unregistered Authentication Agent for unix-process:18574:3979959 (system bus name :1.895, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:14:28 endless polkitd[2932]: Registered Authentication Agent for unix-process:18774:3983096 (system bus name :1.907 [flatpak update -y], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:14:29 endless dbus-daemon[2800]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.907' (uid=1001 pid=18774 comm="flatpak update -y " label="unconfined") mai 23 13:14:29 endless systemd[1]: Starting Locale Service... mai 23 13:14:30 endless dbus-daemon[2800]: [system] Successfully activated service 'org.freedesktop.locale1' mai 23 13:14:30 endless systemd[1]: Started Locale Service. mai 23 13:14:38 endless flatpak-system-helper[18604]: system: Uninstalled runtime/ind.ie.Gnomit.Locale/x86_64/stable mai 23 13:14:39 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.110' (uid=1001 pid=9193 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 13:14:39 endless systemd[3868]: Starting Tracker metadata database store and lookup manager... mai 23 13:14:39 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Successfully activated service 'org.freedesktop.Tracker1' mai 23 13:14:39 endless systemd[3868]: Started Tracker metadata database store and lookup manager. mai 23 13:14:39 endless flatpak-system-helper[18604]: system: Uninstalled app/io.github.EndlessSky.endless-sky/x86_64/stable mai 23 13:14:47 endless flatpak[18774]: libostree pull from 'flathub' for runtime/io.github.maurycyliebner.enve.Locale/x86_64/stable complete security: GPG: summary+commit http: TLS non-delta: meta: 2 content: 0 transfer: secs: 7 size: 1,5 kB mai 23 13:14:54 endless flatpak[18774]: libostree pull from 'flathub' for runtime/io.github.maurycyliebner.enve.Locale/x86_64/stable complete security: GPG: summary+commit http: TLS non-delta: meta: 1 content: 0 transfer: secs: 7 size: 592 bytes mai 23 13:14:54 endless flatpak[18774]: /var/tmp/flatpak-cache-A5OBL0/io.github.maurycyliebner.enve.Locale-YMKRK0/repo-qmNTW3: Pulled runtime/io.github.maurycyliebner.enve.Locale/x86_64/stable from flathub mai 23 13:14:54 endless systemd[3868]: var-tmp-flatpak\x2dcache\x2dA5OBL0-io.github.maurycyliebner.enve.Locale\x2dYMKRK0.mount: Succeeded. mai 23 13:14:54 endless systemd[1]: var-tmp-flatpak\x2dcache\x2dA5OBL0-io.github.maurycyliebner.enve.Locale\x2dYMKRK0.mount: Succeeded. mai 23 13:14:59 endless flatpak-system-helper[18604]: system: Pulled runtime/io.github.maurycyliebner.enve.Locale/x86_64/stable from /var/lib/flatpak/repo/tmp/flatpak-cache-TGVAL0/repo-qmNTW3 mai 23 13:15:00 endless flatpak-system-helper[18604]: system: Updated runtime/io.github.maurycyliebner.enve.Locale/x86_64/stable from flathub mai 23 13:15:07 endless flatpak[18774]: libostree pull from 'flathub' for app/io.exodus.Exodus/x86_64/stable complete security: GPG: summary+commit http: TLS non-delta: meta: 2 content: 0 transfer: secs: 6 size: 2,1 kB mai 23 13:15:08 endless systemd[1]: systemd-localed.service: Succeeded. mai 23 13:15:12 endless tracker-store[18861]: OK mai 23 13:15:12 endless systemd[3868]: tracker-store.service: Succeeded. mai 23 13:15:13 endless gnome-shell[8439]: (../clutter/clutter/clutter-actor-meta.c:109):clutter_actor_meta_real_set_enabled: runtime check failed: (!meta->priv->actor || !CLUTTER_ACTOR_IN_PAINT (meta->priv->actor)) mai 23 13:15:13 endless gnome-shell[8439]: (../clutter/clutter/clutter-actor-meta.c:109):clutter_actor_meta_real_set_enabled: runtime check failed: (!meta->priv->actor || !CLUTTER_ACTOR_IN_PAINT (meta->priv->actor)) mai 23 13:15:14 endless flatpak[18774]: libostree pull from 'flathub' for app/io.exodus.Exodus/x86_64/stable complete security: GPG: summary+commit http: TLS delta: parts: 1 loose: 1 transfer: secs: 7 size: 1,4 kB mai 23 13:15:14 endless NetworkManager[2802]: [1590250514.2017] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:15:14 endless NetworkManager[2802]: [1590250514.2023] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:15:14 endless NetworkManager[2802]: [1590250514.2024] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:15:14 endless NetworkManager[2802]: [1590250514.2029] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:15:19 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:15:19 endless NetworkManager[2802]: [1590250519.7130] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:15:19 endless NetworkManager[2802]: [1590250519.7130] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:15:19 endless NetworkManager[2802]: [1590250519.7138] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:15:19 endless NetworkManager[2802]: [1590250519.7140] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:15:19 endless NetworkManager[2802]: [1590250519.7146] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:15:19 endless NetworkManager[2802]: [1590250519.7153] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:15:19 endless NetworkManager[2802]: [1590250519.7155] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:15:19 endless NetworkManager[2802]: [1590250519.7159] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:15:25 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:15:25 endless NetworkManager[2802]: [1590250525.1544] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:15:25 endless NetworkManager[2802]: [1590250525.1544] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:15:25 endless NetworkManager[2802]: [1590250525.1550] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:15:25 endless NetworkManager[2802]: [1590250525.1553] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:15:25 endless NetworkManager[2802]: [1590250525.1560] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:15:25 endless NetworkManager[2802]: [1590250525.1567] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:15:25 endless NetworkManager[2802]: [1590250525.1568] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:15:25 endless NetworkManager[2802]: [1590250525.1572] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:15:30 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:15:30 endless NetworkManager[2802]: [1590250530.6211] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:15:30 endless NetworkManager[2802]: [1590250530.6211] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:15:30 endless NetworkManager[2802]: [1590250530.6218] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:15:30 endless NetworkManager[2802]: [1590250530.6221] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:15:30 endless NetworkManager[2802]: [1590250530.6226] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:15:30 endless NetworkManager[2802]: [1590250530.6233] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:15:30 endless NetworkManager[2802]: [1590250530.6235] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:15:30 endless NetworkManager[2802]: [1590250530.6240] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:15:36 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:15:36 endless NetworkManager[2802]: [1590250536.0654] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:15:36 endless NetworkManager[2802]: [1590250536.0655] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:15:36 endless NetworkManager[2802]: [1590250536.0661] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:15:36 endless NetworkManager[2802]: [1590250536.0664] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:17:14 endless flatpak[18774]: /var/tmp/flatpak-cache-A5OBL0/io.exodus.Exodus-W1W4K0/repo-NVfr2z: Pulled app/io.exodus.Exodus/x86_64/stable from flathub mai 23 13:17:14 endless systemd[3868]: var-tmp-flatpak\x2dcache\x2dA5OBL0-io.exodus.Exodus\x2dW1W4K0.mount: Succeeded. mai 23 13:17:14 endless systemd[1]: var-tmp-flatpak\x2dcache\x2dA5OBL0-io.exodus.Exodus\x2dW1W4K0.mount: Succeeded. mai 23 13:17:22 endless flatpak-system-helper[18604]: system: Pulled app/io.exodus.Exodus/x86_64/stable from /var/lib/flatpak/repo/tmp/flatpak-cache-5RZ4K0/repo-NVfr2z mai 23 13:17:32 endless flatpak-system-helper[18604]: system: Updated app/io.exodus.Exodus/x86_64/stable from flathub mai 23 13:17:33 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.110' (uid=1001 pid=9193 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 13:17:33 endless systemd[3868]: Starting Tracker metadata database store and lookup manager... mai 23 13:17:33 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Successfully activated service 'org.freedesktop.Tracker1' mai 23 13:17:33 endless systemd[3868]: Started Tracker metadata database store and lookup manager. mai 23 13:17:38 endless flatpak[18774]: libostree pull from 'flathub' for app/com.github.hopsan.Hopsan/x86_64/stable complete security: GPG: summary+commit http: TLS non-delta: meta: 2 content: 0 transfer: secs: 5 size: 1,8 kB mai 23 13:17:50 endless flatpak[18774]: libostree pull from 'flathub' for app/com.github.hopsan.Hopsan/x86_64/stable complete security: GPG: summary+commit http: TLS delta: parts: 1 loose: 1 transfer: secs: 11 size: 303,2 kB mai 23 13:17:50 endless flatpak[18774]: /var/tmp/flatpak-cache-A5OBL0/com.github.hopsan.Hopsan-GBYXK0/repo-5IGNFq: Pulled app/com.github.hopsan.Hopsan/x86_64/stable from flathub mai 23 13:17:50 endless systemd[1]: var-tmp-flatpak\x2dcache\x2dA5OBL0-com.github.hopsan.Hopsan\x2dGBYXK0.mount: Succeeded. mai 23 13:17:50 endless systemd[3868]: var-tmp-flatpak\x2dcache\x2dA5OBL0-com.github.hopsan.Hopsan\x2dGBYXK0.mount: Succeeded. mai 23 13:18:05 endless tracker-store[19138]: OK mai 23 13:18:05 endless systemd[3868]: tracker-store.service: Succeeded. mai 23 13:18:11 endless flatpak-system-helper[18604]: system: Pulled app/com.github.hopsan.Hopsan/x86_64/stable from /var/lib/flatpak/repo/tmp/flatpak-cache-CJ4WK0/repo-5IGNFq mai 23 13:18:14 endless flatpak-system-helper[18604]: system: Updated app/com.github.hopsan.Hopsan/x86_64/stable from flathub mai 23 13:18:15 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.110' (uid=1001 pid=9193 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 13:18:15 endless systemd[3868]: Starting Tracker metadata database store and lookup manager... mai 23 13:18:15 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Successfully activated service 'org.freedesktop.Tracker1' mai 23 13:18:15 endless systemd[3868]: Started Tracker metadata database store and lookup manager. mai 23 13:18:20 endless flatpak[18774]: libostree pull from 'flathub' for app/io.github.maurycyliebner.enve/x86_64/stable complete security: GPG: summary+commit http: TLS non-delta: meta: 2 content: 0 transfer: secs: 5 size: 2,1 kB mai 23 13:18:31 endless flatpak[18774]: libostree pull from 'flathub' for app/io.github.maurycyliebner.enve/x86_64/stable complete security: GPG: summary+commit http: TLS delta: parts: 1 loose: 1 transfer: secs: 10 size: 804,6 kB mai 23 13:18:31 endless flatpak[18774]: /var/tmp/flatpak-cache-A5OBL0/io.github.maurycyliebner.enve-8YMXK0/repo-CSPt5K: Pulled app/io.github.maurycyliebner.enve/x86_64/stable from flathub mai 23 13:18:31 endless systemd[3868]: var-tmp-flatpak\x2dcache\x2dA5OBL0-io.github.maurycyliebner.enve\x2d8YMXK0.mount: Succeeded. mai 23 13:18:31 endless systemd[1]: var-tmp-flatpak\x2dcache\x2dA5OBL0-io.github.maurycyliebner.enve\x2d8YMXK0.mount: Succeeded. mai 23 13:18:40 endless flatpak-system-helper[18604]: system: Pulled app/io.github.maurycyliebner.enve/x86_64/stable from /var/lib/flatpak/repo/tmp/flatpak-cache-K0OXK0/repo-CSPt5K mai 23 13:18:46 endless flatpak-system-helper[18604]: system: Updated app/io.github.maurycyliebner.enve/x86_64/stable from flathub mai 23 13:18:51 endless flatpak[18774]: libostree pull from 'flathub' for runtime/org.kicad_pcb.KiCad.Locale/x86_64/stable complete security: GPG: summary+commit http: TLS non-delta: meta: 2 content: 0 transfer: secs: 5 size: 1,5 kB mai 23 13:18:56 endless flatpak[18774]: libostree pull from 'flathub' for runtime/org.kicad_pcb.KiCad.Locale/x86_64/stable complete security: GPG: summary+commit http: TLS non-delta: meta: 1 content: 0 transfer: secs: 5 size: 592 bytes mai 23 13:18:56 endless flatpak[18774]: /var/tmp/flatpak-cache-A5OBL0/org.kicad_pcb.KiCad.Locale-P0I4K0/repo-9WIVJx: Pulled runtime/org.kicad_pcb.KiCad.Locale/x86_64/stable from flathub mai 23 13:18:56 endless systemd[1]: var-tmp-flatpak\x2dcache\x2dA5OBL0-org.kicad_pcb.KiCad.Locale\x2dP0I4K0.mount: Succeeded. mai 23 13:18:56 endless systemd[3868]: var-tmp-flatpak\x2dcache\x2dA5OBL0-org.kicad_pcb.KiCad.Locale\x2dP0I4K0.mount: Succeeded. mai 23 13:19:00 endless flatpak-system-helper[18604]: system: Pulled runtime/org.kicad_pcb.KiCad.Locale/x86_64/stable from /var/lib/flatpak/repo/tmp/flatpak-cache-QF75K0/repo-9WIVJx mai 23 13:19:00 endless flatpak-system-helper[18604]: system: Updated runtime/org.kicad_pcb.KiCad.Locale/x86_64/stable from flathub mai 23 13:19:06 endless flatpak[18774]: libostree pull from 'flathub' for app/org.kicad_pcb.KiCad/x86_64/stable complete security: GPG: summary+commit http: TLS non-delta: meta: 2 content: 0 transfer: secs: 5 size: 1,9 kB mai 23 13:19:17 endless tracker-store[19220]: OK mai 23 13:19:17 endless systemd[3868]: tracker-store.service: Succeeded. mai 23 13:20:36 endless NetworkManager[2802]: [1590250836.2044] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:20:36 endless NetworkManager[2802]: [1590250836.2052] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:20:36 endless NetworkManager[2802]: [1590250836.2053] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:20:36 endless NetworkManager[2802]: [1590250836.2059] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:20:41 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:20:41 endless NetworkManager[2802]: [1590250841.6021] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:20:41 endless NetworkManager[2802]: [1590250841.6021] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:20:41 endless NetworkManager[2802]: [1590250841.6029] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:20:41 endless NetworkManager[2802]: [1590250841.6032] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:20:41 endless NetworkManager[2802]: [1590250841.6040] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:20:41 endless NetworkManager[2802]: [1590250841.6047] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:20:41 endless NetworkManager[2802]: [1590250841.6049] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:20:41 endless NetworkManager[2802]: [1590250841.6053] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:20:47 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:20:47 endless NetworkManager[2802]: [1590250847.0580] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:20:47 endless NetworkManager[2802]: [1590250847.0580] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:20:47 endless NetworkManager[2802]: [1590250847.0587] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:20:47 endless NetworkManager[2802]: [1590250847.0590] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:20:47 endless NetworkManager[2802]: [1590250847.0596] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:20:47 endless NetworkManager[2802]: [1590250847.0604] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:20:47 endless NetworkManager[2802]: [1590250847.0605] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:20:47 endless NetworkManager[2802]: [1590250847.0609] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:20:52 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:20:52 endless NetworkManager[2802]: [1590250852.5134] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:20:52 endless NetworkManager[2802]: [1590250852.5135] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:20:52 endless NetworkManager[2802]: [1590250852.5147] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:20:52 endless NetworkManager[2802]: [1590250852.5151] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:20:52 endless NetworkManager[2802]: [1590250852.5162] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:20:52 endless NetworkManager[2802]: [1590250852.5183] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:20:52 endless NetworkManager[2802]: [1590250852.5185] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:20:52 endless NetworkManager[2802]: [1590250852.5189] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:20:57 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:20:57 endless NetworkManager[2802]: [1590250857.9701] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:20:57 endless NetworkManager[2802]: [1590250857.9701] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:20:57 endless NetworkManager[2802]: [1590250857.9707] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:20:57 endless NetworkManager[2802]: [1590250857.9710] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:21:16 endless flatpak[18774]: libostree pull from 'flathub' for app/org.kicad_pcb.KiCad/x86_64/stable complete security: GPG: summary+commit http: TLS delta: parts: 7 loose: 52 transfer: secs: 129 size: 278,5 MB mai 23 13:21:16 endless flatpak[18774]: /var/tmp/flatpak-cache-A5OBL0/org.kicad_pcb.KiCad-MLO2K0/repo-lHsVHp: Pulled app/org.kicad_pcb.KiCad/x86_64/stable from flathub mai 23 13:21:16 endless systemd[3868]: var-tmp-flatpak\x2dcache\x2dA5OBL0-org.kicad_pcb.KiCad\x2dMLO2K0.mount: Succeeded. mai 23 13:21:16 endless systemd[1]: var-tmp-flatpak\x2dcache\x2dA5OBL0-org.kicad_pcb.KiCad\x2dMLO2K0.mount: Succeeded. mai 23 13:22:42 endless flatpak-system-helper[18604]: system: Pulled app/org.kicad_pcb.KiCad/x86_64/stable from /var/lib/flatpak/repo/tmp/flatpak-cache-6XL2K0/repo-lHsVHp mai 23 13:22:52 endless flatpak-system-helper[18604]: system: Updated app/org.kicad_pcb.KiCad/x86_64/stable from flathub mai 23 13:22:52 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.110' (uid=1001 pid=9193 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 13:22:52 endless systemd[3868]: Starting Tracker metadata database store and lookup manager... mai 23 13:22:52 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Successfully activated service 'org.freedesktop.Tracker1' mai 23 13:22:52 endless systemd[3868]: Started Tracker metadata database store and lookup manager. mai 23 13:22:57 endless flatpak[18774]: libostree pull from 'flathub' for runtime/org.small_tech.Gnomit.Locale/x86_64/stable complete security: GPG: summary+commit http: TLS non-delta: meta: 2 content: 0 transfer: secs: 5 size: 1,4 kB mai 23 13:23:14 endless flatpak[18774]: libostree pull from 'flathub' for runtime/org.small_tech.Gnomit.Locale/x86_64/stable complete security: GPG: summary+commit http: TLS non-delta: meta: 180 content: 1 transfer: secs: 16 size: 13,1 kB mai 23 13:23:14 endless flatpak[18774]: /var/tmp/flatpak-cache-A5OBL0/org.small_tech.Gnomit.Locale-8591K0/repo-mTimCo: Pulled runtime/org.small_tech.Gnomit.Locale/x86_64/stable from flathub mai 23 13:23:14 endless systemd[3868]: var-tmp-flatpak\x2dcache\x2dA5OBL0-org.small_tech.Gnomit.Locale\x2d8591K0.mount: Succeeded. mai 23 13:23:14 endless systemd[1]: var-tmp-flatpak\x2dcache\x2dA5OBL0-org.small_tech.Gnomit.Locale\x2d8591K0.mount: Succeeded. mai 23 13:23:23 endless flatpak-system-helper[18604]: system: Pulled runtime/org.small_tech.Gnomit.Locale/x86_64/stable from /var/lib/flatpak/repo/tmp/flatpak-cache-JG81K0/repo-mTimCo mai 23 13:23:25 endless tracker-store[19660]: OK mai 23 13:23:25 endless systemd[3868]: tracker-store.service: Succeeded. mai 23 13:23:25 endless flatpak-system-helper[18604]: system: Installed runtime/org.small_tech.Gnomit.Locale/x86_64/stable from flathub mai 23 13:23:33 endless flatpak[18774]: libostree pull from 'flathub' for runtime/org.wesnoth.Wesnoth.Locale/x86_64/stable complete security: GPG: summary+commit http: TLS non-delta: meta: 1 content: 0 transfer: secs: 7 size: 569 bytes mai 23 13:23:44 endless flatpak[18774]: libostree pull from 'flathub' for runtime/org.wesnoth.Wesnoth.Locale/x86_64/stable complete security: GPG: summary+commit http: TLS non-delta: meta: 7 content: 56 transfer: secs: 10 size: 2,4 MB mai 23 13:23:44 endless flatpak[18774]: /var/tmp/flatpak-cache-A5OBL0/org.wesnoth.Wesnoth.Locale-L10UK0/repo-wVnqWc: Pulled runtime/org.wesnoth.Wesnoth.Locale/x86_64/stable from flathub mai 23 13:23:44 endless systemd[1]: var-tmp-flatpak\x2dcache\x2dA5OBL0-org.wesnoth.Wesnoth.Locale\x2dL10UK0.mount: Succeeded. mai 23 13:23:44 endless systemd[3868]: var-tmp-flatpak\x2dcache\x2dA5OBL0-org.wesnoth.Wesnoth.Locale\x2dL10UK0.mount: Succeeded. mai 23 13:23:44 endless flatpak-system-helper[18604]: libostree pull from 'flathub' for runtime/org.wesnoth.Wesnoth.Locale/x86_64/stable complete security: GPG: summary+commit non-delta: meta: 1 content: 0 transfer: secs: 0 size: 569 bytes mai 23 13:23:49 endless flatpak-system-helper[18604]: system: Pulled runtime/org.wesnoth.Wesnoth.Locale/x86_64/stable from /var/lib/flatpak/repo/tmp/flatpak-cache-92XUK0/repo-wVnqWc mai 23 13:23:51 endless flatpak-system-helper[18604]: system: Updated runtime/org.wesnoth.Wesnoth.Locale/x86_64/stable from flathub mai 23 13:23:51 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.110' (uid=1001 pid=9193 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 13:23:51 endless systemd[3868]: Starting Tracker metadata database store and lookup manager... mai 23 13:23:51 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Successfully activated service 'org.freedesktop.Tracker1' mai 23 13:23:51 endless systemd[3868]: Started Tracker metadata database store and lookup manager. mai 23 13:24:24 endless tracker-store[19853]: OK mai 23 13:24:24 endless systemd[3868]: tracker-store.service: Succeeded. mai 23 13:25:58 endless NetworkManager[2802]: [1590251158.2004] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:25:58 endless NetworkManager[2802]: [1590251158.2014] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:25:58 endless NetworkManager[2802]: [1590251158.2016] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:25:58 endless NetworkManager[2802]: [1590251158.2028] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:26:03 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:26:03 endless NetworkManager[2802]: [1590251163.7530] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:26:03 endless NetworkManager[2802]: [1590251163.7530] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:26:03 endless NetworkManager[2802]: [1590251163.7535] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:26:03 endless NetworkManager[2802]: [1590251163.7537] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:26:03 endless NetworkManager[2802]: [1590251163.7541] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:26:03 endless NetworkManager[2802]: [1590251163.7546] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:26:03 endless NetworkManager[2802]: [1590251163.7547] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:26:03 endless NetworkManager[2802]: [1590251163.7549] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:26:09 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:26:09 endless NetworkManager[2802]: [1590251169.2213] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:26:09 endless NetworkManager[2802]: [1590251169.2213] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:26:09 endless NetworkManager[2802]: [1590251169.2221] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:26:09 endless NetworkManager[2802]: [1590251169.2224] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:26:09 endless NetworkManager[2802]: [1590251169.2230] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:26:09 endless NetworkManager[2802]: [1590251169.2237] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:26:09 endless NetworkManager[2802]: [1590251169.2238] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:26:09 endless NetworkManager[2802]: [1590251169.2243] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:26:14 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:26:14 endless NetworkManager[2802]: [1590251174.6651] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:26:14 endless NetworkManager[2802]: [1590251174.6651] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:26:14 endless NetworkManager[2802]: [1590251174.6659] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:26:14 endless NetworkManager[2802]: [1590251174.6662] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:26:14 endless NetworkManager[2802]: [1590251174.6667] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:26:14 endless NetworkManager[2802]: [1590251174.6674] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:26:14 endless NetworkManager[2802]: [1590251174.6675] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:26:14 endless NetworkManager[2802]: [1590251174.6680] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:26:20 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:26:20 endless NetworkManager[2802]: [1590251180.1222] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:26:20 endless NetworkManager[2802]: [1590251180.1222] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:26:20 endless NetworkManager[2802]: [1590251180.1228] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:26:20 endless NetworkManager[2802]: [1590251180.1231] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:30:24 endless polkitd[2932]: Unregistered Authentication Agent for unix-process:18774:3983096 (system bus name :1.907, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:31:20 endless NetworkManager[2802]: [1590251480.2004] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:31:20 endless NetworkManager[2802]: [1590251480.2014] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:31:20 endless NetworkManager[2802]: [1590251480.2016] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:31:20 endless NetworkManager[2802]: [1590251480.2020] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:31:25 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:31:25 endless NetworkManager[2802]: [1590251485.6584] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:31:25 endless NetworkManager[2802]: [1590251485.6584] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:31:25 endless NetworkManager[2802]: [1590251485.6592] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:31:25 endless NetworkManager[2802]: [1590251485.6595] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:31:25 endless NetworkManager[2802]: [1590251485.6600] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:31:25 endless NetworkManager[2802]: [1590251485.6607] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:31:25 endless NetworkManager[2802]: [1590251485.6609] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:31:25 endless NetworkManager[2802]: [1590251485.6614] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:31:31 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:31:31 endless NetworkManager[2802]: [1590251491.1148] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:31:31 endless NetworkManager[2802]: [1590251491.1148] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:31:31 endless NetworkManager[2802]: [1590251491.1156] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:31:31 endless NetworkManager[2802]: [1590251491.1158] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:31:31 endless NetworkManager[2802]: [1590251491.1165] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:31:31 endless NetworkManager[2802]: [1590251491.1172] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:31:31 endless NetworkManager[2802]: [1590251491.1174] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:31:31 endless NetworkManager[2802]: [1590251491.1179] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:31:36 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:31:36 endless NetworkManager[2802]: [1590251496.5822] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:31:36 endless NetworkManager[2802]: [1590251496.5822] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:31:36 endless NetworkManager[2802]: [1590251496.5831] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:31:36 endless NetworkManager[2802]: [1590251496.5835] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:31:36 endless NetworkManager[2802]: [1590251496.5840] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:31:36 endless NetworkManager[2802]: [1590251496.5847] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:31:36 endless NetworkManager[2802]: [1590251496.5848] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:31:36 endless NetworkManager[2802]: [1590251496.5853] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:31:42 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:31:42 endless NetworkManager[2802]: [1590251502.0268] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:31:42 endless NetworkManager[2802]: [1590251502.0269] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:31:42 endless NetworkManager[2802]: [1590251502.0277] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:31:42 endless NetworkManager[2802]: [1590251502.0281] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:33:42 endless eos-updater[6984]: Changing to state Polling mai 23 13:33:42 endless eos-updater[6984]: Using product branch os/eos/amd64/eos3a mai 23 13:33:42 endless eos-updater[6984]: Using product branch os/eos/amd64/eos3a mai 23 13:33:42 endless eos-updater[6984]: Using product branch os/eos/amd64/eos3a mai 23 13:33:42 endless eos-updater[6984]: Using product branch os/eos/amd64/eos3a mai 23 13:33:45 endless eos-updater[6984]: libostree pull from 'eos' for os/eos/amd64/eos3a complete security: GPG: commit http: TLS non-delta: meta: 1 content: 0 transfer: secs: 1 size: 1,1 kB mai 23 13:33:45 endless eos-updater[6984]: Using product branch os/eos/amd64/eos3a mai 23 13:33:45 endless eos-updater[6984]: Using product branch os/eos/amd64/eos3a mai 23 13:33:47 endless eos-updater[6984]: libostree pull from 'eos' for os/eos/amd64/eos3a complete security: GPG: commit http: TLS non-delta: meta: 1 content: 0 transfer: secs: 0 size: 1,1 kB mai 23 13:33:48 endless eos-updater[6984]: Poll: Couldn’t find any updates mai 23 13:33:48 endless eos-updater[6984]: Using product branch os/eos/amd64/eos3a mai 23 13:33:49 endless eos-updater[6984]: libostree pull from 'eos' for os/eos/amd64/eos3a complete security: GPG: commit http: TLS non-delta: meta: 1 content: 0 transfer: secs: 0 size: 1,1 kB mai 23 13:33:49 endless eos-updater[6984]: Using product branch os/eos/amd64/eos3a mai 23 13:33:49 endless eos-updater[6984]: Using product branch os/eos/amd64/eos3a mai 23 13:33:51 endless eos-updater[6984]: libostree pull from 'eos' for os/eos/amd64/eos3a complete security: GPG: commit http: TLS non-delta: meta: 1 content: 0 transfer: secs: 2 size: 1,1 kB mai 23 13:33:51 endless eos-updater[6984]: Changing to state Ready mai 23 13:33:59 endless systemd[1]: flatpak-system-helper.service: Succeeded. mai 23 13:34:34 endless polkitd[2932]: Registered Authentication Agent for unix-process:20322:4103728 (system bus name :1.937 [flatpak uninstall -y --unused], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:34:41 endless dbus-daemon[2800]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.937' (uid=1001 pid=20322 comm="flatpak uninstall -y --unused " label="unconfined") mai 23 13:34:41 endless systemd[1]: Starting Locale Service... mai 23 13:34:41 endless dbus-daemon[2800]: [system] Successfully activated service 'org.freedesktop.locale1' mai 23 13:34:41 endless systemd[1]: Started Locale Service. mai 23 13:34:54 endless dbus-daemon[2800]: [system] Activating via systemd: service name='org.freedesktop.Flatpak.SystemHelper' unit='flatpak-system-helper.service' requested by ':1.937' (uid=1001 pid=20322 comm="flatpak uninstall -y --unused " label="unconfined") mai 23 13:34:54 endless systemd[1]: Starting flatpak system helper... mai 23 13:34:54 endless dbus-daemon[2800]: [system] Successfully activated service 'org.freedesktop.Flatpak.SystemHelper' mai 23 13:34:54 endless systemd[1]: Started flatpak system helper. mai 23 13:34:55 endless flatpak-system-helper[20386]: system: Uninstalled runtime/com.github.babluboy.bookworm.Locale/x86_64/stable mai 23 13:34:55 endless flatpak-system-helper[20386]: system: Uninstalled runtime/com.github.naaando.lyrics.Locale/x86_64/stable mai 23 13:34:56 endless flatpak-system-helper[20386]: system: Uninstalled runtime/com.kristianduske.TrenchBroom.Locale/x86_64/stable mai 23 13:34:56 endless flatpak-system-helper[20386]: system: Uninstalled runtime/org.freedesktop.Platform.openh264/x86_64/19.08 mai 23 13:34:56 endless flatpak-system-helper[20386]: system: Uninstalled runtime/org.gnome.OCRFeeder.Locale/x86_64/stable mai 23 13:34:58 endless flatpak-system-helper[20386]: system: Uninstalled runtime/org.gnome.Platform/x86_64/3.24 mai 23 13:34:59 endless flatpak-system-helper[20386]: system: Uninstalled runtime/org.gnome.Platform.Locale/x86_64/3.24 mai 23 13:35:03 endless flatpak-system-helper[20386]: system: Uninstalled runtime/org.gnome.Platform/x86_64/3.30 mai 23 13:35:10 endless flatpak-system-helper[20386]: system: Uninstalled runtime/org.gnome.Platform.Locale/x86_64/3.30 mai 23 13:35:24 endless systemd[1]: systemd-localed.service: Succeeded. mai 23 13:35:27 endless flatpak-system-helper[20386]: system: Uninstalled runtime/org.gnome.Sdk/x86_64/3.30 mai 23 13:35:32 endless flatpak-system-helper[20386]: system: Uninstalled runtime/org.gnome.Sdk.Locale/x86_64/3.30 mai 23 13:35:32 endless flatpak-system-helper[20386]: system: Uninstalled runtime/org.kde.KStyle.Adwaita/x86_64/5.9 mai 23 13:35:32 endless flatpak-system-helper[20386]: system: Uninstalled runtime/org.kde.KStyle.HighContrast/x86_64/5.9 mai 23 13:35:38 endless flatpak-system-helper[20386]: system: Uninstalled runtime/org.kde.Platform/x86_64/5.9 mai 23 13:35:38 endless flatpak-system-helper[20386]: system: Uninstalled runtime/org.kde.Platform.Locale/x86_64/5.9 mai 23 13:35:38 endless flatpak-system-helper[20386]: system: Uninstalled runtime/org.kde.PlatformTheme.QGnomePlatform.Sources/x86_64/5.9 mai 23 13:35:38 endless flatpak-system-helper[20386]: system: Uninstalled runtime/org.kde.PlatformTheme.QGnomePlatform/x86_64/5.9 mai 23 13:35:38 endless flatpak-system-helper[20386]: system: Uninstalled runtime/org.small_tech.Gnomit.Locale/x86_64/stable mai 23 13:35:38 endless flatpak-system-helper[20386]: system: Uninstalled runtime/org.wesnoth.Wesnoth.Locale/x86_64/stable mai 23 13:36:42 endless NetworkManager[2802]: [1590251802.2045] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:36:42 endless NetworkManager[2802]: [1590251802.2053] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:36:42 endless NetworkManager[2802]: [1590251802.2054] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:36:42 endless NetworkManager[2802]: [1590251802.2059] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:36:47 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:36:47 endless NetworkManager[2802]: [1590251807.5613] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:36:47 endless NetworkManager[2802]: [1590251807.5613] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:36:47 endless NetworkManager[2802]: [1590251807.5623] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:36:47 endless NetworkManager[2802]: [1590251807.5627] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:36:47 endless NetworkManager[2802]: [1590251807.5636] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:36:47 endless NetworkManager[2802]: [1590251807.5643] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:36:47 endless NetworkManager[2802]: [1590251807.5644] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:36:47 endless NetworkManager[2802]: [1590251807.5649] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:36:53 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:36:53 endless NetworkManager[2802]: [1590251813.0172] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:36:53 endless NetworkManager[2802]: [1590251813.0172] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:36:53 endless NetworkManager[2802]: [1590251813.0179] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:36:53 endless NetworkManager[2802]: [1590251813.0181] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:36:53 endless NetworkManager[2802]: [1590251813.0186] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:36:53 endless NetworkManager[2802]: [1590251813.0192] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:36:53 endless NetworkManager[2802]: [1590251813.0194] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:36:53 endless NetworkManager[2802]: [1590251813.0196] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:36:58 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:36:58 endless NetworkManager[2802]: [1590251818.4740] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:36:58 endless NetworkManager[2802]: [1590251818.4740] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:36:58 endless NetworkManager[2802]: [1590251818.4748] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:36:58 endless NetworkManager[2802]: [1590251818.4753] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:36:58 endless NetworkManager[2802]: [1590251818.4760] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:36:58 endless NetworkManager[2802]: [1590251818.4769] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:36:58 endless NetworkManager[2802]: [1590251818.4785] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:36:58 endless NetworkManager[2802]: [1590251818.4798] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:37:03 endless bluetoothd[2947]: connect error: Host is down (112) mai 23 13:37:03 endless NetworkManager[2802]: [1590251823.9292] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:37:03 endless NetworkManager[2802]: [1590251823.9292] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:37:03 endless NetworkManager[2802]: [1590251823.9302] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:37:03 endless NetworkManager[2802]: [1590251823.9305] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:37:08 endless polkitd[2932]: Unregistered Authentication Agent for unix-process:20322:4103728 (system bus name :1.937, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:37:49 endless eos-metrics-eve[2808]: Flushed 1 events to persistent cache. mai 23 13:37:49 endless eos-metrics-eve[2808]: Uploaded 0 events from persistent cache, 2 events from buffer to https://production.metrics.endlessm.com/2/. mai 23 13:37:58 endless polkitd[2932]: Registered Authentication Agent for unix-process:20584:4124148 (system bus name :1.966 [flatpak repair -y], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:37:58 endless polkitd[2932]: Unregistered Authentication Agent for unix-process:20584:4124148 (system bus name :1.966, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:38:29 endless gnome-shell[8439]: (../clutter/clutter/clutter-actor-meta.c:109):clutter_actor_meta_real_set_enabled: runtime check failed: (!meta->priv->actor || !CLUTTER_ACTOR_IN_PAINT (meta->priv->actor)) mai 23 13:38:29 endless gnome-shell[8439]: (../clutter/clutter/clutter-actor-meta.c:109):clutter_actor_meta_real_set_enabled: runtime check failed: (!meta->priv->actor || !CLUTTER_ACTOR_IN_PAINT (meta->priv->actor)) mai 23 13:39:14 endless systemd[3868]: Started Application launched by gnome-shell. mai 23 13:39:17 endless gdm-Xorg-:0[7519]: (II) modeset(0): EDID vendor "CMN", prod id 5596 mai 23 13:39:17 endless gdm-Xorg-:0[7519]: (II) modeset(0): Printing DDC gathered Modelines: mai 23 13:39:17 endless gdm-Xorg-:0[7519]: (II) modeset(0): Modeline "1366x768"x0.0 76.42 1366 1434 1479 1592 768 772 779 800 -hsync -vsync (48.0 kHz eP) mai 23 13:40:20 endless kernel: wlp2s0: deauthenticating from 80:d0:4a:90:f1:d9 by local choice (Reason: 3=DEAUTH_LEAVING) mai 23 13:40:20 endless systemd[1]: Starting Load/Save RF Kill Switch Status... mai 23 13:40:20 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=80:d0:4a:90:f1:d9 reason=3 locally_generated=1 mai 23 13:40:20 endless avahi-daemon[2791]: Interface wlp2s0.IPv6 no longer relevant for mDNS. mai 23 13:40:20 endless avahi-daemon[2791]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address 2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e. mai 23 13:40:20 endless NetworkManager[2802]: [1590252020.2695] manager: rfkill: WiFi hardware radio set disabled mai 23 13:40:20 endless dhclient[15920]: receive_packet failed on wlp2s0: Network is down mai 23 13:40:20 endless NetworkManager[2802]: [1590252020.2696] device (wlp2s0): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed') mai 23 13:40:20 endless avahi-daemon[2791]: Interface wlp2s0.IPv4 no longer relevant for mDNS. mai 23 13:40:20 endless avahi-daemon[2791]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.0.34. mai 23 13:40:20 endless avahi-daemon[2791]: Withdrawing address record for 2804:14d:5ce6:9e6b::1001 on wlp2s0. mai 23 13:40:20 endless avahi-daemon[2791]: Withdrawing address record for 2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e on wlp2s0. mai 23 13:40:20 endless avahi-daemon[2791]: Withdrawing address record for 192.168.0.34 on wlp2s0. mai 23 13:40:20 endless NetworkManager[2802]: [1590252020.3025] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP client pid 15920 mai 23 13:40:20 endless NetworkManager[2802]: [1590252020.3025] dhcp4 (wlp2s0): state changed bound -> done mai 23 13:40:20 endless NetworkManager[2802]: [1590252020.3034] dhcp6 (wlp2s0): canceled DHCP transaction, DHCP client pid 16341 mai 23 13:40:20 endless NetworkManager[2802]: [1590252020.3034] dhcp6 (wlp2s0): state changed bound -> done mai 23 13:40:20 endless gnome-shell[8439]: An active wireless connection, in infrastructure mode, involves no access point? mai 23 13:40:20 endless wpa_supplicant[3353]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/5 mai 23 13:40:20 endless NetworkManager[2802]: [1590252020.5344] manager: NetworkManager state is now DISCONNECTED mai 23 13:40:20 endless wpa_supplicant[3353]: wlp2s0: Reject scan trigger since one is already pending mai 23 13:40:20 endless wpa_supplicant[3353]: wlp2s0: Failed to initiate AP scan mai 23 13:40:20 endless wpa_supplicant[3353]: rfkill: WLAN soft blocked mai 23 13:40:20 endless wpa_supplicant[3353]: rfkill: WLAN soft blocked mai 23 13:40:20 endless wpa_supplicant[3353]: nl80211: Failed to open /proc/sys/net/ipv4/conf/p2p-dev-wlp2s0/drop_unicast_in_l2_multicast: No such file or directory mai 23 13:40:20 endless wpa_supplicant[3353]: nl80211: Failed to set IPv4 unicast in multicast filter mai 23 13:40:20 endless geoclue[6460]: WiFi scan failed mai 23 13:40:20 endless wpa_supplicant[3353]: nl80211: Failed to open /proc/sys/net/ipv4/conf/p2p-dev-wlp2s0/drop_unicast_in_l2_multicast: No such file or directory mai 23 13:40:20 endless NetworkManager[2802]: [1590252020.6756] audit: op="radio-control" arg="wireless-enabled" pid=20628 uid=1001 result="success" mai 23 13:40:23 endless eos-link-user-endlessos.desktop[17140]: [17134:17163:0523/134022.632491:ERROR:connection_factory_impl.cc(420)] Failed to connect to MCS endpoint with error -106 mai 23 13:40:20 endless wpa_supplicant[3353]: nl80211: Failed to set IPv4 unicast in multicast filter mai 23 13:40:20 endless NetworkManager[2802]: [1590252020.6761] manager: rfkill: WiFi now disabled by radio killswitch mai 23 13:40:20 endless wpa_supplicant[3353]: nl80211: Failed to open /proc/sys/net/ipv4/conf/p2p-dev-wlp2s0/drop_unicast_in_l2_multicast: No such file or directory mai 23 13:40:20 endless systemd[1]: Starting Network Manager Script Dispatcher Service... mai 23 13:40:20 endless wpa_supplicant[3353]: nl80211: Failed to set IPv4 unicast in multicast filter mai 23 13:40:21 endless gsd-sharing[8803]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded. mai 23 13:40:20 endless wpa_supplicant[3353]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 mai 23 13:40:21 endless gsd-sharing[8803]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded. mai 23 13:40:20 endless dbus-daemon[2800]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.30' (uid=0 pid=2802 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") mai 23 13:40:21 endless systemd[1]: Started Load/Save RF Kill Switch Status. mai 23 13:40:20 endless wpa_supplicant[3353]: nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0 mai 23 13:40:21 endless systemd[1]: Started Network Manager Script Dispatcher Service. mai 23 13:40:21 endless ntpd[16131]: Deleting interface #3 wlp2s0, 192.168.0.34#123, interface stats: received=692, sent=696, dropped=0, active_time=4393 secs mai 23 13:40:21 endless ntpd[16131]: 18.228.195.237 local addr 192.168.0.34 -> mai 23 13:40:21 endless ntpd[16131]: 85.254.217.5 local addr 192.168.0.34 -> mai 23 13:40:21 endless ntpd[16131]: 201.49.148.135 local addr 192.168.0.34 -> mai 23 13:40:21 endless ntpd[16131]: 45.11.105.253 local addr 192.168.0.34 -> mai 23 13:40:21 endless ntpd[16131]: 200.160.7.186 local addr 192.168.0.34 -> mai 23 13:40:21 endless ntpd[16131]: 200.160.0.8 local addr 192.168.0.34 -> mai 23 13:40:21 endless ntpd[16131]: 45.11.105.223 local addr 192.168.0.34 -> mai 23 13:40:21 endless ntpd[16131]: 91.189.89.198 local addr 192.168.0.34 -> mai 23 13:40:21 endless ntpd[16131]: Deleting interface #5 wlp2s0, fe80::c6c7:3fc7:b338:a37b%3#123, interface stats: received=0, sent=0, dropped=0, active_time=4393 secs mai 23 13:40:21 endless ntpd[16131]: Deleting interface #6 wlp2s0, 2804:14d:5ce6:9e6b::1001#123, interface stats: received=0, sent=0, dropped=0, active_time=4365 secs mai 23 13:40:21 endless ntpd[16131]: Deleting interface #7 wlp2s0, 2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e#123, interface stats: received=0, sent=0, dropped=0, active_time=4365 secs mai 23 13:40:21 endless dbus-daemon[2800]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' mai 23 13:40:21 endless nm-dispatcher[20722]: req:1 'down' [wlp2s0]: new request (5 scripts) mai 23 13:40:21 endless nm-dispatcher[20722]: req:1 'down' [wlp2s0]: start running ordered scripts... mai 23 13:40:27 endless systemd[1]: systemd-rfkill.service: Succeeded. mai 23 13:40:33 endless systemd[1]: NetworkManager-dispatcher.service: Succeeded. mai 23 13:40:38 endless dbus-daemon[2800]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.30' (uid=0 pid=2802 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") mai 23 13:40:38 endless systemd[1]: Starting Network Manager Script Dispatcher Service... mai 23 13:40:38 endless dbus-daemon[2800]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' mai 23 13:40:38 endless systemd[1]: Started Network Manager Script Dispatcher Service. mai 23 13:40:38 endless nm-dispatcher[20895]: req:1 'connectivity-change': new request (5 scripts) mai 23 13:40:38 endless nm-dispatcher[20895]: req:1 'connectivity-change': start running ordered scripts... mai 23 13:40:46 endless eos-link-user-endlessos.desktop[17140]: [17134:17163:0523/134046.251629:ERROR:connection_factory_impl.cc(420)] Failed to connect to MCS endpoint with error -106 mai 23 13:40:46 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Activating via systemd: service name='org.bluez.obex' unit='obex.service' requested by ':1.340' (uid=1001 pid=20628 comm="gnome-control-center wifi " label="unconfined") mai 23 13:40:46 endless systemd[3868]: Starting Bluetooth OBEX service... mai 23 13:40:46 endless obexd[20966]: OBEX daemon 5.50 mai 23 13:40:46 endless dbus-daemon[7460]: [session uid=1001 pid=7460] Successfully activated service 'org.bluez.obex' mai 23 13:40:46 endless systemd[3868]: Started Bluetooth OBEX service. mai 23 13:40:48 endless systemd[1]: NetworkManager-dispatcher.service: Succeeded. mai 23 13:41:03 endless NetworkManager[2802]: [1590252063.6930] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:41:03 endless NetworkManager[2802]: [1590252063.6931] audit: op="connection-activate" uuid="6558e250-5c15-4613-81fc-3c9b743f5a12" name="Moto C Plus" pid=8439 uid=1001 result="success" mai 23 13:41:03 endless NetworkManager[2802]: [1590252063.6933] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:41:03 endless NetworkManager[2802]: [1590252063.6937] manager: NetworkManager state is now CONNECTING mai 23 13:41:03 endless NetworkManager[2802]: [1590252063.6940] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:41:04 endless bluetoothd[2947]: connect error: Invalid exchange (52) mai 23 13:41:04 endless NetworkManager[2802]: [1590252064.2433] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:41:04 endless NetworkManager[2802]: [1590252064.2433] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:41:04 endless NetworkManager[2802]: [1590252064.2437] manager: NetworkManager state is now DISCONNECTED mai 23 13:41:04 endless NetworkManager[2802]: [1590252064.2441] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:41:04 endless NetworkManager[2802]: [1590252064.2445] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:41:44 endless eos-link-user-endlessos.desktop[17140]: [17134:17163:0523/134144.569121:ERROR:connection_factory_impl.cc(420)] Failed to connect to MCS endpoint with error -106 mai 23 13:42:04 endless NetworkManager[2802]: [1590252124.2086] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:42:04 endless NetworkManager[2802]: [1590252124.2091] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:42:04 endless NetworkManager[2802]: [1590252124.2092] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:42:04 endless NetworkManager[2802]: [1590252124.2095] manager: NetworkManager state is now CONNECTING mai 23 13:42:04 endless NetworkManager[2802]: [1590252124.2098] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:42:05 endless bluetoothd[2947]: connect error: Invalid exchange (52) mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8124] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8124] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8129] manager: NetworkManager state is now DISCONNECTED mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8136] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8139] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8145] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8154] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8159] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8167] manager: NetworkManager state is now CONNECTING mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8173] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8473] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8474] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8477] manager: NetworkManager state is now DISCONNECTED mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8481] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8484] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8490] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8497] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8498] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8502] manager: NetworkManager state is now CONNECTING mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8505] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8730] device (A8:96:75:AE:ED:00): Activation: (bluetooth) bluetooth link disconnected. mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8731] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'carrier-changed', sys-iface-state: 'managed') mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8736] manager: NetworkManager state is now DISCONNECTED mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8741] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8744] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8750] policy: auto-activating connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8754] device (A8:96:75:AE:ED:00): Activation: starting connection 'Moto C Plus' (6558e250-5c15-4613-81fc-3c9b743f5a12) mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8755] device (A8:96:75:AE:ED:00): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8759] manager: NetworkManager state is now CONNECTING mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.8762] device (A8:96:75:AE:ED:00): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.9248] device (A8:96:75:AE:ED:00): Error connecting with bluez: GDBus.Error:org.bluez.Error.Failed: Input/output error mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.9249] device (A8:96:75:AE:ED:00): state change: config -> failed (reason 'bluetooth-failed', sys-iface-state: 'managed') mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.9254] manager: NetworkManager state is now DISCONNECTED mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.9258] device (A8:96:75:AE:ED:00): Activation: failed for connection 'Moto C Plus' mai 23 13:42:05 endless NetworkManager[2802]: [1590252125.9261] device (A8:96:75:AE:ED:00): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') mai 23 13:42:15 endless bluetoothd[2947]: a2dp-source profile connect failed for A8:96:75:AE:ED:00: Protocol not available mai 23 13:42:18 endless bluetoothd[2947]: a2dp-source profile connect failed for A8:96:75:AE:ED:00: Protocol not available mai 23 13:42:22 endless NetworkManager[2802]: [1590252142.3019] device (A8:96:75:AE:ED:00): state change: disconnected -> unmanaged (reason 'removed', sys-iface-state: 'removed') mai 23 13:43:07 endless systemd[3868]: gnome-launched-gnome-wifi-panel.desktop-20628.scope: Succeeded. mai 23 13:43:16 endless systemd[3868]: Started Application launched by gnome-shell. mai 23 13:43:16 endless gdm-Xorg-:0[7519]: (II) modeset(0): EDID vendor "CMN", prod id 5596 mai 23 13:43:16 endless gdm-Xorg-:0[7519]: (II) modeset(0): Printing DDC gathered Modelines: mai 23 13:43:16 endless gdm-Xorg-:0[7519]: (II) modeset(0): Modeline "1366x768"x0.0 76.42 1366 1434 1479 1592 768 772 779 800 -hsync -vsync (48.0 kHz eP) mai 23 13:43:19 endless NetworkManager[2802]: [1590252199.7701] manager: rfkill: WiFi hardware radio set enabled mai 23 13:43:19 endless systemd[1]: Starting Load/Save RF Kill Switch Status... mai 23 13:43:19 endless systemd[1]: Started Load/Save RF Kill Switch Status. mai 23 13:43:20 endless kernel: ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536 mai 23 13:43:20 endless NetworkManager[2802]: [1590252200.0507] audit: op="radio-control" arg="wireless-enabled" pid=21083 uid=1001 result="success" mai 23 13:43:20 endless NetworkManager[2802]: [1590252200.0512] manager: rfkill: WiFi now enabled by radio killswitch mai 23 13:43:20 endless NetworkManager[2802]: [1590252200.5990] sup-iface[0x558a7a8ed440,wlp2s0]: supports 5 scan SSIDs mai 23 13:43:20 endless NetworkManager[2802]: [1590252200.5996] device (wlp2s0): supplicant interface state: starting -> ready mai 23 13:43:20 endless NetworkManager[2802]: [1590252200.5996] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') mai 23 13:43:21 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN mai 23 13:43:21 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN mai 23 13:43:21 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN mai 23 13:43:24 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN mai 23 13:43:24 endless systemd[1]: systemd-rfkill.service: Succeeded. mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1860] policy: auto-activating connection 'BethDaniel' (6d8338a5-5a59-4474-94ac-04360e95d6df) mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1875] device (wlp2s0): Activation: starting connection 'BethDaniel' (6d8338a5-5a59-4474-94ac-04360e95d6df) mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1878] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1889] manager: NetworkManager state is now CONNECTING mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1899] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1906] device (wlp2s0): Activation: (wifi) access point 'BethDaniel' has security, but secrets are required. mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1907] device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1913] sup-iface[0x558a7a8ed440,wlp2s0]: wps: type pbc start... mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1949] device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1961] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1969] device (wlp2s0): Activation: (wifi) connection 'BethDaniel' has security, and secrets exist. No new secrets needed. mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1970] Config: added 'ssid' value 'BethDaniel' mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1971] Config: added 'scan_ssid' value '1' mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1972] Config: added 'bgscan' value 'simple:30:-80:86400' mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1973] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256' mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1974] Config: added 'auth_alg' value 'OPEN' mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.1975] Config: added 'psk' value '' mai 23 13:43:25 endless wpa_supplicant[3353]: wlp2s0: SME: Trying to authenticate with 80:d0:4a:90:f1:d9 (SSID='BethDaniel' freq=2412 MHz) mai 23 13:43:25 endless kernel: wlp2s0: authenticate with 80:d0:4a:90:f1:d9 mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.2980] device (wlp2s0): supplicant interface state: ready -> authenticating mai 23 13:43:25 endless wpa_supplicant[3353]: wlp2s0: Trying to associate with 80:d0:4a:90:f1:d9 (SSID='BethDaniel' freq=2412 MHz) mai 23 13:43:25 endless kernel: wlp2s0: send auth to 80:d0:4a:90:f1:d9 (try 1/3) mai 23 13:43:25 endless kernel: wlp2s0: authenticated mai 23 13:43:25 endless kernel: wlp2s0: associate with 80:d0:4a:90:f1:d9 (try 1/3) mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.3005] device (wlp2s0): supplicant interface state: authenticating -> associating mai 23 13:43:25 endless wpa_supplicant[3353]: wlp2s0: Associated with 80:d0:4a:90:f1:d9 mai 23 13:43:25 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 mai 23 13:43:25 endless kernel: wlp2s0: RX AssocResp from 80:d0:4a:90:f1:d9 (capab=0x411 status=0 aid=2) mai 23 13:43:25 endless kernel: wlp2s0: associated mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.3126] device (wlp2s0): supplicant interface state: associating -> associated mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.3473] device (wlp2s0): supplicant interface state: associated -> 4-way handshake mai 23 13:43:25 endless wpa_supplicant[3353]: wlp2s0: WPA: Key negotiation completed with 80:d0:4a:90:f1:d9 [PTK=CCMP GTK=CCMP] mai 23 13:43:25 endless kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready mai 23 13:43:25 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 80:d0:4a:90:f1:d9 completed [id=0 id_str=] mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.3655] device (wlp2s0): supplicant interface state: 4-way handshake -> completed mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.3655] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "BethDaniel" mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.3657] device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.3662] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) mai 23 13:43:25 endless NetworkManager[2802]: [1590252205.3682] dhcp4 (wlp2s0): dhclient started with pid 21197 mai 23 13:43:25 endless avahi-daemon[2791]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::c6c7:3fc7:b338:a37b. mai 23 13:43:25 endless avahi-daemon[2791]: New relevant interface wlp2s0.IPv6 for mDNS. mai 23 13:43:25 endless avahi-daemon[2791]: Registering new address record for fe80::c6c7:3fc7:b338:a37b on wlp2s0.*. mai 23 13:43:25 endless dhclient[21197]: DHCPREQUEST for 192.168.0.34 on wlp2s0 to 255.255.255.255 port 67 mai 23 13:43:25 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-43 noise=-111 txrate=1000 mai 23 13:43:26 endless ntpd[16131]: bind(19) AF_INET6 fe80::c6c7:3fc7:b338:a37b%3#123 flags 0x11 failed: Cannot assign requested address mai 23 13:43:26 endless ntpd[16131]: unable to create socket on wlp2s0 (8) for fe80::c6c7:3fc7:b338:a37b%3#123 mai 23 13:43:26 endless ntpd[16131]: failed to init interface for address fe80::c6c7:3fc7:b338:a37b%3 mai 23 13:43:27 endless NetworkManager[2802]: [1590252207.4509] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) mai 23 13:43:27 endless NetworkManager[2802]: [1590252207.4525] dhcp6 (wlp2s0): dhclient started with pid 21215 mai 23 13:43:27 endless avahi-daemon[2791]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::c6c7:3fc7:b338:a37b. mai 23 13:43:27 endless avahi-daemon[2791]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address 2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e. mai 23 13:43:27 endless avahi-daemon[2791]: Registering new address record for 2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e on wlp2s0.*. mai 23 13:43:27 endless avahi-daemon[2791]: Withdrawing address record for fe80::c6c7:3fc7:b338:a37b on wlp2s0. mai 23 13:43:27 endless dhclient[21215]: XMT: Confirm on wlp2s0, interval 990ms. mai 23 13:43:27 endless dhclient[21215]: RCV: Reply message on wlp2s0 from fe80::82d0:4aff:fe90:f1d6. mai 23 13:43:27 endless dhclient[21215]: message status code Success. mai 23 13:43:27 endless NetworkManager[2802]: [1590252207.6820] dhcp6 (wlp2s0): valid_lft 86400 mai 23 13:43:27 endless NetworkManager[2802]: [1590252207.6820] dhcp6 (wlp2s0): preferred_lft 86400 mai 23 13:43:27 endless NetworkManager[2802]: [1590252207.6820] dhcp6 (wlp2s0): address 2804:14d:5ce6:9e6b::1001 mai 23 13:43:27 endless NetworkManager[2802]: [1590252207.6820] dhcp6 (wlp2s0): nameserver '2804:14d:1:0:181:213:132:5' mai 23 13:43:27 endless NetworkManager[2802]: [1590252207.6820] dhcp6 (wlp2s0): nameserver '2804:14d:1:0:181:213:132:4' mai 23 13:43:27 endless NetworkManager[2802]: [1590252207.6821] dhcp6 (wlp2s0): state changed unknown -> bound, event ID="d3:dd:a0:cd|1590247653" mai 23 13:43:27 endless avahi-daemon[2791]: Registering new address record for 2804:14d:5ce6:9e6b::1001 on wlp2s0.*. mai 23 13:43:27 endless dbus-daemon[2800]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.30' (uid=0 pid=2802 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") mai 23 13:43:27 endless systemd[1]: Starting Network Manager Script Dispatcher Service... mai 23 13:43:27 endless dbus-daemon[2800]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' mai 23 13:43:27 endless systemd[1]: Started Network Manager Script Dispatcher Service. mai 23 13:43:27 endless nm-dispatcher[21224]: req:1 'dhcp6-change' [wlp2s0]: new request (5 scripts) mai 23 13:43:27 endless nm-dispatcher[21224]: req:1 'dhcp6-change' [wlp2s0]: start running ordered scripts... mai 23 13:43:28 endless NetworkManager[2802]: [1590252208.9411] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') mai 23 13:43:28 endless NetworkManager[2802]: [1590252208.9423] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') mai 23 13:43:28 endless NetworkManager[2802]: [1590252208.9426] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') mai 23 13:43:28 endless NetworkManager[2802]: [1590252208.9434] manager: NetworkManager state is now CONNECTED_LOCAL mai 23 13:43:29 endless NetworkManager[2802]: [1590252209.0108] manager: NetworkManager state is now CONNECTED_SITE mai 23 13:43:29 endless NetworkManager[2802]: [1590252209.0110] policy: set 'BethDaniel' (wlp2s0) as default for IPv6 routing and DNS mai 23 13:43:29 endless eos-metrics-ins[3702]: Not recording network ID as it is not required for this image mai 23 13:43:29 endless gsd-sharing[8803]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded. mai 23 13:43:29 endless gsd-sharing[8803]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded. mai 23 13:43:29 endless NetworkManager[2802]: [1590252209.0762] device (wlp2s0): Activation: successful, device activated. mai 23 13:43:29 endless nm-dispatcher[21224]: req:2 'up' [wlp2s0]: new request (5 scripts) mai 23 13:43:29 endless nm-dispatcher[21224]: req:2 'up' [wlp2s0]: start running ordered scripts... mai 23 13:43:29 endless ntpd[16131]: ntpd exiting on signal 15 (Terminated) mai 23 13:43:29 endless systemd[1]: Stopping Network Time Service... mai 23 13:43:29 endless systemd[1]: ntp.service: Succeeded. mai 23 13:43:29 endless systemd[1]: Stopped Network Time Service. mai 23 13:43:29 endless systemd[1]: Starting Network Time Service... mai 23 13:43:29 endless ntpd[21315]: ntpd 4.2.8p12@1.3728-o (1): Starting mai 23 13:43:29 endless ntpd[21315]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 112:119 mai 23 13:43:29 endless systemd[1]: Started Network Time Service. mai 23 13:43:29 endless ntpd[21372]: proto: precision = 0.118 usec (-23) mai 23 13:43:29 endless ntpd[21372]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature mai 23 13:43:29 endless ntpd[21372]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2020-06-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37 mai 23 13:43:29 endless ntpd[21372]: Listen and drop on 0 v6wildcard [::]:123 mai 23 13:43:29 endless ntpd[21372]: Listen and drop on 1 v4wildcard 0.0.0.0:123 mai 23 13:43:29 endless ntpd[21372]: Listen normally on 2 lo 127.0.0.1:123 mai 23 13:43:29 endless ntpd[21372]: Listen normally on 3 lo [::1]:123 mai 23 13:43:29 endless ntpd[21372]: Listen normally on 4 wlp2s0 [2804:14d:5ce6:9e6b::1001]:123 mai 23 13:43:29 endless ntpd[21372]: Listen normally on 5 wlp2s0 [2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e]:123 mai 23 13:43:29 endless ntpd[21372]: Listen normally on 6 wlp2s0 [fe80::c6c7:3fc7:b338:a37b%3]:123 mai 23 13:43:29 endless ntpd[21372]: Listening on routing socket on fd #23 for interface updates mai 23 13:43:29 endless ntpd[21372]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized mai 23 13:43:29 endless ntpd[21372]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized mai 23 13:43:30 endless ntpd[21372]: Soliciting pool server 192.99.2.8 mai 23 13:43:31 endless ntpd[21372]: Soliciting pool server 45.11.105.253 mai 23 13:43:31 endless dhclient[21197]: DHCPREQUEST for 192.168.0.34 on wlp2s0 to 255.255.255.255 port 67 mai 23 13:43:31 endless dhclient[21197]: DHCPACK of 192.168.0.34 from 192.168.0.1 mai 23 13:43:31 endless NetworkManager[2802]: [1590252211.9748] dhcp4 (wlp2s0): address 192.168.0.34 mai 23 13:43:31 endless NetworkManager[2802]: [1590252211.9748] dhcp4 (wlp2s0): plen 24 (255.255.255.0) mai 23 13:43:31 endless NetworkManager[2802]: [1590252211.9748] dhcp4 (wlp2s0): gateway 192.168.0.1 mai 23 13:43:31 endless NetworkManager[2802]: [1590252211.9748] dhcp4 (wlp2s0): lease time 86400 mai 23 13:43:31 endless NetworkManager[2802]: [1590252211.9748] dhcp4 (wlp2s0): nameserver '181.213.132.5' mai 23 13:43:31 endless NetworkManager[2802]: [1590252211.9748] dhcp4 (wlp2s0): nameserver '181.213.132.4' mai 23 13:43:31 endless NetworkManager[2802]: [1590252211.9748] dhcp4 (wlp2s0): state changed unknown -> bound mai 23 13:43:31 endless avahi-daemon[2791]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.0.34. mai 23 13:43:31 endless avahi-daemon[2791]: New relevant interface wlp2s0.IPv4 for mDNS. mai 23 13:43:31 endless avahi-daemon[2791]: Registering new address record for 192.168.0.34 on wlp2s0.IPv4. mai 23 13:43:31 endless NetworkManager[2802]: [1590252211.9787] policy: set 'BethDaniel' (wlp2s0) as default for IPv4 routing and DNS mai 23 13:43:32 endless dhclient[21197]: bound to 192.168.0.34 -- renewal in 41880 seconds. mai 23 13:43:32 endless nm-dispatcher[21224]: req:3 'dhcp4-change' [wlp2s0]: new request (5 scripts) mai 23 13:43:32 endless nm-dispatcher[21224]: req:3 'dhcp4-change' [wlp2s0]: start running ordered scripts... mai 23 13:43:32 endless ntpd[21372]: Soliciting pool server 2a0b:4341:1500:123:: mai 23 13:43:32 endless NetworkManager[2802]: [1590252212.5512] manager: NetworkManager state is now CONNECTED_GLOBAL mai 23 13:43:32 endless eos-metrics-ins[3702]: Not recording network ID as it is not required for this image mai 23 13:43:32 endless nm-dispatcher[21224]: req:4 'connectivity-change': new request (5 scripts) mai 23 13:43:32 endless nm-dispatcher[21224]: req:4 'connectivity-change': start running ordered scripts... mai 23 13:43:32 endless systemd[1]: Started Update or install Google Chrome plugins. mai 23 13:43:32 endless systemd[1]: Started /bin/systemctl --no-block start eos-phone-home.service. mai 23 13:43:32 endless nm-dispatcher[21429]: Running timer as unit: run-r65f53f1847c84ecaa1bc9dc469a23c30.timer mai 23 13:43:32 endless nm-dispatcher[21429]: Will run service as unit: run-r65f53f1847c84ecaa1bc9dc469a23c30.service mai 23 13:43:33 endless eos-chrome-plugin-update[21420]: No need to check the Flash plugin yet (version: 32.0.0.371) mai 23 13:43:33 endless eos-chrome-plugin-update[21420]: No need to check the Widevine plugin yet (version: 4.10.1582.2) mai 23 13:43:33 endless eos-chrome-plugin-update[21420]: All done mai 23 13:43:33 endless systemd[1]: eos-chrome-plugin-update.service: Succeeded. mai 23 13:43:33 endless ntpd[21372]: Soliciting pool server 2606:4700:f1::1 mai 23 13:43:33 endless ntpd[21372]: Soliciting pool server 52.67.171.238 mai 23 13:43:34 endless ntpd[21372]: Soliciting pool server 2001:440:1880:5555::2 mai 23 13:43:34 endless ntpd[21372]: Listen normally on 7 wlp2s0 192.168.0.34:123 mai 23 13:43:34 endless ntpd[21372]: new interface(s) found: waking up resolver mai 23 13:43:35 endless ntpd[21372]: Soliciting pool server 2001:41d0:2:b7a2:0:162:b:123 mai 23 13:43:36 endless ntpd[21372]: Soliciting pool server 188.165.236.162 mai 23 13:43:37 endless ntpd[21372]: Soliciting pool server 146.164.48.66 mai 23 13:43:38 endless ntpd[21372]: Soliciting pool server 52.67.171.238 mai 23 13:43:39 endless ntpd[21372]: Soliciting pool server 45.11.105.253 mai 23 13:43:39 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-37 noise=-111 txrate=1000 mai 23 13:43:40 endless ntpd[21372]: Soliciting pool server 2a00:fd80:aaaa:ffff::eeee:ff1 mai 23 13:43:41 endless ntpd[21372]: Soliciting pool server 2a00:1630:66:ea::e82a mai 23 13:43:42 endless ntpd[21372]: Soliciting pool server 2a01:4f8:c17:b8f::2 mai 23 13:43:43 endless systemd[1]: NetworkManager-dispatcher.service: Succeeded. mai 23 13:44:00 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-32 noise=-111 txrate=1000 mai 23 13:44:51 endless systemd[1]: Started Endless OS Automatic Updater. mai 23 13:44:51 endless systemd[1]: eos-autoupdater.service: Succeeded. mai 23 13:45:14 endless systemd[3868]: gnome-launched-gnome-wifi-panel.desktop-21083.scope: Succeeded. mai 23 13:45:24 endless kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 mai 23 13:45:30 endless gnome-shell[8439]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 5 mai 23 13:45:31 endless systemd-logind[3124]: System is rebooting. mai 23 13:45:31 endless systemd[3868]: gsd-screensaver-proxy.service: Succeeded. mai 23 13:45:31 endless systemd[3868]: Stopped target GNOME Maintenance of expirable data. mai 23 13:45:31 endless systemd[3868]: Stopped target GNOME Media keys handling. mai 23 13:45:31 endless systemd[3868]: Stopped target GNOME Power management handling. mai 23 13:45:31 endless systemd[3868]: Stopped target GNOME RFKill handling. mai 23 13:45:31 endless systemd[3868]: Stopped target GNOME Freedesktop screensaver handling. mai 23 13:45:31 endless systemd[3868]: Stopped target GNOME Sound sample caching handling. mai 23 13:45:31 endless systemd[3868]: Stopped target GNOME USB protection handling. mai 23 13:45:31 endless systemd[3868]: Stopped target GNOME WWan management. mai 23 13:45:31 endless systemd[3868]: Stopped target GNOME XSettings. mai 23 13:45:31 endless systemd[3868]: Stopped target GNOME Keyboard handling. mai 23 13:45:31 endless kernel: rfkill: input handler enabled mai 23 13:45:31 endless systemd[3868]: gsd-rfkill.service: Succeeded. mai 23 13:45:31 endless systemd[3868]: Stopped GNOME RFKill handling. mai 23 13:45:31 endless systemd[3868]: gsd-wwan.service: Succeeded. mai 23 13:45:31 endless systemd[3868]: Stopped GNOME WWan management. mai 23 13:45:31 endless systemd[3868]: at-spi-dbus-bus.service: Succeeded. mai 23 13:45:31 endless systemd[3868]: gsd-a11y-settings.service: Succeeded. mai 23 13:45:31 endless systemd[3868]: gsd-keyboard.service: Succeeded. mai 23 13:45:31 endless systemd[3868]: Stopped GNOME Keyboard handling. mai 23 13:45:31 endless systemd[3868]: gsd-power.service: Succeeded. mai 23 13:45:31 endless systemd[3868]: Stopped GNOME Power management handling. mai 23 13:45:31 endless systemd[3868]: gsd-sound.service: Succeeded. mai 23 13:45:31 endless systemd[3868]: Stopped GNOME Sound sample caching handling. mai 23 13:45:31 endless systemd[3868]: gsd-usb-protection.service: Succeeded. mai 23 13:45:31 endless systemd[3868]: Stopped GNOME USB protection handling. mai 23 13:45:31 endless systemd[3868]: gsd-xsettings.service: Succeeded. mai 23 13:45:31 endless systemd[3868]: Stopped GNOME XSettings. mai 23 13:45:31 endless systemd[3868]: gsd-wacom.service: Succeeded. mai 23 13:45:31 endless systemd[3868]: Stopped target GNOME Accessibility settings. mai 23 13:45:31 endless systemd[3868]: Stopped target GNOME Wacom handling. mai 23 13:45:31 endless systemd[3868]: Stopped target GNOME Color management. mai 23 13:45:31 endless systemd[3868]: Stopped target GNOME Date & Time handling. mai 23 13:45:31 endless systemd[3868]: gsd-sharing.service: Succeeded. mai 23 13:45:31 endless systemd[3868]: Stopped target GNOME Sharing handling. mai 23 13:45:31 endless systemd[3868]: gsd-color.service: Succeeded. mai 23 13:45:31 endless systemd[3868]: Stopped GNOME Color management. mai 23 13:45:31 endless systemd[3868]: gsd-datetime.service: Succeeded. mai 23 13:45:31 endless systemd[3868]: Stopped GNOME Date & Time handling. mai 23 13:45:31 endless systemd[1]: Stopping Session 5 of user daniel. mai 23 13:45:31 endless systemd[1]: Removed slice system-getty.slice. mai 23 13:45:31 endless systemd[1]: systemd-readahead-done.timer: Succeeded. mai 23 13:45:31 endless systemd[1]: Stopped Stop Read-Ahead Data Collection 10s After Completed Startup. mai 23 13:45:31 endless systemd[1]: Stopped target Bluetooth. mai 23 13:45:31 endless systemd[1]: Stopped target endless-extra SD card mounted (if expected). mai 23 13:45:31 endless systemd[1]: Stopped target Graphical Interface. mai 23 13:45:31 endless systemd[1]: Stopped target Multi-User System. mai 23 13:45:31 endless systemd[1]: Stopped target Login Prompts. mai 23 13:45:31 endless systemd[1]: Stopped target Remote Encrypted Volumes. mai 23 13:45:31 endless systemd[1]: Stopped target Sound Card. mai 23 13:45:31 endless systemd[1]: Stopped target Timers. mai 23 13:45:31 endless systemd[1]: eos-autoupdater.timer: Succeeded. mai 23 13:45:31 endless systemd[1]: Stopped Endless OS Automatic Update Timer. mai 23 13:45:31 endless systemd[1]: eos-phone-home.timer: Succeeded. mai 23 13:45:31 endless systemd[1]: Stopped Send system activation/daily ping messages to Endless. mai 23 13:45:31 endless systemd[1]: fake-hwclock.timer: Succeeded. mai 23 13:45:31 endless systemd[1]: Stopped Save the clock time to disk periodically. mai 23 13:45:31 endless systemd[1]: fstrim.timer: Succeeded. mai 23 13:45:31 endless systemd[1]: Stopped Discard unused blocks once a week. mai 23 13:45:31 endless systemd[1]: man-db.timer: Succeeded. mai 23 13:45:31 endless systemd[1]: Stopped Daily man-db regeneration. mai 23 13:45:31 endless systemd[1]: run-r65f53f1847c84ecaa1bc9dc469a23c30.timer: Succeeded. mai 23 13:45:31 endless systemd[1]: Stopped /bin/systemctl --no-block start eos-phone-home.service. mai 23 13:45:31 endless systemd[1]: systemd-tmpfiles-clean.timer: Succeeded. mai 23 13:45:31 endless systemd[1]: Stopped Daily Cleanup of Temporary Directories. mai 23 13:45:31 endless systemd[1]: systemd-rfkill.socket: Succeeded. mai 23 13:45:31 endless systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch. mai 23 13:45:31 endless ModemManager[2789]: Caught signal, shutting down... mai 23 13:45:31 endless systemd[1]: Stopping Modem Manager... mai 23 13:45:31 endless bluetoothd[2947]: Terminating mai 23 13:45:31 endless systemd[1]: Stopping Accounts Service... mai 23 13:45:31 endless systemd[1]: Stopping Bluetooth service... mai 23 13:45:31 endless systemd[1]: Stopping Manage, Install and Generate Color Profiles... mai 23 13:45:31 endless systemd[1]: Stopping Make remote CUPS printers available locally... mai 23 13:45:31 endless systemd[1]: Stopping Restore /run/initramfs on shutdown... mai 23 13:45:31 endless systemd[1]: Stopping swap with zram... mai 23 13:45:31 endless systemd[1]: Stopping EndlessOS Metrics Instrumentation... mai 23 13:45:31 endless systemd[1]: Stopping Endless OS Updater... mai 23 13:45:31 endless NetworkManager[2802]: [1590252331.9710] modem-manager: ModemManager no longer available mai 23 13:45:31 endless ModemManager[2789]: ModemManager is shut down mai 23 13:45:31 endless systemd[1]: Stopping flatpak system helper... mai 23 13:45:31 endless systemd[1]: Stopping GNOME Display Manager... mai 23 13:45:31 endless systemd[1]: Stopping Location Lookup Service... mai 23 13:45:31 endless ntpd[21372]: ntpd exiting on signal 15 (Terminated) mai 23 13:45:31 endless ntpd[21372]: 2001:67c:1560:8003::c7 local addr 2804:14d:5ce6:9e6b::1001 -> mai 23 13:45:31 endless systemd[1]: Stopping Network Time Service... mai 23 13:45:31 endless ntpd[21372]: 2a0b:4341:1500:123:: local addr 2804:14d:5ce6:9e6b::1001 -> mai 23 13:45:31 endless ntpd[21372]: 2606:4700:f1::1 local addr 2804:14d:5ce6:9e6b::1001 -> mai 23 13:45:31 endless ntpd[21372]: 2001:440:1880:5555::2 local addr 2804:14d:5ce6:9e6b::1001 -> mai 23 13:45:31 endless ntpd[21372]: 2001:41d0:2:b7a2:0:162:b:123 local addr 2804:14d:5ce6:9e6b::1001 -> mai 23 13:45:31 endless ntpd[21372]: 188.165.236.162 local addr 192.168.0.34 -> mai 23 13:45:31 endless ntpd[21372]: 146.164.48.66 local addr 192.168.0.34 -> mai 23 13:45:31 endless ntpd[21372]: 52.67.171.238 local addr 192.168.0.34 -> mai 23 13:45:31 endless ntpd[21372]: 45.11.105.253 local addr 192.168.0.34 -> mai 23 13:45:31 endless ntpd[21372]: 2a00:fd80:aaaa:ffff::eeee:ff1 local addr 2804:14d:5ce6:9e6b::1001 -> mai 23 13:45:31 endless ntpd[21372]: 2a00:1630:66:ea::e82a local addr 2804:14d:5ce6:9e6b::1001 -> mai 23 13:45:31 endless ntpd[21372]: 2a01:4f8:c17:b8f::2 local addr 2804:14d:5ce6:9e6b::1001 -> mai 23 13:45:31 endless systemd[1]: Stopping Authorization Manager... mai 23 13:45:31 endless systemd[1]: Stopping Pressure Stall Information Monitor... mai 23 13:45:31 endless systemd[1]: record-boot-success.service: Succeeded. mai 23 13:45:31 endless systemd[1]: Stopped Record Boot Success. mai 23 13:45:31 endless cupsd[2799]: REQUEST localhost - - "POST / HTTP/1.1" 200 154 Cancel-Subscription client-error-not-found mai 23 13:45:31 endless cupsd[2799]: REQUEST localhost - - "POST / HTTP/1.1" 401 123 Cancel-Subscription successful-ok mai 23 13:45:31 endless cupsd[2799]: REQUEST localhost - - "POST / HTTP/1.1" 200 154 Cancel-Subscription client-error-not-found mai 23 13:45:31 endless gsd-print-notif[8799]: Source ID 3 was not found when attempting to remove it mai 23 13:45:31 endless systemd[1]: Stopping RealtimeKit Scheduling Policy Service... mai 23 13:45:31 endless cupsd[2799]: REQUEST localhost - root "POST / HTTP/1.1" 200 123 Cancel-Subscription successful-ok mai 23 13:45:31 endless cupsd[2799]: REQUEST localhost - - "POST / HTTP/1.1" 200 152 Cancel-Subscription successful-ok mai 23 13:45:31 endless systemd[3868]: Stopped target GNOME Printer notifications. mai 23 13:45:31 endless systemd[3868]: gsd-print-notifications.service: Succeeded. mai 23 13:45:31 endless systemd[3868]: Stopped GNOME Printer notifications. mai 23 13:45:31 endless systemd[1]: Stopping Load/Save Random Seed... mai 23 13:45:31 endless systemd[1]: Stopping Thermal Daemon Service... mai 23 13:45:31 endless systemd[1]: Stopping Disk Manager... mai 23 13:45:31 endless systemd[1]: Stopping Daemon for power management... mai 23 13:45:31 endless dbus-daemon[2800]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.30' (uid=0 pid=2802 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") mai 23 13:45:32 endless systemd[3868]: gsd-media-keys.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped GNOME Media keys handling. mai 23 13:45:32 endless systemd[1]: polkit.service: Succeeded. mai 23 13:45:32 endless systemd[1]: Stopped Authorization Manager. mai 23 13:45:32 endless systemd[1]: psi-monitor.service: Succeeded. mai 23 13:45:32 endless systemd[1]: Stopped Pressure Stall Information Monitor. mai 23 13:45:32 endless systemd[1]: colord.service: Succeeded. mai 23 13:45:32 endless systemd[1]: Stopped Manage, Install and Generate Color Profiles. mai 23 13:45:32 endless systemd[1]: rtkit-daemon.service: Succeeded. mai 23 13:45:32 endless systemd[1]: Stopped RealtimeKit Scheduling Policy Service. mai 23 13:45:32 endless systemd[1]: upower.service: Succeeded. mai 23 13:45:32 endless systemd[1]: Stopped Daemon for power management. mai 23 13:45:32 endless systemd[1]: geoclue.service: Succeeded. mai 23 13:45:32 endless systemd[1]: Stopped Location Lookup Service. mai 23 13:45:32 endless systemd[1]: eos-updater.service: Succeeded. mai 23 13:45:32 endless systemd[1]: Stopped Endless OS Updater. mai 23 13:45:32 endless systemd[1]: ntp.service: Succeeded. mai 23 13:45:32 endless systemd[1]: Stopped Network Time Service. mai 23 13:45:32 endless systemd[1]: session-5.scope: Succeeded. mai 23 13:45:32 endless systemd[1]: Stopped Session 5 of user daniel. mai 23 13:45:32 endless thermald[2940]: [WARN]Terminating ... mai 23 13:45:32 endless xdg-desktop-por[9756]: xdg-desktop-portal-gtk: Fatal IO error 11 (Recurso temporariamente indisponível) on X server :0. mai 23 13:45:32 endless eos-link-user-endlessos.desktop[17140]: [17134:17134:0523/134532.048574:ERROR:chrome_browser_main_extra_parts_x11.cc(62)] X IO error received (X server probably went away) mai 23 13:45:32 endless eos-link-user-endlessos.desktop[17140]: [17180:17180:0523/134532.049562:ERROR:x11_util.cc(109)] X IO error received (X server probably went away) mai 23 13:45:32 endless org.gtk.vfs.Daemon[17959]: A connection to the bus can't be made mai 23 13:45:32 endless gdm-Xorg-:0[7519]: (II) event6 - Acer Wireless Radio Control: device removed mai 23 13:45:32 endless systemd[3868]: var-roothome-.cache-doc.mount: Succeeded. mai 23 13:45:32 endless systemd[3868]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE mai 23 13:45:32 endless systemd[3868]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'. mai 23 13:45:32 endless systemd[1]: var-roothome-.cache-doc.mount: Succeeded. mai 23 13:45:32 endless systemd[1]: Unmounted /var/roothome/.cache/doc. mai 23 13:45:32 endless gdm-Xorg-:0[7519]: (II) event3 - Power Button: device removed mai 23 13:45:32 endless systemd[1]: accounts-daemon.service: Succeeded. mai 23 13:45:32 endless systemd[1]: Stopped Accounts Service. mai 23 13:45:32 endless systemd[1]: eos-metrics-instrumentation.service: Succeeded. mai 23 13:45:32 endless bluetoothd[2947]: Endpoint unregistered: sender=:1.489 path=/MediaEndpoint/A2DPSource/sbc mai 23 13:45:32 endless systemd[1]: Stopped EndlessOS Metrics Instrumentation. mai 23 13:45:32 endless systemd[1]: flatpak-system-helper.service: Succeeded. mai 23 13:45:32 endless systemd[1]: Stopped flatpak system helper. mai 23 13:45:32 endless systemd-logind[3124]: Session 5 logged out. Waiting for processes to exit. mai 23 13:45:32 endless systemd[1]: Stopping EndlessOS Metrics Event Recorder Server... mai 23 13:45:32 endless systemd[1]: Stopping Login Service... mai 23 13:45:32 endless systemd[1]: Stopping User Manager for UID 1001... mai 23 13:45:32 endless dbus-daemon[2800]: [system] Activation via systemd failed for unit 'polkit.service': Refusing activation, D-Bus is shutting down. mai 23 13:45:32 endless systemd-logind[3124]: Removed session 5. mai 23 13:45:32 endless bluetoothd[2947]: Stopping SDP server mai 23 13:45:32 endless gdm-Xorg-:0[7519]: (II) event5 - Video Bus: device removed mai 23 13:45:32 endless bluetoothd[2947]: Exit mai 23 13:45:32 endless NetworkManager[2802]: [1590252332.1178] bluez5: NAP: removed interface 5C:C9:D3:DD:A0:CE mai 23 13:45:32 endless gdm-Xorg-:0[7519]: (II) event2 - Power Button: device removed mai 23 13:45:32 endless gdm-Xorg-:0[7519]: (II) event1 - Sleep Button: device removed mai 23 13:45:32 endless gdm-Xorg-:0[7519]: (II) event14 - HD User Facing: HD User Facing: device removed mai 23 13:45:32 endless systemd[1]: dracut-shutdown.service: Succeeded. mai 23 13:45:32 endless systemd[1]: Stopped Restore /run/initramfs on shutdown. mai 23 13:45:32 endless gdm-Xorg-:0[7519]: (II) event15 - SYNA7DB5:01 06CB:7DB7 Mouse: device removed mai 23 13:45:32 endless gdm-Xorg-:0[7519]: (II) event16 - SYNA7DB5:01 06CB:7DB7 Touchpad: device removed mai 23 13:45:32 endless systemd[3868]: gnome-session-manager@gnome.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped GNOME Session Manager (session: gnome). mai 23 13:45:32 endless systemd[3868]: Stopping flatpak-com.google.Chrome-17133.scope. mai 23 13:45:32 endless systemd[1]: systemd-logind.service: Succeeded. mai 23 13:45:32 endless systemd[1]: Stopped Login Service. mai 23 13:45:32 endless systemd[3868]: Stopping flatpak-org.libreoffice.LibreOffice-8873.scope. mai 23 13:45:32 endless systemd[3868]: vte-spawn-d7e1af7c-0549-42d0-bb52-d1709f2ebcbb.scope: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped VTE child process 17832 launched by gnome-terminal-server process 17823. mai 23 13:45:32 endless systemd[3868]: Removed slice gnome\x2dsession\x2dmanager.slice. mai 23 13:45:32 endless systemd[3868]: Stopped target Bluetooth. mai 23 13:45:32 endless systemd[3868]: Stopped target Main User Target. mai 23 13:45:32 endless systemd[3868]: Stopped target GNOME X11 Session (session: gnome). mai 23 13:45:32 endless systemd[3868]: Stopped target Current graphical user session. mai 23 13:45:32 endless systemd[3868]: Stopped target GNOME Session. mai 23 13:45:32 endless systemd[3868]: Stopped target GNOME session X11 services. mai 23 13:45:32 endless systemd[3868]: Stopped target GNOME X11 Session. mai 23 13:45:32 endless systemd[3868]: Stopped target GNOME Session (session: gnome). mai 23 13:45:32 endless systemd[3868]: Stopped target GNOME Smartcard handling. mai 23 13:45:32 endless systemd[3868]: Stopping D-Bus User Message Bus... mai 23 13:45:32 endless systemd[3868]: Stopping Evolution address book service... mai 23 13:45:32 endless systemd[3868]: Stopping Evolution calendar service... mai 23 13:45:32 endless systemd[3868]: Stopping Evolution source registry... mai 23 13:45:32 endless gvfsd[8267]: A connection to the bus can't be made mai 23 13:45:32 endless systemd[3868]: Stopping flatpak session helper... mai 23 13:45:32 endless systemd[3868]: Stopping GLib proxy auto-configuration service... mai 23 13:45:32 endless systemd[3868]: Stopping GNOME Terminal Server... mai 23 13:45:32 endless obexd[20966]: Terminating mai 23 13:45:32 endless systemd[3868]: Stopping GNOME Smartcard handling... mai 23 13:45:32 endless systemd[3868]: Stopping Virtual filesystem service - Apple File Conduit monitor... mai 23 13:45:32 endless systemd[3868]: Stopping Virtual filesystem service... mai 23 13:45:32 endless systemd[3868]: Stopping Virtual filesystem service - GNOME Online Accounts monitor... mai 23 13:45:32 endless systemd[3868]: Stopping Virtual filesystem service - digital camera monitor... mai 23 13:45:32 endless systemd[3868]: Stopping Virtual filesystem metadata service... mai 23 13:45:32 endless systemd[3868]: Stopping Virtual filesystem service - Media Transfer Protocol monitor... mai 23 13:45:32 endless systemd[3868]: Stopping Virtual filesystem service - disk device monitor... mai 23 13:45:32 endless systemd[3868]: Stopping Bluetooth OBEX service... mai 23 13:45:32 endless systemd[3868]: Stopping Sound Service... mai 23 13:45:32 endless systemd[3868]: Stopping Tracker file system data miner... mai 23 13:45:32 endless systemd[3868]: Stopping Portal service... mai 23 13:45:32 endless systemd[3868]: Stopping flatpak document portal service... mai 23 13:45:32 endless systemd[3868]: Stopping sandboxed app permission store... mai 23 13:45:32 endless systemd[3868]: gvfs-gphoto2-volume-monitor.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped Virtual filesystem service - digital camera monitor. mai 23 13:45:32 endless systemd[3868]: glib-pacrunner.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped GLib proxy auto-configuration service. mai 23 13:45:32 endless systemd[3868]: gvfs-mtp-volume-monitor.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped Virtual filesystem service - Media Transfer Protocol monitor. mai 23 13:45:32 endless systemd[3868]: gvfs-goa-volume-monitor.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped Virtual filesystem service - GNOME Online Accounts monitor. mai 23 13:45:32 endless systemd[3868]: xdg-permission-store.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped sandboxed app permission store. mai 23 13:45:32 endless systemd[3868]: gvfs-metadata.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped Virtual filesystem metadata service. mai 23 13:45:32 endless systemd[3868]: flatpak-session-helper.service: Main process exited, code=exited, status=1/FAILURE mai 23 13:45:32 endless systemd[3868]: flatpak-session-helper.service: Failed with result 'exit-code'. mai 23 13:45:32 endless systemd[3868]: Stopped flatpak session helper. mai 23 13:45:32 endless systemd[1]: run-user-1001-doc.mount: Succeeded. mai 23 13:45:32 endless gdm-Xorg-:0[7519]: (II) event4 - AT Translated Set 2 keyboard: device removed mai 23 13:45:32 endless systemd[1]: Unmounted /run/user/1001/doc. mai 23 13:45:32 endless systemd[3868]: run-user-1001-doc.mount: Succeeded. mai 23 13:45:32 endless systemd[3868]: gnome-session-monitor.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped Monitor Session leader for GNOME Session. mai 23 13:45:32 endless systemd[3868]: gvfs-udisks2-volume-monitor.service: Succeeded. mai 23 13:45:32 endless xdg-document-po[9730]: Error releasing name org.freedesktop.portal.Documents: A conexão está fechada mai 23 13:45:32 endless eos-link-user-endlessos.desktop[17140]: [17134:17181:0523/134532.398705:FATAL:bus.cc(1220)] D-Bus connection was disconnected. Aborting. mai 23 13:45:32 endless systemd[3868]: Stopped Virtual filesystem service - disk device monitor. mai 23 13:45:32 endless systemd[3868]: gvfs-afc-volume-monitor.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped Virtual filesystem service - Apple File Conduit monitor. mai 23 13:45:32 endless systemd[3868]: evolution-source-registry.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped Evolution source registry. mai 23 13:45:32 endless systemd[3868]: xdg-desktop-portal.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped Portal service. mai 23 13:45:32 endless systemd[3868]: gnome-terminal-server.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped GNOME Terminal Server. mai 23 13:45:32 endless systemd[3868]: xdg-document-portal.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped flatpak document portal service. mai 23 13:45:32 endless systemd[3868]: flatpak-org.libreoffice.LibreOffice-8873.scope: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped flatpak-org.libreoffice.LibreOffice-8873.scope. mai 23 13:45:32 endless systemd[3868]: flatpak-com.google.Chrome-17133.scope: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped flatpak-com.google.Chrome-17133.scope. mai 23 13:45:32 endless systemd[3868]: Removed slice apps-org.gnome.Terminal.slice. mai 23 13:45:32 endless systemd[3868]: Removed slice apps.slice. mai 23 13:45:32 endless systemd[3868]: dbus.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped D-Bus User Message Bus. mai 23 13:45:32 endless gdm-Xorg-:0[7519]: (II) event13 - Acer WMI hotkeys: device removed mai 23 13:45:32 endless pulseaudio[8416]: XIO: fatal IO error 11 (Recurso temporariamente indisponível) on X server ":0" mai 23 13:45:32 endless pulseaudio[8416]: after 19 requests (19 known processed) with 0 events remaining. mai 23 13:45:32 endless systemd[3868]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE mai 23 13:45:32 endless systemd[3868]: pulseaudio.service: Failed with result 'exit-code'. mai 23 13:45:32 endless systemd[3868]: Stopped Sound Service. mai 23 13:45:32 endless systemd[1]: bluetooth.service: Succeeded. mai 23 13:45:32 endless systemd[1]: Stopped Bluetooth service. mai 23 13:45:32 endless systemd[3868]: dev-zram0.swap: Succeeded. mai 23 13:45:32 endless systemd[1]: dev-zram0.swap: Succeeded. mai 23 13:45:32 endless systemd[1]: Deactivated swap /dev/zram0. mai 23 13:45:32 endless systemd[3868]: obex.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped Bluetooth OBEX service. mai 23 13:45:32 endless systemd[1]: var-roothome-.cache-gvfs.mount: Succeeded. mai 23 13:45:32 endless systemd[3868]: var-roothome-.cache-gvfs.mount: Succeeded. mai 23 13:45:32 endless systemd[1]: Unmounted /var/roothome/.cache/gvfs. mai 23 13:45:32 endless systemd[3868]: run-user-1001-gvfs.mount: Succeeded. mai 23 13:45:32 endless systemd[1]: run-user-1001-gvfs.mount: Succeeded. mai 23 13:45:32 endless systemd[1]: Unmounted /run/user/1001/gvfs. mai 23 13:45:32 endless kernel: zram0: detected capacity change from 12326830080 to 0 mai 23 13:45:32 endless systemd[1]: eos-enable-zram.service: Succeeded. mai 23 13:45:32 endless systemd[1]: Stopped swap with zram. mai 23 13:45:32 endless systemd[3868]: gvfs-daemon.service: Succeeded. mai 23 13:45:32 endless systemd[3868]: Stopped Virtual filesystem service. mai 23 13:45:32 endless evolution-alarm[8868]: evolution-alarm-notify: Fatal IO error 11 (Recurso temporariamente indisponível) on X server :0. mai 23 13:45:32 endless thermald[2940]: [WARN]terminating on user request .. mai 23 13:45:33 endless systemd[3868]: evolution-addressbook-factory.service: Succeeded. mai 23 13:45:33 endless systemd[3868]: Stopped Evolution address book service. mai 23 13:45:33 endless systemd[3868]: evolution-calendar-factory.service: Succeeded. mai 23 13:45:33 endless systemd[3868]: Stopped Evolution calendar service. mai 23 13:45:33 endless systemd[1]: ModemManager.service: Succeeded. mai 23 13:45:33 endless systemd[1]: Stopped Modem Manager. mai 23 13:45:33 endless systemd[1]: cups-browsed.service: Succeeded. mai 23 13:45:33 endless systemd[1]: Stopped Make remote CUPS printers available locally. mai 23 13:45:33 endless systemd[1]: Stopping Avahi mDNS/DNS-SD Stack... mai 23 13:45:33 endless systemd[1]: Stopping CUPS Scheduler... mai 23 13:45:33 endless eos-metrics-eve[2808]: Flushed 3 events to persistent cache. mai 23 13:45:33 endless avahi-daemon[2791]: Got SIGTERM, quitting. mai 23 13:45:33 endless systemd[1]: avahi-daemon.service: Succeeded. mai 23 13:45:33 endless avahi-daemon[2791]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address 2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e. mai 23 13:45:33 endless systemd[1]: Stopped Avahi mDNS/DNS-SD Stack. mai 23 13:45:33 endless avahi-daemon[2791]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.0.34. mai 23 13:45:33 endless avahi-daemon[2791]: avahi-daemon 0.7 exiting. mai 23 13:45:33 endless systemd[3868]: gsd-smartcard.service: Succeeded. mai 23 13:45:33 endless systemd[3868]: Stopped GNOME Smartcard handling. mai 23 13:45:33 endless tracker-miner-fs[9193]: Received signal:15->'Terminado' mai 23 13:45:33 endless tracker-miner-f[9193]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts mai 23 13:45:33 endless tracker-miner-f[9193]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts mai 23 13:45:33 endless tracker-miner-f[9193]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts mai 23 13:45:33 endless tracker-miner-f[9193]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts mai 23 13:45:33 endless tracker-miner-f[9193]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts mai 23 13:45:33 endless tracker-miner-f[9193]: Error while sending AddMatch() message: A conexão está fechada mai 23 13:45:33 endless tracker-miner-f[9193]: Error while sending AddMatch() message: A conexão está fechada mai 23 13:45:33 endless tracker-miner-f[9193]: Error while sending AddMatch() message: A conexão está fechada mai 23 13:45:33 endless systemd[1]: systemd-random-seed.service: Succeeded. mai 23 13:45:33 endless systemd[1]: Stopped Load/Save Random Seed. mai 23 13:45:33 endless ubuntu-appindicators@ubuntu.com[8439]: Failed to acquire org.kde.StatusNotifierWatcher mai 23 13:45:33 endless gnome-shell[8439]: gnome-shell: Fatal IO error 0 (Sucesso) on X server :0. mai 23 13:45:33 endless gdm-Xorg-:0[7519]: (II) UnloadModule: "libinput" mai 23 13:45:33 endless udisksd[2941]: udisks daemon version 2.8.4 exiting mai 23 13:45:33 endless systemd[1]: udisks2.service: Succeeded. mai 23 13:45:33 endless systemd[1]: Stopped Disk Manager. mai 23 13:45:33 endless gdm-Xorg-:0[7519]: (II) Server terminated successfully (0). Closing log file. mai 23 13:45:33 endless systemd[3868]: gsd-housekeeping.service: Succeeded. mai 23 13:45:33 endless systemd[3868]: Stopped GNOME Maintenance of expirable data. mai 23 13:45:33 endless systemd[3868]: Stopped target GNOME Session is initialized. mai 23 13:45:33 endless systemd[3868]: Stopped target GNOME Shell on X11. mai 23 13:45:33 endless dbus-daemon[2800]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' requested by ':1.32' (uid=0 pid=3845 comm="/usr/sbin/gdm " label="unconfined") mai 23 13:45:33 endless dbus-daemon[2800]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.login1.service': Refusing activation, D-Bus is shutting down. mai 23 13:45:33 endless gdm[3845]: GdmLocalDisplayFactory: Failed to issue method call: GDBus.Error:org.freedesktop.systemd1.ShuttingDown: Refusing activation, D-Bus is shutting down. mai 23 13:45:33 endless gdm[3845]: Freeing conversation 'gdm-password' with active job mai 23 13:45:33 endless systemd[1]: eos-metrics-event-recorder.service: Succeeded. mai 23 13:45:35 endless tracker-miner-fs[9193]: OK mai 23 13:45:33 endless systemd[1]: Stopped EndlessOS Metrics Event Recorder Server. mai 23 13:45:33 endless systemd[1]: gdm.service: Succeeded. mai 23 13:45:33 endless systemd[1]: Stopped GNOME Display Manager. mai 23 13:45:33 endless systemd[1]: nvidia-graphics.service: Succeeded. mai 23 13:45:33 endless systemd[1]: Stopped Nvidia graphics management. mai 23 13:45:33 endless systemd[1]: Starting Show Plymouth Reboot Screen... mai 23 13:45:33 endless systemd[1]: thermald.service: Succeeded. mai 23 13:45:33 endless systemd[1]: Stopped Thermal Daemon Service. mai 23 13:45:34 endless systemd[1]: cups.service: Succeeded. mai 23 13:45:34 endless systemd[1]: Stopped CUPS Scheduler. mai 23 13:45:34 endless systemd[3868]: tracker-miner-fs.service: Succeeded. mai 23 13:45:34 endless systemd[3868]: Stopped Tracker file system data miner. mai 23 13:45:34 endless systemd[1]: Received SIGRTMIN+20 from PID 22530 (plymouthd). mai 23 13:45:35 endless systemd[1]: Started Show Plymouth Reboot Screen. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: State 'stop-sigterm' timed out. Killing. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17134 (chrome) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 22026 (ThreadPoolSingl) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17163 (Chrome_IOThread) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17165 (inotify_reader) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17166 (MemoryInfra) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17168 (gdbus) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17170 (CrShutdownDetec) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17171 (dconf worker) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17174 (CompositorTileW) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17175 (VideoCaptureThr) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17176 (BrowserWatchdog) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17177 (ThreadPoolSingl) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17178 (CacheThread_Blo) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17179 (gpu-process_cra) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17181 (ThreadPoolSingl) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17182 (utility_crash_u) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17212 (renderer_crash_) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17259 (extension_crash) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17279 (BatteryStatusNo) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17432 (Chrome_SyncThre) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17569 (LevelDBEnv.IDB) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 17661 (LevelDBEnv) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 20674 (ThreadPoolForeg) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 21725 (ThreadPoolForeg) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 21832 (Shutdown watchd) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Killing process 21843 (ThreadPoolForeg) with signal SIGKILL. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Failed with result 'timeout'. mai 23 13:45:38 endless systemd[3868]: Stopped GNOME Shell on X11. mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Triggering OnFailure= dependencies. mai 23 13:45:38 endless systemd[3868]: Requested transaction contradicts existing jobs: Transaction for gnome-session-failed.target/start is destructive (timers.target has 'stop' job queued, but 'start' is included in transaction). mai 23 13:45:38 endless systemd[3868]: gnome-shell-x11.service: Failed to enqueue OnFailure= job, ignoring: Transaction for gnome-session-failed.target/start is destructive (timers.target has 'stop' job queued, but 'start' is included in transaction). mai 23 13:45:38 endless systemd[3868]: Stopped target GNOME Session Manager is ready. mai 23 13:45:38 endless systemd[3868]: Stopped target Tasks to be run before GNOME Session starts. mai 23 13:45:38 endless systemd[3868]: Stopped target Session services which should run early before the graphical session is brought up. mai 23 13:45:38 endless systemd[3868]: Stopped target Basic System. mai 23 13:45:38 endless systemd[3868]: Reached target Shutdown running GNOME Session. mai 23 13:45:38 endless systemd[3868]: Stopped target Paths. mai 23 13:45:38 endless systemd[3868]: Stopped target Sockets. mai 23 13:45:38 endless systemd[3868]: Stopped target Timers. mai 23 13:45:38 endless systemd[3868]: dbus.socket: Succeeded. mai 23 13:45:38 endless systemd[3868]: Closed D-Bus User Message Bus Socket. mai 23 13:45:38 endless systemd[3868]: dirmngr.socket: Succeeded. mai 23 13:45:38 endless systemd[3868]: Closed GnuPG network certificate management daemon. mai 23 13:45:38 endless systemd[3868]: gpg-agent-browser.socket: Succeeded. mai 23 13:45:38 endless systemd[3868]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers). mai 23 13:45:38 endless systemd[3868]: gpg-agent-extra.socket: Succeeded. mai 23 13:45:38 endless systemd[3868]: Closed GnuPG cryptographic agent and passphrase cache (restricted). mai 23 13:45:38 endless systemd[3868]: gpg-agent-ssh.socket: Succeeded. mai 23 13:45:38 endless systemd[3868]: Closed GnuPG cryptographic agent (ssh-agent emulation). mai 23 13:45:38 endless systemd[3868]: gpg-agent.socket: Succeeded. mai 23 13:45:38 endless systemd[3868]: Closed GnuPG cryptographic agent and passphrase cache. mai 23 13:45:38 endless systemd[3868]: pulseaudio.socket: Succeeded. mai 23 13:45:38 endless systemd[3868]: Closed Sound System. mai 23 13:45:38 endless systemd[3868]: Reached target Shutdown. mai 23 13:45:38 endless systemd[3868]: Starting Restart DBus after GNOME Session shutdown... mai 23 13:45:38 endless systemd[3868]: Condition check resulted in Disable GNOME Shell extensions after failure being skipped. mai 23 13:45:38 endless systemd[3868]: systemd-exit.service: Succeeded. mai 23 13:45:38 endless systemd[3868]: Started Exit the Session. mai 23 13:45:38 endless systemd[3868]: Reached target Exit the Session. mai 23 13:45:38 endless gnome-session-c[22552]: Couldn't connect to session bus: Não foi possível conectar: Conexão recusada mai 23 13:45:38 endless systemd[1]: user@1001.service: Killing process 22552 (gnome-session-c) with signal SIGKILL. mai 23 13:45:38 endless systemd[1]: user@1001.service: Succeeded. mai 23 13:45:38 endless systemd[1]: Stopped User Manager for UID 1001. mai 23 13:45:38 endless systemd[1]: Stopping User Runtime Directory /run/user/1001... mai 23 13:45:38 endless systemd[1]: run-user-1001.mount: Succeeded. mai 23 13:45:38 endless systemd[1]: Unmounted /run/user/1001. mai 23 13:45:38 endless systemd[1]: user-runtime-dir@1001.service: Succeeded. mai 23 13:45:38 endless systemd[1]: Stopped User Runtime Directory /run/user/1001. mai 23 13:45:38 endless systemd[1]: Removed slice User Slice of UID 1001. mai 23 13:45:38 endless systemd[1]: Stopping Permit User Sessions... mai 23 13:45:38 endless systemd[1]: systemd-user-sessions.service: Succeeded. mai 23 13:45:38 endless systemd[1]: Stopped Permit User Sessions. mai 23 13:45:38 endless systemd[1]: Stopped target Network. mai 23 13:45:38 endless systemd[1]: Stopped target User and Group Name Lookups. mai 23 13:45:38 endless systemd[1]: Stopped target Remote File Systems. mai 23 13:45:38 endless systemd[1]: Stopping Network Manager... mai 23 13:45:38 endless systemd[1]: Stopping WPA supplicant... mai 23 13:45:38 endless wpa_supplicant[3353]: nl80211: Failed to open /proc/sys/net/ipv4/conf/p2p-dev-wlp2s0/drop_unicast_in_l2_multicast: No such file or directory mai 23 13:45:38 endless wpa_supplicant[3353]: nl80211: Failed to set IPv4 unicast in multicast filter mai 23 13:45:38 endless NetworkManager[2802]: [1590252338.9432] caught SIGTERM, shutting down normally. mai 23 13:45:38 endless wpa_supplicant[3353]: nl80211: Failed to open /proc/sys/net/ipv4/conf/p2p-dev-wlp2s0/drop_unicast_in_l2_multicast: No such file or directory mai 23 13:45:38 endless wpa_supplicant[3353]: nl80211: Failed to set IPv4 unicast in multicast filter mai 23 13:45:38 endless wpa_supplicant[3353]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 mai 23 13:45:38 endless NetworkManager[2802]: [1590252338.9772] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP client pid 21197 mai 23 13:45:38 endless NetworkManager[2802]: [1590252338.9772] dhcp4 (wlp2s0): state changed bound -> done mai 23 13:45:38 endless NetworkManager[2802]: [1590252338.9773] device (wlp2s0): DHCPv4: 480 seconds grace period started mai 23 13:45:38 endless NetworkManager[2802]: [1590252338.9783] dhcp6 (wlp2s0): canceled DHCP transaction, DHCP client pid 21215 mai 23 13:45:38 endless NetworkManager[2802]: [1590252338.9783] dhcp6 (wlp2s0): state changed bound -> done mai 23 13:45:38 endless NetworkManager[2802]: [1590252338.9784] device (wlp2s0): DHCPv6: 480 seconds grace period started mai 23 13:45:39 endless wpa_supplicant[3353]: p2p-dev-wlp2s0: CTRL-EVENT-TERMINATING mai 23 13:45:39 endless kernel: wlp2s0: deauthenticating from 80:d0:4a:90:f1:d9 by local choice (Reason: 3=DEAUTH_LEAVING) mai 23 13:45:39 endless NetworkManager[2802]: [1590252339.0456] exiting (success) mai 23 13:45:39 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=80:d0:4a:90:f1:d9 reason=3 locally_generated=1 mai 23 13:45:39 endless wpa_supplicant[3353]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/7 mai 23 13:45:39 endless systemd[1]: NetworkManager.service: Succeeded. mai 23 13:45:39 endless systemd[1]: Stopped Network Manager. mai 23 13:45:39 endless wpa_supplicant[3353]: nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0 mai 23 13:45:39 endless wpa_supplicant[3353]: wlp2s0: CTRL-EVENT-TERMINATING mai 23 13:45:39 endless systemd[1]: wpa_supplicant.service: Succeeded. mai 23 13:45:39 endless systemd[1]: Stopped WPA supplicant. mai 23 13:45:39 endless systemd[1]: Stopping D-Bus System Message Bus... mai 23 13:45:39 endless systemd[1]: dbus.service: Succeeded. mai 23 13:45:39 endless systemd[1]: Stopped D-Bus System Message Bus. mai 23 13:45:39 endless systemd[1]: Stopped target Basic System. mai 23 13:45:39 endless systemd[1]: systemd-ask-password-plymouth.path: Succeeded. mai 23 13:45:39 endless systemd[1]: Stopped Forward Password Requests to Plymouth Directory Watch. mai 23 13:45:39 endless systemd[1]: Stopped target Paths. mai 23 13:45:39 endless systemd[1]: cups.path: Succeeded. mai 23 13:45:39 endless systemd[1]: Stopped CUPS Scheduler. mai 23 13:45:39 endless systemd[1]: eos-phone-home.path: Succeeded. mai 23 13:45:39 endless systemd[1]: Stopped Send system activation/daily ping messages to Endless. mai 23 13:45:39 endless systemd[1]: ostree-finalize-staged.path: Succeeded. mai 23 13:45:39 endless systemd[1]: Stopped OSTree Monitor Staged Deployment. mai 23 13:45:39 endless systemd[1]: Stopped target Slices. mai 23 13:45:39 endless systemd[1]: Removed slice User and Session Slice. mai 23 13:45:39 endless systemd[1]: Stopped target Sockets. mai 23 13:45:39 endless systemd[1]: avahi-daemon.socket: Succeeded. mai 23 13:45:39 endless systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket. mai 23 13:45:39 endless systemd[1]: cups.socket: Succeeded. mai 23 13:45:39 endless systemd[1]: Closed CUPS Scheduler. mai 23 13:45:39 endless systemd[1]: dbus.socket: Succeeded. mai 23 13:45:39 endless systemd[1]: Closed D-Bus System Message Bus Socket. mai 23 13:45:39 endless systemd[1]: eos-kalite-system-helper.socket: Succeeded. mai 23 13:45:39 endless systemd[1]: Closed KA Lite Server. mai 23 13:45:39 endless systemd[1]: eos-license-service.socket: Succeeded. mai 23 13:45:39 endless systemd[1]: Closed EndlessOS License Service Socket. mai 23 13:45:39 endless systemd[1]: uuidd.socket: Succeeded. mai 23 13:45:39 endless systemd[1]: Closed UUID daemon activation socket. mai 23 13:45:39 endless systemd[1]: Stopped target System Initialization. mai 23 13:45:39 endless systemd[1]: Stopped target Local Encrypted Volumes. mai 23 13:45:39 endless systemd[1]: systemd-ask-password-wall.path: Succeeded. mai 23 13:45:39 endless systemd[1]: Stopped Forward Password Requests to Wall Directory Watch. mai 23 13:45:39 endless systemd[1]: eos-codecs-activate.service: Succeeded. mai 23 13:45:39 endless systemd[1]: Stopped Helper script to deal with extra codecs. mai 23 13:45:39 endless systemd[1]: Stopping Load/Save Screen Backlight Brightness of backlight:intel_backlight... mai 23 13:45:39 endless systemd[1]: systemd-sysctl.service: Succeeded. mai 23 13:45:39 endless systemd[1]: Stopped Apply Kernel Variables. mai 23 13:45:39 endless systemd[1]: systemd-modules-load.service: Succeeded. mai 23 13:45:39 endless systemd[1]: Stopped Load Kernel Modules. mai 23 13:45:39 endless systemd[1]: Stopping Update UTMP about System Boot/Shutdown... mai 23 13:45:39 endless systemd[1]: systemd-update-utmp.service: Succeeded. mai 23 13:45:39 endless systemd[1]: Stopped Update UTMP about System Boot/Shutdown. mai 23 13:45:39 endless systemd[1]: systemd-tmpfiles-setup.service: Succeeded. mai 23 13:45:39 endless systemd[1]: Stopped Create Volatile Files and Directories. mai 23 13:45:39 endless systemd[1]: Stopped target Local File Systems. mai 23 13:45:39 endless systemd[1]: Unmounting /boot... mai 23 13:45:39 endless systemd[1]: Unmounting Temporary Directory (/tmp)... mai 23 13:45:39 endless systemd[1]: Stopping Flush Journal to Persistent Storage... mai 23 13:45:39 endless systemd[1]: systemd-backlight@backlight:intel_backlight.service: Succeeded. mai 23 13:45:39 endless systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:intel_backlight. mai 23 13:45:39 endless systemd[1]: Removed slice system-systemd\x2dbacklight.slice. mai 23 13:45:39 endless systemd[1]: systemd-readahead-collect.service: Succeeded. mai 23 13:45:39 endless systemd[1]: Stopped Collect Read-Ahead Data. mai 23 13:45:39 endless systemd[1]: systemd-readahead-replay.service: Succeeded. mai 23 13:45:39 endless systemd[1]: Stopped Replay Read-Ahead Data. -- Logs begin at Sat 2020-05-23 04:36:13 -03, end at Sat 2020-05-23 14:17:06 -03. -- mai 23 13:45:50 localhost kernel: microcode: microcode updated early to revision 0xca, date = 2019-09-26 mai 23 13:45:50 localhost kernel: Linux version 5.4.0-19-generic (abuild@ip-10-16-35-10) (gcc version 8.3.0 (Debian 8.3.0-6endless1bem1)) #23+dev177.1a56fd1beos3.8.2 SMP Tue May 5 22:42:53 UTC 2020 (Ubuntu 5.4.0-19.23+dev177.1a56fd1beos3.8.2-generic 5.4.27) mai 23 13:45:50 localhost kernel: Command line: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-94c993d319cdf01ff15a7624dd6855cc9ebe14d7b40f3077a1e965a0de360d8e/vmlinuz-5.4.0-19-generic root=UUID=05c7cd5b-40f9-47d7-a032-e98150535435 rw splash plymouth.ignore-serial-consoles quiet loglevel=2 ostree=/ostree/boot.1/eos/94c993d319cdf01ff15a7624dd6855cc9ebe14d7b40f3077a1e965a0de360d8e/0 mai 23 13:45:50 localhost kernel: KERNEL supported cpus: mai 23 13:45:50 localhost kernel: Intel GenuineIntel mai 23 13:45:50 localhost kernel: AMD AuthenticAMD mai 23 13:45:50 localhost kernel: Hygon HygonGenuine mai 23 13:45:50 localhost kernel: Centaur CentaurHauls mai 23 13:45:50 localhost kernel: zhaoxin Shanghai mai 23 13:45:50 localhost kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' mai 23 13:45:50 localhost kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' mai 23 13:45:50 localhost kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' mai 23 13:45:50 localhost kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' mai 23 13:45:50 localhost kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' mai 23 13:45:50 localhost kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 mai 23 13:45:50 localhost kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 mai 23 13:45:50 localhost kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 mai 23 13:45:50 localhost kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. mai 23 13:45:50 localhost kernel: BIOS-provided physical RAM map: mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000071569fff] usable mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x000000007156a000-0x000000007156afff] ACPI NVS mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x000000007156b000-0x000000007156bfff] reserved mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x000000007156c000-0x00000000731e7fff] usable mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x00000000731e8000-0x0000000073ae7fff] reserved mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x0000000073ae8000-0x0000000089cfdfff] usable mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x0000000089cfe000-0x000000008a88dfff] reserved mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x000000008a88e000-0x000000008af7dfff] ACPI NVS mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x000000008af7e000-0x000000008affdfff] ACPI data mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x000000008affe000-0x000000008affefff] usable mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x000000008afff000-0x000000008fffffff] reserved mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved mai 23 13:45:50 localhost kernel: BIOS-e820: [mem 0x0000000100000000-0x000000026effffff] usable mai 23 13:45:50 localhost kernel: NX (Execute Disable) protection: active mai 23 13:45:50 localhost kernel: e820: update [mem 0x706e4018-0x706f4057] usable ==> usable mai 23 13:45:50 localhost kernel: e820: update [mem 0x706e4018-0x706f4057] usable ==> usable mai 23 13:45:50 localhost kernel: extended physical RAM map: mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x0000000000000000-0x0000000000057fff] usable mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x0000000000058000-0x0000000000058fff] reserved mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x0000000000059000-0x000000000009dfff] usable mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x000000000009e000-0x00000000000fffff] reserved mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x0000000000100000-0x00000000706e4017] usable mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x00000000706e4018-0x00000000706f4057] usable mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x00000000706f4058-0x0000000071569fff] usable mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x000000007156a000-0x000000007156afff] ACPI NVS mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x000000007156b000-0x000000007156bfff] reserved mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x000000007156c000-0x00000000731e7fff] usable mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x00000000731e8000-0x0000000073ae7fff] reserved mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x0000000073ae8000-0x0000000089cfdfff] usable mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x0000000089cfe000-0x000000008a88dfff] reserved mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x000000008a88e000-0x000000008af7dfff] ACPI NVS mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x000000008af7e000-0x000000008affdfff] ACPI data mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x000000008affe000-0x000000008affefff] usable mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x000000008afff000-0x000000008fffffff] reserved mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x00000000e0000000-0x00000000efffffff] reserved mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed00fff] reserved mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x00000000fed10000-0x00000000fed19fff] reserved mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x00000000fed84000-0x00000000fed84fff] reserved mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved mai 23 13:45:50 localhost kernel: reserve setup_data: [mem 0x0000000100000000-0x000000026effffff] usable mai 23 13:45:50 localhost kernel: efi: EFI v2.50 by INSYDE Corp. mai 23 13:45:50 localhost kernel: efi: ACPI 2.0=0x8affd014 SMBIOS=0x8a099000 SMBIOS 3.0=0x8a097000 ESRT=0x8a0950d8 MEMATTR=0x7a5e5018 TPMEventLog=0x706f5018 mai 23 13:45:50 localhost kernel: secureboot: Secure boot enabled mai 23 13:45:50 localhost kernel: Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: SMBIOS 3.0.0 present. mai 23 13:45:50 localhost kernel: DMI: Acer Aspire A515-51/Charmander_KL, BIOS V2.02 01/03/2019 mai 23 13:45:50 localhost kernel: tsc: Detected 2900.000 MHz processor mai 23 13:45:50 localhost kernel: tsc: Detected 2899.886 MHz TSC mai 23 13:45:50 localhost kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved mai 23 13:45:50 localhost kernel: e820: remove [mem 0x000a0000-0x000fffff] usable mai 23 13:45:50 localhost kernel: last_pfn = 0x26f000 max_arch_pfn = 0x400000000 mai 23 13:45:50 localhost kernel: MTRR default type: write-back mai 23 13:45:50 localhost kernel: MTRR fixed ranges enabled: mai 23 13:45:50 localhost kernel: 00000-9FFFF write-back mai 23 13:45:50 localhost kernel: A0000-BFFFF uncachable mai 23 13:45:50 localhost kernel: C0000-FFFFF write-protect mai 23 13:45:50 localhost kernel: MTRR variable ranges enabled: mai 23 13:45:50 localhost kernel: 0 base 00C0000000 mask 7FC0000000 uncachable mai 23 13:45:50 localhost kernel: 1 base 00A0000000 mask 7FE0000000 uncachable mai 23 13:45:50 localhost kernel: 2 base 0090000000 mask 7FF0000000 uncachable mai 23 13:45:50 localhost kernel: 3 base 008C000000 mask 7FFC000000 uncachable mai 23 13:45:50 localhost kernel: 4 base 008B800000 mask 7FFF800000 uncachable mai 23 13:45:50 localhost kernel: 5 disabled mai 23 13:45:50 localhost kernel: 6 disabled mai 23 13:45:50 localhost kernel: 7 disabled mai 23 13:45:50 localhost kernel: 8 disabled mai 23 13:45:50 localhost kernel: 9 disabled mai 23 13:45:50 localhost kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT mai 23 13:45:50 localhost kernel: last_pfn = 0x8afff max_arch_pfn = 0x400000000 mai 23 13:45:50 localhost kernel: esrt: Reserving ESRT space from 0x000000008a0950d8 to 0x000000008a095110. mai 23 13:45:50 localhost kernel: check: Scanning 1 areas for low memory corruption mai 23 13:45:50 localhost kernel: Using GB pages for direct mapping mai 23 13:45:50 localhost kernel: BRK [0x211c01000, 0x211c01fff] PGTABLE mai 23 13:45:50 localhost kernel: BRK [0x211c02000, 0x211c02fff] PGTABLE mai 23 13:45:50 localhost kernel: BRK [0x211c03000, 0x211c03fff] PGTABLE mai 23 13:45:50 localhost kernel: BRK [0x211c04000, 0x211c04fff] PGTABLE mai 23 13:45:50 localhost kernel: BRK [0x211c05000, 0x211c05fff] PGTABLE mai 23 13:45:50 localhost kernel: BRK [0x211c06000, 0x211c06fff] PGTABLE mai 23 13:45:50 localhost kernel: BRK [0x211c07000, 0x211c07fff] PGTABLE mai 23 13:45:50 localhost kernel: BRK [0x211c08000, 0x211c08fff] PGTABLE mai 23 13:45:50 localhost kernel: BRK [0x211c09000, 0x211c09fff] PGTABLE mai 23 13:45:50 localhost kernel: BRK [0x211c0a000, 0x211c0afff] PGTABLE mai 23 13:45:50 localhost kernel: BRK [0x211c0b000, 0x211c0bfff] PGTABLE mai 23 13:45:50 localhost kernel: BRK [0x211c0c000, 0x211c0cfff] PGTABLE mai 23 13:45:50 localhost kernel: secureboot: Secure boot enabled mai 23 13:45:50 localhost kernel: RAMDISK: [mem 0x3d29a000-0x3fffafff] mai 23 13:45:50 localhost kernel: ACPI: Early table checksum verification disabled mai 23 13:45:50 localhost kernel: ACPI: RSDP 0x000000008AFFD014 000024 (v02 ACRSYS) mai 23 13:45:50 localhost kernel: ACPI: XSDT 0x000000008AFBD188 00011C (v01 ACRSYS ACRPRDCT 00000000 01000013) mai 23 13:45:50 localhost kernel: ACPI: FACP 0x000000008AFE8000 00010C (v05 ACRSYS ACRPRDCT 00000000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: DSDT 0x000000008AFC2000 02159F (v02 ACRSYS ACRPRDCT 00000000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: FACS 0x000000008AF59000 000040 mai 23 13:45:50 localhost kernel: ACPI: UEFI 0x000000008AFFB000 000042 (v01 ACRSYS ACRPRDCT 00000002 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: SSDT 0x000000008AFF3000 0004C3 (v02 ACRSYS ACRPRDCT 00001000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: TPM2 0x000000008AFF1000 000034 (v03 ACRSYS ACRPRDCT 00000000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: ASF! 0x000000008AFEC000 0000A5 (v32 ACRSYS ACRPRDCT 00000001 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: BOOT 0x000000008AFEA000 000028 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: HPET 0x000000008AFE7000 000038 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: MCFG 0x000000008AFE5000 00003C (v01 ACRSYS ACRPRDCT 00000001 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: SSDT 0x000000008AFC0000 000F6B (v02 ACRSYS ACRPRDCT 00001000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: WSMT 0x000000008AFBE000 000028 (v01 ACRSYS ACRPRDCT 00000000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: SSDT 0x000000008AFBB000 000346 (v01 ACRSYS ACRPRDCT 00000000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: SSDT 0x000000008AFB6000 00051E (v02 ACRSYS ACRPRDCT 00001000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: DBG2 0x000000008AFB4000 000054 (v00 ACRSYS ACRPRDCT 00000002 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: DMAR 0x000000008AFE4000 0000F0 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: SSDT 0x000000008AFF5000 0058C1 (v01 ACRSYS ACRPRDCT 00001000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: SSDT 0x000000008AFED000 00312B (v02 ACRSYS ACRPRDCT 00003000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: DBGP 0x000000008AFE9000 000034 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: SSDT 0x000000008AFC1000 000517 (v02 ACRSYS ACRPRDCT 00000000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: SSDT 0x000000008AFBC000 00029F (v02 ACRSYS ACRPRDCT 00000000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: DBGP 0x000000008AFB5000 000034 (v01 ACRSYS ACRPRDCT 00000002 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: SSDT 0x000000008AFB0000 0017AE (v02 ACRSYS ACRPRDCT 00003000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: FPDT 0x000000008AFAE000 000044 (v01 ACRSYS ACRPRDCT 00000002 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: SSDT 0x000000008AFF2000 000046 (v02 ACRSYS ACRPRDCT 00003000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: APIC 0x000000008AFE6000 00012C (v03 ACRSYS ACRPRDCT 00000001 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: SSDT 0x000000008AFB7000 003002 (v02 ACRSYS ACRPRDCT 00001000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: NHLT 0x000000008AFAF000 00002D (v00 ACRSYS ACRPRDCT 00000002 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: ASPT 0x000000008AFEB000 000034 (v07 ACRSYS ACRPRDCT 00000001 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: SSDT 0x000000008AFB2000 0012E6 (v02 ACRSYS ACRPRDCT 00001000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: LPIT 0x000000008AFBF000 000094 (v01 ACRSYS ACRPRDCT 00000000 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: UEFI 0x000000008AFFC000 000236 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: BGRT 0x000000008AFAD000 000038 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000) mai 23 13:45:50 localhost kernel: ACPI: Local APIC address 0xfee00000 mai 23 13:45:50 localhost kernel: No NUMA configuration found mai 23 13:45:50 localhost kernel: Faking a node at [mem 0x0000000000000000-0x000000026effffff] mai 23 13:45:50 localhost kernel: NODE_DATA(0) allocated [mem 0x26efd5000-0x26effffff] mai 23 13:45:50 localhost kernel: Zone ranges: mai 23 13:45:50 localhost kernel: DMA [mem 0x0000000000001000-0x0000000000ffffff] mai 23 13:45:50 localhost kernel: DMA32 [mem 0x0000000001000000-0x00000000ffffffff] mai 23 13:45:50 localhost kernel: Normal [mem 0x0000000100000000-0x000000026effffff] mai 23 13:45:50 localhost kernel: Device empty mai 23 13:45:50 localhost kernel: Movable zone start for each node mai 23 13:45:50 localhost kernel: Early memory node ranges mai 23 13:45:50 localhost kernel: node 0: [mem 0x0000000000001000-0x0000000000057fff] mai 23 13:45:50 localhost kernel: node 0: [mem 0x0000000000059000-0x000000000009dfff] mai 23 13:45:50 localhost kernel: node 0: [mem 0x0000000000100000-0x0000000071569fff] mai 23 13:45:50 localhost kernel: node 0: [mem 0x000000007156c000-0x00000000731e7fff] mai 23 13:45:50 localhost kernel: node 0: [mem 0x0000000073ae8000-0x0000000089cfdfff] mai 23 13:45:50 localhost kernel: node 0: [mem 0x000000008affe000-0x000000008affefff] mai 23 13:45:50 localhost kernel: node 0: [mem 0x0000000100000000-0x000000026effffff] mai 23 13:45:50 localhost kernel: Zeroed struct page in unavailable ranges: 31847 pages mai 23 13:45:50 localhost kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000026effffff] mai 23 13:45:50 localhost kernel: On node 0 totalpages: 2065305 mai 23 13:45:50 localhost kernel: DMA zone: 64 pages used for memmap mai 23 13:45:50 localhost kernel: DMA zone: 21 pages reserved mai 23 13:45:50 localhost kernel: DMA zone: 3996 pages, LIFO batch:0 mai 23 13:45:50 localhost kernel: DMA32 zone: 8720 pages used for memmap mai 23 13:45:50 localhost kernel: DMA32 zone: 558077 pages, LIFO batch:63 mai 23 13:45:50 localhost kernel: Normal zone: 23488 pages used for memmap mai 23 13:45:50 localhost kernel: Normal zone: 1503232 pages, LIFO batch:63 mai 23 13:45:50 localhost kernel: tboot: non-0 tboot_addr but it is not of type E820_TYPE_RESERVED mai 23 13:45:50 localhost kernel: Reserving Intel graphics memory at [mem 0x8c000000-0x8fffffff] mai 23 13:45:50 localhost kernel: ACPI: PM-Timer IO Port: 0x1808 mai 23 13:45:50 localhost kernel: ACPI: Local APIC address 0xfee00000 mai 23 13:45:50 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) mai 23 13:45:50 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) mai 23 13:45:50 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) mai 23 13:45:50 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) mai 23 13:45:50 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) mai 23 13:45:50 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) mai 23 13:45:50 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) mai 23 13:45:50 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) mai 23 13:45:50 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1]) mai 23 13:45:50 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1]) mai 23 13:45:50 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1]) mai 23 13:45:50 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1]) mai 23 13:45:50 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1]) mai 23 13:45:50 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1]) mai 23 13:45:50 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1]) mai 23 13:45:50 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1]) mai 23 13:45:50 localhost kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119 mai 23 13:45:50 localhost kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) mai 23 13:45:50 localhost kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) mai 23 13:45:50 localhost kernel: ACPI: IRQ0 used by override. mai 23 13:45:50 localhost kernel: ACPI: IRQ9 used by override. mai 23 13:45:50 localhost kernel: Using ACPI (MADT) for SMP configuration information mai 23 13:45:50 localhost kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000 mai 23 13:45:50 localhost kernel: e820: update [mem 0x7a55c000-0x7a5d6fff] usable ==> reserved mai 23 13:45:50 localhost kernel: smpboot: Allowing 4 CPUs, 0 hotplug CPUs mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0x00058000-0x00058fff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0x0009e000-0x000fffff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0x706e4000-0x706e4fff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0x706f4000-0x706f4fff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0x7156a000-0x7156afff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0x7156b000-0x7156bfff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0x731e8000-0x73ae7fff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0x7a55c000-0x7a5d6fff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0x89cfe000-0x8a88dfff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0x8a88e000-0x8af7dfff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0x8af7e000-0x8affdfff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0x8afff000-0x8fffffff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0x90000000-0xdfffffff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0xe0000000-0xefffffff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0xf0000000-0xfcffffff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0xfd000000-0xfe7fffff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0xfe800000-0xfebfffff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed00fff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0xfed01000-0xfed0ffff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0xfed10000-0xfed19fff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0xfed1a000-0xfed83fff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0xfed84000-0xfed84fff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0xfed85000-0xfedfffff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0xfee01000-0xff9fffff] mai 23 13:45:50 localhost kernel: PM: Registered nosave memory: [mem 0xffa00000-0xffffffff] mai 23 13:45:50 localhost kernel: [mem 0x90000000-0xdfffffff] available for PCI devices mai 23 13:45:50 localhost kernel: Booting paravirtualized kernel on bare hardware mai 23 13:45:50 localhost kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns mai 23 13:45:50 localhost kernel: setup_percpu: NR_CPUS:8192 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1 mai 23 13:45:50 localhost kernel: percpu: Embedded 54 pages/cpu s184320 r8192 d28672 u524288 mai 23 13:45:50 localhost kernel: pcpu-alloc: s184320 r8192 d28672 u524288 alloc=1*2097152 mai 23 13:45:50 localhost kernel: pcpu-alloc: [0] 0 1 2 3 mai 23 13:45:50 localhost kernel: Built 1 zonelists, mobility grouping on. Total pages: 2033012 mai 23 13:45:50 localhost kernel: Policy zone: Normal mai 23 13:45:50 localhost kernel: Kernel command line: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-94c993d319cdf01ff15a7624dd6855cc9ebe14d7b40f3077a1e965a0de360d8e/vmlinuz-5.4.0-19-generic root=UUID=05c7cd5b-40f9-47d7-a032-e98150535435 rw splash plymouth.ignore-serial-consoles quiet loglevel=2 ostree=/ostree/boot.1/eos/94c993d319cdf01ff15a7624dd6855cc9ebe14d7b40f3077a1e965a0de360d8e/0 mai 23 13:45:50 localhost kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) mai 23 13:45:50 localhost kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) mai 23 13:45:50 localhost kernel: mem auto-init: stack:off, heap alloc:on, heap free:off mai 23 13:45:50 localhost kernel: Calgary: detecting Calgary via BIOS EBDA area mai 23 13:45:50 localhost kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing! mai 23 13:45:50 localhost kernel: Memory: 7933260K/8261220K available (14339K kernel code, 2367K rwdata, 5000K rodata, 2696K init, 5040K bss, 327960K reserved, 0K cma-reserved) mai 23 13:45:50 localhost kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 mai 23 13:45:50 localhost kernel: Kernel/User page tables isolation: enabled mai 23 13:45:50 localhost kernel: ftrace: allocating 44135 entries in 173 pages mai 23 13:45:50 localhost kernel: Lockdown: swapper: use of tracefs is restricted; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: Tracing disabled due to lockdown mai 23 13:45:50 localhost kernel: rcu: Hierarchical RCU implementation. mai 23 13:45:50 localhost kernel: rcu: RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=4. mai 23 13:45:50 localhost kernel: Tasks RCU enabled. mai 23 13:45:50 localhost kernel: rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. mai 23 13:45:50 localhost kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 mai 23 13:45:50 localhost kernel: NR_IRQS: 524544, nr_irqs: 1024, preallocated irqs: 16 mai 23 13:45:50 localhost kernel: random: crng done (trusting CPU's manufacturer) mai 23 13:45:50 localhost kernel: Console: colour dummy device 80x25 mai 23 13:45:50 localhost kernel: printk: console [tty0] enabled mai 23 13:45:50 localhost kernel: ACPI: Core revision 20190816 mai 23 13:45:50 localhost kernel: clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635855245 ns mai 23 13:45:50 localhost kernel: APIC: Switch to symmetric I/O mode setup mai 23 13:45:50 localhost kernel: DMAR: Host address width 39 mai 23 13:45:50 localhost kernel: DMAR: DRHD base: 0x000000fed90000 flags: 0x0 mai 23 13:45:50 localhost kernel: DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 19e2ff0505e mai 23 13:45:50 localhost kernel: DMAR: DRHD base: 0x000000fed91000 flags: 0x1 mai 23 13:45:50 localhost kernel: DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da mai 23 13:45:50 localhost kernel: DMAR: RMRR base: 0x0000008a78a000 end: 0x0000008a7a9fff mai 23 13:45:50 localhost kernel: DMAR: RMRR base: 0x0000008b800000 end: 0x0000008fffffff mai 23 13:45:50 localhost kernel: DMAR: ANDD device: 1 name: \_SB.PCI0.I2C0 mai 23 13:45:50 localhost kernel: DMAR: ANDD device: 2 name: \_SB.PCI0.I2C1 mai 23 13:45:50 localhost kernel: DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1 mai 23 13:45:50 localhost kernel: DMAR-IR: HPET id 0 under DRHD base 0xfed91000 mai 23 13:45:50 localhost kernel: DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping. mai 23 13:45:50 localhost kernel: DMAR-IR: Enabled IRQ remapping in x2apic mode mai 23 13:45:50 localhost kernel: x2apic enabled mai 23 13:45:50 localhost kernel: Switched APIC routing to cluster x2apic. mai 23 13:45:50 localhost kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 mai 23 13:45:50 localhost kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x29ccd767b87, max_idle_ns: 440795223720 ns mai 23 13:45:50 localhost kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 5799.77 BogoMIPS (lpj=11599544) mai 23 13:45:50 localhost kernel: pid_max: default: 32768 minimum: 301 mai 23 13:45:50 localhost kernel: LSM: Security Framework initializing mai 23 13:45:50 localhost kernel: Yama: becoming mindful. mai 23 13:45:50 localhost kernel: AppArmor: AppArmor initialized mai 23 13:45:50 localhost kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear) mai 23 13:45:50 localhost kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear) mai 23 13:45:50 localhost kernel: *** VALIDATE tmpfs *** mai 23 13:45:50 localhost kernel: *** VALIDATE proc *** mai 23 13:45:50 localhost kernel: *** VALIDATE cgroup1 *** mai 23 13:45:50 localhost kernel: *** VALIDATE cgroup2 *** mai 23 13:45:50 localhost kernel: mce: CPU0: Thermal monitoring enabled (TM1) mai 23 13:45:50 localhost kernel: process: using mwait in idle threads mai 23 13:45:50 localhost kernel: Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8 mai 23 13:45:50 localhost kernel: Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4 mai 23 13:45:50 localhost kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization mai 23 13:45:50 localhost kernel: Spectre V2 : Mitigation: Full generic retpoline mai 23 13:45:50 localhost kernel: Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch mai 23 13:45:50 localhost kernel: Spectre V2 : Enabling Restricted Speculation for firmware calls mai 23 13:45:50 localhost kernel: Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier mai 23 13:45:50 localhost kernel: Spectre V2 : User space: Mitigation: STIBP via seccomp and prctl mai 23 13:45:50 localhost kernel: Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp mai 23 13:45:50 localhost kernel: MDS: Mitigation: Clear CPU buffers mai 23 13:45:50 localhost kernel: Freeing SMP alternatives memory: 40K mai 23 13:45:50 localhost kernel: TSC deadline timer enabled mai 23 13:45:50 localhost kernel: smpboot: CPU0: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (family: 0x6, model: 0x8e, stepping: 0x9) mai 23 13:45:50 localhost kernel: Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver. mai 23 13:45:50 localhost kernel: ... version: 4 mai 23 13:45:50 localhost kernel: ... bit width: 48 mai 23 13:45:50 localhost kernel: ... generic registers: 4 mai 23 13:45:50 localhost kernel: ... value mask: 0000ffffffffffff mai 23 13:45:50 localhost kernel: ... max period: 00007fffffffffff mai 23 13:45:50 localhost kernel: ... fixed-purpose events: 3 mai 23 13:45:50 localhost kernel: ... event mask: 000000070000000f mai 23 13:45:50 localhost kernel: rcu: Hierarchical SRCU implementation. mai 23 13:45:50 localhost kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter. mai 23 13:45:50 localhost kernel: smp: Bringing up secondary CPUs ... mai 23 13:45:50 localhost kernel: x86: Booting SMP configuration: mai 23 13:45:50 localhost kernel: .... node #0, CPUs: #1 #2 mai 23 13:45:50 localhost kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details. mai 23 13:45:50 localhost kernel: #3 mai 23 13:45:50 localhost kernel: smp: Brought up 1 node, 4 CPUs mai 23 13:45:50 localhost kernel: smpboot: Max logical packages: 1 mai 23 13:45:50 localhost kernel: smpboot: Total of 4 processors activated (23199.08 BogoMIPS) mai 23 13:45:50 localhost kernel: devtmpfs: initialized mai 23 13:45:50 localhost kernel: x86/mm: Memory block size: 128MB mai 23 13:45:50 localhost kernel: PM: Registering ACPI NVS region [mem 0x7156a000-0x7156afff] (4096 bytes) mai 23 13:45:50 localhost kernel: PM: Registering ACPI NVS region [mem 0x8a88e000-0x8af7dfff] (7274496 bytes) mai 23 13:45:50 localhost kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns mai 23 13:45:50 localhost kernel: futex hash table entries: 1024 (order: 4, 65536 bytes, linear) mai 23 13:45:50 localhost kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: Can not register tracer wakeup due to lockdown mai 23 13:45:50 localhost kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: Can not register tracer function_graph due to lockdown mai 23 13:45:50 localhost kernel: pinctrl core: initialized pinctrl subsystem mai 23 13:45:50 localhost kernel: PM: RTC time: 16:45:49, date: 2020-05-23 mai 23 13:45:50 localhost kernel: NET: Registered protocol family 16 mai 23 13:45:50 localhost kernel: audit: initializing netlink subsys (disabled) mai 23 13:45:50 localhost kernel: audit: type=2000 audit(1590252349.032:1): state=initialized audit_enabled=0 res=1 mai 23 13:45:50 localhost kernel: EISA bus registered mai 23 13:45:50 localhost kernel: cpuidle: using governor ladder mai 23 13:45:50 localhost kernel: cpuidle: using governor menu mai 23 13:45:50 localhost kernel: Simple Boot Flag at 0x44 set to 0x1 mai 23 13:45:50 localhost kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it mai 23 13:45:50 localhost kernel: ACPI: bus type PCI registered mai 23 13:45:50 localhost kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 mai 23 13:45:50 localhost kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000) mai 23 13:45:50 localhost kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820 mai 23 13:45:50 localhost kernel: PCI: Using configuration type 1 for base access mai 23 13:45:50 localhost kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance' mai 23 13:45:50 localhost kernel: HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages mai 23 13:45:50 localhost kernel: HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages mai 23 13:45:50 localhost kernel: ACPI: Added _OSI(Module Device) mai 23 13:45:50 localhost kernel: ACPI: Added _OSI(Processor Device) mai 23 13:45:50 localhost kernel: ACPI: Added _OSI(3.0 _SCP Extensions) mai 23 13:45:50 localhost kernel: ACPI: Added _OSI(Processor Aggregator Device) mai 23 13:45:50 localhost kernel: ACPI: Added _OSI(Linux-Dell-Video) mai 23 13:45:50 localhost kernel: ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) mai 23 13:45:50 localhost kernel: ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) mai 23 13:45:50 localhost kernel: ACPI: 13 ACPI AML tables successfully acquired and loaded mai 23 13:45:50 localhost kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored mai 23 13:45:50 localhost kernel: ACPI: Dynamic OEM Table Load: mai 23 13:45:50 localhost kernel: ACPI: SSDT 0xFFFF8AFD651E3000 0006F6 (v02 PmRef Cpu0Ist 00003000 INTL 20160527) mai 23 13:45:50 localhost kernel: ACPI: \_PR_.PR00: _OSC native thermal LVT Acked mai 23 13:45:50 localhost kernel: ACPI: Dynamic OEM Table Load: mai 23 13:45:50 localhost kernel: ACPI: SSDT 0xFFFF8AFD64D80400 0003FF (v02 PmRef Cpu0Cst 00003001 INTL 20160527) mai 23 13:45:50 localhost kernel: ACPI: Dynamic OEM Table Load: mai 23 13:45:50 localhost kernel: ACPI: SSDT 0xFFFF8AFD651CAC00 0000BA (v02 PmRef Cpu0Hwp 00003000 INTL 20160527) mai 23 13:45:50 localhost kernel: ACPI: Dynamic OEM Table Load: mai 23 13:45:50 localhost kernel: ACPI: SSDT 0xFFFF8AFD651E4000 000628 (v02 PmRef HwpLvt 00003000 INTL 20160527) mai 23 13:45:50 localhost kernel: ACPI: Dynamic OEM Table Load: mai 23 13:45:50 localhost kernel: ACPI: SSDT 0xFFFF8AFD65233000 000D14 (v02 PmRef ApIst 00003000 INTL 20160527) mai 23 13:45:50 localhost kernel: ACPI: Dynamic OEM Table Load: mai 23 13:45:50 localhost kernel: ACPI: SSDT 0xFFFF8AFD64D80000 000317 (v02 PmRef ApHwp 00003000 INTL 20160527) mai 23 13:45:50 localhost kernel: ACPI: Dynamic OEM Table Load: mai 23 13:45:50 localhost kernel: ACPI: SSDT 0xFFFF8AFD64D83C00 00030A (v02 PmRef ApCst 00003000 INTL 20160527) mai 23 13:45:50 localhost kernel: ACPI: EC: EC started mai 23 13:45:50 localhost kernel: ACPI: EC: interrupt blocked mai 23 13:45:50 localhost kernel: ACPI: \_SB_.PCI0.LPCB.EC0_: Used as first EC mai 23 13:45:50 localhost kernel: ACPI: \_SB_.PCI0.LPCB.EC0_: GPE=0x50, IRQ=-1, EC_CMD/EC_SC=0x66, EC_DATA=0x62 mai 23 13:45:50 localhost kernel: ACPI: \_SB_.PCI0.LPCB.EC0_: Boot DSDT EC used to handle transactions mai 23 13:45:50 localhost kernel: ACPI: Interpreter enabled mai 23 13:45:50 localhost kernel: ACPI: (supports S0 S3 S4 S5) mai 23 13:45:50 localhost kernel: ACPI: Using IOAPIC for interrupt routing mai 23 13:45:50 localhost kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug mai 23 13:45:50 localhost kernel: ACPI: Enabled 7 GPEs in block 00 to 7F mai 23 13:45:50 localhost kernel: ACPI: Power Resource [FN00] (off) mai 23 13:45:50 localhost kernel: ACPI: Power Resource [FN01] (off) mai 23 13:45:50 localhost kernel: ACPI: Power Resource [FN02] (off) mai 23 13:45:50 localhost kernel: ACPI: Power Resource [FN03] (off) mai 23 13:45:50 localhost kernel: ACPI: Power Resource [FN04] (off) mai 23 13:45:50 localhost kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe]) mai 23 13:45:50 localhost kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3] mai 23 13:45:50 localhost kernel: acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug SHPCHotplug PME] mai 23 13:45:50 localhost kernel: acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability LTR] mai 23 13:45:50 localhost kernel: acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration mai 23 13:45:50 localhost kernel: PCI host bridge to bus 0000:00 mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [mem 0x000ec000-0x000effff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [mem 0x000f0000-0x000fffff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [mem 0x90000000-0xdfffffff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [mem 0xfd000000-0xfe7fffff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: root bus resource [bus 00-fe] mai 23 13:45:50 localhost kernel: pci 0000:00:00.0: [8086:5904] type 00 class 0x060000 mai 23 13:45:50 localhost kernel: pci 0000:00:02.0: [8086:5916] type 00 class 0x030000 mai 23 13:45:50 localhost kernel: pci 0000:00:02.0: reg 0x10: [mem 0xb0000000-0xb0ffffff 64bit] mai 23 13:45:50 localhost kernel: pci 0000:00:02.0: reg 0x18: [mem 0xa0000000-0xafffffff 64bit pref] mai 23 13:45:50 localhost kernel: pci 0000:00:02.0: reg 0x20: [io 0x4000-0x403f] mai 23 13:45:50 localhost kernel: pci 0000:00:02.0: BAR 2: assigned to efifb mai 23 13:45:50 localhost kernel: pci 0000:00:14.0: [8086:9d2f] type 00 class 0x0c0330 mai 23 13:45:50 localhost kernel: pci 0000:00:14.0: reg 0x10: [mem 0xb1310000-0xb131ffff 64bit] mai 23 13:45:50 localhost kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold mai 23 13:45:50 localhost kernel: pci 0000:00:15.0: [8086:9d60] type 00 class 0x118000 mai 23 13:45:50 localhost kernel: pci 0000:00:15.0: reg 0x10: [mem 0xb132a000-0xb132afff 64bit] mai 23 13:45:50 localhost kernel: pci 0000:00:15.1: [8086:9d61] type 00 class 0x118000 mai 23 13:45:50 localhost kernel: pci 0000:00:15.1: reg 0x10: [mem 0xb132b000-0xb132bfff 64bit] mai 23 13:45:50 localhost kernel: pci 0000:00:16.0: [8086:9d3a] type 00 class 0x078000 mai 23 13:45:50 localhost kernel: pci 0000:00:16.0: reg 0x10: [mem 0xb132c000-0xb132cfff 64bit] mai 23 13:45:50 localhost kernel: pci 0000:00:16.0: PME# supported from D3hot mai 23 13:45:50 localhost kernel: pci 0000:00:17.0: [8086:9d03] type 00 class 0x010601 mai 23 13:45:50 localhost kernel: pci 0000:00:17.0: reg 0x10: [mem 0xb1328000-0xb1329fff] mai 23 13:45:50 localhost kernel: pci 0000:00:17.0: reg 0x14: [mem 0xb132f000-0xb132f0ff] mai 23 13:45:50 localhost kernel: pci 0000:00:17.0: reg 0x18: [io 0x4080-0x4087] mai 23 13:45:50 localhost kernel: pci 0000:00:17.0: reg 0x1c: [io 0x4088-0x408b] mai 23 13:45:50 localhost kernel: pci 0000:00:17.0: reg 0x20: [io 0x4060-0x407f] mai 23 13:45:50 localhost kernel: pci 0000:00:17.0: reg 0x24: [mem 0xb132d000-0xb132d7ff] mai 23 13:45:50 localhost kernel: pci 0000:00:17.0: PME# supported from D3hot mai 23 13:45:50 localhost kernel: pci 0000:00:1c.0: [8086:9d14] type 01 class 0x060400 mai 23 13:45:50 localhost kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold mai 23 13:45:50 localhost kernel: pci 0000:00:1c.5: [8086:9d15] type 01 class 0x060400 mai 23 13:45:50 localhost kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold mai 23 13:45:50 localhost kernel: pci 0000:00:1f.0: [8086:9d4e] type 00 class 0x060100 mai 23 13:45:50 localhost kernel: pci 0000:00:1f.2: [8086:9d21] type 00 class 0x058000 mai 23 13:45:50 localhost kernel: pci 0000:00:1f.2: reg 0x10: [mem 0xb1324000-0xb1327fff] mai 23 13:45:50 localhost kernel: pci 0000:00:1f.3: [8086:9d71] type 00 class 0x040380 mai 23 13:45:50 localhost kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xb1320000-0xb1323fff 64bit] mai 23 13:45:50 localhost kernel: pci 0000:00:1f.3: reg 0x20: [mem 0xb1300000-0xb130ffff 64bit] mai 23 13:45:50 localhost kernel: pci 0000:00:1f.3: PME# supported from D3hot D3cold mai 23 13:45:50 localhost kernel: pci 0000:00:1f.4: [8086:9d23] type 00 class 0x0c0500 mai 23 13:45:50 localhost kernel: pci 0000:00:1f.4: reg 0x10: [mem 0xb132e000-0xb132e0ff 64bit] mai 23 13:45:50 localhost kernel: pci 0000:00:1f.4: reg 0x20: [io 0x4040-0x405f] mai 23 13:45:50 localhost kernel: pci 0000:01:00.0: [10ec:5287] type 00 class 0xff0000 mai 23 13:45:50 localhost kernel: pci 0000:01:00.0: reg 0x10: [mem 0xb1205000-0xb1205fff] mai 23 13:45:50 localhost kernel: pci 0000:01:00.0: reg 0x30: [mem 0xffff0000-0xffffffff pref] mai 23 13:45:50 localhost kernel: pci 0000:01:00.0: supports D1 D2 mai 23 13:45:50 localhost kernel: pci 0000:01:00.0: PME# supported from D1 D2 D3hot D3cold mai 23 13:45:50 localhost kernel: pci 0000:01:00.1: [10ec:8168] type 00 class 0x020000 mai 23 13:45:50 localhost kernel: pci 0000:01:00.1: reg 0x10: [io 0x3000-0x30ff] mai 23 13:45:50 localhost kernel: pci 0000:01:00.1: reg 0x18: [mem 0xb1204000-0xb1204fff 64bit] mai 23 13:45:50 localhost kernel: pci 0000:01:00.1: reg 0x20: [mem 0xb1200000-0xb1203fff 64bit] mai 23 13:45:50 localhost kernel: pci 0000:01:00.1: supports D1 D2 mai 23 13:45:50 localhost kernel: pci 0000:01:00.1: PME# supported from D0 D1 D2 D3hot D3cold mai 23 13:45:50 localhost kernel: pci 0000:00:1c.0: PCI bridge to [bus 01] mai 23 13:45:50 localhost kernel: pci 0000:00:1c.0: bridge window [io 0x3000-0x3fff] mai 23 13:45:50 localhost kernel: pci 0000:00:1c.0: bridge window [mem 0xb1200000-0xb12fffff] mai 23 13:45:50 localhost kernel: pci 0000:02:00.0: [168c:0042] type 00 class 0x028000 mai 23 13:45:50 localhost kernel: pci 0000:02:00.0: reg 0x10: [mem 0xb1000000-0xb11fffff 64bit] mai 23 13:45:50 localhost kernel: pci 0000:02:00.0: PME# supported from D0 D3hot D3cold mai 23 13:45:50 localhost kernel: pci 0000:00:1c.5: PCI bridge to [bus 02] mai 23 13:45:50 localhost kernel: pci 0000:00:1c.5: bridge window [mem 0xb1000000-0xb11fffff] mai 23 13:45:50 localhost kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15) mai 23 13:45:50 localhost kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15) mai 23 13:45:50 localhost kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15) mai 23 13:45:50 localhost kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15) mai 23 13:45:50 localhost kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 *11 12 14 15) mai 23 13:45:50 localhost kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 *11 12 14 15) mai 23 13:45:50 localhost kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15) mai 23 13:45:50 localhost kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 15) mai 23 13:45:50 localhost kernel: ACPI: EC: interrupt unblocked mai 23 13:45:50 localhost kernel: ACPI: EC: event unblocked mai 23 13:45:50 localhost kernel: ACPI: \_SB_.PCI0.LPCB.EC0_: GPE=0x50, IRQ=-1, EC_CMD/EC_SC=0x66, EC_DATA=0x62 mai 23 13:45:50 localhost kernel: ACPI: \_SB_.PCI0.LPCB.EC0_: Boot DSDT EC used to handle transactions and events mai 23 13:45:50 localhost kernel: iommu: Default domain type: Translated mai 23 13:45:50 localhost kernel: SCSI subsystem initialized mai 23 13:45:50 localhost kernel: libata version 3.00 loaded. mai 23 13:45:50 localhost kernel: pci 0000:00:02.0: vgaarb: setting as boot VGA device mai 23 13:45:50 localhost kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none mai 23 13:45:50 localhost kernel: pci 0000:00:02.0: vgaarb: bridge control possible mai 23 13:45:50 localhost kernel: vgaarb: loaded mai 23 13:45:50 localhost kernel: ACPI: bus type USB registered mai 23 13:45:50 localhost kernel: usbcore: registered new interface driver usbfs mai 23 13:45:50 localhost kernel: usbcore: registered new interface driver hub mai 23 13:45:50 localhost kernel: usbcore: registered new device driver usb mai 23 13:45:50 localhost kernel: pps_core: LinuxPPS API ver. 1 registered mai 23 13:45:50 localhost kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti mai 23 13:45:50 localhost kernel: PTP clock support registered mai 23 13:45:50 localhost kernel: EDAC MC: Ver: 3.0.0 mai 23 13:45:50 localhost kernel: Registered efivars operations mai 23 13:45:50 localhost kernel: PCI: Using ACPI for IRQ routing mai 23 13:45:50 localhost kernel: PCI: pci_cache_line_size set to 64 bytes mai 23 13:45:50 localhost kernel: e820: reserve RAM buffer [mem 0x00058000-0x0005ffff] mai 23 13:45:50 localhost kernel: e820: reserve RAM buffer [mem 0x0009e000-0x0009ffff] mai 23 13:45:50 localhost kernel: e820: reserve RAM buffer [mem 0x706e4018-0x73ffffff] mai 23 13:45:50 localhost kernel: e820: reserve RAM buffer [mem 0x7156a000-0x73ffffff] mai 23 13:45:50 localhost kernel: e820: reserve RAM buffer [mem 0x731e8000-0x73ffffff] mai 23 13:45:50 localhost kernel: e820: reserve RAM buffer [mem 0x7a55c000-0x7bffffff] mai 23 13:45:50 localhost kernel: e820: reserve RAM buffer [mem 0x89cfe000-0x8bffffff] mai 23 13:45:50 localhost kernel: e820: reserve RAM buffer [mem 0x8afff000-0x8bffffff] mai 23 13:45:50 localhost kernel: e820: reserve RAM buffer [mem 0x26f000000-0x26fffffff] mai 23 13:45:50 localhost kernel: NetLabel: Initializing mai 23 13:45:50 localhost kernel: NetLabel: domain hash size = 128 mai 23 13:45:50 localhost kernel: NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO mai 23 13:45:50 localhost kernel: NetLabel: unlabeled traffic allowed by default mai 23 13:45:50 localhost kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0 mai 23 13:45:50 localhost kernel: hpet0: 8 comparators, 64-bit 24.000000 MHz counter mai 23 13:45:50 localhost kernel: clocksource: Switched to clocksource tsc-early mai 23 13:45:50 localhost kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: Tracing disabled due to lockdown mai 23 13:45:50 localhost kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: Tracing disabled due to lockdown mai 23 13:45:50 localhost kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: Tracing disabled due to lockdown mai 23 13:45:50 localhost kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: Tracing disabled due to lockdown mai 23 13:45:50 localhost kernel: Could not create tracefs 'synthetic_events' entry mai 23 13:45:50 localhost kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: Tracing disabled due to lockdown mai 23 13:45:50 localhost kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: Tracing disabled due to lockdown mai 23 13:45:50 localhost kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: Tracing disabled due to lockdown mai 23 13:45:50 localhost kernel: *** VALIDATE bpf *** mai 23 13:45:50 localhost kernel: VFS: Disk quotas dquot_6.6.0 mai 23 13:45:50 localhost kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) mai 23 13:45:50 localhost kernel: *** VALIDATE ramfs *** mai 23 13:45:50 localhost kernel: *** VALIDATE hugetlbfs *** mai 23 13:45:50 localhost kernel: AppArmor: AppArmor Filesystem Enabled mai 23 13:45:50 localhost kernel: pnp: PnP ACPI init mai 23 13:45:50 localhost kernel: system 00:00: [mem 0xfd000000-0xfdabffff] has been reserved mai 23 13:45:50 localhost kernel: system 00:00: [mem 0xfdad0000-0xfdadffff] has been reserved mai 23 13:45:50 localhost kernel: system 00:00: [mem 0xfdb00000-0xfdffffff] has been reserved mai 23 13:45:50 localhost kernel: system 00:00: [mem 0xfe000000-0xfe01ffff] has been reserved mai 23 13:45:50 localhost kernel: system 00:00: [mem 0xfe036000-0xfe03bfff] has been reserved mai 23 13:45:50 localhost kernel: system 00:00: [mem 0xfe03d000-0xfe3fffff] has been reserved mai 23 13:45:50 localhost kernel: system 00:00: [mem 0xfe410000-0xfe7fffff] has been reserved mai 23 13:45:50 localhost kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active) mai 23 13:45:50 localhost kernel: system 00:01: [io 0x2000-0x20fe] has been reserved mai 23 13:45:50 localhost kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active) mai 23 13:45:50 localhost kernel: system 00:02: [io 0x0680-0x069f] has been reserved mai 23 13:45:50 localhost kernel: system 00:02: [io 0xfd60-0xfd63] has been reserved mai 23 13:45:50 localhost kernel: system 00:02: [io 0xffff] has been reserved mai 23 13:45:50 localhost kernel: system 00:02: [io 0xffff] has been reserved mai 23 13:45:50 localhost kernel: system 00:02: [io 0xffff] has been reserved mai 23 13:45:50 localhost kernel: system 00:02: [io 0x1800-0x18fe] has been reserved mai 23 13:45:50 localhost kernel: system 00:02: [io 0x164e-0x164f] has been reserved mai 23 13:45:50 localhost kernel: system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active) mai 23 13:45:50 localhost kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active) mai 23 13:45:50 localhost kernel: system 00:04: [io 0x1854-0x1857] has been reserved mai 23 13:45:50 localhost kernel: system 00:04: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active) mai 23 13:45:50 localhost kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0303 (active) mai 23 13:45:50 localhost kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active) mai 23 13:45:50 localhost kernel: system 00:07: [mem 0xfed10000-0xfed17fff] has been reserved mai 23 13:45:50 localhost kernel: system 00:07: [mem 0xfed18000-0xfed18fff] has been reserved mai 23 13:45:50 localhost kernel: system 00:07: [mem 0xfed19000-0xfed19fff] has been reserved mai 23 13:45:50 localhost kernel: system 00:07: [mem 0xe0000000-0xefffffff] has been reserved mai 23 13:45:50 localhost kernel: system 00:07: [mem 0xfed20000-0xfed3ffff] has been reserved mai 23 13:45:50 localhost kernel: system 00:07: [mem 0xfed90000-0xfed93fff] could not be reserved mai 23 13:45:50 localhost kernel: system 00:07: [mem 0xfed45000-0xfed8ffff] could not be reserved mai 23 13:45:50 localhost kernel: system 00:07: [mem 0xff000000-0xff000fff] has been reserved mai 23 13:45:50 localhost kernel: system 00:07: [mem 0xff010000-0xffffffff] could not be reserved mai 23 13:45:50 localhost kernel: system 00:07: [mem 0xfee00000-0xfeefffff] could not be reserved mai 23 13:45:50 localhost kernel: system 00:07: [mem 0x90000000-0x9001ffff] has been reserved mai 23 13:45:50 localhost kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active) mai 23 13:45:50 localhost kernel: pnp: PnP ACPI: found 8 devices mai 23 13:45:50 localhost kernel: thermal_sys: Registered thermal governor 'fair_share' mai 23 13:45:50 localhost kernel: thermal_sys: Registered thermal governor 'bang_bang' mai 23 13:45:50 localhost kernel: thermal_sys: Registered thermal governor 'step_wise' mai 23 13:45:50 localhost kernel: thermal_sys: Registered thermal governor 'user_space' mai 23 13:45:50 localhost kernel: thermal_sys: Registered thermal governor 'power_allocator' mai 23 13:45:50 localhost kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns mai 23 13:45:50 localhost kernel: pci 0000:01:00.0: can't claim BAR 6 [mem 0xffff0000-0xffffffff pref]: no compatible bridge window mai 23 13:45:50 localhost kernel: pci 0000:01:00.0: BAR 6: assigned [mem 0xb1210000-0xb121ffff pref] mai 23 13:45:50 localhost kernel: pci 0000:00:1c.0: PCI bridge to [bus 01] mai 23 13:45:50 localhost kernel: pci 0000:00:1c.0: bridge window [io 0x3000-0x3fff] mai 23 13:45:50 localhost kernel: pci 0000:00:1c.0: bridge window [mem 0xb1200000-0xb12fffff] mai 23 13:45:50 localhost kernel: pci 0000:00:1c.5: PCI bridge to [bus 02] mai 23 13:45:50 localhost kernel: pci 0000:00:1c.5: bridge window [mem 0xb1000000-0xb11fffff] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000c3fff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 8 [mem 0x000c4000-0x000c7fff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 9 [mem 0x000c8000-0x000cbfff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 10 [mem 0x000cc000-0x000cffff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 11 [mem 0x000d0000-0x000d3fff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 12 [mem 0x000d4000-0x000d7fff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 13 [mem 0x000d8000-0x000dbfff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 14 [mem 0x000dc000-0x000dffff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 15 [mem 0x000e0000-0x000e3fff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 16 [mem 0x000e4000-0x000e7fff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 17 [mem 0x000e8000-0x000ebfff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 18 [mem 0x000ec000-0x000effff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 19 [mem 0x000f0000-0x000fffff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 20 [mem 0x90000000-0xdfffffff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:00: resource 21 [mem 0xfd000000-0xfe7fffff window] mai 23 13:45:50 localhost kernel: pci_bus 0000:01: resource 0 [io 0x3000-0x3fff] mai 23 13:45:50 localhost kernel: pci_bus 0000:01: resource 1 [mem 0xb1200000-0xb12fffff] mai 23 13:45:50 localhost kernel: pci_bus 0000:02: resource 1 [mem 0xb1000000-0xb11fffff] mai 23 13:45:50 localhost kernel: NET: Registered protocol family 2 mai 23 13:45:50 localhost kernel: tcp_listen_portaddr_hash hash table entries: 4096 (order: 4, 65536 bytes, linear) mai 23 13:45:50 localhost kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes, linear) mai 23 13:45:50 localhost kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear) mai 23 13:45:50 localhost kernel: TCP: Hash tables configured (established 65536 bind 65536) mai 23 13:45:50 localhost kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes, linear) mai 23 13:45:50 localhost kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes, linear) mai 23 13:45:50 localhost kernel: NET: Registered protocol family 1 mai 23 13:45:50 localhost kernel: NET: Registered protocol family 44 mai 23 13:45:50 localhost kernel: pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff] mai 23 13:45:50 localhost kernel: PCI: CLS 64 bytes, default 64 mai 23 13:45:50 localhost kernel: Trying to unpack rootfs image as initramfs... mai 23 13:45:50 localhost kernel: Freeing initrd memory: 46468K mai 23 13:45:50 localhost kernel: DMAR: ACPI device "device:71" under DMAR at fed91000 as 00:15.0 mai 23 13:45:50 localhost kernel: DMAR: ACPI device "device:72" under DMAR at fed91000 as 00:15.1 mai 23 13:45:50 localhost kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB) mai 23 13:45:50 localhost kernel: software IO TLB: mapped [mem 0x85742000-0x89742000] (64MB) mai 23 13:45:50 localhost kernel: check: Scanning for low memory corruption every 60 seconds mai 23 13:45:50 localhost kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: Tracing disabled due to lockdown mai 23 13:45:50 localhost kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: Can not register tracer mmiotrace due to lockdown mai 23 13:45:50 localhost kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: Can not register tracer blk due to lockdown mai 23 13:45:50 localhost kernel: Warning: could not register the block tracer mai 23 13:45:50 localhost kernel: Initialise system trusted keyrings mai 23 13:45:50 localhost kernel: Key type blacklist registered mai 23 13:45:50 localhost kernel: workingset: timestamp_bits=36 max_order=21 bucket_order=0 mai 23 13:45:50 localhost kernel: zbud: loaded mai 23 13:45:50 localhost kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher mai 23 13:45:50 localhost kernel: fuse: init (API version 7.31) mai 23 13:45:50 localhost kernel: *** VALIDATE fuse *** mai 23 13:45:50 localhost kernel: *** VALIDATE fuse *** mai 23 13:45:50 localhost kernel: Platform Keyring initialized mai 23 13:45:50 localhost kernel: Key type asymmetric registered mai 23 13:45:50 localhost kernel: Asymmetric key parser 'x509' registered mai 23 13:45:50 localhost kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244) mai 23 13:45:50 localhost kernel: io scheduler mq-deadline registered mai 23 13:45:50 localhost kernel: pcieport 0000:00:1c.0: AER: enabled with IRQ 122 mai 23 13:45:50 localhost kernel: pcieport 0000:00:1c.5: AER: enabled with IRQ 123 mai 23 13:45:50 localhost kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 mai 23 13:45:50 localhost kernel: efifb: probing for efifb mai 23 13:45:50 localhost kernel: efifb: showing boot graphics mai 23 13:45:50 localhost kernel: efifb: framebuffer at 0xa0000000, using 4128k, total 4128k mai 23 13:45:50 localhost kernel: efifb: mode is 1366x768x32, linelength=5504, pages=1 mai 23 13:45:50 localhost kernel: efifb: scrolling: redraw mai 23 13:45:50 localhost kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 mai 23 13:45:50 localhost kernel: fbcon: Deferring console take-over mai 23 13:45:50 localhost kernel: fb0: EFI VGA frame buffer device mai 23 13:45:50 localhost kernel: intel_idle: MWAIT substates: 0x11142120 mai 23 13:45:50 localhost kernel: intel_idle: v0.4.1 model 0x8E mai 23 13:45:50 localhost kernel: intel_idle: lapic_timer_reliable_states 0xffffffff mai 23 13:45:50 localhost kernel: ACPI: AC Adapter [ACAD] (off-line) mai 23 13:45:50 localhost kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:19/PNP0C0D:00/input/input0 mai 23 13:45:50 localhost kernel: ACPI: Lid Switch [LID0] mai 23 13:45:50 localhost kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 mai 23 13:45:50 localhost kernel: ACPI: Sleep Button [SLPB] mai 23 13:45:50 localhost kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 mai 23 13:45:50 localhost kernel: ACPI: Power Button [PWRB] mai 23 13:45:50 localhost kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 mai 23 13:45:50 localhost kernel: ACPI: Power Button [PWRF] mai 23 13:45:50 localhost kernel: thermal LNXTHERM:00: registered as thermal_zone0 mai 23 13:45:50 localhost kernel: ACPI: Thermal Zone [TZ00] (28 C) mai 23 13:45:50 localhost kernel: thermal LNXTHERM:01: registered as thermal_zone1 mai 23 13:45:50 localhost kernel: ACPI: Thermal Zone [TZ01] (30 C) mai 23 13:45:50 localhost kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled mai 23 13:45:50 localhost kernel: battery: ACPI: Battery Slot [BAT1] (battery present) mai 23 13:45:50 localhost kernel: Linux agpgart interface v0.103 mai 23 13:45:50 localhost kernel: loop: module loaded mai 23 13:45:50 localhost kernel: libphy: Fixed MDIO Bus: probed mai 23 13:45:50 localhost kernel: tun: Universal TUN/TAP device driver, 1.6 mai 23 13:45:50 localhost kernel: PPP generic driver version 2.4.2 mai 23 13:45:50 localhost kernel: VFIO - User Level meta-driver version: 0.3 mai 23 13:45:50 localhost kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver mai 23 13:45:50 localhost kernel: ehci-pci: EHCI PCI platform driver mai 23 13:45:50 localhost kernel: ehci-platform: EHCI generic platform driver mai 23 13:45:50 localhost kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver mai 23 13:45:50 localhost kernel: ohci-pci: OHCI PCI platform driver mai 23 13:45:50 localhost kernel: ohci-platform: OHCI generic platform driver mai 23 13:45:50 localhost kernel: uhci_hcd: USB Universal Host Controller Interface driver mai 23 13:45:50 localhost kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller mai 23 13:45:50 localhost kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1 mai 23 13:45:50 localhost kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0000000081109810 mai 23 13:45:50 localhost kernel: xhci_hcd 0000:00:14.0: cache line size of 64 is not supported mai 23 13:45:50 localhost kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04 mai 23 13:45:50 localhost kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 mai 23 13:45:50 localhost kernel: usb usb1: Product: xHCI Host Controller mai 23 13:45:50 localhost kernel: usb usb1: Manufacturer: Linux 5.4.0-19-generic xhci-hcd mai 23 13:45:50 localhost kernel: usb usb1: SerialNumber: 0000:00:14.0 mai 23 13:45:50 localhost kernel: hub 1-0:1.0: USB hub found mai 23 13:45:50 localhost kernel: hub 1-0:1.0: 12 ports detected mai 23 13:45:50 localhost kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller mai 23 13:45:50 localhost kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2 mai 23 13:45:50 localhost kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed mai 23 13:45:50 localhost kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04 mai 23 13:45:50 localhost kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 mai 23 13:45:50 localhost kernel: usb usb2: Product: xHCI Host Controller mai 23 13:45:50 localhost kernel: usb usb2: Manufacturer: Linux 5.4.0-19-generic xhci-hcd mai 23 13:45:50 localhost kernel: usb usb2: SerialNumber: 0000:00:14.0 mai 23 13:45:50 localhost kernel: hub 2-0:1.0: USB hub found mai 23 13:45:50 localhost kernel: hub 2-0:1.0: 6 ports detected mai 23 13:45:50 localhost kernel: usb: port power management may be unreliable mai 23 13:45:50 localhost kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1 mai 23 13:45:50 localhost kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp mai 23 13:45:50 localhost kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 mai 23 13:45:50 localhost kernel: mousedev: PS/2 mouse device common for all mice mai 23 13:45:50 localhost kernel: rtc_cmos 00:03: RTC can wake from S4 mai 23 13:45:50 localhost kernel: rtc_cmos 00:03: registered as rtc0 mai 23 13:45:50 localhost kernel: rtc_cmos 00:03: alarms up to one month, y3k, 242 bytes nvram, hpet irqs mai 23 13:45:50 localhost kernel: i2c /dev entries driver mai 23 13:45:50 localhost kernel: device-mapper: uevent: version 1.0.3 mai 23 13:45:50 localhost kernel: device-mapper: ioctl: 4.41.0-ioctl (2019-09-16) initialised: dm-devel@redhat.com mai 23 13:45:50 localhost kernel: platform eisa.0: Probing EISA bus 0 mai 23 13:45:50 localhost kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard mai 23 13:45:50 localhost kernel: platform eisa.0: Cannot allocate resource for EISA slot 1 mai 23 13:45:50 localhost kernel: platform eisa.0: Cannot allocate resource for EISA slot 2 mai 23 13:45:50 localhost kernel: platform eisa.0: Cannot allocate resource for EISA slot 3 mai 23 13:45:50 localhost kernel: platform eisa.0: Cannot allocate resource for EISA slot 4 mai 23 13:45:50 localhost kernel: platform eisa.0: Cannot allocate resource for EISA slot 5 mai 23 13:45:50 localhost kernel: platform eisa.0: Cannot allocate resource for EISA slot 6 mai 23 13:45:50 localhost kernel: platform eisa.0: Cannot allocate resource for EISA slot 7 mai 23 13:45:50 localhost kernel: platform eisa.0: Cannot allocate resource for EISA slot 8 mai 23 13:45:50 localhost kernel: platform eisa.0: EISA: Detected 0 cards mai 23 13:45:50 localhost kernel: intel_pstate: Intel P-state driver initializing mai 23 13:45:50 localhost kernel: intel_pstate: HWP enabled mai 23 13:45:50 localhost kernel: ledtrig-cpu: registered to indicate activity on CPUs mai 23 13:45:50 localhost kernel: EFI Variables Facility v0.08 2004-May-17 mai 23 13:45:50 localhost kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4 mai 23 13:45:50 localhost kernel: intel_pmc_core INT33A1:00: initialized mai 23 13:45:50 localhost kernel: drop_monitor: Initializing network drop monitor service mai 23 13:45:50 localhost kernel: NET: Registered protocol family 10 mai 23 13:45:50 localhost kernel: Segment Routing with IPv6 mai 23 13:45:50 localhost kernel: NET: Registered protocol family 17 mai 23 13:45:50 localhost kernel: Key type dns_resolver registered mai 23 13:45:50 localhost kernel: RAS: Correctable Errors collector initialized. mai 23 13:45:50 localhost kernel: microcode: sig=0x806e9, pf=0x80, revision=0xca mai 23 13:45:50 localhost kernel: microcode: Microcode Update Driver: v2.2. mai 23 13:45:50 localhost kernel: IPI shorthand broadcast: enabled mai 23 13:45:50 localhost kernel: sched_clock: Marking stable (1081401577, 411606)->(1088732246, -6919063) mai 23 13:45:50 localhost kernel: registered taskstats version 1 mai 23 13:45:50 localhost kernel: Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: Can not register tracer hwlat due to lockdown mai 23 13:45:50 localhost kernel: Loading compiled-in X.509 certificates mai 23 13:45:50 localhost kernel: Loaded X.509 cert 'Build time autogenerated kernel key: 584e3b987a80545f5643bac9180faee0488eea9c' mai 23 13:45:50 localhost kernel: Loaded X.509 cert 'EOS UEFI Signing 2019: 19430810820a39c8a649ba6a4e5a8f70a9b53ce3' mai 23 13:45:50 localhost kernel: zswap: loaded using pool lzo/zbud mai 23 13:45:50 localhost kernel: Key type ._fscrypt registered mai 23 13:45:50 localhost kernel: Key type .fscrypt registered mai 23 13:45:50 localhost kernel: Key type big_key registered mai 23 13:45:50 localhost kernel: Key type trusted registered mai 23 13:45:50 localhost kernel: Key type encrypted registered mai 23 13:45:50 localhost kernel: AppArmor: AppArmor sha1 policy hashing enabled mai 23 13:45:50 localhost kernel: integrity: Loading X.509 certificate: UEFI:db mai 23 13:45:50 localhost kernel: integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53' mai 23 13:45:50 localhost kernel: integrity: Loading X.509 certificate: UEFI:db mai 23 13:45:50 localhost kernel: integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4' mai 23 13:45:50 localhost kernel: integrity: Loading X.509 certificate: UEFI:db mai 23 13:45:50 localhost kernel: integrity: Loaded X.509 cert 'Acer Database: 84f00f5841571abd2cc11a8c26d5c9c8d2b6b0b5' mai 23 13:45:50 localhost kernel: integrity: Loading X.509 certificate: UEFI:db mai 23 13:45:50 localhost kernel: integrity: Loaded X.509 cert 'Linpus: linpus.com: 2e092cab5e97a89f94a6e272ec7267c267cf4483' mai 23 13:45:50 localhost kernel: integrity: Loading X.509 certificate: UEFI:db mai 23 13:45:50 localhost kernel: integrity: Problem loading X.509 certificate -65 mai 23 13:45:50 localhost kernel: Error adding keys to platform keyring UEFI:db mai 23 13:45:50 localhost kernel: integrity: Loading X.509 certificate: UEFI:db mai 23 13:45:50 localhost kernel: integrity: Problem loading X.509 certificate -65 mai 23 13:45:50 localhost kernel: Error adding keys to platform keyring UEFI:db mai 23 13:45:50 localhost kernel: integrity: Loading X.509 certificate: UEFI:MokListRT mai 23 13:45:50 localhost kernel: integrity: Loaded X.509 cert 'Endless Secure Boot CA: 34ed74bcc9d5eea297f54bdcd6e6cd0fbae5eeb9' mai 23 13:45:50 localhost kernel: ima: Allocated hash algorithm: sha1 mai 23 13:45:50 localhost kernel: ima: No architecture policies found mai 23 13:45:50 localhost kernel: evm: Initialising EVM extended attributes: mai 23 13:45:50 localhost kernel: evm: security.selinux mai 23 13:45:50 localhost kernel: evm: security.SMACK64 mai 23 13:45:50 localhost kernel: evm: security.SMACK64EXEC mai 23 13:45:50 localhost kernel: evm: security.SMACK64TRANSMUTE mai 23 13:45:50 localhost kernel: evm: security.SMACK64MMAP mai 23 13:45:50 localhost kernel: evm: security.apparmor mai 23 13:45:50 localhost kernel: evm: security.ima mai 23 13:45:50 localhost kernel: evm: security.capability mai 23 13:45:50 localhost kernel: evm: HMAC attrs: 0x1 mai 23 13:45:50 localhost kernel: PM: Magic number: 4:655:793 mai 23 13:45:50 localhost kernel: rtc_cmos 00:03: setting system clock to 2020-05-23T16:45:50 UTC (1590252350) mai 23 13:45:50 localhost kernel: Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: Freeing unused decrypted memory: 2040K mai 23 13:45:50 localhost kernel: Freeing unused kernel image memory: 2696K mai 23 13:45:50 localhost kernel: Write protecting the kernel read-only data: 22528k mai 23 13:45:50 localhost kernel: Freeing unused kernel image memory: 2008K mai 23 13:45:50 localhost kernel: Freeing unused kernel image memory: 1144K mai 23 13:45:50 localhost kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found. mai 23 13:45:50 localhost kernel: x86/mm: Checking user space page tables mai 23 13:45:50 localhost kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found. mai 23 13:45:50 localhost kernel: Run /init as init process mai 23 13:45:50 localhost systemd[1]: systemd 244.1+dev71.8f681de-20beos3.8.1 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) mai 23 13:45:50 localhost systemd[1]: Detected architecture x86-64. mai 23 13:45:50 localhost systemd[1]: Running in initial RAM disk. mai 23 13:45:50 localhost systemd[1]: No hostname configured. mai 23 13:45:50 localhost systemd[1]: Set hostname to . mai 23 13:45:50 localhost systemd[1]: Initializing machine ID from random generator. mai 23 13:45:50 localhost kernel: Lockdown: systemd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 mai 23 13:45:50 localhost kernel: usb 1-5: new full-speed USB device number 2 using xhci_hcd mai 23 13:45:50 localhost systemd[1]: Reached target Local File Systems. mai 23 13:45:50 localhost systemd[1]: Reached target Slices. mai 23 13:45:50 localhost systemd[1]: Reached target Swap. mai 23 13:45:50 localhost systemd[1]: Reached target Timers. mai 23 13:45:50 localhost systemd[1]: Listening on Journal Audit Socket. mai 23 13:45:50 localhost systemd[1]: Listening on Journal Socket (/dev/log). mai 23 13:45:50 localhost systemd[1]: Listening on Journal Socket. mai 23 13:45:50 localhost systemd[1]: Listening on udev Control Socket. mai 23 13:45:50 localhost systemd[1]: Listening on udev Kernel Socket. mai 23 13:45:50 localhost systemd[1]: Reached target Sockets. mai 23 13:45:50 localhost systemd[1]: Condition check resulted in dracut ask for additional cmdline parameters being skipped. mai 23 13:45:50 localhost systemd[1]: Condition check resulted in dracut cmdline hook being skipped. mai 23 13:45:50 localhost systemd[1]: Condition check resulted in dracut pre-udev hook being skipped. mai 23 13:45:50 localhost systemd[1]: Condition check resulted in Install custom splash theme to runtime dir being skipped. mai 23 13:45:50 localhost systemd[1]: Starting Create list of static device nodes for the current kernel... mai 23 13:45:50 localhost systemd[1]: Starting Journal Service... mai 23 13:45:50 localhost systemd[1]: Starting Load Kernel Modules... mai 23 13:45:50 localhost systemd[1]: Started Create list of static device nodes for the current kernel. mai 23 13:45:50 localhost systemd[1]: Starting Create Static Device Nodes in /dev... mai 23 13:45:50 localhost systemd[1]: Started Create Static Device Nodes in /dev. mai 23 13:45:50 localhost systemd[1]: Starting udev Kernel Device Manager... mai 23 13:45:50 localhost systemd[1]: Started udev Kernel Device Manager. mai 23 13:45:50 localhost systemd[1]: Condition check resulted in dracut pre-trigger hook being skipped. mai 23 13:45:50 localhost systemd[1]: Starting udev Coldplug all Devices... mai 23 13:45:50 localhost systemd[1]: Started Load Kernel Modules. mai 23 13:45:50 localhost systemd[1]: Starting Apply Kernel Variables... mai 23 13:45:50 localhost systemd[1]: Started Apply Kernel Variables. mai 23 13:45:50 localhost systemd-journald[214]: Journal started mai 23 13:45:50 localhost systemd-journald[214]: Runtime Journal (/run/log/journal/27b26d6c85df485daa52a4b6957f000b) is 8.0M, max 391.8M, 383.8M free. mai 23 13:45:50 localhost systemd-modules-load[215]: Module 'fuse' is built in mai 23 13:45:50 localhost systemd-udevd[217]: /usr/lib/udev/rules.d/50-udev-default.rules:87 Unknown group 'kvm', ignoring mai 23 13:45:50 localhost systemd-modules-load[215]: Inserted module 'vmwgfx' mai 23 13:45:50 localhost systemd[1]: Starting Create Volatile Files and Directories... mai 23 13:45:50 localhost systemd[1]: Started Journal Service. mai 23 13:45:50 localhost systemd[1]: Started Create Volatile Files and Directories. mai 23 13:45:50 localhost systemd[1]: Mounting Kernel Configuration File System... mai 23 13:45:50 localhost systemd[1]: Mounted Kernel Configuration File System. mai 23 13:45:50 localhost systemd[1]: Started udev Coldplug all Devices. mai 23 13:45:50 localhost systemd[1]: Reached target System Initialization. mai 23 13:45:50 localhost systemd[1]: Condition check resulted in dracut initqueue hook being skipped. mai 23 13:45:50 localhost systemd[1]: Reached target Remote File Systems (Pre). mai 23 13:45:50 localhost systemd[1]: Reached target Remote File Systems. mai 23 13:45:50 localhost systemd[1]: Condition check resulted in dracut pre-mount hook being skipped. mai 23 13:45:50 localhost systemd[1]: Starting Show Plymouth Boot Screen... mai 23 13:45:50 localhost systemd[1]: Received SIGRTMIN+20 from PID 248 (plymouthd). mai 23 13:45:50 localhost kernel: usb 1-5: New USB device found, idVendor=04ca, idProduct=3015, bcdDevice= 0.01 mai 23 13:45:50 localhost kernel: usb 1-5: New USB device strings: Mfr=0, Product=0, SerialNumber=0 mai 23 13:45:50 localhost systemd[1]: Started Show Plymouth Boot Screen. mai 23 13:45:50 localhost systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. mai 23 13:45:50 localhost systemd[1]: Started Forward Password Requests to Plymouth Directory Watch. mai 23 13:45:50 localhost systemd[1]: Reached target Paths. mai 23 13:45:50 localhost systemd[1]: Reached target Basic System. mai 23 13:45:50 localhost kernel: hidraw: raw HID events driver (C) Jiri Kosina mai 23 13:45:50 localhost kernel: ahci 0000:00:17.0: version 3.0 mai 23 13:45:50 localhost kernel: ahci 0000:00:17.0: AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x1 impl SATA mode mai 23 13:45:50 localhost kernel: ahci 0000:00:17.0: flags: 64bit ncq pm led clo only pio slum part deso sadm sds apst mai 23 13:45:50 localhost kernel: scsi host0: ahci mai 23 13:45:50 localhost kernel: scsi host1: ahci mai 23 13:45:50 localhost kernel: ata1: SATA max UDMA/133 abar m2048@0xb132d000 port 0xb132d100 irq 125 mai 23 13:45:50 localhost kernel: ata2: DUMMY mai 23 13:45:50 localhost systemd-udevd[233]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. mai 23 13:45:50 localhost kernel: checking generic (a0000000 408000) vs hw (a0000000 10000000) mai 23 13:45:50 localhost kernel: fb0: switching to inteldrmfb from EFI VGA mai 23 13:45:50 localhost kernel: i915 0000:00:02.0: vgaarb: deactivate vga console mai 23 13:45:50 localhost kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). mai 23 13:45:50 localhost kernel: [drm] Driver supports precise vblank timestamp query. mai 23 13:45:50 localhost kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem mai 23 13:45:50 localhost kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) mai 23 13:45:50 localhost kernel: [drm] Initialized i915 1.6.0 20190822 for 0000:00:02.0 on minor 0 mai 23 13:45:50 localhost kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) mai 23 13:45:50 localhost kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5 mai 23 13:45:50 localhost kernel: fbcon: i915drmfb (fb0) is primary device mai 23 13:45:50 localhost kernel: fbcon: Deferring console take-over mai 23 13:45:50 localhost kernel: i915 0000:00:02.0: fb0: i915drmfb frame buffer device mai 23 13:45:50 localhost kernel: usb 1-7: new high-speed USB device number 3 using xhci_hcd mai 23 13:45:51 localhost kernel: usb 1-7: New USB device found, idVendor=0408, idProduct=a061, bcdDevice= 0.04 mai 23 13:45:51 localhost kernel: usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0 mai 23 13:45:51 localhost kernel: usb 1-7: Product: HD User Facing mai 23 13:45:51 localhost kernel: usb 1-7: Manufacturer: SunplusIT Inc mai 23 13:45:51 localhost kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) mai 23 13:45:51 localhost kernel: ata1.00: ATA-10: ST2000LM007-1R8174, ACM1, max UDMA/133 mai 23 13:45:51 localhost kernel: ata1.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA mai 23 13:45:51 localhost kernel: ata1.00: configured for UDMA/133 mai 23 13:45:51 localhost kernel: scsi 0:0:0:0: Direct-Access ATA ST2000LM007-1R81 ACM1 PQ: 0 ANSI: 5 mai 23 13:45:51 localhost kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 mai 23 13:45:51 localhost kernel: sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) mai 23 13:45:51 localhost kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks mai 23 13:45:51 localhost kernel: sd 0:0:0:0: [sda] Write Protect is off mai 23 13:45:51 localhost kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 mai 23 13:45:51 localhost kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA mai 23 13:45:51 localhost kernel: tsc: Refined TSC clocksource calibration: 2903.998 MHz mai 23 13:45:51 localhost kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x29dc03c1beb, max_idle_ns: 440795205215 ns mai 23 13:45:51 localhost kernel: clocksource: Switched to clocksource tsc mai 23 13:45:51 localhost kernel: sda: sda1 sda2 sda3 sda5 mai 23 13:45:51 localhost kernel: sd 0:0:0:0: [sda] Attached SCSI disk mai 23 13:45:51 localhost systemd[1]: Found device ST2000LM007-1R8174 ostree. mai 23 13:45:51 localhost systemd[1]: Reached target Initrd Root Device. mai 23 13:45:51 localhost systemd[1]: Starting EOS repartitioning... mai 23 13:45:51 localhost endless-repartition[268]: repartition: marker not found mai 23 13:45:51 localhost systemd[1]: Started EOS repartitioning. mai 23 13:45:51 localhost systemd[1]: Starting File System Check on /dev/disk/by-uuid/05c7cd5b-40f9-47d7-a032-e98150535435... mai 23 13:45:51 localhost systemd-fsck[276]: ostree: clean, 2713788/121503536 files, 126069002/486954496 blocks mai 23 13:45:51 localhost systemd[1]: Started File System Check on /dev/disk/by-uuid/05c7cd5b-40f9-47d7-a032-e98150535435. mai 23 13:45:51 localhost systemd[1]: Mounting /sysroot... mai 23 13:45:51 localhost systemd[1]: Mounted /sysroot. mai 23 13:45:51 localhost systemd[1]: Starting OSTree Prepare OS/... mai 23 13:45:51 localhost kernel: EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) mai 23 13:45:52 localhost ostree-prepare-root[280]: Resolved OSTree target to: /sysroot/ostree/deploy/eos/deploy/17d99c0a4107b0fe05569ee5906fe30b2c672e8457de8de4a1db729d7af290dd.0 mai 23 13:45:52 localhost systemd[1]: sysroot-ostree-deploy-eos-deploy-17d99c0a4107b0fe05569ee5906fe30b2c672e8457de8de4a1db729d7af290dd.0-boot.mount: Succeeded. mai 23 13:45:52 localhost systemd[1]: sysroot-ostree-deploy-eos-deploy-17d99c0a4107b0fe05569ee5906fe30b2c672e8457de8de4a1db729d7af290dd.0.mount: Succeeded. mai 23 13:45:52 localhost systemd[1]: Started OSTree Prepare OS/. mai 23 13:45:52 localhost systemd[1]: Reached target Initrd Root File System. mai 23 13:45:52 localhost systemd[1]: Starting Reload Configuration from the Real Root... mai 23 13:45:52 localhost systemd[1]: Reloading. mai 23 13:45:52 localhost systemd[1]: initrd-parse-etc.service: Succeeded. mai 23 13:45:52 localhost systemd[1]: Started Reload Configuration from the Real Root. mai 23 13:45:52 localhost systemd[1]: Reached target Initrd File Systems. mai 23 13:45:52 localhost systemd[1]: Reached target Initrd Default Target. mai 23 13:45:52 localhost systemd[1]: Condition check resulted in dracut mount hook being skipped. mai 23 13:45:52 localhost systemd[1]: Condition check resulted in dracut pre-pivot and cleanup hook being skipped. mai 23 13:45:52 localhost systemd[1]: Starting Cleaning Up and Shutting Down Daemons... mai 23 13:45:52 localhost systemd[1]: Stopped target Initrd Default Target. mai 23 13:45:52 localhost systemd[1]: Stopped target Basic System. mai 23 13:45:52 localhost systemd[1]: Stopped target Paths. mai 23 13:45:52 localhost systemd[1]: Stopped target Remote File Systems. mai 23 13:45:52 localhost systemd[1]: Stopped target Remote File Systems (Pre). mai 23 13:45:52 localhost systemd[1]: Stopped target Slices. mai 23 13:45:52 localhost systemd[1]: Stopped target Sockets. mai 23 13:45:52 localhost systemd[1]: Stopped target System Initialization. mai 23 13:45:52 localhost systemd[1]: Stopped target Swap. mai 23 13:45:52 localhost systemd[1]: Stopped target Timers. mai 23 13:45:52 localhost systemd[1]: endless-repartition.service: Succeeded. mai 23 13:45:52 localhost systemd[1]: Stopped EOS repartitioning. mai 23 13:45:52 localhost systemd[1]: Stopped target Initrd Root Device. mai 23 13:45:52 localhost systemd[1]: Condition check resulted in Install custom splash theme to runtime dir being skipped. mai 23 13:45:52 localhost systemd[1]: Starting Plymouth switch root service... mai 23 13:45:52 localhost systemd[1]: systemd-sysctl.service: Succeeded. mai 23 13:45:52 localhost systemd[1]: Stopped Apply Kernel Variables. mai 23 13:45:52 localhost systemd[1]: systemd-modules-load.service: Succeeded. mai 23 13:45:52 localhost systemd[1]: Stopped Load Kernel Modules. mai 23 13:45:52 localhost systemd[1]: systemd-tmpfiles-setup.service: Succeeded. mai 23 13:45:52 localhost systemd[1]: Stopped Create Volatile Files and Directories. mai 23 13:45:52 localhost systemd[1]: Stopped target Local File Systems. mai 23 13:45:52 localhost systemd[1]: systemd-udev-trigger.service: Succeeded. mai 23 13:45:52 localhost systemd[1]: Stopped udev Coldplug all Devices. mai 23 13:45:52 localhost systemd[1]: Stopping udev Kernel Device Manager... mai 23 13:45:52 localhost systemd[1]: initrd-cleanup.service: Succeeded. mai 23 13:45:52 localhost systemd[1]: Started Cleaning Up and Shutting Down Daemons. mai 23 13:45:52 localhost systemd[1]: systemd-udevd.service: Succeeded. mai 23 13:45:52 localhost systemd[1]: Stopped udev Kernel Device Manager. mai 23 13:45:52 localhost systemd[1]: systemd-udevd-control.socket: Succeeded. mai 23 13:45:52 localhost systemd[1]: Closed udev Control Socket. mai 23 13:45:52 localhost systemd[1]: systemd-udevd-kernel.socket: Succeeded. mai 23 13:45:52 localhost systemd[1]: Closed udev Kernel Socket. mai 23 13:45:52 localhost systemd[1]: Starting Cleanup udevd DB... mai 23 13:45:52 localhost systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded. mai 23 13:45:52 localhost systemd[1]: Stopped Create Static Device Nodes in /dev. mai 23 13:45:52 localhost systemd[1]: kmod-static-nodes.service: Succeeded. mai 23 13:45:52 localhost systemd[1]: Stopped Create list of static device nodes for the current kernel. mai 23 13:45:52 localhost systemd[1]: initrd-udevadm-cleanup-db.service: Succeeded. mai 23 13:45:52 localhost systemd[1]: Started Cleanup udevd DB. mai 23 13:45:52 localhost systemd[1]: Reached target Switch Root. mai 23 13:45:52 localhost systemd[1]: plymouth-switch-root.service: Succeeded. mai 23 13:45:52 localhost systemd[1]: Started Plymouth switch root service. mai 23 13:45:52 localhost systemd[1]: Starting Switch Root... mai 23 13:45:52 localhost systemd[1]: Switching root. mai 23 13:45:52 localhost systemd-journald[214]: Journal stopped mai 23 13:46:01 endless systemd-journald[214]: Received SIGTERM from PID 1 (systemd). mai 23 13:46:01 endless systemd[1]: systemd 244.1+dev71.8f681de-20beos3.8.1 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) mai 23 13:46:01 endless systemd[1]: Detected architecture x86-64. mai 23 13:46:01 endless systemd[1]: Set hostname to . mai 23 13:46:01 endless kernel: Lockdown: systemd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 mai 23 13:46:01 endless systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. mai 23 13:46:01 endless systemd[1]: initrd-switch-root.service: Succeeded. mai 23 13:46:01 endless systemd[1]: Stopped Switch Root. mai 23 13:46:01 endless systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1. mai 23 13:46:01 endless systemd[1]: Created slice system-getty.slice. mai 23 13:46:01 endless systemd[1]: Created slice User and Session Slice. mai 23 13:46:01 endless systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. mai 23 13:46:01 endless systemd[1]: Started Forward Password Requests to Wall Directory Watch. mai 23 13:46:01 endless systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. mai 23 13:46:01 endless systemd[1]: Reached target Local Encrypted Volumes. mai 23 13:46:01 endless systemd[1]: Reached target endless-extra SD card mounted (if expected). mai 23 13:46:01 endless systemd[1]: Stopped target Switch Root. mai 23 13:46:01 endless systemd[1]: Stopped target Initrd File Systems. mai 23 13:46:01 endless systemd[1]: Stopped target Initrd Root File System. mai 23 13:46:01 endless systemd[1]: Reached target User and Group Name Lookups. mai 23 13:46:01 endless systemd[1]: Reached target Remote Encrypted Volumes. mai 23 13:46:01 endless systemd[1]: Reached target Remote File Systems. mai 23 13:46:01 endless systemd[1]: Reached target Slices. mai 23 13:46:01 endless systemd[1]: Reached target Swap. mai 23 13:46:01 endless systemd[1]: Listening on Process Core Dump Socket. mai 23 13:46:01 endless systemd[1]: Listening on initctl Compatibility Named Pipe. mai 23 13:46:01 endless systemd[1]: Listening on udev Control Socket. mai 23 13:46:01 endless systemd[1]: Listening on udev Kernel Socket. mai 23 13:46:01 endless systemd[1]: Mounting Huge Pages File System... mai 23 13:46:01 endless systemd[1]: Mounting POSIX Message Queue File System... mai 23 13:46:01 endless systemd[1]: Mounting Arbitrary Executable File Formats File System... mai 23 13:46:01 endless systemd[1]: Mounting Kernel Debug File System... mai 23 13:46:01 endless systemd[1]: Mounting Temporary Directory (/tmp)... mai 23 13:46:01 endless systemd[1]: Starting Restore the current clock... mai 23 13:46:01 endless systemd[1]: Starting Create list of static device nodes for the current kernel... mai 23 13:46:01 endless systemd[1]: ostree-prepare-root.service: Succeeded. mai 23 13:46:01 endless systemd[1]: Stopped OSTree Prepare OS/. mai 23 13:46:01 endless systemd[1]: systemd-fsck-root.service: Succeeded. mai 23 13:46:01 endless systemd[1]: Stopped File System Check on Root Device. mai 23 13:46:01 endless systemd[1]: Stopped Journal Service. mai 23 13:46:01 endless systemd[1]: Starting Journal Service... mai 23 13:46:01 endless systemd[1]: Starting Remount Root and Kernel File Systems... mai 23 13:46:01 endless systemd[1]: Starting udev Coldplug all Devices... mai 23 13:46:01 endless systemd[1]: sysroot-usr.mount: Succeeded. mai 23 13:46:01 endless systemd[1]: sysroot-sysroot.mount: Succeeded. mai 23 13:46:01 endless systemd[1]: sysroot-boot.mount: Succeeded. mai 23 13:46:01 endless systemd[1]: Mounted Huge Pages File System. mai 23 13:46:01 endless systemd[1]: Mounted POSIX Message Queue File System. mai 23 13:46:01 endless systemd[1]: Mounted Kernel Debug File System. mai 23 13:46:01 endless systemd[1]: Mounted Temporary Directory (/tmp). mai 23 13:46:01 endless systemd[1]: Started Create list of static device nodes for the current kernel. mai 23 13:46:01 endless kernel: EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro mai 23 13:46:01 endless systemd[1]: Started Remount Root and Kernel File Systems. mai 23 13:46:01 endless systemd[1]: Starting OSTree Remount OS/ Bind Mounts... mai 23 13:46:01 endless systemd[1]: Condition check resulted in Create System Users being skipped. mai 23 13:46:01 endless systemd[1]: Starting Create Static Device Nodes in /dev... mai 23 13:46:01 endless systemd[1]: Started OSTree Remount OS/ Bind Mounts. mai 23 13:46:01 endless systemd[1]: Condition check resulted in Endless image boot device mapper setup being skipped. mai 23 13:46:01 endless systemd-journald[336]: Journal started mai 23 13:46:01 endless systemd-journald[336]: Runtime Journal (/run/log/journal/af7c8762dd084c14b291671bceeb8079) is 512.0K, max 4.0M, 3.5M free. mai 23 13:46:00 endless systemd[1]: systemd-journald.service: Succeeded. mai 23 13:46:01 endless systemd[1]: Started Journal Service. mai 23 13:46:01 endless fake-hwclock[332]: Current system time: 2020-05-23 16:46:01 mai 23 13:46:01 endless fake-hwclock[332]: fake-hwclock saved clock information is in the past: 2020-05-23 16:45:39 mai 23 13:46:01 endless fake-hwclock[332]: To set system time to this saved clock anyway, use "force" mai 23 13:46:01 endless systemd[1]: fake-hwclock-restore.service: Succeeded. mai 23 13:46:01 endless systemd[1]: Started Restore the current clock. mai 23 13:46:01 endless systemd[1]: Mounted Arbitrary Executable File Formats File System. mai 23 13:46:01 endless systemd[1]: Started udev Coldplug all Devices. mai 23 13:46:01 endless systemd-tmpfiles[341]: /usr/lib/tmpfiles.d/speech-dispatcher.conf:1: Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher → /run/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. mai 23 13:46:01 endless systemd-tmpfiles[341]: /usr/lib/tmpfiles.d/speech-dispatcher.conf:2: Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → /run/speech-dispatcher/.cache; please update the tmpfiles.d/ drop-in file accordingly. mai 23 13:46:01 endless systemd-tmpfiles[341]: /usr/lib/tmpfiles.d/speech-dispatcher.conf:3: Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher → /run/speech-dispatcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. mai 23 13:46:01 endless systemd-tmpfiles[341]: /usr/lib/tmpfiles.d/speech-dispatcher.conf:4: Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache/speech-dispatcher → /run/speech-dispatcher/.cache/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. mai 23 13:46:01 endless systemd-tmpfiles[341]: /usr/lib/tmpfiles.d/speech-dispatcher.conf:5: Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/log → /run/speech-dispatcher/log; please update the tmpfiles.d/ drop-in file accordingly. mai 23 13:46:01 endless systemd[1]: Started Create Static Device Nodes in /dev. mai 23 13:46:01 endless systemd[1]: Reached target Local File Systems (Pre). mai 23 13:46:01 endless systemd[1]: var.mount: Directory /var to mount over is not empty, mounting anyway. mai 23 13:46:01 endless systemd[1]: Mounting /var... mai 23 13:46:01 endless systemd[1]: Mounted /var. mai 23 13:46:01 endless systemd[1]: Condition check resulted in Endless live boot overlayfs setup being skipped. mai 23 13:46:01 endless systemd[1]: Reached target Local File Systems. mai 23 13:46:01 endless systemd[1]: Starting Restore /run/initramfs on shutdown... mai 23 13:46:01 endless systemd[1]: Condition check resulted in Configure default flatpak repositories being skipped. mai 23 13:46:01 endless systemd[1]: Condition check resulted in Remove hack flatpak global override being skipped. mai 23 13:46:01 endless systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... mai 23 13:46:01 endless systemd[1]: Starting Flush Journal to Persistent Storage... mai 23 13:46:01 endless systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped. mai 23 13:46:01 endless systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. mai 23 13:46:01 endless systemd[1]: Starting Collect Read-Ahead Data... mai 23 13:46:01 endless systemd[1]: Starting Replay Read-Ahead Data... mai 23 13:46:01 endless systemd[1]: Started Restore /run/initramfs on shutdown. mai 23 13:46:02 endless systemd[1]: Received SIGRTMIN+20 from PID 248 (plymouthd). mai 23 13:46:02 endless systemd[1]: Started Collect Read-Ahead Data. mai 23 13:46:02 endless systemd[1]: Started Replay Read-Ahead Data. mai 23 13:46:02 endless systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped. mai 23 13:46:02 endless systemd-journald[336]: Time spent on flushing to /var is 27.143ms for 1084 entries. mai 23 13:46:02 endless systemd-journald[336]: System Journal (/var/log/journal/af7c8762dd084c14b291671bceeb8079) is 50.0M, max 50.0M, 0B free. mai 23 13:46:02 endless systemd[1]: Starting Helper script to deal with extra codecs... mai 23 13:46:02 endless systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. mai 23 13:46:08 endless eos-codecs-activate[352]: No GPG keys found in /var/lib/codecs/.gnupg/keys.d, exiting mai 23 13:46:02 endless systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. mai 23 13:46:02 endless systemd[1]: Starting Load Kernel Modules... mai 23 13:46:02 endless systemd[1]: Starting Load/Save Random Seed... mai 23 13:46:02 endless systemd[1]: Starting udev Kernel Device Manager... mai 23 13:46:02 endless systemd[1]: plymouth-read-write.service: Succeeded. mai 23 13:46:02 endless systemd[1]: Started Tell Plymouth To Write Out Runtime Data. mai 23 13:46:02 endless systemd[1]: Started Helper script to deal with extra codecs. mai 23 13:46:02 endless systemd-modules-load[358]: Module 'fuse' is built in mai 23 13:46:03 endless systemd[1]: Started Load Kernel Modules. mai 23 13:46:03 endless systemd[1]: Mounting FUSE Control File System... mai 23 13:46:03 endless systemd[1]: Starting Apply Kernel Variables... mai 23 13:46:03 endless systemd[1]: Mounted FUSE Control File System. mai 23 13:46:03 endless systemd[1]: Condition check resulted in VMware vmblock fuse mount being skipped. mai 23 13:46:03 endless systemd[1]: Started Apply Kernel Variables. mai 23 13:46:03 endless systemd[1]: Started Load/Save Random Seed. mai 23 13:46:03 endless systemd-udevd[360]: /usr/lib/udev/rules.d/50-udev-default.rules:87 Unknown group 'kvm', ignoring mai 23 13:46:07 endless systemd-udevd[360]: /usr/lib/udev/rules.d/84-nm-drivers.rules:10 Invalid value "/bin/sh -c 'ethtool -i $1 | sed -n s/^driver:\ //p' -- $env{INTERFACE}" for PROGRAM (char 24: invalid substitution type), ignoring, but please fix it. mai 23 13:46:08 endless systemd-udevd[360]: Configuration file /usr/lib/udev/rules.d/99-vmware-scsi-udev.rules is marked executable. Please remove executable permission bits. Proceeding anyway. mai 23 13:46:08 endless systemd[1]: Started udev Kernel Device Manager. mai 23 13:46:08 endless systemd[1]: Started Flush Journal to Persistent Storage. mai 23 13:46:08 endless systemd[1]: Starting Create Volatile Files and Directories... mai 23 13:46:08 endless systemd-tmpfiles[725]: /usr/lib/tmpfiles.d/speech-dispatcher.conf:1: Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher → /run/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. mai 23 13:46:08 endless systemd-tmpfiles[725]: /usr/lib/tmpfiles.d/speech-dispatcher.conf:2: Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → /run/speech-dispatcher/.cache; please update the tmpfiles.d/ drop-in file accordingly. mai 23 13:46:08 endless systemd-tmpfiles[725]: /usr/lib/tmpfiles.d/speech-dispatcher.conf:3: Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher → /run/speech-dispatcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. mai 23 13:46:08 endless systemd-tmpfiles[725]: /usr/lib/tmpfiles.d/speech-dispatcher.conf:4: Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache/speech-dispatcher → /run/speech-dispatcher/.cache/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. mai 23 13:46:08 endless systemd-tmpfiles[725]: /usr/lib/tmpfiles.d/speech-dispatcher.conf:5: Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/log → /run/speech-dispatcher/log; please update the tmpfiles.d/ drop-in file accordingly. mai 23 13:46:09 endless kernel: input: Acer Wireless Radio Control as /devices/LNXSYSTM:00/10251229:00/input/input6 mai 23 13:46:10 endless systemd[1]: Created slice system-systemd\x2dbacklight.slice. mai 23 13:46:10 endless systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight... mai 23 13:46:10 endless kernel: io scheduler bfq registered mai 23 13:46:10 endless systemd[1]: Started Load/Save Screen Backlight Brightness of backlight:intel_backlight. mai 23 13:46:10 endless systemd[1]: Started Create Volatile Files and Directories. mai 23 13:46:10 endless systemd[1]: Condition check resulted in Endless OS Post-Boot Flatpak Installer being skipped. mai 23 13:46:10 endless systemd[1]: Condition check resulted in Update is Completed being skipped. mai 23 13:46:10 endless systemd[1]: Starting Update UTMP about System Boot/Shutdown... mai 23 13:46:10 endless systemd[1]: Condition check resulted in Authentication service for virtual machines hosted on VMware being skipped. mai 23 13:46:10 endless systemd[1]: Condition check resulted in Service for virtual machines hosted on VMware being skipped. mai 23 13:46:11 endless systemd[1]: Started Update UTMP about System Boot/Shutdown. mai 23 13:46:11 endless systemd[1]: Reached target System Initialization. mai 23 13:46:11 endless systemd[1]: Started CUPS Scheduler. mai 23 13:46:11 endless systemd[1]: Started Send system activation/daily ping messages to Endless. mai 23 13:46:11 endless systemd[1]: Started OSTree Monitor Staged Deployment. mai 23 13:46:11 endless systemd[1]: Started Endless OS Automatic Update Timer. mai 23 13:46:11 endless systemd[1]: Started Send system activation/daily ping messages to Endless. mai 23 13:46:11 endless systemd[1]: Started Save the clock time to disk periodically. mai 23 13:46:11 endless systemd[1]: Started Discard unused blocks once a week. mai 23 13:46:11 endless systemd[1]: Started Daily man-db regeneration. mai 23 13:46:11 endless systemd[1]: Started Daily Cleanup of Temporary Directories. mai 23 13:46:11 endless systemd[1]: Reached target Paths. mai 23 13:46:11 endless systemd[1]: Reached target Timers. mai 23 13:46:11 endless systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket. mai 23 13:46:11 endless systemd[1]: Listening on CUPS Scheduler. mai 23 13:46:11 endless systemd[1]: Listening on D-Bus System Message Bus Socket. mai 23 13:46:11 endless systemd[1]: Listening on KA Lite Server. mai 23 13:46:11 endless systemd[1]: Listening on EndlessOS License Service Socket. mai 23 13:46:11 endless systemd[1]: Listening on UUID daemon activation socket. mai 23 13:46:11 endless systemd[1]: Reached target Sockets. mai 23 13:46:11 endless systemd[1]: Condition check resulted in Endless Boot Helper being skipped. mai 23 13:46:11 endless systemd[1]: Reached target Basic System. mai 23 13:46:11 endless systemd[1]: Starting Modem Manager... mai 23 13:46:11 endless systemd[1]: Starting Accounts Service... mai 23 13:46:11 endless systemd[1]: Starting Avahi mDNS/DNS-SD Stack... mai 23 13:46:11 endless avahi-daemon[1534]: Found user 'avahi' (UID 102) and group 'avahi' (GID 106). mai 23 13:46:11 endless systemd[1]: Starting Bluetooth UART... mai 23 13:46:11 endless systemd[1]: Started CUPS Scheduler. mai 23 13:46:11 endless systemd[1]: Started D-Bus System Message Bus. mai 23 13:46:11 endless systemd[1]: Starting Network Manager... mai 23 13:46:11 endless systemd[1]: Condition check resulted in configure persistent journal on durable storage being skipped. mai 23 13:46:11 endless systemd[1]: Starting swap with zram... mai 23 13:46:11 endless systemd[1]: Condition check resulted in Endless factory test helper being skipped. mai 23 13:46:11 endless systemd[1]: Starting EndlessOS Metrics Event Recorder Server... mai 23 13:46:11 endless dbus-daemon[1538]: dbus[1538]: Unknown group "power" in message bus configuration file mai 23 13:46:11 endless systemd[1]: Starting Pay As You Go Daemon... mai 23 13:46:11 endless systemd[1]: Condition check resulted in Adjust desktop settings for live boot being skipped. mai 23 13:46:11 endless systemd[1]: Starting Save the current clock... mai 23 13:46:11 endless systemd[1]: Starting Location Lookup Service... mai 23 13:46:11 endless systemd[1]: Condition check resulted in getty on tty2-tty6 if dbus and logind are not available being skipped. mai 23 13:46:11 endless systemd[1]: Reached target Login Prompts. mai 23 13:46:11 endless kernel: mei_me 0000:00:16.0: enabling device (0004 -> 0006) mai 23 13:46:11 endless mtp-probe[1351]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7" mai 23 13:46:11 endless mtp-probe[1351]: bus: 1, device: 3 was not an MTP device mai 23 13:46:11 endless kernel: acer_wmi: Acer Laptop ACPI-WMI Extras mai 23 13:46:11 endless kernel: acer_wmi: Function bitmap for Communication Button: 0x801 mai 23 13:46:11 endless kernel: input: Acer WMI hotkeys as /devices/virtual/input/input7 mai 23 13:46:11 endless systemd-udevd[378]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. mai 23 13:46:11 endless ModemManager[1532]: ModemManager (version 1.10.0) starting in system bus... mai 23 13:46:11 endless systemd[1]: Starting Download Scheduling Daemon... mai 23 13:46:11 endless systemd[1]: Starting Nvidia graphics management... mai 23 13:46:11 endless systemd[1]: Starting Authorization Manager... mai 23 13:46:11 endless systemd[1]: Started Pressure Stall Information Monitor. mai 23 13:46:11 endless psi-monitor[1721]: poll_interval=5s, recovery_interval=15s, stall_threshold=10% mai 23 13:46:11 endless systemd[1]: Starting Login Service... mai 23 13:46:11 endless systemd[1]: Starting Thermal Daemon Service... mai 23 13:46:11 endless systemd[1]: Starting Disk Manager... mai 23 13:46:11 endless systemd[1]: Starting Daemon for power management... mai 23 13:46:11 endless systemd[1]: Condition check resulted in Virtualbox guest utils being skipped. mai 23 13:46:11 endless systemd[1]: fake-hwclock.service: Succeeded. mai 23 13:46:11 endless systemd[1]: Started Save the current clock. mai 23 13:46:11 endless systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. mai 23 13:46:11 endless systemd[1]: Started Send system activation/daily ping messages to Endless. mai 23 13:46:11 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.systemd1' mai 23 13:46:11 endless udisksd[1728]: udisks daemon version 2.8.4 starting mai 23 13:46:11 endless avahi-daemon[1534]: Successfully dropped root privileges. mai 23 13:46:11 endless avahi-daemon[1534]: avahi-daemon 0.7 starting up. mai 23 13:46:11 endless thermald[1727]: [WARN]NO RAPL sysfs present mai 23 13:46:11 endless thermald[1727]: [WARN]22 CPUID levels; family:model:stepping 0x6:8e:9 (6:142:9) mai 23 13:46:11 endless thermald[1727]: [WARN]Polling mode is enabled: 4 mai 23 13:46:11 endless thermald[1727]: [WARN]Thermal DTS: No coretemp sysfs found mai 23 13:46:11 endless thermald[1727]: [WARN]sensor id 2 : No temp sysfs for reading raw temp mai 23 13:46:11 endless thermald[1727]: [WARN]sensor id 2 : No temp sysfs for reading raw temp mai 23 13:46:11 endless thermald[1727]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml" mai 23 13:46:11 endless thermald[1727]: [WARN]error: could not parse file /etc/thermald/thermal-conf.xml mai 23 13:46:11 endless avahi-daemon[1534]: Successfully called chroot(). mai 23 13:46:11 endless thermald[1727]: [WARN]sysfs open failed mai 23 13:46:11 endless thermald[1727]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml" mai 23 13:46:11 endless thermald[1727]: [WARN]error: could not parse file /etc/thermald/thermal-conf.xml mai 23 13:46:11 endless avahi-daemon[1534]: Successfully dropped remaining capabilities. mai 23 13:46:11 endless thermald[1727]: [ERR]Thermal DTS or hwmon: No Zones present Need to configure manually mai 23 13:46:11 endless thermald[1727]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml" mai 23 13:46:11 endless thermald[1727]: [WARN]error: could not parse file /etc/thermald/thermal-conf.xml mai 23 13:46:11 endless systemd[1]: Started Thermal Daemon Service. mai 23 13:46:11 endless systemd[1]: Started Avahi mDNS/DNS-SD Stack. mai 23 13:46:11 endless systemd[1]: Started Make remote CUPS printers available locally. mai 23 13:46:11 endless polkitd[1720]: Started polkitd version 0.116 mai 23 13:46:11 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.4' (uid=0 pid=1532 comm="/usr/sbin/ModemManager --filter-policy=strict " label="unconfined") mai 23 13:46:11 endless udisksd[1728]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory mai 23 13:46:11 endless udisksd[1728]: Failed to load the 'mdraid' libblockdev plugin mai 23 13:46:12 endless avahi-daemon[1534]: No service file found in /etc/avahi/services. mai 23 13:46:12 endless avahi-daemon[1534]: Network interface enumeration completed. mai 23 13:46:12 endless avahi-daemon[1534]: Server startup complete. Host name is endless.local. Local service cookie is 1162645832. mai 23 13:46:12 endless systemd[1]: Started Download Scheduling Daemon. mai 23 13:46:12 endless systemd-logind[1824]: New seat seat0. mai 23 13:46:12 endless systemd-logind[1824]: Watching system buttons on /dev/input/event3 (Power Button) mai 23 13:46:12 endless systemd-logind[1824]: Watching system buttons on /dev/input/event0 (Lid Switch) mai 23 13:46:12 endless systemd-logind[1824]: Watching system buttons on /dev/input/event2 (Power Button) mai 23 13:46:12 endless systemd-logind[1824]: Watching system buttons on /dev/input/event1 (Sleep Button) mai 23 13:46:12 endless systemd-logind[1824]: Watching system buttons on /dev/input/event4 (AT Translated Set 2 keyboard) mai 23 13:46:12 endless systemd[1]: Started Login Service. mai 23 13:46:12 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.14' (uid=0 pid=1536 comm="/usr/sbin/cupsd -l " label="unconfined") mai 23 13:46:12 endless systemd[1]: Started EndlessOS Metrics Event Recorder Server. mai 23 13:46:12 endless systemd[1]: Starting Manage, Install and Generate Color Profiles... mai 23 13:46:12 endless systemd[1]: Started EndlessOS Metrics Instrumentation. mai 23 13:46:13 endless kernel: zram: Added device: zram0 mai 23 13:46:13 endless systemd[1]: Started Nvidia graphics management. mai 23 13:46:13 endless kernel: zram0: detected capacity change from 0 to 12326830080 mai 23 13:46:13 endless systemd[1]: Started Daemon for power management. mai 23 13:46:13 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.ColorManager' mai 23 13:46:13 endless systemd[1]: Started Manage, Install and Generate Color Profiles. mai 23 13:46:14 endless systemd-logind[1824]: Watching system buttons on /dev/input/event7 (Acer WMI hotkeys) mai 23 13:46:14 endless colord[2288]: failed to get session [pid 1536]: Não há dados disponíveis mai 23 13:46:14 endless cupsd[1536]: REQUEST localhost - - "POST / HTTP/1.1" 200 349 Create-Printer-Subscriptions successful-ok mai 23 13:46:14 endless cupsd[1536]: REQUEST localhost - - "POST / HTTP/1.1" 200 176 Create-Printer-Subscriptions successful-ok mai 23 13:46:14 endless NetworkManager[1540]: [1590252374.5803] NetworkManager (version 1.14.6) is starting... (for the first time) mai 23 13:46:14 endless NetworkManager[1540]: [1590252374.5804] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf) mai 23 13:46:14 endless systemd[1]: Started Network Manager. mai 23 13:46:14 endless NetworkManager[1540]: [1590252374.6076] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" mai 23 13:46:14 endless systemd[1]: Reached target Network. mai 23 13:46:14 endless systemd[1]: Starting Network Time Service... mai 23 13:46:14 endless systemd[1]: Condition check resulted in fast remote file copy program daemon being skipped. mai 23 13:46:14 endless NetworkManager[1540]: [1590252374.6104] manager[0x55a71ef6d000]: monitoring kernel firmware directory '/lib/firmware'. mai 23 13:46:14 endless NetworkManager[1540]: [1590252374.6105] monitoring ifupdown state file '/run/network/ifstate'. mai 23 13:46:14 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.21' (uid=0 pid=1540 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") mai 23 13:46:14 endless systemd[1]: Starting Hostname Service... mai 23 13:46:14 endless ntpd[2970]: ntpd 4.2.8p12@1.3728-o (1): Starting mai 23 13:46:14 endless ntpd[2970]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 112:119 mai 23 13:46:14 endless systemd[1]: Started Network Time Service. mai 23 13:46:14 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.hostname1' mai 23 13:46:14 endless systemd[1]: Started Hostname Service. mai 23 13:46:14 endless NetworkManager[1540]: [1590252374.8554] hostname: hostname: using hostnamed mai 23 13:46:14 endless NetworkManager[1540]: [1590252374.8554] hostname: hostname changed from (none) to "endless" mai 23 13:46:14 endless NetworkManager[1540]: [1590252374.8558] dns-mgr[0x55a71ef78110]: init: dns=default, rc-manager=resolvconf mai 23 13:46:14 endless NetworkManager[1540]: [1590252374.8566] rfkill0: found WiFi radio killswitch (at /sys/devices/platform/acer-wmi/rfkill/rfkill0) (platform driver acer-wmi) mai 23 13:46:14 endless NetworkManager[1540]: [1590252374.8718] manager[0x55a71ef6d000]: rfkill: WiFi hardware radio set enabled mai 23 13:46:14 endless NetworkManager[1540]: [1590252374.8721] manager[0x55a71ef6d000]: rfkill: WWAN hardware radio set enabled mai 23 13:46:15 endless ntpd[3056]: proto: precision = 0.114 usec (-23) mai 23 13:46:15 endless ntpd[3056]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature mai 23 13:46:15 endless ntpd[3056]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2020-06-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37 mai 23 13:46:15 endless ntpd[3056]: Listen and drop on 0 v6wildcard [::]:123 mai 23 13:46:15 endless ntpd[3056]: Listen and drop on 1 v4wildcard 0.0.0.0:123 mai 23 13:46:15 endless ntpd[3056]: Listen normally on 2 lo 127.0.0.1:123 mai 23 13:46:15 endless ntpd[3056]: Listen normally on 3 lo [::1]:123 mai 23 13:46:15 endless ntpd[3056]: Listening on routing socket on fd #20 for interface updates mai 23 13:46:15 endless ntpd[3056]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized mai 23 13:46:15 endless ntpd[3056]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized mai 23 13:46:15 endless polkitd[1720]: Loading rules from directory /etc/polkit-1/rules.d mai 23 13:46:15 endless polkitd[1720]: Loading rules from directory /usr/share/polkit-1/rules.d mai 23 13:46:15 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.21' (uid=0 pid=1540 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") mai 23 13:46:15 endless kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) mai 23 13:46:15 endless systemd[1]: Starting Network Manager Script Dispatcher Service... mai 23 13:46:15 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' mai 23 13:46:15 endless systemd[1]: Started Network Manager Script Dispatcher Service. mai 23 13:46:15 endless systemd[1]: eos-paygd.service: Succeeded. mai 23 13:46:15 endless systemd[1]: Started Pay As You Go Daemon. mai 23 13:46:15 endless systemd[1]: Starting Permit User Sessions... mai 23 13:46:15 endless NetworkManager[1540]: [1590252375.8410] ifupdown: interface-parser: parsing file /etc/network/interfaces mai 23 13:46:15 endless NetworkManager[1540]: [1590252375.8534] ifupdown: interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d mai 23 13:46:15 endless NetworkManager[1540]: [1590252375.8615] ifupdown: interface-parser: finished parsing file /etc/network/interfaces mai 23 13:46:15 endless NetworkManager[1540]: [1590252375.8616] ifupdown: management mode: unmanaged mai 23 13:46:15 endless NetworkManager[1540]: [1590252375.8616] settings: Loaded settings plugin: SettingsPluginIfupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-settings-plugin-ifupdown.so") mai 23 13:46:15 endless NetworkManager[1540]: [1590252375.8616] settings: Loaded settings plugin: NMSKeyfilePlugin (internal) mai 23 13:46:15 endless systemd[1]: Started Permit User Sessions. mai 23 13:46:15 endless systemd[1]: Created slice User Slice of UID 1001. mai 23 13:46:15 endless systemd[1]: Starting GNOME Display Manager... mai 23 13:46:15 endless systemd[1]: Starting Hold until boot process finishes up... mai 23 13:46:15 endless systemd[1]: Starting User Runtime Directory /run/user/1001... mai 23 13:46:16 endless systemd[1]: Started User Runtime Directory /run/user/1001. mai 23 13:46:16 endless systemd[1]: Starting User Manager for UID 1001... mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6177] keyfile: new connection /etc/NetworkManager/system-connections/Moto C Plus-6558e250-5c15-4613-81fc-3c9b743f5a12.nmconnection (6558e250-5c15-4613-81fc-3c9b743f5a12,"Moto C Plus") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6368] keyfile: new connection /etc/NetworkManager/system-connections/BethDaniel.nmconnection (6d8338a5-5a59-4474-94ac-04360e95d6df,"BethDaniel") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6504] keyfile: new connection /etc/NetworkManager/system-connections/LG K10 Power_6285.nmconnection (032c135f-1155-4d62-b574-df4d28d2cf53,"LG K10 Power_6285") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6518] keyfile: new connection /etc/NetworkManager/system-connections/CESGRANRIO.nmconnection (c0d76396-ae8b-4a92-b596-e13298982b6f,"CESGRANRIO") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6545] keyfile: new connection /etc/NetworkManager/system-connections/TP-LINK_711D80.nmconnection (adf7292a-70fa-4dd5-8cca-003b66a88732,"TP-LINK_711D80") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6557] keyfile: new connection /etc/NetworkManager/system-connections/VIVO-4048.nmconnection (0a84e934-4196-416d-88de-c87f389b1b4c,"VIVO-4048") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6569] keyfile: new connection /etc/NetworkManager/system-connections/Moto C Plus 4725.nmconnection (42036f44-61a3-4813-8e20-d8b734e425f1,"Moto C Plus 4725") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6611] keyfile: new connection /etc/NetworkManager/system-connections/Visitantes@UHGBrasil.nmconnection (cfaaeb1c-edfc-4f2b-873f-b2ba297f6461,"Visitantes@UHGBrasil") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6625] keyfile: new connection /etc/NetworkManager/system-connections/Moto C Plus.nmconnection (98f71f54-7c53-433a-9467-9ab6c4dda8c5,"Moto C Plus") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6647] keyfile: new connection /etc/NetworkManager/system-connections/FAMILIA_NETO.nmconnection (1dd5072e-4ff6-4cb0-a725-4f0fd1519e03,"FAMILIA_NETO") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6659] keyfile: new connection /etc/NetworkManager/system-connections/DTAL.nmconnection (522a8208-d538-433a-80eb-afbc7ba6e2d2,"DTAL") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6759] keyfile: new connection /etc/NetworkManager/system-connections/DTAL2.nmconnection (5ba9a602-0d71-4722-8317-7c8ea6910f4b,"DTAL2") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6772] keyfile: new connection /etc/NetworkManager/system-connections/ALOWW.nmconnection (f31551de-1137-4a3c-884c-0233373971f8,"ALOWW") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6783] keyfile: new connection /etc/NetworkManager/system-connections/MetropolitanHotel.nmconnection (31322e14-cb92-41d4-bce7-b2c4b6f72057,"MetropolitanHotel") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6796] keyfile: new connection /etc/NetworkManager/system-connections/Moto C Plus 6938.nmconnection (c15cda8b-9003-4187-b83f-8d8b3fa339b5,"Moto C Plus 6938") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6819] keyfile: new connection /etc/NetworkManager/system-connections/Facesg.nmconnection (adfa3899-ed14-479f-ad1c-b4ad83ade290,"Facesg") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6830] keyfile: new connection /etc/NetworkManager/system-connections/FABSTART_VISITANTE.nmconnection (29b6a808-b55b-4dec-b0db-b35fa1f462af,"FABSTART_VISITANTE") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.6842] keyfile: new connection /etc/NetworkManager/system-connections/Xperia T2 Ultra dual_e6b6.nmconnection (44942f41-14f8-452c-8709-e298f6b1f360,"Xperia T2 Ultra dual_e6b6") mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.7308] manager: rfkill: WiFi enabled by radio killswitch; enabled by state file mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.7310] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.7310] manager: Networking is enabled by state file mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.7311] dhcp-init: Using DHCP client 'dhclient' mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.7649] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-wwan.so) mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.7858] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-bluetooth.so) mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.7865] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-adsl.so) mai 23 13:46:16 endless nm-dispatcher[3285]: req:1 'hostname': new request (5 scripts) mai 23 13:46:16 endless nm-dispatcher[3285]: req:1 'hostname': start running ordered scripts... mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.8365] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-wifi.so) mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.8375] device (lo): carrier: link connected mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.8377] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1) mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.9120] Error: failed to open /run/network/ifstate mai 23 13:46:16 endless NetworkManager[1540]: [1590252376.9437] manager: startup complete mai 23 13:46:17 endless systemd[1]: Started GNOME Display Manager. mai 23 13:46:17 endless systemd[1]: Started Setup The Fallback Framebuffer. mai 23 13:46:17 endless systemd[1]: Received SIGRTMIN+21 from PID 248 (plymouthd). mai 23 13:46:17 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' requested by ':1.30' (uid=0 pid=3372 comm="/usr/sbin/gdm " label="unconfined") mai 23 13:46:17 endless fallback-fb-setup[3519]: Cleared /dev/fb0 mai 23 13:46:17 endless systemd[1]: fallback-fb-setup.service: Succeeded. mai 23 13:46:17 endless ntpd[3056]: error resolving pool 0.debian.pool.ntp.org: Name or service not known (-2) mai 23 13:46:17 endless ntpd[3056]: error resolving pool 1.debian.pool.ntp.org: Name or service not known (-2) mai 23 13:46:17 endless systemd[3453]: pam_unix(systemd-user:session): session opened for user daniel by (uid=0) mai 23 13:46:17 endless kernel: Bluetooth: Core ver 2.22 mai 23 13:46:17 endless kernel: NET: Registered protocol family 31 mai 23 13:46:17 endless kernel: Bluetooth: HCI device and connection manager initialized mai 23 13:46:17 endless kernel: Bluetooth: HCI socket layer initialized mai 23 13:46:17 endless kernel: Bluetooth: L2CAP socket layer initialized mai 23 13:46:17 endless kernel: Bluetooth: SCO socket layer initialized mai 23 13:46:18 endless polkitd[1720]: Finished loading, compiling and executing 16 rules mai 23 13:46:18 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' mai 23 13:46:18 endless polkitd[1720]: Acquired the name org.freedesktop.PolicyKit1 on the system bus mai 23 13:46:18 endless systemd[1]: Started Authorization Manager. mai 23 13:46:18 endless eos-metrics-ins[2289]: Not recording location as it is not required for this image mai 23 13:46:18 endless kernel: intel-lpss 0000:00:15.0: enabling device (0000 -> 0002) mai 23 13:46:18 endless kernel: idma64 idma64.0: Found Intel integrated DMA 64-bit mai 23 13:46:18 endless kernel: intel-lpss 0000:00:15.1: enabling device (0000 -> 0002) mai 23 13:46:18 endless kernel: idma64 idma64.1: Found Intel integrated DMA 64-bit mai 23 13:46:18 endless kernel: i2c_hid i2c-SYNA7DB5:01: i2c-SYNA7DB5:01 supply vdd not found, using dummy regulator mai 23 13:46:18 endless kernel: i2c_hid i2c-SYNA7DB5:01: i2c-SYNA7DB5:01 supply vddl not found, using dummy regulator mai 23 13:46:18 endless kernel: mc: Linux media interface: v0.10 mai 23 13:46:19 endless kernel: input: SYNA7DB5:01 06CB:7DB7 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-SYNA7DB5:01/0018:06CB:7DB7.0001/input/input8 mai 23 13:46:19 endless kernel: input: SYNA7DB5:01 06CB:7DB7 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-SYNA7DB5:01/0018:06CB:7DB7.0001/input/input9 mai 23 13:46:19 endless kernel: hid-generic 0018:06CB:7DB7.0001: input,hidraw0: I2C HID v1.00 Mouse [SYNA7DB5:01 06CB:7DB7] on i2c-SYNA7DB5:01 mai 23 13:46:19 endless NetworkManager[1540]: [1590252379.1858] modem-manager: ModemManager not available mai 23 13:46:19 endless systemd[1]: Started Modem Manager. mai 23 13:46:19 endless NetworkManager[1540]: [1590252379.2078] modem-manager: ModemManager now available mai 23 13:46:19 endless accounts-daemon[1533]: started daemon version 0.6.55 mai 23 13:46:19 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.Accounts' mai 23 13:46:19 endless systemd[1]: Started Accounts Service. mai 23 13:46:19 endless dbus-daemon[1538]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.64' (uid=114 pid=1548 comm="/usr/libexec/geoclue " label="unconfined") mai 23 13:46:19 endless systemd[1]: Starting WPA supplicant... mai 23 13:46:19 endless udisksd[1728]: Acquired the name org.freedesktop.UDisks2 on the system message bus mai 23 13:46:19 endless systemd[1]: Started Disk Manager. mai 23 13:46:19 endless dbus-daemon[1538]: [system] Successfully activated service 'fi.w1.wpa_supplicant1' mai 23 13:46:19 endless systemd[1]: Started WPA supplicant. mai 23 13:46:19 endless wpa_supplicant[3673]: Successfully initialized wpa_supplicant mai 23 13:46:19 endless systemd[1]: Started Location Lookup Service. mai 23 13:46:19 endless kernel: input: SYNA7DB5:01 06CB:7DB7 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-SYNA7DB5:01/0018:06CB:7DB7.0001/input/input11 mai 23 13:46:19 endless kernel: input: SYNA7DB5:01 06CB:7DB7 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-SYNA7DB5:01/0018:06CB:7DB7.0001/input/input12 mai 23 13:46:19 endless kernel: hid-multitouch 0018:06CB:7DB7.0001: input,hidraw0: I2C HID v1.00 Mouse [SYNA7DB5:01 06CB:7DB7] on i2c-SYNA7DB5:01 mai 23 13:46:20 endless eos-metrics-ins[2289]: Failed to load /etc/metrics/location.conf, unable to record location label: No such file or directory mai 23 13:46:20 endless eos-metrics-ins[2289]: Not recording network ID as it is not required for this image mai 23 13:46:20 endless ntpd[3056]: error resolving pool 2.debian.pool.ntp.org: Name or service not known (-2) mai 23 13:46:20 endless ntpd[3056]: error resolving pool 3.debian.pool.ntp.org: Name or service not known (-2) mai 23 13:46:20 endless gdm-Xorg-:0[3655]: X.Org X Server 1.20.4 mai 23 13:46:20 endless gdm-Xorg-:0[3655]: X Protocol Version 11, Revision 0 mai 23 13:46:20 endless gdm-Xorg-:0[3655]: Build Operating System: Linux 4.9.0-8-amd64 x86_64 Endless mai 23 13:46:20 endless gdm-Xorg-:0[3655]: Current Operating System: Linux endless 5.4.0-19-generic #23+dev177.1a56fd1beos3.8.2 SMP Tue May 5 22:42:53 UTC 2020 x86_64 mai 23 13:46:20 endless gdm-Xorg-:0[3655]: Kernel command line: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-94c993d319cdf01ff15a7624dd6855cc9ebe14d7b40f3077a1e965a0de360d8e/vmlinuz-5.4.0-19-generic root=UUID=05c7cd5b-40f9-47d7-a032-e98150535435 rw splash plymouth.ignore-serial-consoles quiet loglevel=2 ostree=/ostree/boot.1/eos/94c993d319cdf01ff15a7624dd6855cc9ebe14d7b40f3077a1e965a0de360d8e/0 mai 23 13:46:20 endless gdm-Xorg-:0[3655]: Build Date: 10 June 2019 05:21:50AM mai 23 13:46:20 endless gdm-Xorg-:0[3655]: xorg-server 2:1.20.4-1endless1bem1 (https://www.debian.org/support) mai 23 13:46:20 endless gdm-Xorg-:0[3655]: Current version of pixman: 0.36.0 mai 23 13:46:20 endless gdm-Xorg-:0[3655]: Before reporting problems, check http://wiki.x.org mai 23 13:46:20 endless gdm-Xorg-:0[3655]: to make sure that you have the latest version. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: Markers: (--) probed, (**) from config file, (==) default setting, mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (++) from command line, (!!) notice, (II) informational, mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (++) Log file: "/dev/null", Time: Sat May 23 13:46:20 2020 mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (==) Using system config directory "/usr/share/X11/xorg.conf.d" mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (==) No Layout section. Using the first Screen section. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (==) No screen section available. Using defaults. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (**) |-->Screen "Default Screen Section" (0) mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (**) | |-->Monitor "" mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (==) No monitor specified for screen "Default Screen Section". mai 23 13:46:20 endless gdm-Xorg-:0[3655]: Using a default monitor configuration. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (==) Automatically adding devices mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (==) Automatically enabling devices mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (==) Automatically adding GPU devices mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (==) Automatically binding GPU devices mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (==) Max clients allowed: 256, resource mask: 0x1fffff mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (WW) The directory "/usr/share/fonts/X11/misc" does not exist. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: Entry deleted from font path. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: Entry deleted from font path. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: Entry deleted from font path. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: Entry deleted from font path. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: Entry deleted from font path. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: Entry deleted from font path. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: Entry deleted from font path. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (==) FontPath set to: mai 23 13:46:20 endless gdm-Xorg-:0[3655]: built-ins mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (==) ModulePath set to "/usr/lib/xorg/modules" mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (II) The server relies on udev to provide the list of input devices. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: If no devices become available, reconfigure udev or disable AutoAddDevices. mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (II) Loader magic: 0x559014fe7e20 mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (II) Module ABI versions: mai 23 13:46:20 endless gdm-Xorg-:0[3655]: X.Org ANSI C Emulation: 0.4 mai 23 13:46:20 endless gdm-Xorg-:0[3655]: X.Org Video Driver: 24.0 mai 23 13:46:20 endless gdm-Xorg-:0[3655]: X.Org XInput driver : 24.1 mai 23 13:46:20 endless gdm-Xorg-:0[3655]: X.Org Server Extension : 10.0 mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (++) using VT number 1 mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration mai 23 13:46:20 endless gdm-Xorg-:0[3655]: (II) xfree86: Adding drm device (/dev/dri/card0) mai 23 13:46:21 endless gdm-Xorg-:0[3655]: (--) PCI:*(0@0:2:0) 8086:5916:1025:1193 rev 2, Mem @ 0xb0000000/16777216, 0xa0000000/268435456, I/O @ 0x00004000/64, BIOS @ 0x????????/131072 mai 23 13:46:21 endless gdm-Xorg-:0[3655]: (II) LoadModule: "glx" mai 23 13:46:21 endless gdm-Xorg-:0[3655]: (II) Loading /usr/lib/xorg/modules/extensions/libglx.so mai 23 13:46:21 endless systemd[3453]: Reached target Paths. mai 23 13:46:21 endless kernel: usbcore: registered new interface driver btusb mai 23 13:46:21 endless systemd[3453]: Reached target Timers. mai 23 13:46:21 endless systemd[3453]: Starting D-Bus User Message Bus Socket. mai 23 13:46:21 endless systemd[3453]: Listening on GnuPG network certificate management daemon. mai 23 13:46:21 endless systemd[3453]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). mai 23 13:46:21 endless systemd[3453]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). mai 23 13:46:21 endless systemd[3453]: Listening on GnuPG cryptographic agent (ssh-agent emulation). mai 23 13:46:21 endless systemd[3453]: Listening on GnuPG cryptographic agent and passphrase cache. mai 23 13:46:21 endless systemd[3453]: Listening on Sound System. mai 23 13:46:21 endless systemd[3453]: Reached target Bluetooth. mai 23 13:46:21 endless systemd[3453]: Listening on D-Bus User Message Bus Socket. mai 23 13:46:21 endless systemd[3453]: Reached target Sockets. mai 23 13:46:21 endless systemd[3453]: Reached target Basic System. mai 23 13:46:21 endless systemd[3453]: Starting Sound Service... mai 23 13:46:21 endless systemd[1]: Started User Manager for UID 1001. mai 23 13:46:21 endless systemd[1]: Starting Update Bluetooth adapter address... mai 23 13:46:21 endless systemd[1]: bluetooth-address-update.service: Succeeded. mai 23 13:46:21 endless systemd[1]: Started Update Bluetooth adapter address. mai 23 13:46:21 endless systemd[1]: Starting Bluetooth service... mai 23 13:46:21 endless bluetoothd[3770]: Bluetooth daemon 5.50 mai 23 13:46:21 endless systemd[1]: Started Bluetooth service. mai 23 13:46:21 endless systemd[1]: Reached target Bluetooth. mai 23 13:46:21 endless bluetoothd[3770]: Starting SDP server mai 23 13:46:21 endless kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 mai 23 13:46:21 endless kernel: Bluetooth: BNEP filters: protocol multicast mai 23 13:46:21 endless kernel: Bluetooth: BNEP socket layer initialized mai 23 13:46:21 endless bluetoothd[3770]: Bluetooth management interface 1.14 initialized mai 23 13:46:21 endless bluetoothd[3770]: Sap driver initialization failed. mai 23 13:46:21 endless bluetoothd[3770]: sap-server: Operation not permitted (1) mai 23 13:46:22 endless NetworkManager[1540]: [1590252382.0601] bluez: use BlueZ version 5 mai 23 13:46:22 endless NetworkManager[1540]: [1590252382.1367] bluez5: NAP: added interface 5C:C9:D3:DD:A0:CE mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) Module glx: vendor="X.Org Foundation" mai 23 13:46:22 endless gdm-Xorg-:0[3655]: compiled for 1.20.4, module version = 1.0.0 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: ABI class: X.Org Server Extension, version 10.0 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (==) Matched modesetting as autoconfigured driver 0 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (==) Matched fbdev as autoconfigured driver 1 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (==) Matched vesa as autoconfigured driver 2 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (==) Assigned the driver to the xf86ConfigLayout mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) LoadModule: "modesetting" mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) Module modesetting: vendor="X.Org Foundation" mai 23 13:46:22 endless gdm-Xorg-:0[3655]: compiled for 1.20.4, module version = 1.20.4 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: Module class: X.Org Video Driver mai 23 13:46:22 endless gdm-Xorg-:0[3655]: ABI class: X.Org Video Driver, version 24.0 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) LoadModule: "fbdev" mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) Module fbdev: vendor="X.Org Foundation" mai 23 13:46:22 endless gdm-Xorg-:0[3655]: compiled for 1.20.3, module version = 0.5.0 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: Module class: X.Org Video Driver mai 23 13:46:22 endless gdm-Xorg-:0[3655]: ABI class: X.Org Video Driver, version 24.0 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) LoadModule: "vesa" mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) Module vesa: vendor="X.Org Foundation" mai 23 13:46:22 endless gdm-Xorg-:0[3655]: compiled for 1.20.3, module version = 2.4.0 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: Module class: X.Org Video Driver mai 23 13:46:22 endless gdm-Xorg-:0[3655]: ABI class: X.Org Video Driver, version 24.0 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) modesetting: Driver for Modesetting Kernel Drivers: kms mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) FBDEV: driver for framebuffer: fbdev mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) VESA: driver for VESA chipsets: vesa mai 23 13:46:22 endless gdm-Xorg-:0[3655]: xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) modeset(0): using drv /dev/dri/card0 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (WW) Falling back to old probe method for fbdev mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) Loading sub module "fbdevhw" mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) LoadModule: "fbdevhw" mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) Loading /usr/lib/xorg/modules/libfbdevhw.so mai 23 13:46:22 endless kernel: Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) Module fbdevhw: vendor="X.Org Foundation" mai 23 13:46:22 endless gdm-Xorg-:0[3655]: compiled for 1.20.4, module version = 0.0.2 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: ABI class: X.Org Video Driver, version 24.0 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) modeset(0): Creating default Display subsection in Screen section mai 23 13:46:22 endless gdm-Xorg-:0[3655]: "Default Screen Section" for depth/fbbpp 24/32 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (==) modeset(0): Depth 24, (==) framebuffer bpp 32 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (==) modeset(0): RGB weight 888 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (==) modeset(0): Default visual is TrueColor mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) Loading sub module "glamoregl" mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) LoadModule: "glamoregl" mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so mai 23 13:46:22 endless gdm-Xorg-:0[3655]: (II) Module glamoregl: vendor="X.Org Foundation" mai 23 13:46:22 endless gdm-Xorg-:0[3655]: compiled for 1.20.4, module version = 1.0.1 mai 23 13:46:22 endless gdm-Xorg-:0[3655]: ABI class: X.Org ANSI C Emulation, version 0.4 mai 23 13:46:23 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.70' (uid=1001 pid=3747 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") mai 23 13:46:23 endless systemd[1]: Starting RealtimeKit Scheduling Policy Service... mai 23 13:46:23 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1' mai 23 13:46:23 endless systemd[1]: Started RealtimeKit Scheduling Policy Service. mai 23 13:46:23 endless rtkit-daemon[3835]: Successfully called chroot. mai 23 13:46:23 endless rtkit-daemon[3835]: Successfully dropped privileges. mai 23 13:46:23 endless rtkit-daemon[3835]: Successfully limited resources. mai 23 13:46:23 endless rtkit-daemon[3835]: Running. mai 23 13:46:23 endless rtkit-daemon[3835]: Canary thread running. mai 23 13:46:23 endless rtkit-daemon[3835]: Watchdog thread running. mai 23 13:46:23 endless gdm-Xorg-:0[3655]: (II) modeset(0): glamor X acceleration enabled on Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) mai 23 13:46:23 endless gdm-Xorg-:0[3655]: (II) modeset(0): glamor initialized mai 23 13:46:23 endless gdm-Xorg-:0[3655]: (II) modeset(0): Output eDP-1 has no monitor section mai 23 13:46:23 endless kernel: broken atomic modeset userspace detected, disabling atomic mai 23 13:46:23 endless gdm-Xorg-:0[3655]: (II) modeset(0): Output HDMI-1 has no monitor section mai 23 13:46:23 endless gdm-Xorg-:0[3655]: (II) modeset(0): EDID for output eDP-1 mai 23 13:46:23 endless gdm-Xorg-:0[3655]: (II) modeset(0): Manufacturer: CMN Model: 15dc Serial#: 0 mai 23 13:46:23 endless gdm-Xorg-:0[3655]: (II) modeset(0): Year: 2015 Week: 45 mai 23 13:46:23 endless gdm-Xorg-:0[3655]: (II) modeset(0): EDID Version: 1.4 mai 23 13:46:23 endless gdm-Xorg-:0[3655]: (II) modeset(0): Digital Display Input mai 23 13:46:23 endless gdm-Xorg-:0[3655]: (II) modeset(0): 6 bits per channel mai 23 13:46:23 endless gdm-Xorg-:0[3655]: (II) modeset(0): Digital interface is DisplayPort mai 23 13:46:23 endless gdm-Xorg-:0[3655]: (II) modeset(0): Max Image Size [cm]: horiz.: 34 vert.: 19 mai 23 13:46:23 endless gdm-Xorg-:0[3655]: (II) modeset(0): Gamma: 2.20 mai 23 13:46:23 endless gdm-Xorg-:0[3655]: (II) modeset(0): No DPMS capabilities specified mai 23 13:46:23 endless gdm-Xorg-:0[3655]: (II) modeset(0): Supported color encodings: RGB 4:4:4 mai 23 13:46:23 endless dbus-daemon[1538]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.93" (uid=1001 pid=3747 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=3770 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): First detailed timing is preferred mode mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Preferred mode is native pixel format and refresh rate mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): redX: 0.569 redY: 0.332 greenX: 0.328 greenY: 0.581 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): blueX: 0.163 blueY: 0.147 whiteX: 0.313 whiteY: 0.329 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Manufacturer's mask: 0 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Supported detailed timing: mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): clock: 76.4 MHz Image Size: 344 x 193 mm mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): h_active: 1366 h_sync: 1434 h_sync_end 1479 h_blank_end 1592 h_border: 0 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): v_active: 768 v_sync: 772 v_sync_end 779 v_blanking: 800 v_border: 0 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): N156BGA-EB2 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): CMN mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): N156BGA-EB2 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): EDID (in hex): mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): 00ffffffffffff000daedc1500000000 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): 2d1901049522137802c3f59155549429 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): 25505400000001010101010101010101 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): 010101010101da1d56e250002030442d mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): 470058c110000018000000fe004e3135 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): 364247412d4542320a20000000fe0043 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): 4d4e0a202020202020202020000000fe mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): 004e3135364247412d4542320a2000f1 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Printing probed modes for output eDP-1 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "1366x768"x60.0 76.42 1366 1434 1479 1592 768 772 779 800 -hsync -vsync (48.0 kHz eP) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "1360x768"x59.8 84.75 1360 1432 1568 1776 768 771 781 798 -hsync +vsync (47.7 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "1360x768"x60.0 72.00 1360 1408 1440 1520 768 771 781 790 +hsync -vsync (47.4 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "1280x720"x120.0 156.12 1280 1376 1512 1744 720 721 724 746 doublescan -hsync +vsync (89.5 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "1280x720"x120.0 120.75 1280 1304 1320 1360 720 721 724 740 doublescan +hsync -vsync (88.8 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "1280x720"x59.9 74.50 1280 1344 1472 1664 720 723 728 748 -hsync +vsync (44.8 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "1280x720"x59.7 63.75 1280 1328 1360 1440 720 723 728 741 +hsync -vsync (44.3 kHz d) mai 23 13:46:23 endless systemd[3453]: Started D-Bus User Message Bus. mai 23 13:46:23 endless rtkit-daemon[3835]: Supervising 0 threads of 0 processes of 1 users. mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "1024x768"x120.1 133.47 1024 1100 1212 1400 768 768 770 794 doublescan -hsync +vsync (95.3 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "960x720"x120.0 117.00 960 1024 1128 1300 720 720 722 750 doublescan -hsync +vsync (90.0 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "928x696"x120.1 109.15 928 976 1088 1264 696 696 698 719 doublescan -hsync +vsync (86.4 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "896x672"x120.0 102.40 896 960 1060 1224 672 672 674 697 doublescan -hsync +vsync (83.7 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "1024x576"x119.9 98.50 1024 1092 1200 1376 576 577 580 597 doublescan -hsync +vsync (71.6 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "1024x576"x119.9 78.38 1024 1048 1064 1104 576 577 580 592 doublescan +hsync -vsync (71.0 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "1024x576"x59.9 46.50 1024 1064 1160 1296 576 579 584 599 -hsync +vsync (35.9 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "1024x576"x59.8 42.00 1024 1072 1104 1184 576 579 584 593 +hsync -vsync (35.5 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "960x600"x119.9 96.62 960 1028 1128 1296 600 601 604 622 doublescan -hsync +vsync (74.6 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "960x600"x120.0 77.00 960 984 1000 1040 600 601 604 617 doublescan +hsync -vsync (74.0 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "960x540"x119.9 86.50 960 1024 1124 1288 540 541 544 560 doublescan -hsync +vsync (67.2 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "960x540"x120.0 69.25 960 984 1000 1040 540 541 544 555 doublescan +hsync -vsync (66.6 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "960x540"x59.6 40.75 960 992 1088 1216 540 543 548 562 -hsync +vsync (33.5 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "960x540"x59.8 37.25 960 1008 1040 1120 540 543 548 556 +hsync -vsync (33.3 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "800x600"x120.0 81.00 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (75.0 kHz d) mai 23 13:46:23 endless rtkit-daemon[3835]: Supervising 0 threads of 0 processes of 1 users. mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "840x525"x120.0 73.12 840 892 980 1120 525 526 529 544 doublescan -hsync +vsync (65.3 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "840x525"x119.8 59.50 840 864 880 920 525 526 529 540 doublescan +hsync -vsync (64.7 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "864x486"x59.9 32.50 864 888 968 1072 486 489 494 506 -hsync +vsync (30.3 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "864x486"x59.6 30.50 864 912 944 1024 486 489 494 500 +hsync -vsync (29.8 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "800x512"x120.3 51.56 800 800 828 832 512 512 514 515 doublescan +hsync +vsync (62.0 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "700x525"x120.0 61.00 700 744 820 940 525 526 532 541 doublescan +hsync +vsync (64.9 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "800x450"x119.9 59.12 800 848 928 1056 450 451 454 467 doublescan -hsync +vsync (56.0 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "800x450"x119.6 48.75 800 824 840 880 450 451 454 463 doublescan +hsync -vsync (55.4 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "640x512"x120.0 54.00 640 664 720 844 512 512 514 533 doublescan +hsync +vsync (64.0 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "720x450"x119.8 53.25 720 760 836 952 450 451 454 467 doublescan -hsync +vsync (55.9 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "700x450"x119.9 51.75 700 740 812 924 450 451 456 467 doublescan -hsync +vsync (56.0 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "700x450"x119.8 43.25 700 724 740 780 450 451 456 463 doublescan +hsync -vsync (55.4 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "640x480"x120.0 54.00 640 688 744 900 480 480 482 500 doublescan +hsync +vsync (60.0 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "720x405"x59.5 22.50 720 744 808 896 405 408 413 422 -hsync +vsync (25.1 kHz d) mai 23 13:46:23 endless rtkit-daemon[3835]: Supervising 0 threads of 0 processes of 1 users. mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "720x405"x59.0 21.75 720 768 800 880 405 408 413 419 +hsync -vsync (24.7 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "684x384"x119.8 42.62 684 720 788 892 384 385 390 399 doublescan -hsync +vsync (47.8 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "684x384"x119.7 36.12 684 708 724 764 384 385 390 395 doublescan +hsync -vsync (47.3 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "680x384"x119.6 42.38 680 716 784 888 384 385 390 399 doublescan -hsync +vsync (47.7 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "680x384"x119.9 36.00 680 704 720 760 384 385 390 395 doublescan +hsync -vsync (47.4 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "640x400"x119.8 41.75 640 676 740 840 400 401 404 415 doublescan -hsync +vsync (49.7 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "640x400"x120.0 35.50 640 664 680 720 400 401 404 411 doublescan +hsync -vsync (49.3 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "576x432"x120.1 40.81 576 608 668 760 432 432 434 447 doublescan -hsync +vsync (53.7 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "640x360"x119.7 37.25 640 672 736 832 360 361 364 374 doublescan -hsync +vsync (44.8 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "640x360"x119.7 31.88 640 664 680 720 360 361 364 370 doublescan +hsync -vsync (44.3 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "640x360"x59.8 18.00 640 664 720 800 360 363 368 376 -hsync +vsync (22.5 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "640x360"x59.3 17.75 640 688 720 800 360 363 368 374 +hsync -vsync (22.2 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "512x384"x120.0 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (48.4 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "512x288"x120.0 23.25 512 532 580 648 288 289 292 299 doublescan -hsync +vsync (35.9 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "512x288"x119.8 21.00 512 536 552 592 288 289 292 296 doublescan +hsync -vsync (35.5 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "480x270"x119.3 20.38 480 496 544 608 270 271 274 281 doublescan -hsync +vsync (33.5 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "480x270"x119.6 18.62 480 504 520 560 270 271 274 278 doublescan +hsync -vsync (33.3 kHz d) mai 23 13:46:23 endless rtkit-daemon[3835]: Supervising 0 threads of 0 processes of 1 users. mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "400x300"x120.6 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (37.9 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "400x300"x112.7 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (35.2 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "432x243"x119.8 16.25 432 444 484 536 243 244 247 253 doublescan -hsync +vsync (30.3 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "432x243"x119.1 15.25 432 456 472 512 243 244 247 250 doublescan +hsync -vsync (29.8 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "320x240"x120.1 12.59 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (31.5 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "360x202"x119.0 11.25 360 372 404 448 202 204 206 211 doublescan -hsync +vsync (25.1 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "360x202"x118.3 10.88 360 384 400 440 202 204 206 209 doublescan +hsync -vsync (24.7 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "320x180"x119.7 9.00 320 332 360 400 180 181 184 188 doublescan -hsync +vsync (22.5 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "320x180"x118.6 8.88 320 344 360 400 180 181 184 187 doublescan +hsync -vsync (22.2 kHz d) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): EDID for output HDMI-1 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Output eDP-1 connected mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Output HDMI-1 disconnected mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Using exact sizes for initial modes mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) modeset(0): Output eDP-1 using initial mode 1366x768 +0+0 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (==) modeset(0): DPI set to (96, 96) mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) Loading sub module "fb" mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) LoadModule: "fb" mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) Loading /usr/lib/xorg/modules/libfb.so mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) Module fb: vendor="X.Org Foundation" mai 23 13:46:24 endless gdm-Xorg-:0[3655]: compiled for 1.20.4, module version = 1.0.0 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: ABI class: X.Org ANSI C Emulation, version 0.4 mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) UnloadModule: "fbdev" mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) Unloading fbdev mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) UnloadSubModule: "fbdevhw" mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) Unloading fbdevhw mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) UnloadModule: "vesa" mai 23 13:46:24 endless gdm-Xorg-:0[3655]: (II) Unloading vesa mai 23 13:46:23 endless rtkit-daemon[3835]: Supervising 0 threads of 0 processes of 1 users. mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (==) modeset(0): Backing store enabled mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (==) modeset(0): Silken mouse enabled mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) modeset(0): Initializing kms color map for depth 24, 8 bpc. mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (==) modeset(0): DPMS enabled mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) modeset(0): [DRI2] Setup complete mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) modeset(0): [DRI2] DRI driver: i965 mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) modeset(0): [DRI2] VDPAU driver: i965 mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension Generic Event Extension mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension SHAPE mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension MIT-SHM mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension XInputExtension mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension XTEST mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension BIG-REQUESTS mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension SYNC mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension XKEYBOARD mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension XC-MISC mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension SECURITY mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension XFIXES mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension RENDER mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension RANDR mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension COMPOSITE mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension DAMAGE mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension MIT-SCREEN-SAVER mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension DOUBLE-BUFFER mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension RECORD mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension DPMS mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension Present mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension DRI3 mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension X-Resource mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension XVideo mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension XVideo-MotionCompensation mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension SELinux mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) SELinux: Disabled on system mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension GLX mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) AIGLX: Loaded and initialized i965 mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) GLX: Initialized DRI2 GL provider for screen 0 mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension XFree86-VidModeExtension mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension XFree86-DGA mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension XFree86-DRI mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) Initializing extension DRI2 mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) modeset(0): Damage tracking initialized mai 23 13:46:25 endless gdm-Xorg-:0[3655]: (II) modeset(0): Setting screen physical size to 361 x 203 mai 23 13:46:27 endless systemd[1]: NetworkManager-dispatcher.service: Succeeded. mai 23 13:46:32 endless kernel: videodev: Linux video capture interface: v2.00 mai 23 13:46:32 endless systemd[3453]: Started Sound Service. mai 23 13:46:32 endless systemd[3453]: Reached target Main User Target. mai 23 13:46:32 endless pulseaudio[3747]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.93" (uid=1001 pid=3747 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=3770 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") mai 23 13:46:32 endless systemd[3453]: Startup finished in 15.264s. mai 23 13:46:33 endless kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database mai 23 13:46:33 endless kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' mai 23 13:46:33 endless kernel: r8169 0000:01:00.1: can't disable ASPM; OS doesn't have ASPM control mai 23 13:46:33 endless NetworkManager[1540]: [1590252393.1821] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) mai 23 13:46:33 endless kernel: libphy: r8169: probed mai 23 13:46:33 endless kernel: r8169 0000:01:00.1 eth0: RTL8411b, 98:29:a6:e7:43:08, XID 5c8, IRQ 130 mai 23 13:46:33 endless kernel: r8169 0000:01:00.1 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] mai 23 13:46:33 endless systemd-udevd[392]: Using default interface naming scheme 'v243'. mai 23 13:46:33 endless systemd-udevd[392]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. mai 23 13:46:33 endless kernel: r8169 0000:01:00.1 enp1s0f1: renamed from eth0 mai 23 13:46:33 endless NetworkManager[1540]: [1590252393.2033] device (eth0): interface index 2 renamed iface from 'eth0' to 'enp1s0f1' mai 23 13:46:33 endless kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 mai 23 13:46:33 endless kernel: cfg80211: failed to load regulatory.db mai 23 13:46:33 endless NetworkManager[1540]: [1590252393.2566] device (enp1s0f1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') mai 23 13:46:33 endless systemd-udevd[381]: Using default interface naming scheme 'v243'. mai 23 13:46:33 endless kernel: Generic FE-GE Realtek PHY r8169-101:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-101:00, irq=IGNORE) mai 23 13:46:33 endless kernel: r8169 0000:01:00.1 enp1s0f1: Link is Down mai 23 13:46:33 endless NetworkManager[1540]: [1590252393.4349] keyfile: add connection /run/NetworkManager/system-connections/Conexão cabeada 1.nmconnection (e1490ef1-ddb5-3bac-9c40-416c87bd6d18,"Conexão cabeada 1") mai 23 13:46:33 endless NetworkManager[1540]: [1590252393.4363] settings: (enp1s0f1): created default wired connection 'Conexão cabeada 1' mai 23 13:46:33 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.21' (uid=0 pid=1540 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") mai 23 13:46:33 endless systemd[1]: Starting Network Manager Script Dispatcher Service... mai 23 13:46:33 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' mai 23 13:46:33 endless systemd[1]: Started Network Manager Script Dispatcher Service. mai 23 13:46:33 endless nm-dispatcher[3932]: req:1 'connectivity-change': new request (5 scripts) mai 23 13:46:33 endless nm-dispatcher[3932]: req:1 'connectivity-change': start running ordered scripts... mai 23 13:46:34 endless kernel: uvcvideo: Found UVC 1.00 device HD User Facing (0408:a061) mai 23 13:46:34 endless kernel: uvcvideo 1-7:1.0: Entity type for entity Extension 4 was not initialized! mai 23 13:46:34 endless kernel: uvcvideo 1-7:1.0: Entity type for entity Extension 3 was not initialized! mai 23 13:46:34 endless kernel: uvcvideo 1-7:1.0: Entity type for entity Processing 2 was not initialized! mai 23 13:46:34 endless kernel: uvcvideo 1-7:1.0: Entity type for entity Camera 1 was not initialized! mai 23 13:46:34 endless kernel: input: HD User Facing: HD User Facing as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/input/input14 mai 23 13:46:34 endless kernel: usbcore: registered new interface driver uvcvideo mai 23 13:46:34 endless kernel: USB Video Class driver (1.1.1) mai 23 13:46:34 endless eos-phone-home[1730]: INFO:__main__:Already activated! mai 23 13:46:34 endless eos-phone-home[1730]: INFO:__main__:Getting variable: live mai 23 13:46:34 endless eos-phone-home[1730]: INFO:__main__:Getting variable: cmdline mai 23 13:46:34 endless eos-phone-home[1730]: INFO:__main__: - Cmdline: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-94c993d319cdf01ff15a7624dd6855cc9ebe14d7b40f3077a1e965a0de360d8e/vmlinuz-5.4.0-19-generic root=UUID=05c7cd5b-40f9-47d7-a032-e98150535435 rw splash plymouth.ignore-serial-consoles quiet loglevel=2 ostree=/ostree/boot.1/eos/94c993d319cdf01ff15a7624dd6855cc9ebe14d7b40f3077a1e965a0de360d8e/0 mai 23 13:46:34 endless eos-phone-home[1730]: INFO:__main__:Count age: 45686.340034246445 mai 23 13:46:34 endless eos-phone-home[1730]: INFO:__main__:Ping not due yet. mai 23 13:46:34 endless systemd[1]: eos-phone-home.service: Succeeded. mai 23 13:46:34 endless kernel: ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 mai 23 13:46:34 endless kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) mai 23 13:46:34 endless kernel: RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer mai 23 13:46:34 endless kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules mai 23 13:46:34 endless kernel: RAPL PMU: hw unit of domain package 2^-14 Joules mai 23 13:46:34 endless kernel: RAPL PMU: hw unit of domain dram 2^-14 Joules mai 23 13:46:34 endless kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules mai 23 13:46:34 endless kernel: RAPL PMU: hw unit of domain psys 2^-14 Joules mai 23 13:46:34 endless kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker mai 23 13:46:34 endless kernel: snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) mai 23 13:46:34 endless kernel: snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) mai 23 13:46:34 endless kernel: snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0 mai 23 13:46:34 endless kernel: snd_hda_codec_realtek hdaudioC0D0: inputs: mai 23 13:46:34 endless kernel: snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 mai 23 13:46:34 endless kernel: snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 mai 23 13:46:34 endless kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5 mai 23 13:46:34 endless kernel: pcieport 0000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) mai 23 13:46:34 endless kernel: pcieport 0000:00:1c.5: AER: device [8086:9d15] error status/mask=00000041/00002000 mai 23 13:46:34 endless kernel: pcieport 0000:00:1c.5: AER: [ 0] RxErr mai 23 13:46:34 endless kernel: pcieport 0000:00:1c.5: AER: [ 6] BadTLP mai 23 13:46:34 endless kernel: input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input15 mai 23 13:46:34 endless kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input16 mai 23 13:46:34 endless kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17 mai 23 13:46:34 endless kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18 mai 23 13:46:34 endless kernel: input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input19 mai 23 13:46:34 endless kernel: input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input20 mai 23 13:46:34 endless systemd[3453]: Reached target Sound Card. mai 23 13:46:34 endless systemd[1]: Reached target Sound Card. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device Acer Wireless Radio Control (/dev/input/event6) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Acer Wireless Radio Control: Applying InputClass "libinput keyboard catchall" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) LoadModule: "libinput" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) Module libinput: vendor="X.Org Foundation" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: compiled for 1.20.3, module version = 0.28.2 mai 23 13:46:34 endless gdm-Xorg-:0[3655]: Module class: X.Org XInput Driver mai 23 13:46:34 endless gdm-Xorg-:0[3655]: ABI class: X.Org XInput driver, version 24.1 mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) Using input driver 'libinput' for 'Acer Wireless Radio Control' mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Acer Wireless Radio Control: always reports core events mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "Device" "/dev/input/event6" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "_source" "server/udev" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event6 - Acer Wireless Radio Control: is tagged by udev as: Keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event6 - Acer Wireless Radio Control: device is a keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event6 - Acer Wireless Radio Control: device removed mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/10251229:00/input/input6/event6" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) XINPUT: Adding extended input device "Acer Wireless Radio Control" (type: KEYBOARD, id 6) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "xkb_layout" "br" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event6 - Acer Wireless Radio Control: is tagged by udev as: Keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event6 - Acer Wireless Radio Control: device is a keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device Power Button (/dev/input/event3) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Power Button: Applying InputClass "libinput keyboard catchall" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) Using input driver 'libinput' for 'Power Button' mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Power Button: always reports core events mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "Device" "/dev/input/event3" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "_source" "server/udev" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event3 - Power Button: is tagged by udev as: Keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event3 - Power Button: device is a keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event3 - Power Button: device removed mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "xkb_layout" "br" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event3 - Power Button: is tagged by udev as: Keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event3 - Power Button: device is a keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device Video Bus (/dev/input/event5) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Video Bus: Applying InputClass "libinput keyboard catchall" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) Using input driver 'libinput' for 'Video Bus' mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Video Bus: always reports core events mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "Device" "/dev/input/event5" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "_source" "server/udev" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event5 - Video Bus: is tagged by udev as: Keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event5 - Video Bus: device is a keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event5 - Video Bus: device removed mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5/event5" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "xkb_layout" "br" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event5 - Video Bus: is tagged by udev as: Keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event5 - Video Bus: device is a keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device Lid Switch (/dev/input/event0) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) No input driver specified, ignoring this device. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) This device may have been added with another device file. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device Power Button (/dev/input/event2) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Power Button: Applying InputClass "libinput keyboard catchall" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) Using input driver 'libinput' for 'Power Button' mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Power Button: always reports core events mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "Device" "/dev/input/event2" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "_source" "server/udev" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event2 - Power Button: is tagged by udev as: Keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event2 - Power Button: device is a keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event2 - Power Button: device removed mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event2" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 9) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "xkb_layout" "br" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event2 - Power Button: is tagged by udev as: Keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event2 - Power Button: device is a keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device Sleep Button (/dev/input/event1) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Sleep Button: Applying InputClass "libinput keyboard catchall" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) Using input driver 'libinput' for 'Sleep Button' mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Sleep Button: always reports core events mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "Device" "/dev/input/event1" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "_source" "server/udev" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event1 - Sleep Button: is tagged by udev as: Keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event1 - Sleep Button: device is a keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event1 - Sleep Button: device removed mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1/event1" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 10) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "xkb_layout" "br" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event1 - Sleep Button: is tagged by udev as: Keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event1 - Sleep Button: device is a keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device HD User Facing: HD User Facing (/dev/input/event10) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) HD User Facing: HD User Facing: Applying InputClass "libinput keyboard catchall" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) Using input driver 'libinput' for 'HD User Facing: HD User Facing' mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) HD User Facing: HD User Facing: always reports core events mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "Device" "/dev/input/event10" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "_source" "server/udev" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event10 - HD User Facing: HD User Facing: is tagged by udev as: Keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event10 - HD User Facing: HD User Facing: device is a keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event10 - HD User Facing: HD User Facing: device removed mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/input/input14/event10" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) XINPUT: Adding extended input device "HD User Facing: HD User Facing" (type: KEYBOARD, id 11) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "xkb_layout" "br" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event10 - HD User Facing: HD User Facing: is tagged by udev as: Keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event10 - HD User Facing: HD User Facing: device is a keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device SYNA7DB5:01 06CB:7DB7 Mouse (/dev/input/event8) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) SYNA7DB5:01 06CB:7DB7 Mouse: Applying InputClass "libinput pointer catchall" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) Using input driver 'libinput' for 'SYNA7DB5:01 06CB:7DB7 Mouse' mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) SYNA7DB5:01 06CB:7DB7 Mouse: always reports core events mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "Device" "/dev/input/event8" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "_source" "server/udev" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event8 - SYNA7DB5:01 06CB:7DB7 Mouse: is tagged by udev as: Mouse mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event8 - SYNA7DB5:01 06CB:7DB7 Mouse: device is a pointer mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event8 - SYNA7DB5:01 06CB:7DB7 Mouse: device removed mai 23 13:46:34 endless kernel: ath10k_pci 0000:02:00.0: qca9377 hw1.1 target 0x05020001 chip_id 0x003821ff sub 11ad:08a6 mai 23 13:46:34 endless kernel: ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 mai 23 13:46:34 endless kernel: ath10k_pci 0000:02:00.0: firmware ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877 mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-SYNA7DB5:01/0018:06CB:7DB7.0001/input/input11/event8" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) XINPUT: Adding extended input device "SYNA7DB5:01 06CB:7DB7 Mouse" (type: MOUSE, id 12) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "AccelerationScheme" "none" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) SYNA7DB5:01 06CB:7DB7 Mouse: (accel) selected scheme none/0 mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) SYNA7DB5:01 06CB:7DB7 Mouse: (accel) acceleration factor: 2.000 mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) SYNA7DB5:01 06CB:7DB7 Mouse: (accel) acceleration threshold: 4 mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event8 - SYNA7DB5:01 06CB:7DB7 Mouse: is tagged by udev as: Mouse mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event8 - SYNA7DB5:01 06CB:7DB7 Mouse: device is a pointer mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device SYNA7DB5:01 06CB:7DB7 Mouse (/dev/input/mouse0) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) No input driver specified, ignoring this device. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) This device may have been added with another device file. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device SYNA7DB5:01 06CB:7DB7 Touchpad (/dev/input/event9) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) SYNA7DB5:01 06CB:7DB7 Touchpad: Applying InputClass "libinput touchpad catchall" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) Using input driver 'libinput' for 'SYNA7DB5:01 06CB:7DB7 Touchpad' mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) SYNA7DB5:01 06CB:7DB7 Touchpad: always reports core events mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "Device" "/dev/input/event9" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "_source" "server/udev" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event9 - SYNA7DB5:01 06CB:7DB7 Touchpad: is tagged by udev as: Touchpad mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event9 - SYNA7DB5:01 06CB:7DB7 Touchpad: device is a touchpad mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event9 - SYNA7DB5:01 06CB:7DB7 Touchpad: device removed mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-SYNA7DB5:01/0018:06CB:7DB7.0001/input/input12/event9" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) XINPUT: Adding extended input device "SYNA7DB5:01 06CB:7DB7 Touchpad" (type: TOUCHPAD, id 13) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "AccelerationScheme" "none" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) SYNA7DB5:01 06CB:7DB7 Touchpad: (accel) selected scheme none/0 mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) SYNA7DB5:01 06CB:7DB7 Touchpad: (accel) acceleration factor: 2.000 mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) SYNA7DB5:01 06CB:7DB7 Touchpad: (accel) acceleration threshold: 4 mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event9 - SYNA7DB5:01 06CB:7DB7 Touchpad: is tagged by udev as: Touchpad mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event9 - SYNA7DB5:01 06CB:7DB7 Touchpad: device is a touchpad mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device SYNA7DB5:01 06CB:7DB7 Touchpad (/dev/input/mouse1) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) No input driver specified, ignoring this device. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) This device may have been added with another device file. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event11) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) No input driver specified, ignoring this device. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) This device may have been added with another device file. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event12) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) No input driver specified, ignoring this device. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) This device may have been added with another device file. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event13) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) No input driver specified, ignoring this device. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) This device may have been added with another device file. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event14) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) No input driver specified, ignoring this device. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) This device may have been added with another device file. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=9 (/dev/input/event15) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) No input driver specified, ignoring this device. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) This device may have been added with another device file. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=10 (/dev/input/event16) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) No input driver specified, ignoring this device. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) This device may have been added with another device file. mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event4) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard' mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) AT Translated Set 2 keyboard: always reports core events mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "Device" "/dev/input/event4" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "_source" "server/udev" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event4 - AT Translated Set 2 keyboard: device is a keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event4 - AT Translated Set 2 keyboard: device removed mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input4/event4" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 14) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "xkb_layout" "br" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event4 - AT Translated Set 2 keyboard: device is a keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device Acer WMI hotkeys (/dev/input/event7) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Acer WMI hotkeys: Applying InputClass "libinput keyboard catchall" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) Using input driver 'libinput' for 'Acer WMI hotkeys' mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Acer WMI hotkeys: always reports core events mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "Device" "/dev/input/event7" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "_source" "server/udev" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event7 - Acer WMI hotkeys: is tagged by udev as: Keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event7 - Acer WMI hotkeys: device is a keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event7 - Acer WMI hotkeys: device removed mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "config_info" "udev:/sys/devices/virtual/input/input7/event7" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) XINPUT: Adding extended input device "Acer WMI hotkeys" (type: KEYBOARD, id 15) mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (**) Option "xkb_layout" "br" mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event7 - Acer WMI hotkeys: is tagged by udev as: Keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event7 - Acer WMI hotkeys: device is a keyboard mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) config/udev: removing device HD User Facing: HD User Facing mai 23 13:46:34 endless gdm-Xorg-:0[3655]: (II) event10 - HD User Facing: HD User Facing: device removed mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) UnloadModule: "libinput" mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device HD User Facing: HD User Facing (/dev/input/event10) mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (**) HD User Facing: HD User Facing: Applying InputClass "libinput keyboard catchall" mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) Using input driver 'libinput' for 'HD User Facing: HD User Facing' mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (**) HD User Facing: HD User Facing: always reports core events mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (**) Option "Device" "/dev/input/event10" mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (**) Option "_source" "server/udev" mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) event10 - HD User Facing: HD User Facing: is tagged by udev as: Keyboard mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) event10 - HD User Facing: HD User Facing: device is a keyboard mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) event10 - HD User Facing: HD User Facing: device removed mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/input/input14/event10" mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) XINPUT: Adding extended input device "HD User Facing: HD User Facing" (type: KEYBOARD, id 11) mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (**) Option "xkb_layout" "br" mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) event10 - HD User Facing: HD User Facing: is tagged by udev as: Keyboard mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) event10 - HD User Facing: HD User Facing: device is a keyboard mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event12) mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) No input driver specified, ignoring this device. mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) This device may have been added with another device file. mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=9 (/dev/input/event15) mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) No input driver specified, ignoring this device. mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) This device may have been added with another device file. mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event13) mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) No input driver specified, ignoring this device. mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) This device may have been added with another device file. mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event11) mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) No input driver specified, ignoring this device. mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) This device may have been added with another device file. mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event14) mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) No input driver specified, ignoring this device. mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) This device may have been added with another device file. mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=10 (/dev/input/event16) mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) No input driver specified, ignoring this device. mai 23 13:46:35 endless gdm-Xorg-:0[3655]: (II) This device may have been added with another device file. mai 23 13:46:35 endless systemd-udevd[368]: controlC0: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99. mai 23 13:46:35 endless kernel: ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 8aedfa4a mai 23 13:46:35 endless kernel: cryptd: max_cpu_qlen set to 1000 mai 23 13:46:35 endless kernel: ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536 mai 23 13:46:35 endless kernel: ath10k_pci 0000:02:00.0: htt-ver 3.56 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 mai 23 13:46:35 endless NetworkManager[1540]: [1590252395.2997] wifi-nl80211: (wlan0): using nl80211 for WiFi device control mai 23 13:46:35 endless NetworkManager[1540]: [1590252395.3000] device (wlan0): driver supports Access Point (AP) mode mai 23 13:46:35 endless systemd-udevd[373]: Using default interface naming scheme 'v243'. mai 23 13:46:35 endless NetworkManager[1540]: [1590252395.3007] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/3) mai 23 13:46:35 endless systemd-udevd[373]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. mai 23 13:46:35 endless kernel: ath: EEPROM regdomain: 0x69 mai 23 13:46:35 endless kernel: ath: EEPROM indicates we should expect a direct regpair map mai 23 13:46:35 endless kernel: ath: Country alpha2 being used: 00 mai 23 13:46:35 endless kernel: ath: Regpair used: 0x69 mai 23 13:46:35 endless kernel: ath10k_pci 0000:02:00.0 wlp2s0: renamed from wlan0 mai 23 13:46:35 endless NetworkManager[1540]: [1590252395.3043] supplicant: wpa_supplicant running mai 23 13:46:35 endless NetworkManager[1540]: [1590252395.3193] device (wlan0): interface index 3 renamed iface from 'wlan0' to 'wlp2s0' mai 23 13:46:35 endless NetworkManager[1540]: [1590252395.3297] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: device [8086:9d15] error status/mask=00000081/00002000 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: [ 0] RxErr mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: [ 7] BadDLLP mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: can't find device of ID00e5 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: can't find device of ID00e5 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: can't find device of ID00e5 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: can't find device of ID00e5 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: can't find device of ID00e5 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: can't find device of ID00e5 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: can't find device of ID00e5 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: device [8086:9d15] error status/mask=00000001/00002000 mai 23 13:46:35 endless kernel: pcieport 0000:00:1c.5: AER: [ 0] RxErr mai 23 13:46:35 endless kernel: AVX2 version of gcm_enc/dec engaged. mai 23 13:46:35 endless kernel: AES CTR mode by8 optimization enabled mai 23 13:46:35 endless kernel: ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536 mai 23 13:46:35 endless NetworkManager[1540]: [1590252395.5842] Error: failed to open /run/network/ifstate mai 23 13:46:35 endless NetworkManager[1540]: [1590252395.6031] rfkill3: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0/ieee80211/phy0/rfkill3) (driver ath10k_pci) mai 23 13:46:35 endless gdm-launch-environment][4093]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0) mai 23 13:46:35 endless systemd[1]: Created slice User Slice of UID 109. mai 23 13:46:35 endless systemd[1]: Starting User Runtime Directory /run/user/109... mai 23 13:46:35 endless systemd-logind[1824]: New session c1 of user Debian-gdm. mai 23 13:46:35 endless systemd[1]: Started User Runtime Directory /run/user/109. mai 23 13:46:35 endless systemd[1]: Starting User Manager for UID 109... mai 23 13:46:35 endless systemd[4149]: pam_unix(systemd-user:session): session opened for user Debian-gdm by (uid=0) mai 23 13:46:35 endless ModemManager[1532]: Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.1': not supported by any plugin mai 23 13:46:35 endless NetworkManager[1540]: [1590252395.7954] sup-iface[0x55a71ef70980,wlp2s0]: supports 5 scan SSIDs mai 23 13:46:35 endless NetworkManager[1540]: [1590252395.7966] device (wlp2s0): supplicant interface state: starting -> ready mai 23 13:46:35 endless NetworkManager[1540]: [1590252395.7966] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') mai 23 13:46:36 endless systemd[4149]: Reached target Paths. mai 23 13:46:36 endless systemd[4149]: Reached target Timers. mai 23 13:46:36 endless systemd[4149]: Starting D-Bus User Message Bus Socket. mai 23 13:46:36 endless systemd[4149]: Listening on GnuPG network certificate management daemon. mai 23 13:46:36 endless systemd[4149]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). mai 23 13:46:36 endless systemd[4149]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). mai 23 13:46:36 endless systemd[4149]: Listening on GnuPG cryptographic agent (ssh-agent emulation). mai 23 13:46:36 endless systemd[4149]: Listening on GnuPG cryptographic agent and passphrase cache. mai 23 13:46:36 endless systemd[4149]: Listening on Sound System. mai 23 13:46:36 endless systemd[4149]: Listening on D-Bus User Message Bus Socket. mai 23 13:46:36 endless systemd[4149]: Reached target Sockets. mai 23 13:46:36 endless systemd[4149]: Reached target Basic System. mai 23 13:46:36 endless systemd[1]: Started User Manager for UID 109. mai 23 13:46:36 endless systemd[4149]: Starting Sound Service... mai 23 13:46:36 endless systemd[1]: Started Session c1 of user Debian-gdm. mai 23 13:46:36 endless rtkit-daemon[3835]: Successfully made thread 4250 of process 4250 (n/a) owned by '109' high priority at nice level -11. mai 23 13:46:36 endless rtkit-daemon[3835]: Supervising 1 threads of 1 processes of 2 users. mai 23 13:46:36 endless systemd[4149]: Started D-Bus User Message Bus. mai 23 13:46:36 endless wpa_supplicant[3673]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN mai 23 13:46:36 endless wpa_supplicant[3673]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN mai 23 13:46:37 endless dbus-daemon[4263]: [session uid=109 pid=4263] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.2' (uid=109 pid=4293 comm="/usr/libexec/gnome-session-check-accelerated " label="unconfined") mai 23 13:46:37 endless systemd[4149]: Starting Accessibility services bus... mai 23 13:46:37 endless dbus-daemon[4263]: [session uid=109 pid=4263] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=109 pid=4299 comm="/usr/libexec/at-spi-bus-launcher " label="unconfined") mai 23 13:46:37 endless systemd[4149]: Starting Virtual filesystem service... mai 23 13:46:37 endless ModemManager[1532]: Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0': not supported by any plugin mai 23 13:46:37 endless dbus-daemon[4263]: [session uid=109 pid=4263] Successfully activated service 'org.gtk.vfs.Daemon' mai 23 13:46:37 endless systemd[4149]: Started Virtual filesystem service. mai 23 13:46:37 endless dbus-daemon[4263]: [session uid=109 pid=4263] Successfully activated service 'org.a11y.Bus' mai 23 13:46:37 endless systemd[4149]: Started Accessibility services bus. mai 23 13:46:38 endless systemd[4149]: Created slice gnome\x2dsession\x2dmanager.slice. mai 23 13:46:38 endless systemd[4149]: Starting Monitor Session leader for GNOME Session... mai 23 13:46:38 endless systemd[4149]: Started OpenSSH Agent. mai 23 13:46:38 endless systemd[4149]: Reached target Session services which should run early before the graphical session is brought up. mai 23 13:46:38 endless systemd[4149]: Starting Tracker metadata extractor... mai 23 13:46:38 endless systemd[4149]: Starting Tracker file system data miner... mai 23 13:46:39 endless gnome-session-c[4338]: Error creating FIFO: Arquivo existe mai 23 13:46:39 endless systemd[4149]: Started Monitor Session leader for GNOME Session. mai 23 13:46:39 endless systemd[4149]: Reached target Tasks to be run before GNOME Session starts. mai 23 13:46:39 endless systemd[4149]: Starting GNOME Session Manager (session: gnome-login)... mai 23 13:46:39 endless agent-launch[4343]: dbus-update-activation-environment: setting SSH_AUTH_SOCK=/run/user/109/openssh_agent mai 23 13:46:39 endless agent-launch[4343]: dbus-update-activation-environment: setting SSH_AGENT_LAUNCHER=openssh mai 23 13:46:39 endless agent-launch[4339]: SSH_AUTH_SOCK=/run/user/109/openssh_agent; export SSH_AUTH_SOCK; mai 23 13:46:39 endless agent-launch[4339]: echo Agent pid 4339; mai 23 13:46:39 endless tracker-miner-f[4341]: Set scheduler policy to SCHED_IDLE mai 23 13:46:39 endless tracker-extract[4340]: Set scheduler policy to SCHED_IDLE mai 23 13:46:39 endless tracker-extract[4340]: Setting priority nice level to 19 mai 23 13:46:39 endless tracker-miner-f[4341]: Setting priority nice level to 19 mai 23 13:46:39 endless tracker-miner-f[4341]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location. mai 23 13:46:39 endless tracker-miner-f[4341]: Unable to get XDG user directory path for special directory &DOWNLOAD. Ignoring this location. mai 23 13:46:39 endless tracker-miner-f[4341]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location. mai 23 13:46:39 endless tracker-miner-f[4341]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location. mai 23 13:46:39 endless tracker-miner-f[4341]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location. mai 23 13:46:39 endless tracker-miner-f[4341]: Unable to get XDG user directory path for special directory &DOWNLOAD. Ignoring this location. mai 23 13:46:39 endless tracker-miner-f[4341]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location. mai 23 13:46:39 endless tracker-miner-f[4341]: Unable to get XDG user directory path for special directory &DOWNLOAD. Ignoring this location. mai 23 13:46:39 endless tracker-miner-f[4341]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location. mai 23 13:46:39 endless tracker-miner-f[4341]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location. mai 23 13:46:39 endless tracker-miner-f[4341]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location. mai 23 13:46:39 endless tracker-miner-f[4341]: Path '&DOWNLOAD' being removed from recursive directories list, as it also exists in single directories list mai 23 13:46:39 endless wpa_supplicant[3673]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN mai 23 13:46:39 endless systemd[4149]: Started GNOME Session Manager (session: gnome-login). mai 23 13:46:39 endless systemd[4149]: Reached target GNOME Session Manager is ready. mai 23 13:46:39 endless systemd[4149]: Starting GNOME Shell on X11... mai 23 13:46:40 endless kernel: intel_rapl_common: Found RAPL domain package mai 23 13:46:40 endless kernel: intel_rapl_common: Found RAPL domain core mai 23 13:46:40 endless kernel: intel_rapl_common: Found RAPL domain uncore mai 23 13:46:40 endless kernel: intel_rapl_common: Found RAPL domain dram mai 23 13:46:40 endless eos-enable-zram[4371]: Setting up swapspace version 1, size = 11,5 GiB (12326825984 bytes) mai 23 13:46:40 endless eos-enable-zram[4371]: no label, UUID=872e163b-4e73-410c-95b0-985fb4a9a9cc mai 23 13:46:40 endless systemd[1]: bluetooth-uart.service: Succeeded. mai 23 13:46:40 endless systemd[1]: Started Bluetooth UART. mai 23 13:46:40 endless systemd[1]: Starting Load/Save RF Kill Switch Status... mai 23 13:46:40 endless systemd[1]: Started swap with zram. mai 23 13:46:40 endless kernel: Adding 12037916k swap on /dev/zram0. Priority:-2 extents:1 across:12037916k SSFS mai 23 13:46:40 endless systemd[1]: Condition check resulted in Remove swap partitions and reclaim their space being skipped. mai 23 13:46:40 endless systemd[1]: Started Load/Save RF Kill Switch Status. mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4088] policy: auto-activating connection 'BethDaniel' (6d8338a5-5a59-4474-94ac-04360e95d6df) mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4104] device (wlp2s0): Activation: starting connection 'BethDaniel' (6d8338a5-5a59-4474-94ac-04360e95d6df) mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4115] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4121] manager: NetworkManager state is now CONNECTING mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4128] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4133] device (wlp2s0): Activation: (wifi) access point 'BethDaniel' has security, but secrets are required. mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4134] device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4138] sup-iface[0x55a71ef70980,wlp2s0]: wps: type pbc start... mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4197] device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4211] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4217] device (wlp2s0): Activation: (wifi) connection 'BethDaniel' has security, and secrets exist. No new secrets needed. mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4220] Config: added 'ssid' value 'BethDaniel' mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4221] Config: added 'scan_ssid' value '1' mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4222] Config: added 'bgscan' value 'simple:30:-80:86400' mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4223] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256' mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4224] Config: added 'auth_alg' value 'OPEN' mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4227] Config: added 'psk' value '' mai 23 13:46:40 endless wpa_supplicant[3673]: wlp2s0: SME: Trying to authenticate with 80:d0:4a:90:f1:d9 (SSID='BethDaniel' freq=2412 MHz) mai 23 13:46:40 endless kernel: wlp2s0: authenticate with 80:d0:4a:90:f1:d9 mai 23 13:46:40 endless kernel: wlp2s0: send auth to 80:d0:4a:90:f1:d9 (try 1/3) mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4753] device (wlp2s0): supplicant interface state: ready -> authenticating mai 23 13:46:40 endless wpa_supplicant[3673]: wlp2s0: Trying to associate with 80:d0:4a:90:f1:d9 (SSID='BethDaniel' freq=2412 MHz) mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4771] device (wlp2s0): supplicant interface state: authenticating -> associating mai 23 13:46:40 endless kernel: wlp2s0: authenticated mai 23 13:46:40 endless kernel: wlp2s0: associate with 80:d0:4a:90:f1:d9 (try 1/3) mai 23 13:46:40 endless kernel: wlp2s0: RX AssocResp from 80:d0:4a:90:f1:d9 (capab=0x411 status=0 aid=2) mai 23 13:46:40 endless wpa_supplicant[3673]: wlp2s0: Associated with 80:d0:4a:90:f1:d9 mai 23 13:46:40 endless wpa_supplicant[3673]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 mai 23 13:46:40 endless kernel: wlp2s0: associated mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.4904] device (wlp2s0): supplicant interface state: associating -> associated mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.5228] device (wlp2s0): supplicant interface state: associated -> 4-way handshake mai 23 13:46:40 endless wpa_supplicant[3673]: wlp2s0: WPA: Key negotiation completed with 80:d0:4a:90:f1:d9 [PTK=CCMP GTK=CCMP] mai 23 13:46:40 endless wpa_supplicant[3673]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 80:d0:4a:90:f1:d9 completed [id=0 id_str=] mai 23 13:46:40 endless kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.6558] device (wlp2s0): supplicant interface state: 4-way handshake -> completed mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.6559] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "BethDaniel" mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.6561] device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.6568] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) mai 23 13:46:40 endless NetworkManager[1540]: [1590252400.8230] dhcp4 (wlp2s0): dhclient started with pid 4465 mai 23 13:46:40 endless wpa_supplicant[3673]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-40 noise=-91 txrate=1000 mai 23 13:46:41 endless avahi-daemon[1534]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::c6c7:3fc7:b338:a37b. mai 23 13:46:41 endless avahi-daemon[1534]: New relevant interface wlp2s0.IPv6 for mDNS. mai 23 13:46:41 endless avahi-daemon[1534]: Registering new address record for fe80::c6c7:3fc7:b338:a37b on wlp2s0.*. mai 23 13:46:41 endless dhclient[4465]: DHCPREQUEST for 192.168.0.34 on wlp2s0 to 255.255.255.255 port 67 mai 23 13:46:41 endless dhclient[4465]: DHCPACK of 192.168.0.34 from 192.168.0.1 mai 23 13:46:41 endless NetworkManager[1540]: [1590252401.3765] dhcp4 (wlp2s0): address 192.168.0.34 mai 23 13:46:41 endless NetworkManager[1540]: [1590252401.3766] dhcp4 (wlp2s0): plen 24 (255.255.255.0) mai 23 13:46:41 endless NetworkManager[1540]: [1590252401.3766] dhcp4 (wlp2s0): gateway 192.168.0.1 mai 23 13:46:41 endless NetworkManager[1540]: [1590252401.3766] dhcp4 (wlp2s0): lease time 86400 mai 23 13:46:41 endless NetworkManager[1540]: [1590252401.3766] dhcp4 (wlp2s0): nameserver '181.213.132.5' mai 23 13:46:41 endless NetworkManager[1540]: [1590252401.3766] dhcp4 (wlp2s0): nameserver '181.213.132.4' mai 23 13:46:41 endless NetworkManager[1540]: [1590252401.3766] dhcp4 (wlp2s0): state changed unknown -> bound mai 23 13:46:41 endless avahi-daemon[1534]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.0.34. mai 23 13:46:41 endless avahi-daemon[1534]: New relevant interface wlp2s0.IPv4 for mDNS. mai 23 13:46:41 endless avahi-daemon[1534]: Registering new address record for 192.168.0.34 on wlp2s0.IPv4. mai 23 13:46:41 endless NetworkManager[1540]: [1590252401.3780] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') mai 23 13:46:41 endless NetworkManager[1540]: [1590252401.3787] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') mai 23 13:46:41 endless NetworkManager[1540]: [1590252401.3790] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') mai 23 13:46:41 endless NetworkManager[1540]: [1590252401.3795] manager: NetworkManager state is now CONNECTED_LOCAL mai 23 13:46:41 endless dhclient[4465]: bound to 192.168.0.34 -- renewal in 41928 seconds. mai 23 13:46:41 endless NetworkManager[1540]: [1590252401.5286] manager: NetworkManager state is now CONNECTED_SITE mai 23 13:46:41 endless NetworkManager[1540]: [1590252401.5287] policy: set 'BethDaniel' (wlp2s0) as default for IPv4 routing and DNS mai 23 13:46:41 endless eos-metrics-ins[2289]: Not recording network ID as it is not required for this image mai 23 13:46:41 endless NetworkManager[1540]: [1590252401.7256] device (wlp2s0): Activation: successful, device activated. mai 23 13:46:41 endless nm-dispatcher[3932]: req:2 'up' [wlp2s0]: new request (5 scripts) mai 23 13:46:41 endless nm-dispatcher[3932]: req:2 'up' [wlp2s0]: start running ordered scripts... mai 23 13:46:42 endless NetworkManager[1540]: [1590252402.1678] manager: NetworkManager state is now CONNECTED_GLOBAL mai 23 13:46:42 endless nm-dispatcher[3932]: req:3 'connectivity-change': new request (5 scripts) mai 23 13:46:42 endless eos-metrics-ins[2289]: Not recording network ID as it is not required for this image mai 23 13:46:42 endless mogwai-schedule[1716]: Exiting due to reaching inactivity timeout mai 23 13:46:42 endless systemd[1]: mogwai-scheduled.service: Succeeded. mai 23 13:46:42 endless ntpd[3056]: ntpd exiting on signal 15 (Terminated) mai 23 13:46:42 endless systemd[1]: Stopping Network Time Service... mai 23 13:46:42 endless systemd[1]: ntp.service: Succeeded. mai 23 13:46:42 endless systemd[1]: Stopped Network Time Service. mai 23 13:46:42 endless systemd[1]: Starting Network Time Service... mai 23 13:46:42 endless ntpd[4592]: ntpd 4.2.8p12@1.3728-o (1): Starting mai 23 13:46:42 endless ntpd[4592]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 112:119 mai 23 13:46:42 endless ntpd[4611]: proto: precision = 0.136 usec (-23) mai 23 13:46:42 endless systemd[1]: Started Network Time Service. mai 23 13:46:42 endless ntpd[4611]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature mai 23 13:46:42 endless ntpd[4611]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2020-06-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37 mai 23 13:46:42 endless ntpd[4611]: Listen and drop on 0 v6wildcard [::]:123 mai 23 13:46:42 endless ntpd[4611]: Listen and drop on 1 v4wildcard 0.0.0.0:123 mai 23 13:46:42 endless ntpd[4611]: Listen normally on 2 lo 127.0.0.1:123 mai 23 13:46:42 endless ntpd[4611]: Listen normally on 3 wlp2s0 192.168.0.34:123 mai 23 13:46:42 endless ntpd[4611]: Listen normally on 4 lo [::1]:123 mai 23 13:46:42 endless ntpd[4611]: bind(21) AF_INET6 fe80::c6c7:3fc7:b338:a37b%3#123 flags 0x11 failed: Cannot assign requested address mai 23 13:46:42 endless ntpd[4611]: unable to create socket on wlp2s0 (5) for fe80::c6c7:3fc7:b338:a37b%3#123 mai 23 13:46:42 endless ntpd[4611]: failed to init interface for address fe80::c6c7:3fc7:b338:a37b%3 mai 23 13:46:42 endless ntpd[4611]: Listening on routing socket on fd #21 for interface updates mai 23 13:46:42 endless ntpd[4611]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized mai 23 13:46:42 endless ntpd[4611]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized mai 23 13:46:42 endless nm-dispatcher[3932]: req:3 'connectivity-change': start running ordered scripts... mai 23 13:46:42 endless systemd[1]: Started Update or install Google Chrome plugins. mai 23 13:46:42 endless systemd[1]: Started /bin/systemctl --no-block start eos-phone-home.service. mai 23 13:46:42 endless nm-dispatcher[4630]: Running timer as unit: run-rfb1673c161834bebbed58beb29327790.timer mai 23 13:46:42 endless nm-dispatcher[4630]: Will run service as unit: run-rfb1673c161834bebbed58beb29327790.service mai 23 13:46:43 endless ntpd[4611]: Soliciting pool server 85.91.1.180 mai 23 13:46:43 endless NetworkManager[1540]: [1590252403.7278] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) mai 23 13:46:43 endless NetworkManager[1540]: [1590252403.7292] dhcp6 (wlp2s0): dhclient started with pid 4711 mai 23 13:46:43 endless avahi-daemon[1534]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::c6c7:3fc7:b338:a37b. mai 23 13:46:43 endless avahi-daemon[1534]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address 2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e. mai 23 13:46:43 endless avahi-daemon[1534]: Registering new address record for 2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e on wlp2s0.*. mai 23 13:46:43 endless avahi-daemon[1534]: Withdrawing address record for fe80::c6c7:3fc7:b338:a37b on wlp2s0. mai 23 13:46:43 endless NetworkManager[1540]: [1590252403.7303] policy: set 'BethDaniel' (wlp2s0) as default for IPv6 routing and DNS mai 23 13:46:44 endless eos-chrome-plugin-update[4628]: No need to check the Flash plugin yet (version: 32.0.0.371) mai 23 13:46:44 endless eos-chrome-plugin-update[4628]: No need to check the Widevine plugin yet (version: 4.10.1582.2) mai 23 13:46:44 endless eos-chrome-plugin-update[4628]: All done mai 23 13:46:44 endless systemd[1]: eos-chrome-plugin-update.service: Succeeded. mai 23 13:46:44 endless dhclient[4711]: XMT: Confirm on wlp2s0, interval 950ms. mai 23 13:46:44 endless dhclient[4711]: RCV: Reply message on wlp2s0 from fe80::82d0:4aff:fe90:f1d6. mai 23 13:46:44 endless dhclient[4711]: message status code Success. mai 23 13:46:44 endless NetworkManager[1540]: [1590252404.6005] dhcp6 (wlp2s0): valid_lft 86400 mai 23 13:46:44 endless NetworkManager[1540]: [1590252404.6005] dhcp6 (wlp2s0): preferred_lft 86400 mai 23 13:46:44 endless NetworkManager[1540]: [1590252404.6005] dhcp6 (wlp2s0): address 2804:14d:5ce6:9e6b::1001 mai 23 13:46:44 endless NetworkManager[1540]: [1590252404.6005] dhcp6 (wlp2s0): nameserver '2804:14d:1:0:181:213:132:5' mai 23 13:46:44 endless NetworkManager[1540]: [1590252404.6005] dhcp6 (wlp2s0): nameserver '2804:14d:1:0:181:213:132:4' mai 23 13:46:44 endless NetworkManager[1540]: [1590252404.6005] dhcp6 (wlp2s0): state changed unknown -> bound, event ID="d3:dd:a0:cd|1590247653" mai 23 13:46:44 endless ntpd[4611]: Soliciting pool server 94.198.159.10 mai 23 13:46:44 endless avahi-daemon[1534]: Registering new address record for 2804:14d:5ce6:9e6b::1001 on wlp2s0.*. mai 23 13:46:44 endless nm-dispatcher[3932]: req:4 'dhcp6-change' [wlp2s0]: new request (5 scripts) mai 23 13:46:44 endless nm-dispatcher[3932]: req:4 'dhcp6-change' [wlp2s0]: start running ordered scripts... mai 23 13:46:44 endless ntpd[4611]: Soliciting pool server 143.107.229.210 mai 23 13:46:45 endless systemd[1]: systemd-rfkill.service: Succeeded. mai 23 13:46:45 endless ntpd[4611]: Soliciting pool server 45.11.105.243 mai 23 13:46:45 endless ntpd[4611]: Soliciting pool server 209.58.185.100 mai 23 13:46:45 endless ntpd[4611]: Soliciting pool server 2001:41d0:2:b7a2:0:162:b:123 mai 23 13:46:46 endless rtkit-daemon[3835]: Supervising 1 threads of 1 processes of 1 users. mai 23 13:46:46 endless rtkit-daemon[3835]: Successfully made thread 4798 of process 4250 (n/a) owned by '109' RT at priority 5. mai 23 13:46:46 endless rtkit-daemon[3835]: Supervising 2 threads of 1 processes of 1 users. mai 23 13:46:46 endless rtkit-daemon[3835]: Supervising 2 threads of 1 processes of 1 users. mai 23 13:46:46 endless rtkit-daemon[3835]: Successfully made thread 4799 of process 4250 (n/a) owned by '109' RT at priority 5. mai 23 13:46:46 endless rtkit-daemon[3835]: Supervising 3 threads of 1 processes of 1 users. mai 23 13:46:46 endless systemd[4149]: Started Sound Service. mai 23 13:46:46 endless systemd[4149]: Reached target Main User Target. mai 23 13:46:46 endless bluetoothd[3770]: Endpoint registered: sender=:1.130 path=/MediaEndpoint/A2DPSource/sbc mai 23 13:46:46 endless ntpd[4611]: Soliciting pool server 162.159.200.123 mai 23 13:46:46 endless ntpd[4611]: Soliciting pool server 89.111.15.218 mai 23 13:46:46 endless ntpd[4611]: Soliciting pool server 45.11.105.253 mai 23 13:46:46 endless kernel: Bluetooth: RFCOMM TTY layer initialized mai 23 13:46:46 endless kernel: Bluetooth: RFCOMM socket layer initialized mai 23 13:46:46 endless kernel: Bluetooth: RFCOMM ver 1.11 mai 23 13:46:46 endless gdm-Xorg-:0[3655]: (II) modeset(0): EDID vendor "CMN", prod id 5596 mai 23 13:46:46 endless gdm-Xorg-:0[3655]: (II) modeset(0): Printing DDC gathered Modelines: mai 23 13:46:46 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "1366x768"x0.0 76.42 1366 1434 1479 1592 768 772 779 800 -hsync -vsync (48.0 kHz eP) mai 23 13:46:47 endless ntpd[4611]: Soliciting pool server 200.189.40.8 mai 23 13:46:47 endless ntpd[4611]: Soliciting pool server 200.160.0.8 mai 23 13:46:47 endless ntpd[4611]: Listen normally on 6 wlp2s0 [2804:14d:5ce6:9e6b::1001]:123 mai 23 13:46:47 endless ntpd[4611]: Listen normally on 7 wlp2s0 [2804:14d:5ce6:9e6b:a18d:417f:26b4:d94e]:123 mai 23 13:46:47 endless ntpd[4611]: Listen normally on 8 wlp2s0 [fe80::c6c7:3fc7:b338:a37b%3]:123 mai 23 13:46:47 endless ntpd[4611]: new interface(s) found: waking up resolver mai 23 13:46:48 endless ntpd[4611]: Soliciting pool server 192.99.2.8 mai 23 13:46:48 endless gnome-shell[4358]: Getting parental controls for user 109 mai 23 13:46:51 endless ntpd[4611]: receive: Unexpected origin timestamp 0xe273d1fb.9ab34dfe does not match aorg 0000000000.00000000 from server@162.159.200.123 xmt 0xe273d1fb.3db0160c mai 23 13:46:51 endless ntpd[4611]: receive: Unexpected origin timestamp 0xe273d1fb.9a0bfb6d does not match aorg 0000000000.00000000 from server@192.99.2.8 xmt 0xe273d1fb.51e3f89d mai 23 13:46:51 endless ntpd[4611]: receive: Unexpected origin timestamp 0xe273d1fb.9ab43074 does not match aorg 0000000000.00000000 from server@85.91.1.180 xmt 0xe273d1fb.55ad85df mai 23 13:46:51 endless ntpd[4611]: receive: Unexpected origin timestamp 0xe273d1fb.9ab1fe31 does not match aorg 0000000000.00000000 from server@89.111.15.218 xmt 0xe273d1fb.5bc01691 mai 23 13:46:51 endless systemd[1]: systemd-hostnamed.service: Succeeded. mai 23 13:46:54 endless gnome-shell[4358]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. mai 23 13:46:54 endless gnome-shell[4358]: Will monitor session c1 mai 23 13:46:54 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.131' (uid=109 pid=4358 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:46:54 endless systemd[1]: Starting Locale Service... mai 23 13:46:54 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.locale1' mai 23 13:46:54 endless systemd[1]: Started Locale Service. mai 23 13:46:54 endless dbus-daemon[4263]: [session uid=109 pid=4263] Activating service name='org.freedesktop.portal.IBus' requested by ':1.25' (uid=109 pid=4890 comm="ibus-daemon --panel disable --xim " label="unconfined") mai 23 13:46:54 endless dbus-daemon[4263]: [session uid=109 pid=4263] Successfully activated service 'org.freedesktop.portal.IBus' mai 23 13:46:54 endless at-spi-bus-launcher[4318]: dbus-daemon[4318]: Activating service name='org.a11y.atspi.Registry' requested by ':1.2' (uid=109 pid=4907 comm="/usr/lib/ibus/ibus-x11 --kill-daemon " label="unconfined") mai 23 13:46:54 endless at-spi-bus-launcher[4318]: dbus-daemon[4318]: Successfully activated service 'org.a11y.atspi.Registry' mai 23 13:46:54 endless at-spi-bus-launcher[4921]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry mai 23 13:46:54 endless systemd[1]: NetworkManager-dispatcher.service: Succeeded. mai 23 13:46:55 endless dbus-daemon[4263]: [session uid=109 pid=4263] Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' requested by ':1.23' (uid=109 pid=4358 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:46:55 endless systemd[4149]: Starting sandboxed app permission store... mai 23 13:46:55 endless dbus-daemon[4263]: [session uid=109 pid=4263] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' mai 23 13:46:55 endless systemd[4149]: Started sandboxed app permission store. mai 23 13:46:55 endless polkitd[1720]: Registered Authentication Agent for unix-session:c1 (system bus name :1.131 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:46:55 endless dbus-daemon[4263]: [session uid=109 pid=4263] Activating service name='org.gnome.Shell.Notifications' requested by ':1.23' (uid=109 pid=4358 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:46:55 endless dbus-daemon[4263]: [session uid=109 pid=4263] Successfully activated service 'org.gnome.Shell.Notifications' mai 23 13:46:55 endless dbus-daemon[4263]: [session uid=109 pid=4263] Activating service name='ca.desrt.dconf' requested by ':1.23' (uid=109 pid=4358 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:46:55 endless dbus-daemon[4263]: [session uid=109 pid=4263] Successfully activated service 'ca.desrt.dconf' mai 23 13:46:55 endless systemd[4149]: Started GNOME Shell on X11. mai 23 13:46:55 endless systemd[4149]: Reached target GNOME Shell on X11. mai 23 13:46:55 endless systemd[4149]: Reached target GNOME Session is initialized. mai 23 13:46:55 endless systemd[4149]: Reached target GNOME session X11 services. mai 23 13:46:55 endless systemd[4149]: Reached target GNOME X11 Session. mai 23 13:46:55 endless systemd[4149]: Reached target GNOME Session (session: gnome-login). mai 23 13:46:55 endless systemd[4149]: Starting Signal initialization done to GNOME Session Manager... mai 23 13:46:55 endless systemd[4149]: Starting GNOME Accessibility settings... mai 23 13:46:55 endless systemd[4149]: Starting GNOME Color management... mai 23 13:46:55 endless systemd[4149]: Starting GNOME Keyboard handling... mai 23 13:46:55 endless systemd[4149]: Starting GNOME Media keys handling... mai 23 13:46:55 endless systemd[4149]: Starting GNOME Power management handling... mai 23 13:46:55 endless systemd[4149]: Starting GNOME Printer notifications... mai 23 13:46:55 endless systemd[4149]: Starting GNOME RFKill handling... mai 23 13:46:55 endless systemd[4149]: Starting GNOME Smartcard handling... mai 23 13:46:55 endless systemd[4149]: Starting GNOME Sound sample caching handling... mai 23 13:46:55 endless systemd[4149]: Starting GNOME USB protection handling... mai 23 13:46:55 endless systemd[4149]: Starting GNOME Wacom handling... mai 23 13:46:55 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.138' (uid=109 pid=4987 comm="/usr/libexec/gsd-rfkill " label="unconfined") mai 23 13:46:55 endless systemd[4149]: Starting GNOME WWan management... mai 23 13:46:55 endless dbus-daemon[1538]: [system] Activating via systemd: service name='com.endlessm.RecordBootSuccess' unit='record-boot-success.service' requested by ':1.141' (uid=109 pid=5018 comm="dbus-send --system --type=method_call --dest=org.f" label="unconfined") mai 23 13:46:55 endless systemd[4149]: Starting GNOME XSettings... mai 23 13:46:55 endless dbus-daemon[1538]: [system] Activating via systemd: service name='com.endlessm.MogwaiSchedule1' unit='mogwai-scheduled.service' requested by ':1.131' (uid=109 pid=4358 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:46:55 endless systemd[4149]: Started GNOME Accessibility settings. mai 23 13:46:55 endless systemd[4149]: Reached target GNOME Accessibility settings. mai 23 13:46:55 endless systemd[4149]: gnome-session-signal-init.service: Succeeded. mai 23 13:46:55 endless systemd[4149]: Started Signal initialization done to GNOME Session Manager. mai 23 13:46:55 endless systemd[4149]: Started GNOME Smartcard handling. mai 23 13:46:55 endless systemd[4149]: Reached target GNOME Smartcard handling. mai 23 13:46:55 endless gnome-session-binary[4345]: Entering running state mai 23 13:46:56 endless xbrlapi.desktop[5017]: openConnection: connect: Arquivo ou diretório inexistente mai 23 13:46:56 endless xbrlapi.desktop[5017]: cannot connect to braille devices daemon brltty at :0 mai 23 13:46:55 endless systemd[4149]: Started GNOME WWan management. mai 23 13:46:55 endless systemd[4149]: Reached target GNOME WWan management. mai 23 13:46:55 endless systemd[4149]: Started GNOME Printer notifications. mai 23 13:46:55 endless systemd[4149]: Reached target GNOME Printer notifications. mai 23 13:46:55 endless cupsd[1536]: REQUEST localhost - - "POST / HTTP/1.1" 200 366 Create-Printer-Subscriptions successful-ok mai 23 13:46:55 endless systemd[4149]: Started GNOME USB protection handling. mai 23 13:46:55 endless systemd[4149]: Reached target GNOME USB protection handling. mai 23 13:46:55 endless systemd[4149]: Started GNOME Sound sample caching handling. mai 23 13:46:55 endless systemd[4149]: Reached target GNOME Sound sample caching handling. mai 23 13:46:55 endless systemd[4149]: Started GNOME Keyboard handling. mai 23 13:46:55 endless systemd[4149]: Reached target GNOME Keyboard handling. mai 23 13:46:55 endless systemd[4149]: Started GNOME Power management handling. mai 23 13:46:55 endless systemd[4149]: Reached target GNOME Power management handling. mai 23 13:46:55 endless systemd[4149]: Started GNOME Wacom handling. mai 23 13:46:55 endless systemd[4149]: Reached target GNOME Wacom handling. mai 23 13:46:55 endless systemd[4149]: Started GNOME Color management. mai 23 13:46:55 endless systemd[4149]: Reached target GNOME Color management. mai 23 13:46:55 endless systemd[4149]: Started GNOME Media keys handling. mai 23 13:46:55 endless systemd[4149]: Reached target GNOME Media keys handling. mai 23 13:46:56 endless systemd[1]: Starting Hostname Service... mai 23 13:46:56 endless systemd[1]: Starting Download Scheduling Daemon... mai 23 13:46:56 endless systemd[1]: Starting Record Boot Success... mai 23 13:46:56 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.hostname1' mai 23 13:46:56 endless systemd[1]: Started Hostname Service. mai 23 13:46:56 endless systemd[4149]: Started GNOME RFKill handling. mai 23 13:46:56 endless systemd[4149]: Reached target GNOME RFKill handling. mai 23 13:46:56 endless kernel: rfkill: input handler disabled mai 23 13:46:56 endless upowerd[1729]: up_kbd_backlight_brightness_read: assertion 'fd >= 0' failed mai 23 13:46:56 endless gsd-power[4984]: Failed to get brightness: GDBus.Error:org.freedesktop.UPower.GeneralError: error reading brightness mai 23 13:46:56 endless dbus-daemon[1538]: [system] Successfully activated service 'com.endlessm.MogwaiSchedule1' mai 23 13:46:56 endless systemd[1]: Started Download Scheduling Daemon. mai 23 13:46:56 endless record-boot-success[5068]: Marked boot as successful mai 23 13:46:56 endless /usr/lib/eos-boot-helper/record-boot-success/record-boot-success[5068]: Marked boot as successful mai 23 13:46:56 endless dbus-daemon[1538]: [system] Successfully activated service 'com.endlessm.RecordBootSuccess' mai 23 13:46:56 endless systemd[1]: Started Record Boot Success. mai 23 13:46:56 endless dbus-daemon[4263]: [session uid=109 pid=4263] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.22' (uid=109 pid=4341 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 13:46:56 endless systemd[4149]: Starting Tracker metadata database store and lookup manager... mai 23 13:46:56 endless systemd[4149]: Started Tracker metadata extractor. mai 23 13:46:56 endless dbus-daemon[4263]: [session uid=109 pid=4263] Successfully activated service 'org.freedesktop.Tracker1' mai 23 13:46:56 endless systemd[4149]: Started Tracker metadata database store and lookup manager. mai 23 13:46:56 endless systemd[4149]: Started Tracker file system data miner. mai 23 13:46:56 endless gsd-media-keys[4983]: Failed to grab accelerator for keybinding settings:playback-random mai 23 13:46:56 endless gsd-media-keys[4983]: Failed to grab accelerator for keybinding settings:playback-repeat mai 23 13:46:56 endless gsd-media-keys[4983]: Failed to grab accelerator for keybinding settings:hibernate mai 23 13:46:56 endless gsd-media-keys[4983]: Failed to grab accelerator for keybinding settings:rfkill mai 23 13:46:56 endless systemd[4149]: Started GNOME XSettings. mai 23 13:46:56 endless systemd[4149]: Reached target GNOME XSettings. mai 23 13:46:56 endless systemd[4149]: Reached target GNOME Session. mai 23 13:46:56 endless systemd[4149]: Reached target GNOME X11 Session (session: gnome-login). mai 23 13:46:56 endless systemd[4149]: Reached target Current graphical user session. mai 23 13:46:56 endless systemd[4149]: Condition check resulted in GNOME Welcome Tour being skipped. mai 23 13:46:56 endless systemd[4149]: Startup finished in 21.367s. mai 23 13:46:56 endless colord[2288]: failed to get session [pid 4978]: Não há dados disponíveis mai 23 13:46:57 endless wpa_supplicant[3673]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN mai 23 13:46:57 endless dbus-daemon[1538]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.131' (uid=109 pid=4358 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:46:57 endless systemd[1]: Starting Fingerprint Authentication Daemon... mai 23 13:46:58 endless dbus-daemon[1538]: [system] Successfully activated service 'net.reactivated.Fprint' mai 23 13:46:58 endless systemd[1]: Started Fingerprint Authentication Daemon. mai 23 13:46:59 endless gnome-shell[4358]: Registering session with GDM mai 23 13:46:59 endless systemd[1]: Received SIGRTMIN+21 from PID 248 (plymouthd). mai 23 13:46:59 endless systemd[1]: plymouth-quit-wait.service: Succeeded. mai 23 13:46:59 endless systemd[1]: Started Hold until boot process finishes up. mai 23 13:46:59 endless systemd[1]: plymouth-start.service: Succeeded. mai 23 13:46:59 endless systemd[1]: Reached target Multi-User System. mai 23 13:46:59 endless systemd[1]: Reached target Graphical Interface. mai 23 13:46:59 endless systemd[1]: Started Stop Read-Ahead Data Collection 10s After Completed Startup. mai 23 13:46:59 endless systemd[1]: Starting Update UTMP about System Runlevel Changes... mai 23 13:46:59 endless systemd[1]: systemd-update-utmp-runlevel.service: Succeeded. mai 23 13:46:59 endless systemd[1]: Started Update UTMP about System Runlevel Changes. mai 23 13:46:59 endless systemd[1]: Startup finished in 1.179s (kernel) + 3.238s (initrd) + 1min 5.896s (userspace) = 1min 10.315s. mai 23 13:47:06 endless systemd[4149]: tracker-extract.service: Succeeded. mai 23 13:47:25 endless systemd[1]: systemd-localed.service: Succeeded. mai 23 13:47:26 endless systemd[1]: systemd-hostnamed.service: Succeeded. mai 23 13:47:26 endless mogwai-schedule[5066]: Exiting due to reaching inactivity timeout mai 23 13:47:26 endless systemd[1]: mogwai-scheduled.service: Succeeded. mai 23 13:47:27 endless tracker-store[5192]: OK mai 23 13:47:27 endless systemd[4149]: tracker-store.service: Succeeded. mai 23 13:47:28 endless systemd[1]: fprintd.service: Succeeded. mai 23 13:47:29 endless systemd[1]: Starting Stop Read-Ahead Data Collection... mai 23 13:47:29 endless systemd[1]: systemd-readahead-done.service: Succeeded. mai 23 13:47:29 endless systemd[1]: Started Stop Read-Ahead Data Collection. mai 23 13:47:29 endless gdm-password][5336]: gkr-pam: unable to locate daemon control file mai 23 13:47:29 endless gdm-password][5336]: gkr-pam: stashed password to try later in open session mai 23 13:47:29 endless gdm-password][5336]: pam_unix(gdm-password:session): session opened for user daniel by (uid=0) mai 23 13:47:29 endless systemd[1]: Started Session 3 of user daniel. mai 23 13:47:29 endless systemd-logind[1824]: New session 3 of user daniel. mai 23 13:47:29 endless kernel: rfkill: input handler enabled mai 23 13:47:29 endless gdm-password][5336]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring mai 23 13:47:30 endless rtkit-daemon[3835]: Supervising 3 threads of 1 processes of 1 users. mai 23 13:47:30 endless rtkit-daemon[3835]: Successfully made thread 5585 of process 3747 (n/a) owned by '1001' RT at priority 5. mai 23 13:47:30 endless rtkit-daemon[3835]: Supervising 4 threads of 2 processes of 2 users. mai 23 13:47:30 endless rtkit-daemon[3835]: Supervising 4 threads of 2 processes of 2 users. mai 23 13:47:30 endless rtkit-daemon[3835]: Successfully made thread 5586 of process 3747 (n/a) owned by '1001' RT at priority 5. mai 23 13:47:30 endless rtkit-daemon[3835]: Supervising 5 threads of 2 processes of 2 users. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME X11 Session (session: gnome-login). mai 23 13:47:30 endless systemd[4149]: Stopped target Current graphical user session. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME Session. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME X11 Session. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME Session (session: gnome-login). mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME Accessibility settings. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME Color management. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME Keyboard handling. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME Media keys handling. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME Power management handling. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME Printer notifications. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME RFKill handling. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME Smartcard handling. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME Sound sample caching handling. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME USB protection handling. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME Wacom handling. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME WWan management. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME XSettings. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME session X11 services. mai 23 13:47:30 endless systemd[4149]: Stopping GNOME Accessibility settings... mai 23 13:47:30 endless systemd[4149]: Stopping GNOME Color management... mai 23 13:47:30 endless systemd[4149]: Stopping GNOME Keyboard handling... mai 23 13:47:30 endless systemd[4149]: Stopping GNOME Media keys handling... mai 23 13:47:30 endless systemd[4149]: Stopping GNOME Power management handling... mai 23 13:47:30 endless systemd[4149]: Stopping GNOME Printer notifications... mai 23 13:47:30 endless systemd[4149]: Stopping GNOME RFKill handling... mai 23 13:47:30 endless systemd[4149]: Stopping GNOME Smartcard handling... mai 23 13:47:30 endless systemd[4149]: Stopping GNOME Sound sample caching handling... mai 23 13:47:30 endless systemd[4149]: Stopping GNOME USB protection handling... mai 23 13:47:30 endless systemd[4149]: Stopping GNOME Wacom handling... mai 23 13:47:30 endless systemd[4149]: Stopping GNOME WWan management... mai 23 13:47:30 endless systemd[4149]: Stopping GNOME XSettings... mai 23 13:47:30 endless cupsd[1536]: REQUEST localhost - - "POST / HTTP/1.1" 200 158 Cancel-Subscription successful-ok mai 23 13:47:30 endless cupsd[1536]: REQUEST localhost - - "POST / HTTP/1.1" 200 158 Cancel-Subscription client-error-not-found mai 23 13:47:30 endless gsd-print-notif[4985]: Source ID 7 was not found when attempting to remove it mai 23 13:47:30 endless systemd[4149]: gsd-rfkill.service: Succeeded. mai 23 13:47:30 endless systemd[4149]: Stopped GNOME RFKill handling. mai 23 13:47:30 endless systemd[4149]: gsd-smartcard.service: Succeeded. mai 23 13:47:30 endless systemd[4149]: Stopped GNOME Smartcard handling. mai 23 13:47:30 endless systemd[4149]: gsd-wwan.service: Succeeded. mai 23 13:47:30 endless systemd[4149]: Stopped GNOME WWan management. mai 23 13:47:30 endless systemd[4149]: gsd-a11y-settings.service: Succeeded. mai 23 13:47:30 endless systemd[4149]: Stopped GNOME Accessibility settings. mai 23 13:47:30 endless systemd[4149]: gsd-wacom.service: Succeeded. mai 23 13:47:30 endless systemd[4149]: Stopped GNOME Wacom handling. mai 23 13:47:30 endless systemd[4149]: gsd-print-notifications.service: Succeeded. mai 23 13:47:30 endless systemd[4149]: Stopped GNOME Printer notifications. mai 23 13:47:30 endless systemd[4149]: gsd-media-keys.service: Succeeded. mai 23 13:47:30 endless systemd[4149]: Stopped GNOME Media keys handling. mai 23 13:47:30 endless systemd[4149]: gsd-sound.service: Succeeded. mai 23 13:47:30 endless systemd[4149]: Stopped GNOME Sound sample caching handling. mai 23 13:47:30 endless systemd[4149]: gsd-keyboard.service: Succeeded. mai 23 13:47:30 endless systemd[4149]: Stopped GNOME Keyboard handling. mai 23 13:47:30 endless systemd[4149]: gsd-color.service: Succeeded. mai 23 13:47:30 endless systemd[4149]: Stopped GNOME Color management. mai 23 13:47:30 endless systemd[4149]: gsd-power.service: Succeeded. mai 23 13:47:30 endless systemd[4149]: Stopped GNOME Power management handling. mai 23 13:47:30 endless systemd[4149]: gsd-usb-protection.service: Succeeded. mai 23 13:47:30 endless systemd[4149]: Stopped GNOME USB protection handling. mai 23 13:47:30 endless systemd[4149]: gsd-xsettings.service: Succeeded. mai 23 13:47:30 endless systemd[4149]: Stopped GNOME XSettings. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME Session is initialized. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME Shell on X11. mai 23 13:47:30 endless systemd[4149]: Stopping GNOME Shell on X11... mai 23 13:47:30 endless gdm-launch-environment][4093]: pam_unix(gdm-launch-environment:session): session closed for user Debian-gdm mai 23 13:47:30 endless systemd[4149]: gnome-session-monitor.service: Succeeded. mai 23 13:47:30 endless systemd[4149]: Stopped Monitor Session leader for GNOME Session. mai 23 13:47:30 endless kernel: gdm-session-wor (4093): drop_caches: 2 mai 23 13:47:30 endless systemd[1]: session-c1.scope: Succeeded. mai 23 13:47:30 endless systemd-logind[1824]: Session c1 logged out. Waiting for processes to exit. mai 23 13:47:30 endless systemd-logind[1824]: Removed session c1. mai 23 13:47:30 endless gdm[3372]: Child process -4264 was already dead. mai 23 13:47:30 endless /etc/gdm3/Xsession[5674]: /etc/gdm3/Xsession: Beginning session setup... mai 23 13:47:30 endless bluetoothd[3770]: Endpoint unregistered: sender=:1.130 path=/MediaEndpoint/A2DPSource/sbc mai 23 13:47:30 endless systemd[4149]: pulseaudio.service: Succeeded. mai 23 13:47:30 endless polkitd[1720]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.131, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) (disconnected from bus) mai 23 13:47:30 endless systemd[4149]: gnome-shell-x11.service: Succeeded. mai 23 13:47:30 endless systemd[4149]: Stopped GNOME Shell on X11. mai 23 13:47:30 endless systemd[4149]: Stopped target GNOME Session Manager is ready. mai 23 13:47:30 endless systemd[4149]: Stopping GNOME Session Manager (session: gnome-login)... mai 23 13:47:30 endless gnome-session[4345]: gnome-session-binary[4345]: WARNING: Could not get session class: Endereço ou dispositivo inexistente mai 23 13:47:30 endless gnome-session-binary[4345]: WARNING: Could not get session class: Endereço ou dispositivo inexistente mai 23 13:47:30 endless systemd[4149]: at-spi-dbus-bus.service: Succeeded. mai 23 13:47:30 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.2' (uid=1001 pid=5690 comm="flatpak --installations " label="unconfined") mai 23 13:47:30 endless systemd[3453]: Starting Virtual filesystem service... mai 23 13:47:31 endless systemd[4149]: gnome-session-manager@gnome-login.service: Succeeded. mai 23 13:47:31 endless systemd[4149]: Stopped GNOME Session Manager (session: gnome-login). mai 23 13:47:31 endless systemd[4149]: Stopped target Tasks to be run before GNOME Session starts. mai 23 13:47:31 endless systemd[4149]: Stopped target Session services which should run early before the graphical session is brought up. mai 23 13:47:31 endless systemd[4149]: Reached target Shutdown running GNOME Session. mai 23 13:47:31 endless systemd[4149]: Starting Restart DBus after GNOME Session shutdown... mai 23 13:47:31 endless systemd[4149]: Stopped target Shutdown running GNOME Session. mai 23 13:47:31 endless systemd[4149]: Started Restart DBus after GNOME Session shutdown. mai 23 13:47:31 endless gvfsd[4307]: A connection to the bus can't be made mai 23 13:47:31 endless systemd[4149]: Stopping D-Bus User Message Bus... mai 23 13:47:31 endless tracker-miner-fs[4341]: Received signal:15->'Terminado' mai 23 13:47:31 endless tracker-miner-f[4341]: Error while sending AddMatch() message: A conexão está fechada mai 23 13:47:31 endless tracker-miner-f[4341]: Error while sending AddMatch() message: A conexão está fechada mai 23 13:47:31 endless tracker-miner-f[4341]: Error while sending AddMatch() message: A conexão está fechada mai 23 13:47:31 endless systemd[4149]: dbus.service: Killing process 5704 (pool-dconf-serv) with signal SIGKILL. mai 23 13:47:31 endless systemd[4149]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE mai 23 13:47:31 endless systemd[4149]: xdg-permission-store.service: Failed with result 'exit-code'. mai 23 13:47:31 endless systemd[4149]: dbus.service: Succeeded. mai 23 13:47:31 endless systemd[4149]: Stopped D-Bus User Message Bus. mai 23 13:47:31 endless systemd[4149]: Started D-Bus User Message Bus. mai 23 13:47:31 endless systemd[4149]: gnome-session-restart-dbus.service: Succeeded. mai 23 13:47:31 endless tracker-miner-fs[4341]: OK mai 23 13:47:31 endless systemd[3453]: run-user-109-gvfs.mount: Succeeded. mai 23 13:47:31 endless systemd[1]: run-user-109-gvfs.mount: Succeeded. mai 23 13:47:31 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.gtk.vfs.Daemon' mai 23 13:47:31 endless systemd[3453]: Started Virtual filesystem service. mai 23 13:47:31 endless /etc/gdm3/Xsession[5747]: dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus mai 23 13:47:31 endless /etc/gdm3/Xsession[5747]: dbus-update-activation-environment: setting DISPLAY=:0 mai 23 13:47:31 endless /etc/gdm3/Xsession[5747]: dbus-update-activation-environment: setting XAUTHORITY=/var/run/gdm3/auth-for-daniel-L939K0/database mai 23 13:47:32 endless /etc/gdm3/Xsession[5762]: localuser:daniel being added to access control list mai 23 13:47:32 endless /etc/gdm3/Xsession[5786]: dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge mai 23 13:47:32 endless /etc/gdm3/Xsession[5792]: dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting USER=daniel mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11 mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting HOME=/sysroot/home/daniel mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting QT4_IM_MODULE=ibus mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting DESKTOP_SESSION=endless-xorg mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting IM_CONFIG_PHASE=1 mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting LOGNAME=daniel mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting GTK_IM_MODULE=ibus mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting XDG_SESSION_CLASS=user mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting USERNAME=daniel mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting GTK_OVERLAY_SCROLLING=0 mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting WINDOWPATH=1 mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/sysroot/home/daniel/.local/share/flatpak/exports/bin:/var/lib/flatpak/exports/bin: mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting GDM_LANG=pt_BR.UTF-8 mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1001 mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting DISPLAY=:0 mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting LANG=pt_BR.UTF-8 mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting XDG_CURRENT_DESKTOP=endless:GNOME mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting XAUTHORITY=/var/run/gdm3/auth-for-daniel-L939K0/database mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=endless-xorg mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting XMODIFIERS=@im=ibus mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting SHELL=/bin/bash mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting GDMSESSION=endless-xorg mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1001/gnupg/S.gpg-agent:0:1 mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting QT_IM_MODULE=ibus mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting PWD=/sysroot/home/daniel mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting XDG_DATA_DIRS=/run/share/:/sysroot/home/daniel/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/var/endless-extra/flatpak/exports/share/:/usr/local/share/:/usr/share/ mai 23 13:47:32 endless /etc/gdm3/Xsession[5793]: dbus-update-activation-environment: setting CLUTTER_IM_MODULE=ibus mai 23 13:47:32 endless /etc/gdm3/Xsession[5674]: VirtualBox Additions disabled, not in a Virtual Machine mai 23 13:47:32 endless systemd[4149]: run-user-109-gvfs.mount: Succeeded. mai 23 13:47:32 endless systemd[4149]: tracker-miner-fs.service: Succeeded. mai 23 13:47:32 endless systemd[4149]: gvfs-daemon.service: Succeeded. mai 23 13:47:33 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating service name='org.freedesktop.portal.IBus' requested by ':1.13' (uid=1001 pid=5813 comm="/usr/bin/ibus-daemon --daemonize --xim " label="unconfined") mai 23 13:47:33 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.freedesktop.portal.IBus' mai 23 13:47:33 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.20' (uid=1001 pid=5825 comm="/usr/lib/ibus/ibus-x11 --kill-daemon " label="unconfined") mai 23 13:47:33 endless systemd[3453]: Starting Accessibility services bus... mai 23 13:47:33 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.a11y.Bus' mai 23 13:47:33 endless systemd[3453]: Started Accessibility services bus. mai 23 13:47:33 endless at-spi-bus-launcher[5842]: dbus-daemon[5842]: Activating service name='org.a11y.atspi.Registry' requested by ':1.2' (uid=1001 pid=5819 comm="/usr/lib/ibus/ibus-ui-gtk3 " label="unconfined") mai 23 13:47:33 endless at-spi-bus-launcher[5842]: dbus-daemon[5842]: Successfully activated service 'org.a11y.atspi.Registry' mai 23 13:47:33 endless at-spi-bus-launcher[5848]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry mai 23 13:47:35 endless systemd[3453]: Created slice gnome\x2dsession\x2dmanager.slice. mai 23 13:47:35 endless systemd[3453]: Condition check resulted in GNOME Initial Setup Copy Worker being skipped. mai 23 13:47:35 endless systemd[3453]: Starting Monitor Session leader for GNOME Session... mai 23 13:47:35 endless systemd[3453]: Started OpenSSH Agent. mai 23 13:47:35 endless systemd[3453]: Reached target Session services which should run early before the graphical session is brought up. mai 23 13:47:35 endless systemd[3453]: Starting Tracker metadata extractor... mai 23 13:47:35 endless systemd[3453]: Starting Tracker file system data miner... mai 23 13:47:35 endless systemd[3453]: Started Monitor Session leader for GNOME Session. mai 23 13:47:35 endless gnome-session-c[5852]: Error creating FIFO: Arquivo existe mai 23 13:47:35 endless systemd[3453]: Reached target Tasks to be run before GNOME Session starts. mai 23 13:47:35 endless systemd[3453]: Starting GNOME Session Manager (session: gnome)... mai 23 13:47:35 endless systemd[3453]: ssh-agent.service: Succeeded. mai 23 13:47:35 endless tracker-miner-f[5855]: Set scheduler policy to SCHED_IDLE mai 23 13:47:35 endless tracker-miner-f[5855]: Setting priority nice level to 19 mai 23 13:47:35 endless tracker-miner-f[5855]: Path '/sysroot/home/daniel/Downloads' being removed from recursive directories list, as it also exists in single directories list mai 23 13:47:35 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.44' (uid=1001 pid=5855 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 13:47:35 endless systemd[3453]: Starting Virtual filesystem service - disk device monitor... mai 23 13:47:35 endless tracker-extract[5854]: Set scheduler policy to SCHED_IDLE mai 23 13:47:35 endless tracker-extract[5854]: Setting priority nice level to 19 mai 23 13:47:35 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor' mai 23 13:47:35 endless systemd[3453]: Started Virtual filesystem service - disk device monitor. mai 23 13:47:35 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.44' (uid=1001 pid=5855 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 13:47:35 endless systemd[3453]: Starting Virtual filesystem service - digital camera monitor... mai 23 13:47:36 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor' mai 23 13:47:36 endless systemd[3453]: Started Virtual filesystem service - digital camera monitor. mai 23 13:47:36 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.44' (uid=1001 pid=5855 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 13:47:36 endless systemd[3453]: Starting Virtual filesystem service - Apple File Conduit monitor... mai 23 13:47:36 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor' mai 23 13:47:36 endless systemd[3453]: Started Virtual filesystem service - Apple File Conduit monitor. mai 23 13:47:36 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.44' (uid=1001 pid=5855 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 13:47:36 endless gnome-keyring-ssh.desktop[5890]: SSH_AUTH_SOCK=/run/user/1001/keyring/ssh mai 23 13:47:36 endless systemd[3453]: Starting Virtual filesystem service - Media Transfer Protocol monitor... mai 23 13:47:36 endless systemd[3453]: Started GNOME Session Manager (session: gnome). mai 23 13:47:36 endless systemd[3453]: Reached target GNOME Session Manager is ready. mai 23 13:47:36 endless systemd[3453]: Starting GNOME Shell on X11... mai 23 13:47:36 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor' mai 23 13:47:36 endless systemd[3453]: Started Virtual filesystem service - Media Transfer Protocol monitor. mai 23 13:47:36 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.44' (uid=1001 pid=5855 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 13:47:38 endless gdm-Xorg-:0[3655]: (II) modeset(0): EDID vendor "CMN", prod id 5596 mai 23 13:47:38 endless gdm-Xorg-:0[3655]: (II) modeset(0): Printing DDC gathered Modelines: mai 23 13:47:38 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "1366x768"x0.0 76.42 1366 1434 1479 1592 768 772 779 800 -hsync -vsync (48.0 kHz eP) mai 23 13:47:38 endless systemd[3453]: Starting Virtual filesystem service - GNOME Online Accounts monitor... mai 23 13:47:38 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating service name='org.gnome.OnlineAccounts' requested by ':1.56' (uid=1001 pid=5921 comm="/usr/libexec/gvfs-goa-volume-monitor " label="unconfined") mai 23 13:47:39 endless gnome-shell[5894]: Getting parental controls for user 1001 mai 23 13:47:40 endless systemd[1]: Stopping User Manager for UID 109... mai 23 13:47:40 endless systemd[4149]: Removed slice gnome\x2dsession\x2dmanager.slice. mai 23 13:47:40 endless systemd[4149]: Stopped target Main User Target. mai 23 13:47:40 endless systemd[4149]: Stopping D-Bus User Message Bus... mai 23 13:47:40 endless systemd[4149]: Stopping OpenSSH Agent... mai 23 13:47:40 endless systemd[4149]: ssh-agent.service: Main process exited, code=exited, status=2/INVALIDARGUMENT mai 23 13:47:40 endless systemd[4149]: dbus.service: Succeeded. mai 23 13:47:40 endless systemd[4149]: Stopped D-Bus User Message Bus. mai 23 13:47:40 endless agent-launch[5937]: dbus-update-activation-environment: error: unable to connect to D-Bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. mai 23 13:47:40 endless systemd[4149]: ssh-agent.service: Control process exited, code=exited, status=71/OSERR mai 23 13:47:40 endless systemd[4149]: ssh-agent.service: Failed with result 'exit-code'. mai 23 13:47:40 endless systemd[4149]: Stopped OpenSSH Agent. mai 23 13:47:40 endless systemd[4149]: Stopped target Basic System. mai 23 13:47:40 endless systemd[4149]: Stopped target Paths. mai 23 13:47:40 endless systemd[4149]: Stopped target Sockets. mai 23 13:47:40 endless systemd[4149]: Stopped target Timers. mai 23 13:47:40 endless systemd[4149]: dbus.socket: Succeeded. mai 23 13:47:40 endless systemd[4149]: Closed D-Bus User Message Bus Socket. mai 23 13:47:40 endless systemd[4149]: dirmngr.socket: Succeeded. mai 23 13:47:40 endless systemd[4149]: Closed GnuPG network certificate management daemon. mai 23 13:47:40 endless systemd[4149]: gpg-agent-browser.socket: Succeeded. mai 23 13:47:40 endless systemd[4149]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers). mai 23 13:47:40 endless systemd[4149]: gpg-agent-extra.socket: Succeeded. mai 23 13:47:40 endless systemd[4149]: Closed GnuPG cryptographic agent and passphrase cache (restricted). mai 23 13:47:40 endless systemd[4149]: gpg-agent-ssh.socket: Succeeded. mai 23 13:47:40 endless systemd[4149]: Closed GnuPG cryptographic agent (ssh-agent emulation). mai 23 13:47:40 endless systemd[4149]: gpg-agent.socket: Succeeded. mai 23 13:47:40 endless systemd[4149]: Closed GnuPG cryptographic agent and passphrase cache. mai 23 13:47:40 endless systemd[4149]: pulseaudio.socket: Succeeded. mai 23 13:47:40 endless systemd[4149]: Closed Sound System. mai 23 13:47:40 endless systemd[4149]: Reached target Shutdown. mai 23 13:47:40 endless systemd[4149]: systemd-exit.service: Succeeded. mai 23 13:47:40 endless systemd[4149]: Started Exit the Session. mai 23 13:47:40 endless systemd[4149]: Reached target Exit the Session. mai 23 13:47:40 endless systemd[1]: user@109.service: Succeeded. mai 23 13:47:40 endless systemd[1]: Stopped User Manager for UID 109. mai 23 13:47:40 endless systemd[1]: Stopping User Runtime Directory /run/user/109... mai 23 13:47:40 endless systemd[3453]: run-user-109.mount: Succeeded. mai 23 13:47:40 endless systemd[1]: run-user-109.mount: Succeeded. mai 23 13:47:40 endless systemd[1]: user-runtime-dir@109.service: Succeeded. mai 23 13:47:40 endless systemd[1]: Stopped User Runtime Directory /run/user/109. mai 23 13:47:40 endless systemd[1]: Removed slice User Slice of UID 109. mai 23 13:47:41 endless goa-daemon[5935]: goa-daemon version 3.36.0 starting mai 23 13:47:41 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating service name='org.gnome.Identity' requested by ':1.57' (uid=1001 pid=5935 comm="/usr/libexec/goa-daemon " label="unconfined") mai 23 13:47:41 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.gnome.Identity' mai 23 13:47:41 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.gnome.OnlineAccounts' mai 23 13:47:41 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor' mai 23 13:47:41 endless systemd[3453]: Started Virtual filesystem service - GNOME Online Accounts monitor. mai 23 13:47:42 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating via systemd: service name='org.gtk.GLib.PACRunner' unit='glib-pacrunner.service' requested by ':1.57' (uid=1001 pid=5935 comm="/usr/libexec/goa-daemon " label="unconfined") mai 23 13:47:43 endless systemd[3453]: Starting GLib proxy auto-configuration service... mai 23 13:47:43 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.gtk.GLib.PACRunner' mai 23 13:47:43 endless systemd[3453]: Started GLib proxy auto-configuration service. mai 23 13:47:43 endless goa-daemon[5935]: /org/gnome/OnlineAccounts/Accounts/account_1568089395_0: Setting AttentionNeeded to TRUE because EnsureCredentials() failed with: Falha ao atualizar o token de acesso (rest-proxy-error-quark, 400): Bad Request (goa-error-quark, 4) mai 23 13:47:50 endless systemd[3453]: Started Tracker metadata extractor. mai 23 13:47:57 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.44' (uid=1001 pid=5855 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 13:47:57 endless systemd[3453]: Started Tracker file system data miner. mai 23 13:47:57 endless systemd[3453]: Starting Tracker metadata database store and lookup manager... mai 23 13:47:57 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.freedesktop.Tracker1' mai 23 13:47:57 endless systemd[3453]: Started Tracker metadata database store and lookup manager. mai 23 13:48:30 endless geoclue[1548]: Service not used for 60 seconds. Shutting down.. mai 23 13:48:30 endless systemd[1]: geoclue.service: Succeeded. mai 23 13:48:42 endless systemd[1]: Started /bin/systemctl --no-block start eos-phone-home.service. mai 23 13:48:42 endless systemd[1]: Started Send system activation/daily ping messages to Endless. mai 23 13:48:42 endless systemd[1]: run-rfb1673c161834bebbed58beb29327790.service: Succeeded. mai 23 13:48:42 endless systemd[1]: run-rfb1673c161834bebbed58beb29327790.timer: Succeeded. mai 23 13:48:45 endless eos-phone-home[6152]: INFO:__main__:Already activated! mai 23 13:48:45 endless eos-phone-home[6152]: INFO:__main__:Getting variable: live mai 23 13:48:45 endless eos-phone-home[6152]: INFO:__main__:Getting variable: cmdline mai 23 13:48:45 endless eos-phone-home[6152]: INFO:__main__: - Cmdline: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-94c993d319cdf01ff15a7624dd6855cc9ebe14d7b40f3077a1e965a0de360d8e/vmlinuz-5.4.0-19-generic root=UUID=05c7cd5b-40f9-47d7-a032-e98150535435 rw splash plymouth.ignore-serial-consoles quiet loglevel=2 ostree=/ostree/boot.1/eos/94c993d319cdf01ff15a7624dd6855cc9ebe14d7b40f3077a1e965a0de360d8e/0 mai 23 13:48:45 endless eos-phone-home[6152]: INFO:__main__:Count age: 45817.61792254448 mai 23 13:48:45 endless eos-phone-home[6152]: INFO:__main__:Ping not due yet. mai 23 13:48:45 endless systemd[1]: eos-phone-home.service: Succeeded. mai 23 13:48:58 endless gnome-shell[5894]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. mai 23 13:48:58 endless gnome-shell[5894]: Will monitor session 3 mai 23 13:48:58 endless gnome-shell[6228]: current session already has an ibus-daemon. mai 23 13:48:58 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.238' (uid=1001 pid=5894 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:48:58 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' requested by ':1.55' (uid=1001 pid=5894 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:48:58 endless systemd[1]: Starting Location Lookup Service... mai 23 13:48:58 endless systemd[3453]: Starting sandboxed app permission store... mai 23 13:48:58 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' mai 23 13:48:58 endless systemd[3453]: Started sandboxed app permission store. mai 23 13:48:58 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.GeoClue2' mai 23 13:48:58 endless systemd[1]: Started Location Lookup Service. mai 23 13:49:02 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating service name='org.gnome.Shell.CalendarServer' requested by ':1.55' (uid=1001 pid=5894 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:49:02 endless gnome-shell[5894]: Attempting to add actor of type 'StBoxLayout' to a container of type 'StBoxLayout', but the actor has already a parent of type 'StBoxLayout'. mai 23 13:49:02 endless kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 mai 23 13:49:02 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service' requested by ':1.67' (uid=1001 pid=6276 comm="/usr/libexec/gnome-shell-calendar-server " label="unconfined") mai 23 13:49:03 endless systemd[3453]: Starting Evolution source registry... mai 23 13:49:03 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating service name='ca.desrt.dconf' requested by ':1.69' (uid=1001 pid=6280 comm="/usr/libexec/evolution-source-registry " label="unconfined") mai 23 13:49:03 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'ca.desrt.dconf' mai 23 13:49:03 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.69' (uid=1001 pid=6280 comm="/usr/libexec/evolution-source-registry " label="unconfined") mai 23 13:49:03 endless systemd[3453]: Starting Virtual filesystem metadata service... mai 23 13:49:03 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.gtk.vfs.Metadata' mai 23 13:49:03 endless systemd[3453]: Started Virtual filesystem metadata service. mai 23 13:49:03 endless polkitd[1720]: Registered Authentication Agent for unix-session:3 (system bus name :1.238 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:49:03 endless gnome-shell[5894]: Telepathy is not available, chat integration will be disabled. mai 23 13:49:03 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.gnome.evolution.dataserver.Sources5' mai 23 13:49:03 endless systemd[3453]: Started Evolution source registry. mai 23 13:49:04 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.gnome.Shell.CalendarServer' mai 23 13:49:06 endless systemd[3453]: gnome-shell-x11.service: start operation timed out. Terminating. mai 23 13:49:08 endless gnome-shell[5894]: ../../../gobject/gsignal.c:1745: signal "clicked" already exists in the 'StButton' class ancestry mai 23 13:49:12 endless systemd[3453]: gnome-shell-x11.service: State 'stop-sigterm' timed out. Killing. mai 23 13:49:12 endless systemd[3453]: gnome-shell-x11.service: Killing process 5894 (gnome-shell) with signal SIGKILL. mai 23 13:49:12 endless systemd[3453]: gnome-shell-x11.service: Killing process 5910 (gdbus) with signal SIGKILL. mai 23 13:49:12 endless systemd[3453]: gnome-shell-x11.service: Killing process 5911 (dconf worker) with signal SIGKILL. mai 23 13:49:12 endless systemd[3453]: gnome-shell-x11.service: Killing process 5913 (gnome-s:disk$1) with signal SIGKILL. mai 23 13:49:12 endless systemd[3453]: gnome-shell-x11.service: Killing process 5914 (n/a) with signal SIGKILL. mai 23 13:49:12 endless systemd[3453]: gnome-shell-x11.service: Killing process 5915 (n/a) with signal SIGKILL. mai 23 13:49:12 endless systemd[3453]: gnome-shell-x11.service: Killing process 5917 (n/a) with signal SIGKILL. mai 23 13:49:12 endless systemd[3453]: gnome-shell-x11.service: Killing process 5918 (n/a) with signal SIGKILL. mai 23 13:49:12 endless systemd[3453]: gnome-shell-x11.service: Killing process 5919 (n/a) with signal SIGKILL. mai 23 13:49:12 endless systemd[3453]: gnome-shell-x11.service: Killing process 5920 (JS Helper) with signal SIGKILL. mai 23 13:49:12 endless systemd[3453]: gnome-shell-x11.service: Killing process 6226 (pool-gnome-shel) with signal SIGKILL. mai 23 13:49:12 endless systemd[3453]: gnome-shell-x11.service: Main process exited, code=killed, status=9/KILL mai 23 13:49:12 endless systemd[3453]: gnome-shell-x11.service: Failed with result 'timeout'. mai 23 13:49:12 endless polkitd[1720]: Unregistered Authentication Agent for unix-session:3 (system bus name :1.238, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) (disconnected from bus) mai 23 13:49:12 endless systemd[3453]: Failed to start GNOME Shell on X11. mai 23 13:49:12 endless systemd[3453]: Dependency failed for GNOME Shell on X11. mai 23 13:49:12 endless systemd[3453]: Dependency failed for GNOME X11 Session. mai 23 13:49:12 endless systemd[3453]: Dependency failed for GNOME X11 Session (session: gnome). mai 23 13:49:12 endless systemd[3453]: gnome-session-x11@gnome.target: Job gnome-session-x11@gnome.target/start failed with result 'dependency'. mai 23 13:49:12 endless systemd[3453]: gnome-session-x11@gnome.target: Triggering OnFailure= dependencies. mai 23 13:49:12 endless systemd[3453]: gnome-session-x11.target: Job gnome-session-x11.target/start failed with result 'dependency'. mai 23 13:49:12 endless systemd[3453]: gnome-session-x11.target: Triggering OnFailure= dependencies. mai 23 13:49:12 endless systemd[3453]: gnome-shell-x11.target: Job gnome-shell-x11.target/start failed with result 'dependency'. mai 23 13:49:12 endless systemd[3453]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 1. mai 23 13:49:12 endless systemd[3453]: Started GNOME Session Failed lockdown screen (user). mai 23 13:49:12 endless systemd[3453]: Stopped GNOME Shell on X11. mai 23 13:49:12 endless systemd[3453]: Starting GNOME Shell on X11... mai 23 13:49:12 endless gdm-Xorg-:0[3655]: (II) modeset(0): EDID vendor "CMN", prod id 5596 mai 23 13:49:12 endless gdm-Xorg-:0[3655]: (II) modeset(0): Printing DDC gathered Modelines: mai 23 13:49:12 endless gdm-Xorg-:0[3655]: (II) modeset(0): Modeline "1366x768"x0.0 76.42 1366 1434 1479 1592 768 772 779 800 -hsync -vsync (48.0 kHz eP) mai 23 13:49:12 endless gnome-shell[6300]: Getting parental controls for user 1001 mai 23 13:49:12 endless gnome-shell[6300]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. mai 23 13:49:12 endless gnome-shell[6300]: Will monitor session 3 mai 23 13:49:12 endless gnome-shell[6318]: current session already has an ibus-daemon. mai 23 13:49:13 endless gnome-shell[6300]: Attempting to add actor of type 'StBoxLayout' to a container of type 'StBoxLayout', but the actor has already a parent of type 'StBoxLayout'. mai 23 13:49:13 endless kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 mai 23 13:49:13 endless polkitd[1720]: Registered Authentication Agent for unix-session:3 (system bus name :1.265 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:49:13 endless gnome-shell[6300]: Telepathy is not available, chat integration will be disabled. mai 23 13:49:13 endless gnome-shell[6300]: Failed to create file /run/user/1001/gnome-shell-disable-extensions: Erro ao abrir arquivo “/run/user/1001/gnome-shell-disable-extensions”: Arquivo existe mai 23 13:49:13 endless gnome-shell[6300]: ../../../gobject/gsignal.c:1745: signal "clicked" already exists in the 'StButton' class ancestry mai 23 13:49:14 endless gnome-shell[6300]: Some code accessed the property 'AppIconButton' on the module 'appIconBar'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. mai 23 13:49:15 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating service name='org.gnome.Shell.Notifications' requested by ':1.73' (uid=1001 pid=6300 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:49:15 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.gnome.Shell.Notifications' mai 23 13:49:15 endless systemd[3453]: Started GNOME Shell on X11. mai 23 13:49:15 endless systemd[3453]: Reached target GNOME Session is initialized. mai 23 13:49:15 endless systemd[3453]: Reached target GNOME Session Failed. mai 23 13:49:15 endless systemd[3453]: Reached target GNOME session X11 services. mai 23 13:49:15 endless systemd[3453]: Reached target GNOME Session (session: gnome). mai 23 13:49:15 endless systemd[3453]: Starting Signal initialization done to GNOME Session Manager... mai 23 13:49:15 endless systemd[3453]: Starting GNOME Accessibility settings... mai 23 13:49:15 endless systemd[3453]: Starting GNOME Color management... mai 23 13:49:15 endless systemd[3453]: Starting GNOME Date & Time handling... mai 23 13:49:15 endless systemd[3453]: Starting GNOME Maintenance of expirable data... mai 23 13:49:15 endless systemd[3453]: Starting GNOME Keyboard handling... mai 23 13:49:15 endless systemd[3453]: Starting GNOME Media keys handling... mai 23 13:49:15 endless systemd[3453]: Starting GNOME Power management handling... mai 23 13:49:15 endless systemd[3453]: Starting GNOME Printer notifications... mai 23 13:49:15 endless systemd[3453]: Starting GNOME RFKill handling... mai 23 13:49:15 endless systemd[3453]: Starting GNOME Freedesktop screensaver handling... mai 23 13:49:15 endless systemd[3453]: Starting GNOME Sharing handling... mai 23 13:49:15 endless systemd[3453]: Starting GNOME Smartcard handling... mai 23 13:49:15 endless systemd[3453]: Starting GNOME Sound sample caching handling... mai 23 13:49:15 endless systemd[3453]: Starting GNOME USB protection handling... mai 23 13:49:15 endless systemd[3453]: Starting GNOME Wacom handling... mai 23 13:49:15 endless systemd[3453]: Starting GNOME WWan management... mai 23 13:49:15 endless systemd[3453]: Starting GNOME XSettings... mai 23 13:49:15 endless systemd[3453]: gnome-session-signal-init.service: Succeeded. mai 23 13:49:15 endless systemd[3453]: Started Signal initialization done to GNOME Session Manager. mai 23 13:49:15 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating via systemd: service name='org.gnome.evolution.dataserver.Calendar8' unit='evolution-calendar-factory.service' requested by ':1.67' (uid=1001 pid=6276 comm="/usr/libexec/gnome-shell-calendar-server " label="unconfined") mai 23 13:49:15 endless dbus-daemon[1538]: [system] Activating via systemd: service name='com.endlessm.MogwaiSchedule1' unit='mogwai-scheduled.service' requested by ':1.265' (uid=1001 pid=6300 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:49:15 endless systemd[1]: Starting Download Scheduling Daemon... mai 23 13:49:15 endless NetworkManager[1540]: [1590252555.9490] agent-manager: req[0x7f24880031d0, :1.265/org.gnome.Shell.NetworkAgent/1001]: agent registered mai 23 13:49:15 endless systemd[3453]: Starting Evolution calendar service... mai 23 13:49:16 endless gnome-session-binary[5857]: Entering running state mai 23 13:49:16 endless tracker-store.desktop[6421]: (uint32 2,) mai 23 13:49:16 endless dbus-daemon[1538]: [system] Successfully activated service 'com.endlessm.MogwaiSchedule1' mai 23 13:49:16 endless systemd[1]: Started Download Scheduling Daemon. mai 23 13:49:16 endless gnome-shell[6300]: pushModal: invocation of begin_modal failed mai 23 13:49:16 endless gnome-shell[6300]: pushModal: invocation of begin_modal failed mai 23 13:49:16 endless gnome-shell[6300]: pushModal: invocation of begin_modal failed mai 23 13:49:16 endless gnome-shell[6300]: pushModal: invocation of begin_modal failed mai 23 13:49:16 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.343' (uid=1001 pid=6342 comm="/usr/libexec/gsd-rfkill " label="unconfined") mai 23 13:49:16 endless systemd[3453]: Started GNOME Freedesktop screensaver handling. mai 23 13:49:16 endless systemd[3453]: Reached target GNOME Freedesktop screensaver handling. mai 23 13:49:16 endless systemd[3453]: Started GNOME USB protection handling. mai 23 13:49:16 endless systemd[3453]: Reached target GNOME USB protection handling. mai 23 13:49:16 endless cupsd[1536]: REQUEST localhost - - "POST / HTTP/1.1" 200 362 Create-Printer-Subscriptions successful-ok mai 23 13:49:16 endless systemd[3453]: Started GNOME WWan management. mai 23 13:49:16 endless systemd[3453]: Reached target GNOME WWan management. mai 23 13:49:16 endless systemd[3453]: Started GNOME Maintenance of expirable data. mai 23 13:49:16 endless systemd[3453]: Reached target GNOME Maintenance of expirable data. mai 23 13:49:16 endless systemd[3453]: Started GNOME Sharing handling. mai 23 13:49:16 endless systemd[3453]: Reached target GNOME Sharing handling. mai 23 13:49:16 endless systemd[3453]: Started GNOME Accessibility settings. mai 23 13:49:16 endless systemd[3453]: Reached target GNOME Accessibility settings. mai 23 13:49:16 endless systemd[3453]: Started GNOME Sound sample caching handling. mai 23 13:49:16 endless systemd[3453]: Reached target GNOME Sound sample caching handling. mai 23 13:49:16 endless systemd[1]: Starting Hostname Service... mai 23 13:49:17 endless gsd-sharing[6345]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded. mai 23 13:49:17 endless gsd-sharing[6345]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded. mai 23 13:49:17 endless systemd[3453]: Started GNOME Keyboard handling. mai 23 13:49:17 endless systemd[3453]: Started GNOME Printer notifications. mai 23 13:49:17 endless systemd[3453]: Reached target GNOME Keyboard handling. mai 23 13:49:17 endless systemd[3453]: Reached target GNOME Printer notifications. mai 23 13:49:17 endless systemd[3453]: Started GNOME Wacom handling. mai 23 13:49:17 endless systemd[3453]: Reached target GNOME Wacom handling. mai 23 13:49:17 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.365' (uid=1001 pid=6338 comm="/usr/libexec/gsd-keyboard " label="unconfined") mai 23 13:49:17 endless systemd[1]: Starting Locale Service... mai 23 13:49:17 endless gnome-shell[6300]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). mai 23 13:49:17 endless gnome-shell[6300]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). mai 23 13:49:17 endless gnome-shell[6300]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). mai 23 13:49:17 endless gnome-shell[6300]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). mai 23 13:49:17 endless gnome-shell[6300]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). mai 23 13:49:17 endless gnome-shell[6300]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). mai 23 13:49:17 endless gnome-shell[6300]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). mai 23 13:49:17 endless gnome-shell[6300]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). mai 23 13:49:17 endless gnome-shell[6300]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). mai 23 13:49:17 endless systemd[3453]: Started GNOME Power management handling. mai 23 13:49:17 endless systemd[3453]: Reached target GNOME Power management handling. mai 23 13:49:17 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.hostname1' mai 23 13:49:17 endless systemd[1]: Started Hostname Service. mai 23 13:49:17 endless kernel: rfkill: input handler disabled mai 23 13:49:17 endless systemd[3453]: Started GNOME RFKill handling. mai 23 13:49:17 endless systemd[3453]: Reached target GNOME RFKill handling. mai 23 13:49:17 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.locale1' mai 23 13:49:17 endless systemd[1]: Started Locale Service. mai 23 13:49:17 endless dbus-daemon[1538]: [system] Activating via systemd: service name='com.endlessm.RecordBootSuccess' unit='record-boot-success.service' requested by ':1.373' (uid=1001 pid=6418 comm="dbus-send --system --type=method_call --dest=org.f" label="unconfined") mai 23 13:49:17 endless upowerd[1729]: up_kbd_backlight_brightness_read: assertion 'fd >= 0' failed mai 23 13:49:17 endless gsd-power[6340]: Failed to get brightness: GDBus.Error:org.freedesktop.UPower.GeneralError: error reading brightness mai 23 13:49:17 endless vmware-user.desktop[6571]: vmware-user: could not open /proc/fs/vmblock/dev mai 23 13:49:17 endless systemd[3453]: Started GNOME XSettings. mai 23 13:49:17 endless systemd[3453]: Reached target GNOME XSettings. mai 23 13:49:17 endless kernel: traps: vmtoolsd[6571] general protection fault ip:7fe32b0680dc sp:7fff1ada6418 error:0 in libvmtools.so.0.0.0[7fe32b05c000+45000] mai 23 13:49:18 endless systemd[3453]: Started GNOME Smartcard handling. mai 23 13:49:18 endless systemd[3453]: Reached target GNOME Smartcard handling. mai 23 13:49:18 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.376' (uid=1001 pid=6336 comm="/usr/libexec/gsd-datetime " label="unconfined") mai 23 13:49:18 endless systemd[1]: Starting Time & Date Service... mai 23 13:49:18 endless systemd[3453]: Started GNOME Media keys handling. mai 23 13:49:18 endless systemd[3453]: Reached target GNOME Media keys handling. mai 23 13:49:18 endless gsd-power[6340]: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed mai 23 13:49:18 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.timedate1' mai 23 13:49:18 endless systemd[1]: Started Time & Date Service. mai 23 13:49:21 endless gnome-shell[6300]: GNOME Shell started at Sat May 23 2020 13:49:13 GMT-0300 (-03) mai 23 13:49:21 endless gnome-shell[6300]: Registering session with GDM mai 23 13:49:22 endless systemd[3453]: Started GNOME Color management. mai 23 13:49:22 endless systemd[3453]: Reached target GNOME Color management. mai 23 13:49:23 endless systemd[3453]: Started GNOME Date & Time handling. mai 23 13:49:23 endless systemd[3453]: Reached target GNOME Date & Time handling. mai 23 13:49:23 endless systemd[3453]: Reached target GNOME Session. mai 23 13:49:23 endless systemd[3453]: Reached target Current graphical user session. mai 23 13:49:23 endless systemd[3453]: Condition check resulted in GNOME Initial Setup being skipped. mai 23 13:49:23 endless systemd[3453]: Condition check resulted in GNOME Welcome Tour being skipped. mai 23 13:49:24 endless colord[2288]: failed to get session [pid 6335]: Não há dados disponíveis mai 23 13:49:25 endless gsd-media-keys[6339]: Failed to grab accelerator for keybinding settings:rfkill mai 23 13:49:25 endless gsd-media-keys[6339]: Failed to grab accelerator for keybinding settings:playback-repeat mai 23 13:49:25 endless gsd-media-keys[6339]: Failed to grab accelerator for keybinding settings:playback-random mai 23 13:49:25 endless gsd-media-keys[6339]: Failed to grab accelerator for keybinding settings:hibernate mai 23 13:49:25 endless dbus-daemon[1538]: [system] Activating via systemd: service name='com.endlessm.Updater' unit='eos-updater.service' requested by ':1.383' (uid=1001 pid=6422 comm="/usr/bin/gnome-software --gapplication-service " label="unconfined") mai 23 13:49:25 endless systemd[1]: Starting Endless OS Updater... mai 23 13:49:25 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.gnome.evolution.dataserver.Calendar8' mai 23 13:49:25 endless systemd[3453]: Started Evolution calendar service. mai 23 13:49:25 endless eos-updater[6657]: Acquired a message bus connection mai 23 13:49:25 endless eos-updater[6657]: Clearing error state and changing to state Ready mai 23 13:49:25 endless eos-updater[6657]: Exporting objects mai 23 13:49:25 endless dbus-daemon[1538]: [system] Successfully activated service 'com.endlessm.Updater' mai 23 13:49:25 endless eos-updater[6657]: Acquired the name com.endlessm.Updater mai 23 13:49:25 endless systemd[1]: Started Endless OS Updater. mai 23 13:49:25 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating via systemd: service name='org.gnome.evolution.dataserver.AddressBook10' unit='evolution-addressbook-factory.service' requested by ':1.109' (uid=1001 pid=6395 comm="/usr/libexec/evolution-calendar-factory " label="unconfined") mai 23 13:49:25 endless systemd[3453]: Starting Evolution address book service... mai 23 13:49:26 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook10' mai 23 13:49:26 endless systemd[3453]: Started Evolution address book service. mai 23 13:49:28 endless gnome-software[6422]: plugin appstream took 2,7 seconds to do setup mai 23 13:49:28 endless gnome-software[6422]: enabled plugins: desktop-categories, dpkg, eos-updater, external-appstream, os-release, provenance, appstream, provenance-license, desktop-menu-path, flatpak, hardcoded-blacklist, rewrite-resource, eos, eos-blacklist, icons, malcontent, odrs, key-colors, key-colors-metadata mai 23 13:49:28 endless gnome-software[6422]: disabled plugins: dummy, repos, generic-updates mai 23 13:49:29 endless mogwai-schedule[6358]: Holding service for D-Bus peer ‘:1.383’ because: monitoring allow-downloads property mai 23 13:49:42 endless dbus-daemon[1538]: [system] Failed to activate service 'com.endlessm.RecordBootSuccess': timed out (service_start_timeout=25000ms) mai 23 13:49:48 endless systemd[1]: systemd-hostnamed.service: Succeeded. mai 23 13:49:48 endless systemd[1]: systemd-timedated.service: Succeeded. mai 23 13:49:57 endless NetworkManager[1540]: [1590252597.1283] settings-connection[0x55a71ef78370,6d8338a5-5a59-4474-94ac-04360e95d6df]: write: successfully updated (keyfile: update /etc/NetworkManager/system-connections/BethDaniel.nmconnection (6d8338a5-5a59-4474-94ac-04360e95d6df,"BethDaniel")) mai 23 13:49:57 endless NetworkManager[1540]: [1590252597.1296] audit: op="connection-update" uuid="6d8338a5-5a59-4474-94ac-04360e95d6df" name="BethDaniel" args="802-11-wireless-security.psk,connection.timestamp,user.data" pid=6300 uid=1001 result="success" mai 23 13:49:58 endless systemd[1]: systemd-localed.service: Succeeded. mai 23 13:50:25 endless gnome-shell[6300]: Removing an access point that was never added mai 23 13:50:56 endless systemd[3453]: Started Application launched by gnome-shell. mai 23 13:50:57 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating via systemd: service name='org.freedesktop.Flatpak' unit='flatpak-session-helper.service' requested by ':1.118' (uid=1001 pid=6934 comm="/usr/bin/flatpak run --branch=stable --arch=x86_64" label="unconfined") mai 23 13:50:57 endless systemd[3453]: Starting flatpak session helper... mai 23 13:50:57 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.freedesktop.Flatpak' mai 23 13:50:57 endless systemd[3453]: Started flatpak session helper. mai 23 13:50:57 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Activating via systemd: service name='org.freedesktop.portal.Documents' unit='xdg-document-portal.service' requested by ':1.118' (uid=1001 pid=6934 comm="/usr/bin/flatpak run --branch=stable --arch=x86_64" label="unconfined") mai 23 13:50:58 endless systemd[3453]: Starting flatpak document portal service... mai 23 13:50:58 endless dbus-daemon[3867]: [session uid=1001 pid=3867] Successfully activated service 'org.freedesktop.portal.Documents' mai 23 13:50:58 endless systemd[3453]: Started flatpak document portal service. mai 23 13:50:58 endless systemd[3453]: Started flatpak-org.libreoffice.LibreOffice-6934.scope. mai 23 13:50:58 endless systemd[3453]: gnome-launched-org.libreoffice.LibreOffice.writer.desktop-6934.scope: Succeeded. mai 23 13:51:11 endless soffice.bin[6989]: Failed to load module "canberra-gtk-module" mai 23 13:51:11 endless soffice.bin[6989]: Failed to load module "canberra-gtk-module" mai 23 13:51:26 endless systemd[3453]: tracker-extract.service: Succeeded. mai 23 13:51:31 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.383' (uid=1001 pid=6422 comm="/usr/bin/gnome-software --gapplication-service " label="unconfined") mai 23 13:51:31 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.locale1' mai 23 13:51:31 endless systemd[1]: Starting Locale Service... mai 23 13:51:31 endless systemd[1]: Started Locale Service. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Session Failed. mai 23 13:51:43 endless systemd[3453]: Stopped target Current graphical user session. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Session. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Session (session: gnome). mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Accessibility settings. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Color management. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Date & Time handling. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Maintenance of expirable data. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Keyboard handling. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Media keys handling. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Power management handling. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Printer notifications. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME RFKill handling. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Freedesktop screensaver handling. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Sharing handling. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Smartcard handling. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Sound sample caching handling. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME USB protection handling. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Wacom handling. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME WWan management. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME XSettings. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME session X11 services. mai 23 13:51:43 endless systemd[3453]: Stopping GNOME Accessibility settings... mai 23 13:51:43 endless systemd[3453]: Stopping GNOME Color management... mai 23 13:51:43 endless systemd[3453]: Stopping GNOME Date & Time handling... mai 23 13:51:43 endless systemd[3453]: Stopping GNOME Maintenance of expirable data... mai 23 13:51:43 endless systemd[3453]: Stopping GNOME Keyboard handling... mai 23 13:51:43 endless systemd[3453]: Stopping GNOME Media keys handling... mai 23 13:51:43 endless systemd[3453]: Stopping GNOME Power management handling... mai 23 13:51:43 endless systemd[3453]: Stopping GNOME Printer notifications... mai 23 13:51:43 endless systemd[3453]: Stopping GNOME RFKill handling... mai 23 13:51:43 endless systemd[3453]: Stopping GNOME Freedesktop screensaver handling... mai 23 13:51:43 endless systemd[3453]: Stopping GNOME Sharing handling... mai 23 13:51:43 endless systemd[3453]: Stopping GNOME Smartcard handling... mai 23 13:51:43 endless systemd[3453]: Stopping GNOME Sound sample caching handling... mai 23 13:51:43 endless systemd[3453]: Stopping GNOME USB protection handling... mai 23 13:51:43 endless systemd[3453]: Stopping GNOME Wacom handling... mai 23 13:51:43 endless systemd[3453]: Stopping GNOME WWan management... mai 23 13:51:43 endless systemd[3453]: Stopping GNOME XSettings... mai 23 13:51:43 endless cupsd[1536]: REQUEST localhost - - "POST / HTTP/1.1" 200 154 Cancel-Subscription successful-ok mai 23 13:51:43 endless cupsd[1536]: REQUEST localhost - - "POST / HTTP/1.1" 200 154 Cancel-Subscription client-error-not-found mai 23 13:51:43 endless gsd-print-notif[6341]: Source ID 3 was not found when attempting to remove it mai 23 13:51:43 endless systemd[3453]: gnome-session-failed.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME Session Failed lockdown screen (user). mai 23 13:51:43 endless kernel: rfkill: input handler enabled mai 23 13:51:43 endless systemd[3453]: gsd-a11y-settings.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME Accessibility settings. mai 23 13:51:43 endless systemd[3453]: gsd-color.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME Color management. mai 23 13:51:43 endless systemd[3453]: gsd-datetime.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME Date & Time handling. mai 23 13:51:43 endless systemd[3453]: gsd-housekeeping.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME Maintenance of expirable data. mai 23 13:51:43 endless systemd[3453]: gsd-power.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME Power management handling. mai 23 13:51:43 endless systemd[3453]: gsd-print-notifications.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME Printer notifications. mai 23 13:51:43 endless systemd[3453]: gsd-rfkill.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME RFKill handling. mai 23 13:51:43 endless systemd[3453]: gsd-screensaver-proxy.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME Freedesktop screensaver handling. mai 23 13:51:43 endless systemd[3453]: gsd-sharing.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME Sharing handling. mai 23 13:51:43 endless systemd[3453]: gsd-smartcard.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME Smartcard handling. mai 23 13:51:43 endless systemd[3453]: gsd-sound.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME Sound sample caching handling. mai 23 13:51:43 endless systemd[3453]: gsd-usb-protection.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME USB protection handling. mai 23 13:51:43 endless systemd[3453]: gsd-wacom.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME Wacom handling. mai 23 13:51:43 endless systemd[3453]: gsd-wwan.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME WWan management. mai 23 13:51:43 endless systemd[3453]: gsd-keyboard.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME Keyboard handling. mai 23 13:51:43 endless systemd[3453]: gsd-media-keys.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME Media keys handling. mai 23 13:51:43 endless systemd[3453]: gsd-xsettings.service: Succeeded. mai 23 13:51:43 endless systemd[3453]: Stopped GNOME XSettings. mai 23 13:51:43 endless systemd[3453]: Stopped target GNOME Session is initialized. mai 23 13:51:43 endless systemd[3453]: Stopping GNOME Shell on X11... mai 23 13:51:44 endless gnome-shell[6300]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct. mai 23 13:51:44 endless gnome-shell[6300]: Object Meta.BackgroundActor (0x55600524f380), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: #0 7ffd635a22a0 I resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571 (3505245b6c40 @ 25) mai 23 13:51:44 endless gnome-shell[6300]: #1 556004c6b028 i /usr/share/gnome-shell/extensions/eos-watermark@endlessm.com/extension.js:273 (2c432e3de6a0 @ 86) mai 23 13:51:44 endless gnome-shell[6300]: #2 7ffd635a3130 I self-hosted:1009 (2bbfaf04de20 @ 423) mai 23 13:51:44 endless gnome-shell[6300]: JS ERROR: Error: Argument 'instance' (type interface) may not be null _init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571:24 _onDestroy@/usr/share/gnome-shell/extensions/eos-watermark@endlessm.com/extension.js:273:45 mai 23 13:51:44 endless gnome-shell[6300]: JS ERROR: TypeError: actor.get_meta_window(...) is null _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:2043:32 onStopped@resource:///org/gnome/shell/ui/windowManager.js:2013:39 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:71:13 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:147:56 mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cff7c80. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cff7c80. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cff8c60. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d001740. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d001740. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d002130. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d009d50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d009d50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c9ddcb0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d014190. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d014190. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d0148e0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d01bba0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d01bba0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d01cd50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d023ca0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d023ca0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d024ec0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d02b170. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d02b170. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d02bb90. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d0338d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d0338d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d033fc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d03af10. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d03af10. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d03b8e0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d041b80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d041b80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d043180. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d04a740. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d04a740. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d04b570. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d0527f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d0527f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d0531e0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d05a270. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d05a270. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d05ac30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d063350. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d063350. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d063d70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d06b880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d06b880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d06c980. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d072ca0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d072ca0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d074860. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d07b170. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d07b170. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d07bb90. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d083080. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d083080. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d0839f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d08a2e0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d08a2e0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d08ad00. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d091fa0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d091fa0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d093130. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d099c80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d099c80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d09ae20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d0a1d00. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d0a1d00. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d0a2720. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d0a95d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d0a95d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d0a9ff0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d0b1480. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600d0b1480. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600d0b1cd0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cfeebc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600cf9ef70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cfa7630. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cfa7630. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cfa8810. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cf9ef70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cfafc80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cfafc80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cfb0460. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cf9ef70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cfb7500. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cfb7500. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cfb8860. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cf9ef70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cfbfbe0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cfbfbe0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cfc0600. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cf9ef70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cfc6d70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cfc6d70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cfc7740. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cf9ef70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cfcf080. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cfcf080. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cfd0060. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cf9ef70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cfd7080. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cfd7080. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cfd79d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cf9ef70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf06c80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf06c80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf07640. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf0e180. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf0e180. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf0ead0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf16580. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf16580. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf16f20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf1dc80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf1dc80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf1e3c0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf25460. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf25460. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf266c0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf2e480. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf2e480. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf2eb50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf35880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf35880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf36010. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf3d110. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf3d110. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf3dae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf44ca0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf44ca0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf456c0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf4c8d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf4c8d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf4d460. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf54080. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf54080. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf54830. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf5e2f0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf5e2f0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf5ed10. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf65800. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf65800. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf661d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf6d470. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf6d470. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf6de90. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf75320. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf75320. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf76550. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf7c880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf7c880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf7d800. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf84af0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cf84af0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cf85c60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cefcee0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600ce7bd60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ce85880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ce85880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ce86110. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600ce7bd60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ce8cc00. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ce8cc00. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ce8d5d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600ce7bd60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ce945d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ce945d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ce95460. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600ce7bd60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ce9c480. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ce9c480. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ce9d0c0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600ce7bd60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cea4330. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cea4330. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cea4d50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600ce7bd60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ceac040. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ceac040. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ceaca10. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600ce7bd60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ceb3d70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ceb3d70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ceb4740. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600ce7bd60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cebade0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cebade0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cebc060. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600ce7bd60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cec28d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cec28d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cec3ac0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600ce7bd60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cecce20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cecce20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cecdc60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600ce7bd60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ced4650. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ced4650. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ced5070. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600ce7bd60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cedc530. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cedc530. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cedcf00. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600ce7bd60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cee39e0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cee39e0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cee4c60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600ce7bd60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600b452b30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b45bd90. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b45bd90. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b45cbc0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b452b30. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b4638f0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b4638f0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b464860. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b452b30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b46b940. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b46b940. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b46c3a0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b452b30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b473200. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b473200. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b473c60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b452b30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b47a6b0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b47a6b0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b47b110. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b452b30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b4823c0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b4823c0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b4835c0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b452b30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b48c880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b48c880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b48d2b0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b452b30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b494480. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b494480. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b494d50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b452b30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b49b830. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b49b830. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b49c200. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b452b30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ce526d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ce526d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ce530a0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b452b30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ce5a480. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ce5a480. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ce5b5a0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b452b30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ce62080. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ce62080. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ce629d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b452b30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbd8930. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbd8930. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cbd9350. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbe0430. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbe0430. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cbe0e50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbe70a0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbe70a0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cbe8180. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbefc80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbefc80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cbf0ac0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cce89e0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cce89e0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cce9440. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cceff90. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cceff90. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ccf09c0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ccf7c10. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ccf7c10. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ccf8670. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ccffc80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ccffc80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cd00d00. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cd06840. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cd06840. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cd07a70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cd0f590. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cd0f590. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cd0ffb0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cd17880. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cd17880. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cd1a460. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cd204f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cd204f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cd20f10. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b4219d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b4219d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b422c60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b429880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b429880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b42a8c0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b430720. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b430720. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b4320b0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b438ff0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b438ff0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b439a20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cbcf4f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbf8c80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbf8c80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cbf9600. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc00ef0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc00ef0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc018c0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc08860. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc08860. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc09230. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc2cc80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc2cc80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc2dc60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc34ae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc34ae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc35950. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc3cb90. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc3cb90. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc3d580. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc440b0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc440b0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc45060. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc4bc40. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc4bc40. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc4c660. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc54310. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc54310. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc554c0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc5cfd0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc5cfd0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc5e460. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc65520. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc65520. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc65ec0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc6d6f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc6d6f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc6e060. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc74b10. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc74b10. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc75530. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc9d290. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc9d290. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc9ec50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cca03a0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cca03a0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc9e460. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc82320. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc82320. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc83520. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc8a1b0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc8a1b0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc8abd0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc92080. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc92080. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc92880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc9a480. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cc9a480. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cc9b180. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ccac190. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ccac190. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ccacfc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ccb3c80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ccb3c80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ccb46e0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ccbbaf0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ccbbaf0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ccbc440. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ccc2f30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ccc2f30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ccc3950. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cccb480. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cccb480. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ccccc60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ccd3010. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ccd3010. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ccd6460. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ccdd120. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ccdd120. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ccddac0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cd24360. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cd24360. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cd24db0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cd44c20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cd44c20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cd45670. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cd2c380. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cd2c380. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cd2d090. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600cc23a50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cad7610. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cad7610. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cad8860. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cadf1a0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cadf1a0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cadfbc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cae75b0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cae75b0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cae87e0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600caee6c0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600caee6c0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600caf01a0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600caf6cb0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600caf6cb0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600caf76d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cafe980. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cafe980. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600caff370. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb06880. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb06880. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb07250. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb0dcf0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb0dcf0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb0eb20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb155f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb155f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb163c0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb1dc80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb1dc80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb1e6a0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb24930. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb24930. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb25350. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb2ce70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb2ce70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb2d860. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb35080. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb35080. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb38460. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb3dc30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb3dc30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb3ee50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb46740. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb46740. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb47130. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb4e480. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb4e480. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb4edf0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb556a0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb556a0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb560c0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb5cf60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb5cf60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb5ec60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb64c20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb64c20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb66060. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb6d0e0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb6d0e0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb6dad0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb74b70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb74b70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb75590. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb7c830. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb7c830. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb7d250. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb83910. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb83910. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb84730. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb8ba20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb8ba20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb8c7f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb93900. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb93900. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb96460. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb9cd70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cb9cd70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cb9d760. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cba4e20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cba4e20. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cba5850. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbac0f0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbac0f0. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cbad320. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbb3bb0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbb3bb0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cbb4dd0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbbc880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbbc880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cbbd220. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbc3d30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600cbc3d30. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600cbc4750. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600caceae0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9a7880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9a7880. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c9a8860. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9d4570. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9d4570. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c9d5790. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c73d790. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c73d790. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c73e150. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9e70a0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9e70a0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c9e7af0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9fd8d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9fd8d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c9fe330. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca05460. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca05460. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca06460. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca0c780. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca0c780. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca0d5f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca148f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca148f0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca15c60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca1d560. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca1d560. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca1df50. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca26290. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca26290. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca26cc0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca2e5d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca2e5d0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca2f860. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca36380. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca36380. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca37570. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca3d9e0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca3d9e0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca3e3a0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca46340. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca46340. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca46d70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca4e080. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca4e080. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca4ea80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca55510. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca55510. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca56860. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca5d1a0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca5d1a0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca5e410. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca65c80. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca65c80. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca66110. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca6ca70. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca6ca70. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca6d4a0. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca74ba0. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca74ba0. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca755c0. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca7d080. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca7d080. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca7dc60. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca83ad0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca83ad0. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca85130. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:44 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:44 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca8bbe0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca8bbe0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca8c600. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca93c80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca93c80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca94560. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca9b050. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ca9b050. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ca9e460. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600caa5330. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600caa5330. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600caa6530. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600caac8d0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600caac8d0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600caadaa0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c99ed20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8f0b00. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8f0b00. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c8f1920. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8f8ce0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8f8ce0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c8f9700. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c900c80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c900c80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c901bf0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c907ec0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c907ec0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c9088e0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c90ffc0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c90ffc0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c911130. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c918080. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c918080. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c919060. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9220d0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9220d0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c922670. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c929a90. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c929a90. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c92a450. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9318a0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9318a0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c931f40. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c938a30. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c938a30. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c939c60. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9405a0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9405a0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c9417c0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c948b40. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c948b40. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c94a060. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9508d0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9508d0. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c9512a0. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c958160. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c958160. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c958b80. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c95fc20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c95fc20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c960c60. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9670d0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9670d0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c967ef0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c96fa10. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c96fa10. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c970390. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c977640. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c977640. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c97a460. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ad89670. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ad89670. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ad8a090. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9d0e50. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9d0e50. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c9e9ce0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9f08b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9f08b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c9bedf0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9965a0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c9965a0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c9985b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c996db0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c996db0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c997240. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c98d660. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c98d660. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c98e080. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c8e7f20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600c89f570. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8a9080. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8a9080. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c8a9890. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c89f570. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8b89f0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8b89f0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c8b9410. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c89f570. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8b1000. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8b1000. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c8b1a20. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c89f570. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8c0140. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8c0140. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c8c1320. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c89f570. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8c7e40. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8c7e40. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c8c9010. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c89f570. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8d0110. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8d0110. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c8d0b30. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c89f570. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600c85df80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c865f90. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c865f90. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c866c60. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c85df80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c86e910. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c86e910. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c86f2e0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c85df80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c876500. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c876500. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c877460. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c85df80. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c87cec0. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c87cec0. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c880460. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c85df80. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c887af0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c887af0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c888510. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c85df80. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c88efc0. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c88efc0. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c88f9e0. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c85df80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600c7cd2b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7d6400. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7d6400. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c7d6da0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c7cd2b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7dd9e0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7dd9e0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c7de3b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c7cd2b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7e5f40. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7e5f40. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c7e7170. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c7cd2b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7eec00. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7eec00. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c7f0060. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c7cd2b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7f7020. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7f7020. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c7f7a40. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c7cd2b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7fe130. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7fe130. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c7feb00. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c7cd2b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8055a0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8055a0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c805f90. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c7cd2b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c80dac0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c80dac0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c80e860. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c7cd2b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c815080. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c815080. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c815da0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c7cd2b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c81ce50. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c81ce50. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c81d7f0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c7cd2b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8246f0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c8246f0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c825110. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c7cd2b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c82bc80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c82bc80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c82d060. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c7cd2b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c833f40. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c833f40. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c8350e0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c7cd2b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c83bbc0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c83bbc0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c83d0b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c7cd2b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c649dc0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c649dc0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c64a760. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c651c80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c651c80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c652370. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c659080. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c659080. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c65a2a0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c661c80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c661c80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c662370. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c669880. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c669880. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c669ff0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c671310. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c671310. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c671cb0. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c67af90. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c67af90. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c67b9b0. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c681c50. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c681c50. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c683080. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c68a080. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c68a080. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c68a930. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c691c40. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c691c40. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c692610. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c69a0d0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c69a0d0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c69aac0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6a1550. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6a1550. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c6a1f70. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6a8ef0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6a8ef0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c6aa0c0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6b10d0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6b10d0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c6b1a70. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6b8570. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6b8570. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c6b8f10. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6c09b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6c09b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c6c1860. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6c8290. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6c8290. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c6c8cb0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6cf340. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6cf340. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c6d05a0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6d7c80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6d7c80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c6d8360. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6deea0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6deea0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c6df8c0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6e6c00. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6e6c00. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c6e75a0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6eec80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6eec80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c6ef400. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6f8530. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c6f8530. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c6f9700. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c700480. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c700480. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c700bd0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c708080. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c708080. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c7088b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c70fba0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c70fba0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c710570. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c716c80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c716c80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c717650. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c71eb40. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c71eb40. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c71fda0. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c727080. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c727080. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c727a10. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c72e4b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c72e4b0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c72eed0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c735fc0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c735fc0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c736990. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5b0280. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5b0280. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c73ef80. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c746160. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c746160. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c747860. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c74e480. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c74e480. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:45 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c74ebc0. mai 23 13:51:45 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c757cb0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c757cb0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c7586d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c75f550. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c75f550. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c75ffb0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c766ae0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c766ae0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c767500. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c76edc0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c76edc0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c770080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c777480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c777480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c777d00. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c77efa0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c77efa0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c77f9c0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7866c0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7866c0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c787090. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c78dc80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c78dc80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c78ece0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c795800. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c795800. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c796a20. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c79dce0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c79dce0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c79e6f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7a6480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7a6480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c7a6d80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7ad0c0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c7ad0c0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c7ada60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c641850. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c589080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c589080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c589750. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c590320. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c590320. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c590cc0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c598070. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c598070. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c599220. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5a0880. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5a0880. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c5a10c0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5a7360. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5a7360. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c5a7d80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5af890. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5af890. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c4e4b90. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5b80c0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5b80c0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c5b8af0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5bedd0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5bedd0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c5bffc0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5c7480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5c7480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c5c7e80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5ce950. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5ce950. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c5cf320. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5d5dc0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5d5dc0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c5d67e0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5deaa0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5deaa0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c5df460. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5e7d90. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5e7d90. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c5e8bc0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5efca0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5efca0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c5f0490. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5f7770. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5f7770. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c5f8140. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5ff5f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5ff5f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c5fffe0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c606ac0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c606ac0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c607c60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c60ec80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c60ec80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c60fc90. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c617080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c617080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c617a00. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c61e4d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c61e4d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c61f500. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c626880. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c626880. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c6271a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c57f970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4bda90. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4bda90. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c4be480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4c5010. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4c5010. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c4c6060. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4ccf40. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4ccf40. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c4cd960. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4d50e0. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4d50e0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c4d5f40. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4dc880. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4dc880. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c4dd1d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4e41a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4e41a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c4e51a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4ec480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4ec480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c4ecc30. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4f6570. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4f6570. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c4f6f60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4fda30. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4fda30. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c4fec30. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c506480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c506480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c506cd0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c50d570. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c50d570. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c50df60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c514a70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c514a70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c515440. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c51c4f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c51c4f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c51cf10. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5245d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5245d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c5257f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c52c880. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c52c880. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c52d060. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c533b60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c533b60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c534550. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c53ba70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c53ba70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c53c440. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5435d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5435d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c543f20. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c54a7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c54a7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c54e460. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c555880. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c555880. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c556120. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c55cc80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c55cc80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c55d5d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5640e0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c5640e0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c564ab0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c4b3b50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3285b0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3285b0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c3296b0. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c32fe70. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c32fe70. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c331060. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c337ef0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c337ef0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c339120. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c340410. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c340410. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c340db0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3478b0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3478b0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c34a460. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c351920. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c351920. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c352340. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c359200. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c359200. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c35a460. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3606f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3606f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c361920. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c368ba0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c368ba0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c3695c0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c371480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c371480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c372460. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c378620. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c378620. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c379040. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c37fef0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c37fef0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c380d10. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c388080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c388080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c388dc0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c38f090. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c38f090. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c38fa80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3975a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3975a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c397fc0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c39f480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c39f480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c39fcb0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3a5f30. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3a5f30. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c3a7150. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3ae400. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3ae400. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c3af620. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3b5ef0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3b5ef0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c3b68a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3bda90. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3bda90. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c3be450. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3c5370. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3c5370. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c3c5d60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3cf030. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3cf030. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c3d0250. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3d6d10. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3d6d10. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c3d7f30. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3df220. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3df220. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c3dfbc0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3e6c60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3e6c60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c3e7680. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3ee110. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3ee110. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c3eeb30. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3f6480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3f6480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c3f7c60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3fe0b0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c3fe0b0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c3feed0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c405970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c405970. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c406390. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c40dc80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c40dc80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c40e460. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x5560062a1a20. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x5560062a1a20. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5560062a1f80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b93c090. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b93c090. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b93c520. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b261c80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b261c80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b262c60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c443880. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c443880. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c443d10. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c448a70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c448a70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c449a60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c44e480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c44e480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c44e910. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c453cc0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c453cc0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c454c60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c45d2d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c45d2d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c45e480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c464f20. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c464f20. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c465910. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c46cbf0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c46cbf0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c46d5c0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4749a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c4749a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c4753c0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c47bf60. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c47bf60. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c47cd50. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c484050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c484050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c484e20. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c48c580. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c48c580. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c48d860. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c493950. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c493950. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c494320. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c31f640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c207080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c207080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c207890. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c20e2a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c20e2a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c20ec70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c216720. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c216720. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c217110. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c21dc80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c21dc80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c21e9c0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c225480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c225480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c225e70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c22d5a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c22d5a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c22e860. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c235480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c235480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c235c60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c23cdb0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c23cdb0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c23d780. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c244830. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c244830. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c245a50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c24c0e0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c24c0e0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c24cb00. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c253da0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c253da0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c254760. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c25de90. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c25de90. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c25e860. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c265310. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c265310. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c265d00. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c26cfb0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c26cfb0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c26e1a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c275480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c275480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c275e20. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c27c180. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c27c180. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c27cad0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c283e20. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c283e20. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c2847f0. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c28cac0. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c28cac0. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c28d490. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c293720. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c293720. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c294550. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c29bc80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c29bc80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c29c620. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2a38a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2a38a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c2a42f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2aa620. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2aa620. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c2aafc0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2b26d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2b26d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c2b3860. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2ba880. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2ba880. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c2bb9c0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2c2520. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2c2520. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c2c3720. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2ca220. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2ca220. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c2cabc0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2d2080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2d2080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c2d2860. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2db740. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2db740. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c2dc160. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2e3020. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2e3020. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c2e4220. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2ebca0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2ebca0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c2ec6e0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2f3180. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2f3180. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c2f3ba0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2faea0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c2faea0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c2fb870. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c302390. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c302390. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c302d60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c1fc7f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0eba90. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0eba90. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c0ecc60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0f3e10. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0f3e10. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c0f47e0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0fb880. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0fb880. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c0fc100. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c102a80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c102a80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c103c90. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c10a710. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c10a710. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c10b930. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1123c0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1123c0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c112de0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c11b080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c11b080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c11baa0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c122140. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c122140. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c122b30. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1295d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1295d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c12a3f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c131730. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c131730. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c132550. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1390a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1390a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c139a60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c140cd0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c140cd0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c1416c0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c14a9b0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c14a9b0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c14b3d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c152080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c152080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c153890. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c159be0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c159be0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c15ae00. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c162100. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c162100. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c162b20. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c16a080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c16a080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c16a800. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c170b40. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c170b40. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c171c90. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c179800. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c179800. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c17aa20. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1814e0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1814e0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c182740. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c188a70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c188a70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c189490. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c190c80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c190c80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c191560. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c198880. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c198880. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c199060. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1a0130. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1a0130. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c1a0f50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1a7e00. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1a7e00. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c1a8c30. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1af6f0. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1af6f0. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c1b00e0. mai 23 13:51:46 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1b6f90. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1b6f90. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c1b79b0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1bec50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1bec50. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c1bf640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1c8720. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1c8720. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c1c9950. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1d0000. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1d0000. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c1d1220. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1d7ef0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1d7ef0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c1d88e0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1dfc10. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c1dfc10. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c1e05e0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600c0e2b70. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf45d60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf45d60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bf46780. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfbf4d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfbf4d0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bfbfef0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfc6a40. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfc6a40. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bfc7860. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfce440. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfce440. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bfcf240. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfd8e20. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfd8e20. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bfd97f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfe0340. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfe0340. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bfe14a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfe8810. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfe8810. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bfe91e0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfefab0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfefab0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bff0c60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bff7990. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bff7990. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bff8b60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfff620. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfff620. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c000010. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0072f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0072f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c007ce0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c017ca0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c017ca0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c0186f0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c00fc80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c00fc80. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c010c60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c01e9a0. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c01e9a0. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c01f860. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c026930. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c026930. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c027350. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c02e080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c02e080. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c02ec60. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c035cd0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c035cd0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c0366a0. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c03d640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c03d640. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c03e460. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c045480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c045480. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c046090. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c04cc20. mai 23 13:51:46 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:46 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c04cc20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c04d5e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c056720. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c056720. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c0570f0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c05e2e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c05e2e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c05ecd0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c065bd0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c065bd0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c066d80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c06e0e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c06e0e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c06f2d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c075570. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c075570. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c075f90. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c07db40. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c07db40. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c07e560. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c085470. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c085470. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c085e20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c08c500. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c08c500. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c08d860. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0945d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0945d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c0957c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c09cc80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c09cc80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c09d4b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0a3f60. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0a3f60. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c0a4950. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0ab7f0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0ab7f0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c0ac210. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0b3480. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0b3480. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c0b4c60. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0bafa0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0bafa0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c0bbdc0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0c2f10. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600c0c2f10. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600c0c3900. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf3d050. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bf5f6b0. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf68600. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf68600. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bf68fd0. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf5f6b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf70c80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf70c80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bf71530. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf5f6b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf77e10. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf77e10. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bf787b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf5f6b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf7f660. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf7f660. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bf808c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf5f6b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf87480. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf87480. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bf88460. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf5f6b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf8eef0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf8eef0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bf8f8b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf5f6b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf97440. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf97440. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bf98c60. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf5f6b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf9f080. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf9f080. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bf9fdd0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf5f6b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfa6880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfa6880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bfa76a0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf5f6b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfae590. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfae590. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bfaf3c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf5f6b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfb6880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bfb6880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bfb7040. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bf5f6b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600befc510. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf05140. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf05140. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bf05ae0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600befc510. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf0c9b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf0c9b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bf0dbe0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600befc510. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf14d20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf14d20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bf156e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600befc510. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf1ccd0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf1ccd0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bf1dcf0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600befc510. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf24980. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bf24980. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bf25350. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600befc510. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600beb20e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bebb880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bebb880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bebd170. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600beb20e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bec5480. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bec5480. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bec5e80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600beb20e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600becd950. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600becd950. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bece340. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600beb20e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bed5880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bed5880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bed5fe0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600beb20e0. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bedc280. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bedc280. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bedd060. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600beb20e0. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bee4150. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bee4150. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bee4f70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600beb20e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600be9e450. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600be89e80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600be75a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd64600. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd64600. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bd65710. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd6c220. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd6c220. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bd6cc40. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd73f40. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd73f40. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bd74930. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd7c490. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd7c490. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bd7ce30. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd838c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd838c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bd84690. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd8d200. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd8d200. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bd8e030. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd95c80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd95c80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bd96160. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd9c4b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd9c4b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bd9ced0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bda42b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bda42b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bda4cd0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdacc80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdacc80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bdadda0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdb38d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdb38d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bdb4aa0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdbc3d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdbc3d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bdbcdf0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdc4080. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdc4080. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bdc4880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdcb410. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdcb410. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bdcc540. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdd2c80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdd2c80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bdd4460. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bddace0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bddace0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bddbf10. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bde31d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bde31d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bde3ba0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdea640. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdea640. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bdeb060. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdf2120. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdf2120. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bdf2b40. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdf9810. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bdf9810. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bdfa5f0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be015d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be015d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600be04460. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be0b650. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be0b650. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600be0c070. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be13410. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be13410. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600be13e00. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be1acd0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be1acd0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600be1b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be22120. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be22120. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600be233e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be29c00. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be29c00. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600be2ae20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be32880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be32880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600be330e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be39b70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be39b70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600be3a590. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be41c30. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be41c30. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600be42650. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be490e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be490e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600be4a3a0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be50e00. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be50e00. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600be51fe0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be59290. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600be59290. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600be5a060. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd5b670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bd0b1d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd14880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd14880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bd15a50. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd0b1d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd1c500. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd1c500. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bd1d460. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd0b1d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd243c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd243c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bd24d90. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd0b1d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd2c480. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd2c480. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bd2cc60. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd0b1d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd33710. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd33710. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bd34490. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd0b1d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd3b160. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd3b160. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bd3bf90. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd0b1d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd42af0. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bd42af0. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bd434a0. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bd0b1d0. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc41640. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc41640. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bc41fe0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc48c80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc48c80. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bc49480. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc50320. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc50320. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bc51860. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc57d60. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc57d60. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bc58f90. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc60480. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc60480. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bc61530. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc68120. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc68120. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bc68af0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc6fe20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc6fe20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bc70810. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc778e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc778e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bc78b40. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc7ed50. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc7ed50. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bc7ff40. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc89840. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc89840. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bc8a210. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc90cb0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc90cb0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bc916d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc98a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bc98a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bc99460. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bca0b90. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bca0b90. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bca1930. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bca7850. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bca7850. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bca8620. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bcafed0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bcafed0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bcb08f0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bcb7b50. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bcb7b50. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bcb84f0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bcbefc0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bcbefc0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bcbf9e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bcc70a0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bcc70a0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bcc82c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bcced30. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bcced30. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bccff60. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bcd6a20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bcd6a20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bcd7410. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bcde880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bcde880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bcdf240. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bce8880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bce8880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bce9860. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bcefbe0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600bcefbe0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600bcf0e00. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600bc384d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bc23f90. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bc0fb00. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bbfa670. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x556009ffb410. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bbc0d90. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bbada50. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bb98010. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bb828a0. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bb6e450. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bb58f40. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bb44240. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bb2ffb0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bb07e00. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600baf3a40. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600badfe50. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bb1e220. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600bac9570. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600b98bd50. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600b977140. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600baad850. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8546e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8546e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b855100. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8af080. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8af080. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b8af9b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8b6550. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8b6550. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b8b7460. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8bec20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8bec20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b8bfa40. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8c6880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8c6880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b8c7000. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8ce7f0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8ce7f0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b8cf210. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8d5f80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8d5f80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b8d69a0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8dce10. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8dce10. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b8de060. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8e5190. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8e5190. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b8e63c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8ed750. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8ed750. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b8f0460. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8f6ca0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8f6ca0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b8f76c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8fedf0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8fedf0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b8ff810. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b9073c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b9073c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b908580. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b90e150. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b90e150. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b90f370. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b9168d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b9168d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b916ef0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b91e480. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b91e480. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b91ee80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b9251f0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b9251f0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b926c60. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b92dfd0. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b92dfd0. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b92ed80. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b936080. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b936080. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600a24b320. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b9404d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b9404d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b940ef0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b947e80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b947e80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b9488a0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b94fc80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b94fc80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b950600. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b957ba0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b957ba0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b958d10. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b95f160. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b95f160. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b960390. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b84b050. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600b86c940. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b875e70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b875e70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b876860. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b86c940. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b87dcf0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b87dcf0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b87e710. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b86c940. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b884e90. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b884e90. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b8858b0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b86c940. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b88cb20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b88cb20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b88e460. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b86c940. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8954a0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8954a0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b895ec0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b86c940. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b89cad0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b89cad0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b89d490. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b86c940. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8a6c80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b8a6c80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b8a7450. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b86c940. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7b2620. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7b2620. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b7b3860. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7ba580. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7ba580. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b7bafa0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7c2430. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7c2430. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b7c3250. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7ca080. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7ca080. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b7caa20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7d1880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7d1880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b7d1fd0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7d91d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7d91d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b7d9bc0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7e1770. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7e1770. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b7e2190. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7e9110. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7e9110. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b7ec460. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7f3080. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7f3080. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b7f38e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7faaa0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7faaa0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b7fb4c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b802c80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b802c80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b8033d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b809f20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b809f20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b80a940. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b812740. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b812740. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b8139a0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b819cf0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b819cf0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b81a6e0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b822350. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b822350. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b822cb0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b82a0c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b82a0c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b82aa60. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b830e20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b830e20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b831810. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b7a8a70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600b726850. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b72f8d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b72f8d0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b731060. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b726850. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b737880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b737880. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b7388c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b726850. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b73f480. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b73f480. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b73fd80. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b726850. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b747170. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b747170. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b747b60. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b726850. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b74f480. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b74f480. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b74fce0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b726850. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b756860. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b756860. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b757c60. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b726850. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b760590. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b760590. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b761790. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b726850. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b768b30. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b768b30. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b769500. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b726850. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b770120. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b770120. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b770b40. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b726850. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b778100. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b778100. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b778b20. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b726850. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b77f6f0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b77f6f0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b780860. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b726850. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b787030. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b787030. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b787e50. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b726850. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b78f8d0. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b78f8d0. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b7902c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b726850. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600b6ac540. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6b4e40. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6b4e40. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b6b6010. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b6ac540. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6bd1c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6bd1c0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b6bdbe0. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b6ac540. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6c4770. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6c4770. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b6c5c60. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b6ac540. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6cec40. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6cec40. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:47 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b6cfa70. mai 23 13:51:47 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b6ac540. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6d6ef0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6d6ef0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b6d7910. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b6ac540. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6de910. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6de910. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b6df300. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b6ac540. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6e5e70. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6e5e70. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b6e6890. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b6ac540. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6ed9c0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6ed9c0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b6ee3e0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b6ac540. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6f5c80. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6f5c80. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b6f6df0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b6ac540. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6fd940. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6fd940. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b6fe360. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b6ac540. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7058f0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b7058f0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b706310. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b6ac540. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b70d080. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b70d080. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b70d870. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b6ac540. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b61a720. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b61a720. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b61b4c0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b622a20. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b622a20. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b623950. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b62a4f0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b62a4f0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b62b720. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6320d0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6320d0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b632ac0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b63a690. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b63a690. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b63b0b0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b642620. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b642620. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b643860. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6493b0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6493b0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b64a5d0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b651a10. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b651a10. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b654460. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b65c480. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b65c480. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b65cd90. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b663150. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b663150. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b663b40. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b66b470. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b66b470. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b66cc60. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b673480. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b673480. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b6744e0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b67a8b0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b67a8b0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b67b2d0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b682c80. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b682c80. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b6836a0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b68a880. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b68a880. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b68afe0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6919f0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b6919f0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b693060. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b612350. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b504d70. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b504d70. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b505670. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b50c480. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b50c480. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b50d060. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5143d0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5143d0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b515220. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b51c690. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b51c690. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b51d080. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b524080. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b524080. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b524a10. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b52b390. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b52b390. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b52bd30. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b535910. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b535910. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b536c60. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b53c5c0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b53c5c0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b53e060. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5453d0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5453d0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b545da0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b54d770. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b54d770. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b54e140. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5544e0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5544e0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b554eb0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b55c850. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b55c850. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b55dc60. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b564660. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: == Stack trace for context 0x55600499c6d0 == mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b564660. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b5657b0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b56c380. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b56c380. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b56cd50. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b574320. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b574320. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b574cf0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ad825c0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ad825c0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ad82fe0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ad8bc90. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600ad8bc90. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600ad8c980. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b59d340. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b59d340. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b59e120. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5a5080. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5a5080. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b5a58c0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5ac890. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5ac890. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b5ad260. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5b4690. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5b4690. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b5b5060. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5bcc80. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5bcc80. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b5bdc60. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5c58a0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5c58a0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b5c72c0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5ce2c0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5ce2c0. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b5cec90. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5d6080. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5d6080. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b5d7060. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55600b4fc450. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5ddd00. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_appDisplay_AppDisplayIcon 0x55600b5ddd00. mai 23 13:51:48 endless systemd[3453]: gnome-shell-x11.service: State 'stop-sigterm' timed out. Killing. mai 23 13:51:48 endless gnome-shell[6300]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. mai 23 13:51:48 endless gnome-shell[6300]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55600b5de6a0. mai 23 13:51:48 endless systemd[3453]: gnome-shell-x11.service: Killing process 6300 (gnome-shell) with signal SIGKILL. mai 23 13:51:48 endless systemd[3453]: gnome-shell-x11.service: Killing process 6304 (gdbus) with signal SIGKILL. mai 23 13:51:48 endless systemd[3453]: gnome-shell-x11.service: Killing process 6308 (gnome-s:disk$0) with signal SIGKILL. mai 23 13:51:48 endless systemd[3453]: gnome-shell-x11.service: Killing process 6309 (gnome-s:disk$1) with signal SIGKILL. mai 23 13:51:48 endless systemd[3453]: gnome-shell-x11.service: Killing process 6310 (gnome-s:disk$2) with signal SIGKILL. mai 23 13:51:48 endless systemd[3453]: gnome-shell-x11.service: Killing process 6311 (gnome-s:disk$3) with signal SIGKILL. mai 23 13:51:48 endless systemd[3453]: gnome-shell-x11.service: Killing process 6313 (JS Helper) with signal SIGKILL. mai 23 13:51:48 endless systemd[3453]: gnome-shell-x11.service: Killing process 6314 (JS Helper) with signal SIGKILL. mai 23 13:51:48 endless systemd[3453]: gnome-shell-x11.service: Killing process 6315 (JS Helper) with signal SIGKILL. mai 23 13:51:48 endless systemd[3453]: gnome-shell-x11.service: Killing process 6316 (JS Helper) with signal SIGKILL. mai 23 13:51:48 endless polkitd[1720]: Unregistered Authentication Agent for unix-session:3 (system bus name :1.265, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) (disconnected from bus) mai 23 13:51:48 endless systemd[3453]: gnome-shell-x11.service: Main process exited, code=killed, status=9/KILL mai 23 13:51:48 endless systemd[3453]: gnome-shell-x11.service: Failed with result 'timeout'. mai 23 13:51:48 endless systemd[3453]: Stopped GNOME Shell on X11. mai 23 13:51:48 endless systemd[3453]: gnome-shell-x11.service: Triggering OnFailure= dependencies. mai 23 13:51:48 endless systemd[3453]: Requested transaction contradicts existing jobs: Transaction for gnome-session-failed.target/start is destructive (gnome-session-pre.target has 'stop' job queued, but 'start' is included in transaction). mai 23 13:51:48 endless systemd[3453]: gnome-shell-x11.service: Failed to enqueue OnFailure= job, ignoring: Transaction for gnome-session-failed.target/start is destructive (gnome-session-pre.target has 'stop' job queued, but 'start' is included in transaction). mai 23 13:51:48 endless systemd[3453]: Stopped target GNOME Session Manager is ready. mai 23 13:51:48 endless systemd[3453]: Stopping GNOME Session Manager (session: gnome)... mai 23 13:51:48 endless systemd[3453]: Condition check resulted in Disable GNOME Shell extensions after failure being skipped. mai 23 13:51:48 endless mogwai-schedule[6358]: Releasing hold on service for D-Bus peer ‘:1.383’ mai 23 13:51:48 endless systemd[3453]: at-spi-dbus-bus.service: Succeeded. mai 23 13:51:48 endless systemd[3453]: gnome-session-manager@gnome.service: Succeeded. mai 23 13:51:48 endless systemd[3453]: Stopped GNOME Session Manager (session: gnome). mai 23 13:51:48 endless systemd[3453]: Stopped target Tasks to be run before GNOME Session starts. mai 23 13:51:48 endless systemd[3453]: Stopped target Session services which should run early before the graphical session is brought up. mai 23 13:51:48 endless systemd[3453]: Reached target Shutdown running GNOME Session. mai 23 13:51:48 endless systemd[3453]: Stopping Monitor Session leader for GNOME Session... mai 23 13:51:48 endless systemd[3453]: Starting Restart DBus after GNOME Session shutdown... mai 23 13:51:48 endless systemd[3453]: Stopped target Shutdown running GNOME Session. mai 23 13:51:48 endless systemd[3453]: Started Restart DBus after GNOME Session shutdown. mai 23 13:51:48 endless systemd[3453]: Reached target Shutdown running GNOME Session. mai 23 13:51:48 endless systemd[3453]: Stopped target Shutdown running GNOME Session. mai 23 13:51:48 endless systemd[3453]: Stopping D-Bus User Message Bus... mai 23 13:51:48 endless systemd[3453]: gnome-session-monitor.service: Succeeded. mai 23 13:51:48 endless systemd[3453]: Stopped Monitor Session leader for GNOME Session. mai 23 13:51:48 endless gvfsd[5695]: A connection to the bus can't be made mai 23 13:51:48 endless gdm-password][5336]: pam_unix(gdm-password:session): session closed for user daniel mai 23 13:51:48 endless systemd[1]: run-user-1001-gvfs.mount: Succeeded. mai 23 13:51:48 endless systemd[3453]: run-user-1001-gvfs.mount: Succeeded. mai 23 13:51:48 endless systemd[3453]: gvfs-daemon.service: Succeeded. mai 23 13:51:48 endless systemd[3453]: gvfs-gphoto2-volume-monitor.service: Succeeded. mai 23 13:51:48 endless systemd[3453]: gvfs-udisks2-volume-monitor.service: Succeeded. mai 23 13:51:48 endless systemd[3453]: gvfs-afc-volume-monitor.service: Succeeded. mai 23 13:51:48 endless systemd[3453]: gvfs-mtp-volume-monitor.service: Succeeded. mai 23 13:51:48 endless systemd[3453]: gvfs-goa-volume-monitor.service: Succeeded. mai 23 13:51:48 endless evolution-calen[6395]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: A conexão está fechada (g-io-error-quark, 18) mai 23 13:51:48 endless evolution-calen[6395]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: A conexão está fechada (g-io-error-quark, 18) mai 23 13:51:48 endless systemd[3453]: glib-pacrunner.service: Succeeded. mai 23 13:51:48 endless evolution-addre[6721]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: A conexão está fechada (g-io-error-quark, 18) mai 23 13:51:48 endless systemd[3453]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE mai 23 13:51:48 endless systemd[3453]: xdg-permission-store.service: Failed with result 'exit-code'. mai 23 13:51:48 endless systemd[3453]: gvfs-metadata.service: Succeeded. mai 23 13:51:48 endless systemd[3453]: gnome-session-restart-dbus.service: Succeeded. mai 23 13:51:48 endless systemd[3453]: run-user-1001-doc.mount: Succeeded. mai 23 13:51:48 endless systemd[1]: run-user-1001-doc.mount: Succeeded. mai 23 13:51:48 endless systemd[3453]: flatpak-session-helper.service: Main process exited, code=exited, status=1/FAILURE mai 23 13:51:48 endless systemd[3453]: flatpak-session-helper.service: Failed with result 'exit-code'. mai 23 13:51:48 endless systemd[3453]: dbus.service: Succeeded. mai 23 13:51:48 endless systemd[3453]: Stopped D-Bus User Message Bus. mai 23 13:51:48 endless systemd[3453]: xdg-document-portal.service: Main process exited, code=exited, status=20/n/a mai 23 13:51:48 endless systemd[3453]: xdg-document-portal.service: Failed with result 'exit-code'. mai 23 13:51:48 endless systemd[3453]: Started D-Bus User Message Bus. mai 23 13:51:49 endless systemd[3453]: evolution-source-registry.service: Succeeded. mai 23 13:51:49 endless systemd[3453]: evolution-calendar-factory.service: Succeeded. mai 23 13:51:49 endless systemd[3453]: evolution-addressbook-factory.service: Succeeded. mai 23 13:51:49 endless systemd[3453]: tracker-store.service: Succeeded. mai 23 13:51:50 endless kernel: gdm-session-wor (5336): drop_caches: 2 mai 23 13:51:50 endless gdm-Xorg-:0[3655]: (II) event6 - Acer Wireless Radio Control: device removed mai 23 13:51:50 endless gdm-Xorg-:0[3655]: (II) event3 - Power Button: device removed mai 23 13:51:50 endless gdm-Xorg-:0[3655]: (II) event5 - Video Bus: device removed mai 23 13:51:50 endless gdm-Xorg-:0[3655]: (II) event2 - Power Button: device removed mai 23 13:51:50 endless gdm-Xorg-:0[3655]: (II) event1 - Sleep Button: device removed mai 23 13:51:50 endless gdm-Xorg-:0[3655]: (II) event8 - SYNA7DB5:01 06CB:7DB7 Mouse: device removed mai 23 13:51:50 endless gdm-Xorg-:0[3655]: (II) event9 - SYNA7DB5:01 06CB:7DB7 Touchpad: device removed mai 23 13:51:50 endless gdm-Xorg-:0[3655]: (II) event4 - AT Translated Set 2 keyboard: device removed mai 23 13:51:50 endless gdm-Xorg-:0[3655]: (II) event7 - Acer WMI hotkeys: device removed mai 23 13:51:50 endless gdm-Xorg-:0[3655]: (II) event10 - HD User Facing: HD User Facing: device removed mai 23 13:51:50 endless gdm-Xorg-:0[3655]: (II) UnloadModule: "libinput" mai 23 13:51:50 endless gdm-Xorg-:0[3655]: (II) UnloadModule: "libinput" mai 23 13:51:50 endless gdm-Xorg-:0[3655]: (II) UnloadModule: "libinput" mai 23 13:51:50 endless gdm-Xorg-:0[3655]: (II) UnloadModule: "libinput" mai 23 13:51:50 endless gdm-Xorg-:0[3655]: (II) Server terminated successfully (0). Closing log file. mai 23 13:51:51 endless systemd-logind[1824]: Session 3 logged out. Waiting for processes to exit. mai 23 13:51:51 endless rtkit-daemon[3835]: Supervising 2 threads of 1 processes of 1 users. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: X.Org X Server 1.20.4 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: X Protocol Version 11, Revision 0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Build Operating System: Linux 4.9.0-8-amd64 x86_64 Endless mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Current Operating System: Linux endless 5.4.0-19-generic #23+dev177.1a56fd1beos3.8.2 SMP Tue May 5 22:42:53 UTC 2020 x86_64 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Kernel command line: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/eos-94c993d319cdf01ff15a7624dd6855cc9ebe14d7b40f3077a1e965a0de360d8e/vmlinuz-5.4.0-19-generic root=UUID=05c7cd5b-40f9-47d7-a032-e98150535435 rw splash plymouth.ignore-serial-consoles quiet loglevel=2 ostree=/ostree/boot.1/eos/94c993d319cdf01ff15a7624dd6855cc9ebe14d7b40f3077a1e965a0de360d8e/0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Build Date: 10 June 2019 05:21:50AM mai 23 13:51:51 endless gdm-Xorg-:0[7222]: xorg-server 2:1.20.4-1endless1bem1 (https://www.debian.org/support) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Current version of pixman: 0.36.0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Before reporting problems, check http://wiki.x.org mai 23 13:51:51 endless gdm-Xorg-:0[7222]: to make sure that you have the latest version. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Markers: (--) probed, (**) from config file, (==) default setting, mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (++) from command line, (!!) notice, (II) informational, mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown. mai 23 13:51:51 endless rtkit-daemon[3835]: Successfully made thread 7223 of process 3747 (n/a) owned by '1001' RT at priority 5. mai 23 13:51:51 endless rtkit-daemon[3835]: Supervising 3 threads of 1 processes of 1 users. mai 23 13:51:51 endless pulseaudio[3747]: W: [pulseaudio] module.c: After module unload, module 'module-null-sink' was still loaded! mai 23 13:51:51 endless systemd[3453]: pulseaudio.service: Succeeded. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (++) Log file: "/dev/null", Time: Sat May 23 13:51:51 2020 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) Using system config directory "/usr/share/X11/xorg.conf.d" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) No Layout section. Using the first Screen section. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) No screen section available. Using defaults. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (**) |-->Screen "Default Screen Section" (0) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (**) | |-->Monitor "" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) No monitor specified for screen "Default Screen Section". mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Using a default monitor configuration. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) Automatically adding devices mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) Automatically enabling devices mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) Automatically adding GPU devices mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) Automatically binding GPU devices mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) Max clients allowed: 256, resource mask: 0x1fffff mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (WW) The directory "/usr/share/fonts/X11/misc" does not exist. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Entry deleted from font path. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Entry deleted from font path. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Entry deleted from font path. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Entry deleted from font path. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Entry deleted from font path. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Entry deleted from font path. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Entry deleted from font path. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) FontPath set to: mai 23 13:51:51 endless gdm-Xorg-:0[7222]: built-ins mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) ModulePath set to "/usr/lib/xorg/modules" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) The server relies on udev to provide the list of input devices. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: If no devices become available, reconfigure udev or disable AutoAddDevices. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Loader magic: 0x56054eb9de20 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Module ABI versions: mai 23 13:51:51 endless gdm-Xorg-:0[7222]: X.Org ANSI C Emulation: 0.4 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: X.Org Video Driver: 24.0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: X.Org XInput driver : 24.1 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: X.Org Server Extension : 10.0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (++) using VT number 1 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) xfree86: Adding drm device (/dev/dri/card0) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (--) PCI:*(0@0:2:0) 8086:5916:1025:1193 rev 2, Mem @ 0xb0000000/16777216, 0xa0000000/268435456, I/O @ 0x00004000/64, BIOS @ 0x????????/131072 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) LoadModule: "glx" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Loading /usr/lib/xorg/modules/extensions/libglx.so mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Module glx: vendor="X.Org Foundation" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: compiled for 1.20.4, module version = 1.0.0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: ABI class: X.Org Server Extension, version 10.0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) Matched modesetting as autoconfigured driver 0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) Matched fbdev as autoconfigured driver 1 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) Matched vesa as autoconfigured driver 2 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) Assigned the driver to the xf86ConfigLayout mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) LoadModule: "modesetting" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Module modesetting: vendor="X.Org Foundation" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: compiled for 1.20.4, module version = 1.20.4 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Module class: X.Org Video Driver mai 23 13:51:51 endless gdm-Xorg-:0[7222]: ABI class: X.Org Video Driver, version 24.0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) LoadModule: "fbdev" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Module fbdev: vendor="X.Org Foundation" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: compiled for 1.20.3, module version = 0.5.0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Module class: X.Org Video Driver mai 23 13:51:51 endless gdm-Xorg-:0[7222]: ABI class: X.Org Video Driver, version 24.0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) LoadModule: "vesa" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Module vesa: vendor="X.Org Foundation" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: compiled for 1.20.3, module version = 2.4.0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: Module class: X.Org Video Driver mai 23 13:51:51 endless gdm-Xorg-:0[7222]: ABI class: X.Org Video Driver, version 24.0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modesetting: Driver for Modesetting Kernel Drivers: kms mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) FBDEV: driver for framebuffer: fbdev mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) VESA: driver for VESA chipsets: vesa mai 23 13:51:51 endless gdm-Xorg-:0[7222]: xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) mai 23 13:51:51 endless kernel: Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): using drv /dev/dri/card0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (WW) Falling back to old probe method for fbdev mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Loading sub module "fbdevhw" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) LoadModule: "fbdevhw" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Loading /usr/lib/xorg/modules/libfbdevhw.so mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Module fbdevhw: vendor="X.Org Foundation" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: compiled for 1.20.4, module version = 0.0.2 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: ABI class: X.Org Video Driver, version 24.0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Creating default Display subsection in Screen section mai 23 13:51:51 endless gdm-Xorg-:0[7222]: "Default Screen Section" for depth/fbbpp 24/32 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) modeset(0): Depth 24, (==) framebuffer bpp 32 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) modeset(0): RGB weight 888 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) modeset(0): Default visual is TrueColor mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Loading sub module "glamoregl" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) LoadModule: "glamoregl" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Module glamoregl: vendor="X.Org Foundation" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: compiled for 1.20.4, module version = 1.0.1 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: ABI class: X.Org ANSI C Emulation, version 0.4 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): glamor X acceleration enabled on Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): glamor initialized mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Output eDP-1 has no monitor section mai 23 13:51:51 endless kernel: broken atomic modeset userspace detected, disabling atomic mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Output HDMI-1 has no monitor section mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): EDID for output eDP-1 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Manufacturer: CMN Model: 15dc Serial#: 0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Year: 2015 Week: 45 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): EDID Version: 1.4 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Digital Display Input mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): 6 bits per channel mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Digital interface is DisplayPort mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Max Image Size [cm]: horiz.: 34 vert.: 19 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Gamma: 2.20 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): No DPMS capabilities specified mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Supported color encodings: RGB 4:4:4 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): First detailed timing is preferred mode mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Preferred mode is native pixel format and refresh rate mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): redX: 0.569 redY: 0.332 greenX: 0.328 greenY: 0.581 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): blueX: 0.163 blueY: 0.147 whiteX: 0.313 whiteY: 0.329 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Manufacturer's mask: 0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Supported detailed timing: mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): clock: 76.4 MHz Image Size: 344 x 193 mm mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): h_active: 1366 h_sync: 1434 h_sync_end 1479 h_blank_end 1592 h_border: 0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): v_active: 768 v_sync: 772 v_sync_end 779 v_blanking: 800 v_border: 0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): N156BGA-EB2 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): CMN mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): N156BGA-EB2 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): EDID (in hex): mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): 00ffffffffffff000daedc1500000000 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): 2d1901049522137802c3f59155549429 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): 25505400000001010101010101010101 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): 010101010101da1d56e250002030442d mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): 470058c110000018000000fe004e3135 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): 364247412d4542320a20000000fe0043 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): 4d4e0a202020202020202020000000fe mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): 004e3135364247412d4542320a2000f1 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Printing probed modes for output eDP-1 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1366x768"x60.0 76.42 1366 1434 1479 1592 768 772 779 800 -hsync -vsync (48.0 kHz eP) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1360x768"x59.8 84.75 1360 1432 1568 1776 768 771 781 798 -hsync +vsync (47.7 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1360x768"x60.0 72.00 1360 1408 1440 1520 768 771 781 790 +hsync -vsync (47.4 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1280x720"x120.0 156.12 1280 1376 1512 1744 720 721 724 746 doublescan -hsync +vsync (89.5 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1280x720"x120.0 120.75 1280 1304 1320 1360 720 721 724 740 doublescan +hsync -vsync (88.8 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1280x720"x59.9 74.50 1280 1344 1472 1664 720 723 728 748 -hsync +vsync (44.8 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1280x720"x59.7 63.75 1280 1328 1360 1440 720 723 728 741 +hsync -vsync (44.3 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1024x768"x120.1 133.47 1024 1100 1212 1400 768 768 770 794 doublescan -hsync +vsync (95.3 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "960x720"x120.0 117.00 960 1024 1128 1300 720 720 722 750 doublescan -hsync +vsync (90.0 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "928x696"x120.1 109.15 928 976 1088 1264 696 696 698 719 doublescan -hsync +vsync (86.4 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "896x672"x120.0 102.40 896 960 1060 1224 672 672 674 697 doublescan -hsync +vsync (83.7 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1024x576"x119.9 98.50 1024 1092 1200 1376 576 577 580 597 doublescan -hsync +vsync (71.6 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1024x576"x119.9 78.38 1024 1048 1064 1104 576 577 580 592 doublescan +hsync -vsync (71.0 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1024x576"x59.9 46.50 1024 1064 1160 1296 576 579 584 599 -hsync +vsync (35.9 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1024x576"x59.8 42.00 1024 1072 1104 1184 576 579 584 593 +hsync -vsync (35.5 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "960x600"x119.9 96.62 960 1028 1128 1296 600 601 604 622 doublescan -hsync +vsync (74.6 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "960x600"x120.0 77.00 960 984 1000 1040 600 601 604 617 doublescan +hsync -vsync (74.0 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "960x540"x119.9 86.50 960 1024 1124 1288 540 541 544 560 doublescan -hsync +vsync (67.2 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "960x540"x120.0 69.25 960 984 1000 1040 540 541 544 555 doublescan +hsync -vsync (66.6 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "960x540"x59.6 40.75 960 992 1088 1216 540 543 548 562 -hsync +vsync (33.5 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "960x540"x59.8 37.25 960 1008 1040 1120 540 543 548 556 +hsync -vsync (33.3 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "800x600"x120.0 81.00 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (75.0 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "840x525"x120.0 73.12 840 892 980 1120 525 526 529 544 doublescan -hsync +vsync (65.3 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "840x525"x119.8 59.50 840 864 880 920 525 526 529 540 doublescan +hsync -vsync (64.7 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "864x486"x59.9 32.50 864 888 968 1072 486 489 494 506 -hsync +vsync (30.3 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "864x486"x59.6 30.50 864 912 944 1024 486 489 494 500 +hsync -vsync (29.8 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "800x512"x120.3 51.56 800 800 828 832 512 512 514 515 doublescan +hsync +vsync (62.0 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "700x525"x120.0 61.00 700 744 820 940 525 526 532 541 doublescan +hsync +vsync (64.9 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "800x450"x119.9 59.12 800 848 928 1056 450 451 454 467 doublescan -hsync +vsync (56.0 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "800x450"x119.6 48.75 800 824 840 880 450 451 454 463 doublescan +hsync -vsync (55.4 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "640x512"x120.0 54.00 640 664 720 844 512 512 514 533 doublescan +hsync +vsync (64.0 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "720x450"x119.8 53.25 720 760 836 952 450 451 454 467 doublescan -hsync +vsync (55.9 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "700x450"x119.9 51.75 700 740 812 924 450 451 456 467 doublescan -hsync +vsync (56.0 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "700x450"x119.8 43.25 700 724 740 780 450 451 456 463 doublescan +hsync -vsync (55.4 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "640x480"x120.0 54.00 640 688 744 900 480 480 482 500 doublescan +hsync +vsync (60.0 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "720x405"x59.5 22.50 720 744 808 896 405 408 413 422 -hsync +vsync (25.1 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "720x405"x59.0 21.75 720 768 800 880 405 408 413 419 +hsync -vsync (24.7 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "684x384"x119.8 42.62 684 720 788 892 384 385 390 399 doublescan -hsync +vsync (47.8 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "684x384"x119.7 36.12 684 708 724 764 384 385 390 395 doublescan +hsync -vsync (47.3 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "680x384"x119.6 42.38 680 716 784 888 384 385 390 399 doublescan -hsync +vsync (47.7 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "680x384"x119.9 36.00 680 704 720 760 384 385 390 395 doublescan +hsync -vsync (47.4 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "640x400"x119.8 41.75 640 676 740 840 400 401 404 415 doublescan -hsync +vsync (49.7 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "640x400"x120.0 35.50 640 664 680 720 400 401 404 411 doublescan +hsync -vsync (49.3 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "576x432"x120.1 40.81 576 608 668 760 432 432 434 447 doublescan -hsync +vsync (53.7 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "640x360"x119.7 37.25 640 672 736 832 360 361 364 374 doublescan -hsync +vsync (44.8 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "640x360"x119.7 31.88 640 664 680 720 360 361 364 370 doublescan +hsync -vsync (44.3 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "640x360"x59.8 18.00 640 664 720 800 360 363 368 376 -hsync +vsync (22.5 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "640x360"x59.3 17.75 640 688 720 800 360 363 368 374 +hsync -vsync (22.2 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "512x384"x120.0 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (48.4 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "512x288"x120.0 23.25 512 532 580 648 288 289 292 299 doublescan -hsync +vsync (35.9 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "512x288"x119.8 21.00 512 536 552 592 288 289 292 296 doublescan +hsync -vsync (35.5 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "480x270"x119.3 20.38 480 496 544 608 270 271 274 281 doublescan -hsync +vsync (33.5 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "480x270"x119.6 18.62 480 504 520 560 270 271 274 278 doublescan +hsync -vsync (33.3 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "400x300"x120.6 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (37.9 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "400x300"x112.7 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (35.2 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "432x243"x119.8 16.25 432 444 484 536 243 244 247 253 doublescan -hsync +vsync (30.3 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "432x243"x119.1 15.25 432 456 472 512 243 244 247 250 doublescan +hsync -vsync (29.8 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "320x240"x120.1 12.59 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (31.5 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "360x202"x119.0 11.25 360 372 404 448 202 204 206 211 doublescan -hsync +vsync (25.1 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "360x202"x118.3 10.88 360 384 400 440 202 204 206 209 doublescan +hsync -vsync (24.7 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "320x180"x119.7 9.00 320 332 360 400 180 181 184 188 doublescan -hsync +vsync (22.5 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "320x180"x118.6 8.88 320 344 360 400 180 181 184 187 doublescan +hsync -vsync (22.2 kHz d) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): EDID for output HDMI-1 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Output eDP-1 connected mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Output HDMI-1 disconnected mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Using exact sizes for initial modes mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Output eDP-1 using initial mode 1366x768 +0+0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) modeset(0): DPI set to (96, 96) mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Loading sub module "fb" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) LoadModule: "fb" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Loading /usr/lib/xorg/modules/libfb.so mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Module fb: vendor="X.Org Foundation" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: compiled for 1.20.4, module version = 1.0.0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: ABI class: X.Org ANSI C Emulation, version 0.4 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) UnloadModule: "fbdev" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Unloading fbdev mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) UnloadSubModule: "fbdevhw" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Unloading fbdevhw mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) UnloadModule: "vesa" mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Unloading vesa mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) modeset(0): Backing store enabled mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) modeset(0): Silken mouse enabled mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Initializing kms color map for depth 24, 8 bpc. mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (==) modeset(0): DPMS enabled mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): [DRI2] Setup complete mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): [DRI2] DRI driver: i965 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): [DRI2] VDPAU driver: i965 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension Generic Event Extension mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension SHAPE mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension MIT-SHM mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension XInputExtension mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension XTEST mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension BIG-REQUESTS mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension SYNC mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension XKEYBOARD mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension XC-MISC mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension SECURITY mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension XFIXES mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension RENDER mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension RANDR mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension COMPOSITE mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension DAMAGE mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension MIT-SCREEN-SAVER mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension DOUBLE-BUFFER mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension RECORD mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension DPMS mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension Present mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension DRI3 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension X-Resource mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension XVideo mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension XVideo-MotionCompensation mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension SELinux mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) SELinux: Disabled on system mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension GLX mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) AIGLX: Loaded and initialized i965 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) GLX: Initialized DRI2 GL provider for screen 0 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension XFree86-VidModeExtension mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension XFree86-DGA mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension XFree86-DRI mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) Initializing extension DRI2 mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Damage tracking initialized mai 23 13:51:51 endless gdm-Xorg-:0[7222]: (II) modeset(0): Setting screen physical size to 361 x 203 mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device Acer Wireless Radio Control (/dev/input/event6) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Acer Wireless Radio Control: Applying InputClass "libinput keyboard catchall" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) LoadModule: "libinput" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) Module libinput: vendor="X.Org Foundation" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: compiled for 1.20.3, module version = 0.28.2 mai 23 13:51:52 endless gdm-Xorg-:0[7222]: Module class: X.Org XInput Driver mai 23 13:51:52 endless gdm-Xorg-:0[7222]: ABI class: X.Org XInput driver, version 24.1 mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) Using input driver 'libinput' for 'Acer Wireless Radio Control' mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Acer Wireless Radio Control: always reports core events mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "Device" "/dev/input/event6" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "_source" "server/udev" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event6 - Acer Wireless Radio Control: is tagged by udev as: Keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event6 - Acer Wireless Radio Control: device is a keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event6 - Acer Wireless Radio Control: device removed mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/10251229:00/input/input6/event6" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) XINPUT: Adding extended input device "Acer Wireless Radio Control" (type: KEYBOARD, id 6) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "xkb_layout" "br" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event6 - Acer Wireless Radio Control: is tagged by udev as: Keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event6 - Acer Wireless Radio Control: device is a keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device Power Button (/dev/input/event3) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Power Button: Applying InputClass "libinput keyboard catchall" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) Using input driver 'libinput' for 'Power Button' mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Power Button: always reports core events mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "Device" "/dev/input/event3" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "_source" "server/udev" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event3 - Power Button: is tagged by udev as: Keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event3 - Power Button: device is a keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event3 - Power Button: device removed mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "xkb_layout" "br" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event3 - Power Button: is tagged by udev as: Keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event3 - Power Button: device is a keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device Video Bus (/dev/input/event5) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Video Bus: Applying InputClass "libinput keyboard catchall" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) Using input driver 'libinput' for 'Video Bus' mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Video Bus: always reports core events mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "Device" "/dev/input/event5" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "_source" "server/udev" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event5 - Video Bus: is tagged by udev as: Keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event5 - Video Bus: device is a keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event5 - Video Bus: device removed mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5/event5" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "xkb_layout" "br" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event5 - Video Bus: is tagged by udev as: Keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event5 - Video Bus: device is a keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device Lid Switch (/dev/input/event0) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) No input driver specified, ignoring this device. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) This device may have been added with another device file. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device Power Button (/dev/input/event2) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Power Button: Applying InputClass "libinput keyboard catchall" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) Using input driver 'libinput' for 'Power Button' mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Power Button: always reports core events mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "Device" "/dev/input/event2" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "_source" "server/udev" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event2 - Power Button: is tagged by udev as: Keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event2 - Power Button: device is a keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event2 - Power Button: device removed mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event2" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 9) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "xkb_layout" "br" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event2 - Power Button: is tagged by udev as: Keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event2 - Power Button: device is a keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device Sleep Button (/dev/input/event1) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Sleep Button: Applying InputClass "libinput keyboard catchall" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) Using input driver 'libinput' for 'Sleep Button' mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Sleep Button: always reports core events mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "Device" "/dev/input/event1" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "_source" "server/udev" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event1 - Sleep Button: is tagged by udev as: Keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event1 - Sleep Button: device is a keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event1 - Sleep Button: device removed mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1/event1" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 10) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "xkb_layout" "br" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event1 - Sleep Button: is tagged by udev as: Keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event1 - Sleep Button: device is a keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device HD User Facing: HD User Facing (/dev/input/event10) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) HD User Facing: HD User Facing: Applying InputClass "libinput keyboard catchall" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) Using input driver 'libinput' for 'HD User Facing: HD User Facing' mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) HD User Facing: HD User Facing: always reports core events mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "Device" "/dev/input/event10" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "_source" "server/udev" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event10 - HD User Facing: HD User Facing: is tagged by udev as: Keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event10 - HD User Facing: HD User Facing: device is a keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event10 - HD User Facing: HD User Facing: device removed mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/input/input14/event10" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) XINPUT: Adding extended input device "HD User Facing: HD User Facing" (type: KEYBOARD, id 11) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "xkb_layout" "br" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event10 - HD User Facing: HD User Facing: is tagged by udev as: Keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event10 - HD User Facing: HD User Facing: device is a keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device SYNA7DB5:01 06CB:7DB7 Mouse (/dev/input/event8) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) SYNA7DB5:01 06CB:7DB7 Mouse: Applying InputClass "libinput pointer catchall" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) Using input driver 'libinput' for 'SYNA7DB5:01 06CB:7DB7 Mouse' mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) SYNA7DB5:01 06CB:7DB7 Mouse: always reports core events mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "Device" "/dev/input/event8" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "_source" "server/udev" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event8 - SYNA7DB5:01 06CB:7DB7 Mouse: is tagged by udev as: Mouse mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event8 - SYNA7DB5:01 06CB:7DB7 Mouse: device is a pointer mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event8 - SYNA7DB5:01 06CB:7DB7 Mouse: device removed mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-SYNA7DB5:01/0018:06CB:7DB7.0001/input/input11/event8" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) XINPUT: Adding extended input device "SYNA7DB5:01 06CB:7DB7 Mouse" (type: MOUSE, id 12) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "AccelerationScheme" "none" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) SYNA7DB5:01 06CB:7DB7 Mouse: (accel) selected scheme none/0 mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) SYNA7DB5:01 06CB:7DB7 Mouse: (accel) acceleration factor: 2.000 mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) SYNA7DB5:01 06CB:7DB7 Mouse: (accel) acceleration threshold: 4 mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event8 - SYNA7DB5:01 06CB:7DB7 Mouse: is tagged by udev as: Mouse mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event8 - SYNA7DB5:01 06CB:7DB7 Mouse: device is a pointer mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device SYNA7DB5:01 06CB:7DB7 Mouse (/dev/input/mouse0) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) No input driver specified, ignoring this device. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) This device may have been added with another device file. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device SYNA7DB5:01 06CB:7DB7 Touchpad (/dev/input/event9) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) SYNA7DB5:01 06CB:7DB7 Touchpad: Applying InputClass "libinput touchpad catchall" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) Using input driver 'libinput' for 'SYNA7DB5:01 06CB:7DB7 Touchpad' mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) SYNA7DB5:01 06CB:7DB7 Touchpad: always reports core events mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "Device" "/dev/input/event9" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "_source" "server/udev" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event9 - SYNA7DB5:01 06CB:7DB7 Touchpad: is tagged by udev as: Touchpad mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event9 - SYNA7DB5:01 06CB:7DB7 Touchpad: device is a touchpad mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event9 - SYNA7DB5:01 06CB:7DB7 Touchpad: device removed mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-SYNA7DB5:01/0018:06CB:7DB7.0001/input/input12/event9" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) XINPUT: Adding extended input device "SYNA7DB5:01 06CB:7DB7 Touchpad" (type: TOUCHPAD, id 13) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "AccelerationScheme" "none" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) SYNA7DB5:01 06CB:7DB7 Touchpad: (accel) selected scheme none/0 mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) SYNA7DB5:01 06CB:7DB7 Touchpad: (accel) acceleration factor: 2.000 mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) SYNA7DB5:01 06CB:7DB7 Touchpad: (accel) acceleration threshold: 4 mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event9 - SYNA7DB5:01 06CB:7DB7 Touchpad: is tagged by udev as: Touchpad mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event9 - SYNA7DB5:01 06CB:7DB7 Touchpad: device is a touchpad mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device SYNA7DB5:01 06CB:7DB7 Touchpad (/dev/input/mouse1) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) No input driver specified, ignoring this device. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) This device may have been added with another device file. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event11) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) No input driver specified, ignoring this device. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) This device may have been added with another device file. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event12) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) No input driver specified, ignoring this device. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) This device may have been added with another device file. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event13) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) No input driver specified, ignoring this device. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) This device may have been added with another device file. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event14) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) No input driver specified, ignoring this device. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) This device may have been added with another device file. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=9 (/dev/input/event15) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) No input driver specified, ignoring this device. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) This device may have been added with another device file. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=10 (/dev/input/event16) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) No input driver specified, ignoring this device. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) This device may have been added with another device file. mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event4) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard' mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) AT Translated Set 2 keyboard: always reports core events mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "Device" "/dev/input/event4" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "_source" "server/udev" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event4 - AT Translated Set 2 keyboard: device is a keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event4 - AT Translated Set 2 keyboard: device removed mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input4/event4" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 14) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "xkb_layout" "br" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event4 - AT Translated Set 2 keyboard: device is a keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) config/udev: Adding input device Acer WMI hotkeys (/dev/input/event7) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Acer WMI hotkeys: Applying InputClass "libinput keyboard catchall" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) Using input driver 'libinput' for 'Acer WMI hotkeys' mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Acer WMI hotkeys: always reports core events mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "Device" "/dev/input/event7" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "_source" "server/udev" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event7 - Acer WMI hotkeys: is tagged by udev as: Keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event7 - Acer WMI hotkeys: device is a keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event7 - Acer WMI hotkeys: device removed mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "config_info" "udev:/sys/devices/virtual/input/input7/event7" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) XINPUT: Adding extended input device "Acer WMI hotkeys" (type: KEYBOARD, id 15) mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (**) Option "xkb_layout" "br" mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event7 - Acer WMI hotkeys: is tagged by udev as: Keyboard mai 23 13:51:52 endless gdm-Xorg-:0[7222]: (II) event7 - Acer WMI hotkeys: device is a keyboard mai 23 13:51:53 endless org.libreoffice.LibreOffice.writer.desktop[6989]: X IO Error mai 23 13:51:53 endless systemd[3453]: flatpak-org.libreoffice.LibreOffice-6934.scope: Succeeded. mai 23 13:51:53 endless systemd[1]: session-3.scope: Succeeded. mai 23 13:51:53 endless gdm-launch-environment][7243]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0) mai 23 13:51:53 endless systemd-logind[1824]: Removed session 3. mai 23 13:51:53 endless systemd[1]: Created slice User Slice of UID 109. mai 23 13:51:53 endless systemd[1]: Starting User Runtime Directory /run/user/109... mai 23 13:51:53 endless systemd-logind[1824]: New session c2 of user Debian-gdm. mai 23 13:51:53 endless systemd[1]: Started User Runtime Directory /run/user/109. mai 23 13:51:53 endless systemd[1]: Starting User Manager for UID 109... mai 23 13:51:53 endless systemd[7288]: pam_unix(systemd-user:session): session opened for user Debian-gdm by (uid=0) mai 23 13:51:54 endless systemd[7288]: Reached target Paths. mai 23 13:51:54 endless systemd[7288]: Reached target Timers. mai 23 13:51:54 endless systemd[7288]: Starting D-Bus User Message Bus Socket. mai 23 13:51:54 endless systemd[7288]: Listening on GnuPG network certificate management daemon. mai 23 13:51:54 endless systemd[7288]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). mai 23 13:51:54 endless systemd[7288]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). mai 23 13:51:54 endless systemd[7288]: Listening on GnuPG cryptographic agent (ssh-agent emulation). mai 23 13:51:54 endless systemd[7288]: Listening on GnuPG cryptographic agent and passphrase cache. mai 23 13:51:54 endless systemd[7288]: Listening on Sound System. mai 23 13:51:54 endless systemd[7288]: Listening on D-Bus User Message Bus Socket. mai 23 13:51:54 endless systemd[7288]: Reached target Sockets. mai 23 13:51:54 endless systemd[7288]: Reached target Basic System. mai 23 13:51:54 endless systemd[1]: Started User Manager for UID 109. mai 23 13:51:54 endless systemd[7288]: Starting Sound Service... mai 23 13:51:54 endless systemd[1]: Started Session c2 of user Debian-gdm. mai 23 13:51:54 endless rtkit-daemon[3835]: Successfully made thread 7383 of process 7383 (n/a) owned by '109' high priority at nice level -11. mai 23 13:51:54 endless rtkit-daemon[3835]: Supervising 1 threads of 1 processes of 2 users. mai 23 13:51:54 endless systemd[7288]: Started D-Bus User Message Bus. mai 23 13:51:58 endless dbus-daemon[7415]: [session uid=109 pid=7415] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=109 pid=7419 comm="/usr/libexec/gnome-session-check-accelerated " label="unconfined") mai 23 13:51:58 endless systemd[7288]: Starting Accessibility services bus... mai 23 13:51:59 endless dbus-daemon[7415]: [session uid=109 pid=7415] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=109 pid=7425 comm="/usr/libexec/at-spi-bus-launcher " label="unconfined") mai 23 13:51:59 endless systemd[7288]: Starting Virtual filesystem service... mai 23 13:51:59 endless dbus-daemon[7415]: [session uid=109 pid=7415] Successfully activated service 'org.gtk.vfs.Daemon' mai 23 13:51:59 endless systemd[7288]: Started Virtual filesystem service. mai 23 13:51:59 endless dbus-daemon[7415]: [session uid=109 pid=7415] Successfully activated service 'org.a11y.Bus' mai 23 13:51:59 endless systemd[7288]: Started Accessibility services bus. mai 23 13:52:00 endless rtkit-daemon[3835]: Supervising 1 threads of 1 processes of 2 users. mai 23 13:52:00 endless rtkit-daemon[3835]: Successfully made thread 7456 of process 7383 (n/a) owned by '109' RT at priority 5. mai 23 13:52:00 endless rtkit-daemon[3835]: Supervising 2 threads of 1 processes of 2 users. mai 23 13:52:00 endless rtkit-daemon[3835]: Supervising 2 threads of 1 processes of 2 users. mai 23 13:52:00 endless rtkit-daemon[3835]: Successfully made thread 7457 of process 7383 (n/a) owned by '109' RT at priority 5. mai 23 13:52:00 endless rtkit-daemon[3835]: Supervising 3 threads of 1 processes of 2 users. mai 23 13:52:00 endless bluetoothd[3770]: Endpoint registered: sender=:1.429 path=/MediaEndpoint/A2DPSource/sbc mai 23 13:52:01 endless systemd[7288]: Started Sound Service. mai 23 13:52:01 endless systemd[7288]: Created slice gnome\x2dsession\x2dmanager.slice. mai 23 13:52:01 endless systemd[7288]: Reached target Main User Target. mai 23 13:52:01 endless systemd[7288]: Starting Monitor Session leader for GNOME Session... mai 23 13:52:01 endless systemd[7288]: Started OpenSSH Agent. mai 23 13:52:01 endless systemd[7288]: Reached target Session services which should run early before the graphical session is brought up. mai 23 13:52:01 endless systemd[7288]: Starting Tracker metadata extractor... mai 23 13:52:01 endless systemd[7288]: Starting Tracker file system data miner... mai 23 13:52:01 endless gnome-session-c[7459]: Error creating FIFO: Arquivo existe mai 23 13:52:01 endless systemd[7288]: Started Monitor Session leader for GNOME Session. mai 23 13:52:01 endless systemd[7288]: Reached target Tasks to be run before GNOME Session starts. mai 23 13:52:01 endless systemd[7288]: Starting GNOME Session Manager (session: gnome-login)... mai 23 13:52:01 endless tracker-miner-f[7462]: Set scheduler policy to SCHED_IDLE mai 23 13:52:01 endless tracker-miner-f[7462]: Setting priority nice level to 19 mai 23 13:52:01 endless tracker-miner-f[7462]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location. mai 23 13:52:01 endless tracker-miner-f[7462]: Unable to get XDG user directory path for special directory &DOWNLOAD. Ignoring this location. mai 23 13:52:01 endless tracker-miner-f[7462]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location. mai 23 13:52:01 endless tracker-miner-f[7462]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location. mai 23 13:52:01 endless tracker-miner-f[7462]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location. mai 23 13:52:01 endless tracker-miner-f[7462]: Unable to get XDG user directory path for special directory &DOWNLOAD. Ignoring this location. mai 23 13:52:01 endless tracker-miner-f[7462]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location. mai 23 13:52:01 endless tracker-miner-f[7462]: Unable to get XDG user directory path for special directory &DOWNLOAD. Ignoring this location. mai 23 13:52:01 endless tracker-miner-f[7462]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location. mai 23 13:52:01 endless tracker-miner-f[7462]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location. mai 23 13:52:01 endless tracker-miner-f[7462]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location. mai 23 13:52:01 endless tracker-miner-f[7462]: Path '&DOWNLOAD' being removed from recursive directories list, as it also exists in single directories list mai 23 13:52:01 endless systemd[7288]: Started GNOME Session Manager (session: gnome-login). mai 23 13:52:01 endless systemd[7288]: Reached target GNOME Session Manager is ready. mai 23 13:52:01 endless systemd[7288]: Starting GNOME Shell on X11... mai 23 13:52:01 endless tracker-extract[7461]: Set scheduler policy to SCHED_IDLE mai 23 13:52:01 endless tracker-extract[7461]: Setting priority nice level to 19 mai 23 13:52:01 endless agent-launch[7477]: dbus-update-activation-environment: setting SSH_AUTH_SOCK=/run/user/109/openssh_agent mai 23 13:52:01 endless agent-launch[7477]: dbus-update-activation-environment: setting SSH_AGENT_LAUNCHER=openssh mai 23 13:52:01 endless agent-launch[7460]: SSH_AUTH_SOCK=/run/user/109/openssh_agent; export SSH_AUTH_SOCK; mai 23 13:52:01 endless agent-launch[7460]: echo Agent pid 7460; mai 23 13:52:04 endless gdm-Xorg-:0[7222]: (II) modeset(0): EDID vendor "CMN", prod id 5596 mai 23 13:52:04 endless gdm-Xorg-:0[7222]: (II) modeset(0): Printing DDC gathered Modelines: mai 23 13:52:04 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1366x768"x0.0 76.42 1366 1434 1479 1592 768 772 779 800 -hsync -vsync (48.0 kHz eP) mai 23 13:52:05 endless dbus-daemon[7415]: [session uid=109 pid=7415] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.9' (uid=109 pid=7462 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 13:52:05 endless systemd[7288]: Started Tracker file system data miner. mai 23 13:52:05 endless systemd[7288]: Starting Tracker metadata database store and lookup manager... mai 23 13:52:06 endless dbus-daemon[7415]: [session uid=109 pid=7415] Successfully activated service 'org.freedesktop.Tracker1' mai 23 13:52:06 endless systemd[7288]: Started Tracker metadata database store and lookup manager. mai 23 13:52:06 endless gnome-shell[7473]: Getting parental controls for user 109 mai 23 13:52:14 endless gnome-shell[7473]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. mai 23 13:52:14 endless gnome-shell[7473]: Will monitor session c2 mai 23 13:52:15 endless dbus-daemon[7415]: [session uid=109 pid=7415] Activating service name='org.freedesktop.portal.IBus' requested by ':1.26' (uid=109 pid=7518 comm="ibus-daemon --panel disable --xim " label="unconfined") mai 23 13:52:15 endless at-spi-bus-launcher[7437]: dbus-daemon[7437]: Activating service name='org.a11y.atspi.Registry' requested by ':1.2' (uid=109 pid=7526 comm="/usr/lib/ibus/ibus-x11 --kill-daemon " label="unconfined") mai 23 13:52:15 endless dbus-daemon[7415]: [session uid=109 pid=7415] Successfully activated service 'org.freedesktop.portal.IBus' mai 23 13:52:15 endless at-spi-bus-launcher[7437]: dbus-daemon[7437]: Successfully activated service 'org.a11y.atspi.Registry' mai 23 13:52:15 endless at-spi-bus-launcher[7536]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry mai 23 13:52:15 endless systemd[7288]: Started Tracker metadata extractor. mai 23 13:52:15 endless dbus-daemon[7415]: [session uid=109 pid=7415] Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' requested by ':1.23' (uid=109 pid=7473 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:52:15 endless systemd[7288]: Starting sandboxed app permission store... mai 23 13:52:15 endless polkitd[1720]: Registered Authentication Agent for unix-session:c2 (system bus name :1.433 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:52:15 endless dbus-daemon[7415]: [session uid=109 pid=7415] Activating service name='org.gnome.Shell.Notifications' requested by ':1.23' (uid=109 pid=7473 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:52:15 endless dbus-daemon[7415]: [session uid=109 pid=7415] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' mai 23 13:52:15 endless systemd[7288]: Started sandboxed app permission store. mai 23 13:52:15 endless dbus-daemon[7415]: [session uid=109 pid=7415] Successfully activated service 'org.gnome.Shell.Notifications' mai 23 13:52:15 endless dbus-daemon[7415]: [session uid=109 pid=7415] Activating service name='ca.desrt.dconf' requested by ':1.23' (uid=109 pid=7473 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:52:15 endless systemd[7288]: Started GNOME Shell on X11. mai 23 13:52:15 endless systemd[7288]: Reached target GNOME Shell on X11. mai 23 13:52:15 endless systemd[7288]: Reached target GNOME Session is initialized. mai 23 13:52:15 endless systemd[7288]: Reached target GNOME session X11 services. mai 23 13:52:15 endless systemd[7288]: Reached target GNOME X11 Session. mai 23 13:52:15 endless systemd[7288]: Reached target GNOME Session (session: gnome-login). mai 23 13:52:15 endless systemd[7288]: Starting Signal initialization done to GNOME Session Manager... mai 23 13:52:15 endless systemd[7288]: Starting GNOME Accessibility settings... mai 23 13:52:15 endless systemd[7288]: Starting GNOME Color management... mai 23 13:52:15 endless systemd[7288]: Starting GNOME Keyboard handling... mai 23 13:52:15 endless systemd[7288]: Starting GNOME Media keys handling... mai 23 13:52:15 endless systemd[7288]: Starting GNOME Power management handling... mai 23 13:52:15 endless systemd[7288]: Starting GNOME Printer notifications... mai 23 13:52:15 endless systemd[7288]: Starting GNOME RFKill handling... mai 23 13:52:15 endless systemd[7288]: Starting GNOME Smartcard handling... mai 23 13:52:15 endless systemd[7288]: Starting GNOME Sound sample caching handling... mai 23 13:52:15 endless systemd[7288]: Starting GNOME USB protection handling... mai 23 13:52:15 endless dbus-daemon[7415]: [session uid=109 pid=7415] Successfully activated service 'ca.desrt.dconf' mai 23 13:52:15 endless systemd[7288]: Starting GNOME Wacom handling... mai 23 13:52:15 endless systemd[7288]: Starting GNOME WWan management... mai 23 13:52:15 endless systemd[7288]: Starting GNOME XSettings... mai 23 13:52:15 endless systemd[7288]: gnome-session-signal-init.service: Succeeded. mai 23 13:52:15 endless systemd[7288]: Started Signal initialization done to GNOME Session Manager. mai 23 13:52:15 endless gnome-session-binary[7464]: Entering running state mai 23 13:52:16 endless dbus-daemon[1538]: [system] Activating via systemd: service name='com.endlessm.RecordBootSuccess' unit='record-boot-success.service' requested by ':1.471' (uid=109 pid=7588 comm="dbus-send --system --type=method_call --dest=org.f" label="unconfined") mai 23 13:52:16 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.472' (uid=109 pid=7573 comm="/usr/libexec/gsd-rfkill " label="unconfined") mai 23 13:52:16 endless systemd[7288]: Started GNOME WWan management. mai 23 13:52:16 endless systemd[7288]: Reached target GNOME WWan management. mai 23 13:52:16 endless systemd[7288]: Started GNOME Accessibility settings. mai 23 13:52:16 endless systemd[7288]: Reached target GNOME Accessibility settings. mai 23 13:52:16 endless systemd[7288]: Started GNOME USB protection handling. mai 23 13:52:16 endless systemd[7288]: Reached target GNOME USB protection handling. mai 23 13:52:16 endless cupsd[1536]: REQUEST localhost - - "POST / HTTP/1.1" 200 366 Create-Printer-Subscriptions successful-ok mai 23 13:52:16 endless systemd[7288]: Started GNOME Sound sample caching handling. mai 23 13:52:16 endless systemd[7288]: Reached target GNOME Sound sample caching handling. mai 23 13:52:16 endless systemd[1]: Starting Hostname Service... mai 23 13:52:16 endless systemd[7288]: Started GNOME Printer notifications. mai 23 13:52:16 endless systemd[7288]: Started GNOME Keyboard handling. mai 23 13:52:16 endless systemd[7288]: Reached target GNOME Keyboard handling. mai 23 13:52:16 endless systemd[7288]: Reached target GNOME Printer notifications. mai 23 13:52:16 endless xbrlapi.desktop[7587]: openConnection: connect: Arquivo ou diretório inexistente mai 23 13:52:16 endless xbrlapi.desktop[7587]: cannot connect to braille devices daemon brltty at :0 mai 23 13:52:16 endless systemd[7288]: Started GNOME Wacom handling. mai 23 13:52:16 endless systemd[7288]: Reached target GNOME Wacom handling. mai 23 13:52:16 endless systemd[7288]: Started GNOME Media keys handling. mai 23 13:52:16 endless systemd[7288]: Reached target GNOME Media keys handling. mai 23 13:52:16 endless systemd[7288]: Started GNOME Power management handling. mai 23 13:52:16 endless systemd[7288]: Reached target GNOME Power management handling. mai 23 13:52:16 endless systemd[7288]: Started GNOME Smartcard handling. mai 23 13:52:16 endless systemd[7288]: Reached target GNOME Smartcard handling. mai 23 13:52:16 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.hostname1' mai 23 13:52:16 endless systemd[1]: Started Hostname Service. mai 23 13:52:16 endless systemd[7288]: Started GNOME RFKill handling. mai 23 13:52:16 endless systemd[7288]: Reached target GNOME RFKill handling. mai 23 13:52:16 endless kernel: rfkill: input handler disabled mai 23 13:52:16 endless systemd[7288]: Started GNOME Color management. mai 23 13:52:16 endless systemd[7288]: Reached target GNOME Color management. mai 23 13:52:16 endless dbus-daemon[1538]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.433' (uid=109 pid=7473 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:52:16 endless systemd[1]: Starting Fingerprint Authentication Daemon... mai 23 13:52:16 endless dbus-daemon[1538]: [system] Successfully activated service 'net.reactivated.Fprint' mai 23 13:52:16 endless systemd[1]: Started Fingerprint Authentication Daemon. mai 23 13:52:17 endless upowerd[1729]: up_kbd_backlight_brightness_read: assertion 'fd >= 0' failed mai 23 13:52:17 endless gsd-power[7571]: Failed to get brightness: GDBus.Error:org.freedesktop.UPower.GeneralError: error reading brightness mai 23 13:52:17 endless gsd-media-keys[7569]: Failed to grab accelerator for keybinding settings:playback-random mai 23 13:52:17 endless gsd-media-keys[7569]: Failed to grab accelerator for keybinding settings:hibernate mai 23 13:52:17 endless gsd-media-keys[7569]: Failed to grab accelerator for keybinding settings:playback-repeat mai 23 13:52:17 endless gsd-media-keys[7569]: Failed to grab accelerator for keybinding settings:rfkill mai 23 13:52:17 endless systemd[7288]: Started GNOME XSettings. mai 23 13:52:17 endless systemd[7288]: Reached target GNOME XSettings. mai 23 13:52:17 endless systemd[7288]: Reached target GNOME Session. mai 23 13:52:17 endless systemd[7288]: Reached target GNOME X11 Session (session: gnome-login). mai 23 13:52:17 endless systemd[7288]: Reached target Current graphical user session. mai 23 13:52:17 endless systemd[7288]: Condition check resulted in GNOME Welcome Tour being skipped. mai 23 13:52:17 endless systemd[7288]: Startup finished in 24.215s. mai 23 13:52:17 endless colord[2288]: failed to get session [pid 7566]: Não há dados disponíveis mai 23 13:52:17 endless gnome-shell[7473]: Registering session with GDM mai 23 13:52:18 endless mogwai-schedule[6358]: Exiting due to reaching inactivity timeout mai 23 13:52:18 endless systemd[1]: mogwai-scheduled.service: Succeeded. mai 23 13:52:25 endless systemd[7288]: tracker-extract.service: Succeeded. mai 23 13:52:29 endless gdm-password][7798]: gkr-pam: unable to locate daemon control file mai 23 13:52:29 endless gdm-password][7798]: gkr-pam: stashed password to try later in open session mai 23 13:52:29 endless gdm-password][7798]: pam_unix(gdm-password:session): session opened for user daniel by (uid=0) mai 23 13:52:29 endless systemd-logind[1824]: New session 5 of user daniel. mai 23 13:52:29 endless systemd[1]: Started Session 5 of user daniel. mai 23 13:52:29 endless kernel: rfkill: input handler enabled mai 23 13:52:29 endless gdm-password][7798]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring mai 23 13:52:29 endless ntpd[4611]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME X11 Session (session: gnome-login). mai 23 13:52:29 endless systemd[7288]: Stopped target Current graphical user session. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME Session. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME X11 Session. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME Session (session: gnome-login). mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME Accessibility settings. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME Color management. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME Keyboard handling. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME Media keys handling. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME Power management handling. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME Printer notifications. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME RFKill handling. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME Smartcard handling. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME Sound sample caching handling. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME USB protection handling. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME Wacom handling. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME WWan management. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME XSettings. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME session X11 services. mai 23 13:52:29 endless systemd[7288]: Stopping GNOME Accessibility settings... mai 23 13:52:29 endless systemd[7288]: Stopping GNOME Color management... mai 23 13:52:29 endless systemd[7288]: Stopping GNOME Keyboard handling... mai 23 13:52:29 endless systemd[7288]: Stopping GNOME Media keys handling... mai 23 13:52:29 endless systemd[7288]: Stopping GNOME Power management handling... mai 23 13:52:29 endless systemd[7288]: Stopping GNOME Printer notifications... mai 23 13:52:29 endless systemd[7288]: Stopping GNOME RFKill handling... mai 23 13:52:29 endless systemd[7288]: Stopping GNOME Smartcard handling... mai 23 13:52:29 endless systemd[7288]: Stopping GNOME Sound sample caching handling... mai 23 13:52:29 endless systemd[7288]: Stopping GNOME USB protection handling... mai 23 13:52:29 endless systemd[7288]: Stopping GNOME Wacom handling... mai 23 13:52:29 endless systemd[7288]: Stopping GNOME WWan management... mai 23 13:52:29 endless cupsd[1536]: REQUEST localhost - - "POST / HTTP/1.1" 200 158 Cancel-Subscription successful-ok mai 23 13:52:29 endless systemd[7288]: Stopping GNOME XSettings... mai 23 13:52:29 endless cupsd[1536]: REQUEST localhost - - "POST / HTTP/1.1" 200 158 Cancel-Subscription client-error-not-found mai 23 13:52:29 endless gsd-print-notif[7572]: Source ID 6 was not found when attempting to remove it mai 23 13:52:29 endless systemd[7288]: gsd-a11y-settings.service: Succeeded. mai 23 13:52:29 endless systemd[7288]: Stopped GNOME Accessibility settings. mai 23 13:52:29 endless systemd[7288]: gsd-print-notifications.service: Succeeded. mai 23 13:52:29 endless systemd[7288]: Stopped GNOME Printer notifications. mai 23 13:52:29 endless systemd[7288]: gsd-rfkill.service: Succeeded. mai 23 13:52:29 endless systemd[7288]: Stopped GNOME RFKill handling. mai 23 13:52:29 endless systemd[7288]: gsd-smartcard.service: Succeeded. mai 23 13:52:29 endless systemd[7288]: Stopped GNOME Smartcard handling. mai 23 13:52:29 endless systemd[7288]: gsd-sound.service: Succeeded. mai 23 13:52:29 endless systemd[7288]: Stopped GNOME Sound sample caching handling. mai 23 13:52:29 endless systemd[7288]: gsd-usb-protection.service: Succeeded. mai 23 13:52:29 endless systemd[7288]: Stopped GNOME USB protection handling. mai 23 13:52:29 endless systemd[7288]: gsd-wwan.service: Succeeded. mai 23 13:52:29 endless systemd[7288]: Stopped GNOME WWan management. mai 23 13:52:29 endless systemd[7288]: gnome-session-monitor.service: Succeeded. mai 23 13:52:29 endless systemd[7288]: Stopped Monitor Session leader for GNOME Session. mai 23 13:52:29 endless gdm-launch-environment][7243]: pam_unix(gdm-launch-environment:session): session closed for user Debian-gdm mai 23 13:52:29 endless systemd[7288]: gsd-power.service: Succeeded. mai 23 13:52:29 endless systemd[7288]: Stopped GNOME Power management handling. mai 23 13:52:29 endless systemd[7288]: gsd-wacom.service: Succeeded. mai 23 13:52:29 endless systemd[7288]: Stopped GNOME Wacom handling. mai 23 13:52:29 endless systemd[7288]: gsd-keyboard.service: Succeeded. mai 23 13:52:29 endless systemd[7288]: Stopped GNOME Keyboard handling. mai 23 13:52:29 endless systemd[7288]: gsd-color.service: Succeeded. mai 23 13:52:29 endless systemd[7288]: Stopped GNOME Color management. mai 23 13:52:29 endless systemd[7288]: gsd-media-keys.service: Succeeded. mai 23 13:52:29 endless systemd[7288]: Stopped GNOME Media keys handling. mai 23 13:52:29 endless systemd[7288]: gsd-xsettings.service: Succeeded. mai 23 13:52:29 endless systemd[7288]: Stopped GNOME XSettings. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME Session is initialized. mai 23 13:52:29 endless systemd[7288]: Stopped target GNOME Shell on X11. mai 23 13:52:29 endless systemd[7288]: Stopping GNOME Shell on X11... mai 23 13:52:30 endless kernel: gdm-session-wor (7243): drop_caches: 2 mai 23 13:52:30 endless systemd[1]: session-c2.scope: Succeeded. mai 23 13:52:30 endless systemd-logind[1824]: Session c2 logged out. Waiting for processes to exit. mai 23 13:52:30 endless systemd-logind[1824]: Removed session c2. mai 23 13:52:30 endless gdm[3372]: Child process -7395 was already dead. mai 23 13:52:30 endless /etc/gdm3/Xsession[7906]: /etc/gdm3/Xsession: Beginning session setup... mai 23 13:52:30 endless bluetoothd[3770]: Endpoint unregistered: sender=:1.429 path=/MediaEndpoint/A2DPSource/sbc mai 23 13:52:30 endless systemd[7288]: pulseaudio.service: Succeeded. mai 23 13:52:30 endless polkitd[1720]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.433, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) (disconnected from bus) mai 23 13:52:30 endless systemd[7288]: gnome-shell-x11.service: Succeeded. mai 23 13:52:30 endless systemd[7288]: Stopped GNOME Shell on X11. mai 23 13:52:30 endless systemd[7288]: Stopped target GNOME Session Manager is ready. mai 23 13:52:30 endless systemd[7288]: Stopping GNOME Session Manager (session: gnome-login)... mai 23 13:52:30 endless gnome-session[7464]: gnome-session-binary[7464]: WARNING: Could not get session class: Endereço ou dispositivo inexistente mai 23 13:52:30 endless gnome-session-binary[7464]: WARNING: Could not get session class: Endereço ou dispositivo inexistente mai 23 13:52:30 endless systemd[7288]: at-spi-dbus-bus.service: Succeeded. mai 23 13:52:30 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.1' (uid=1001 pid=7910 comm="flatpak --installations " label="unconfined") mai 23 13:52:30 endless systemd[3453]: Starting Virtual filesystem service... mai 23 13:52:30 endless systemd[7288]: gnome-session-manager@gnome-login.service: Succeeded. mai 23 13:52:30 endless systemd[7288]: Stopped GNOME Session Manager (session: gnome-login). mai 23 13:52:30 endless systemd[7288]: Stopped target Tasks to be run before GNOME Session starts. mai 23 13:52:32 endless tracker-store[7506]: Received signal:15->'Terminado' mai 23 13:52:32 endless tracker-store[7506]: OK mai 23 13:52:32 endless tracker-miner-fs[7462]: Received signal:15->'Terminado' mai 23 13:52:32 endless tracker-miner-fs[7462]: OK mai 23 13:52:30 endless systemd[7288]: Stopped target Session services which should run early before the graphical session is brought up. mai 23 13:52:32 endless gvfsd[7428]: A connection to the bus can't be made mai 23 13:52:30 endless systemd[7288]: Reached target Shutdown running GNOME Session. mai 23 13:52:30 endless systemd[7288]: Starting Restart DBus after GNOME Session shutdown... mai 23 13:52:30 endless systemd[7288]: Stopped target Shutdown running GNOME Session. mai 23 13:52:30 endless systemd[7288]: Started Restart DBus after GNOME Session shutdown. mai 23 13:52:30 endless systemd[7288]: Stopping D-Bus User Message Bus... mai 23 13:52:30 endless systemd[7288]: gnome-session-restart-dbus.service: Succeeded. mai 23 13:52:30 endless tracker-miner-f[7462]: Error while sending AddMatch() message: A conexão está fechada mai 23 13:52:30 endless tracker-miner-f[7462]: Error while sending AddMatch() message: A conexão está fechada mai 23 13:52:30 endless tracker-miner-f[7462]: Error while sending AddMatch() message: A conexão está fechada mai 23 13:52:30 endless systemd[7288]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE mai 23 13:52:30 endless systemd[7288]: xdg-permission-store.service: Failed with result 'exit-code'. mai 23 13:52:30 endless systemd[7288]: dbus.service: Succeeded. mai 23 13:52:30 endless systemd[7288]: Stopped D-Bus User Message Bus. mai 23 13:52:30 endless systemd[7288]: Started D-Bus User Message Bus. mai 23 13:52:30 endless systemd[3453]: run-user-109-gvfs.mount: Succeeded. mai 23 13:52:30 endless systemd[1]: run-user-109-gvfs.mount: Succeeded. mai 23 13:52:32 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.gtk.vfs.Daemon' mai 23 13:52:32 endless systemd[3453]: Started Virtual filesystem service. mai 23 13:52:33 endless /etc/gdm3/Xsession[7969]: dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus mai 23 13:52:33 endless /etc/gdm3/Xsession[7969]: dbus-update-activation-environment: setting DISPLAY=:0 mai 23 13:52:33 endless /etc/gdm3/Xsession[7969]: dbus-update-activation-environment: setting XAUTHORITY=/var/run/gdm3/auth-for-daniel-J7G1K0/database mai 23 13:52:33 endless /etc/gdm3/Xsession[7984]: localuser:daniel being added to access control list mai 23 13:52:33 endless /etc/gdm3/Xsession[8008]: dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge mai 23 13:52:34 endless /etc/gdm3/Xsession[8014]: dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting USER=daniel mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11 mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting HOME=/sysroot/home/daniel mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting QT4_IM_MODULE=ibus mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting DESKTOP_SESSION=endless-xorg mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting IM_CONFIG_PHASE=1 mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting LOGNAME=daniel mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting GTK_IM_MODULE=ibus mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting XDG_SESSION_CLASS=user mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting USERNAME=daniel mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting GTK_OVERLAY_SCROLLING=0 mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting WINDOWPATH=1:1 mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/sysroot/home/daniel/.local/share/flatpak/exports/bin:/var/lib/flatpak/exports/bin: mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting GDM_LANG=pt_BR.UTF-8 mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1001 mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting DISPLAY=:0 mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting LANG=pt_BR.UTF-8 mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting XDG_CURRENT_DESKTOP=endless:GNOME mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting XAUTHORITY=/var/run/gdm3/auth-for-daniel-J7G1K0/database mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=endless-xorg mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting XMODIFIERS=@im=ibus mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting SHELL=/bin/bash mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting GDMSESSION=endless-xorg mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1001/gnupg/S.gpg-agent:0:1 mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting QT_IM_MODULE=ibus mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting PWD=/sysroot/home/daniel mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting XDG_DATA_DIRS=/run/share/:/sysroot/home/daniel/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/var/endless-extra/flatpak/exports/share/:/usr/local/share/:/usr/share/ mai 23 13:52:34 endless /etc/gdm3/Xsession[8015]: dbus-update-activation-environment: setting CLUTTER_IM_MODULE=ibus mai 23 13:52:34 endless /etc/gdm3/Xsession[7906]: VirtualBox Additions disabled, not in a Virtual Machine mai 23 13:52:34 endless systemd[7288]: run-user-109-gvfs.mount: Succeeded. mai 23 13:52:34 endless systemd[7288]: tracker-miner-fs.service: Succeeded. mai 23 13:52:34 endless systemd[7288]: tracker-store.service: Succeeded. mai 23 13:52:34 endless systemd[7288]: gvfs-daemon.service: Succeeded. mai 23 13:52:34 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.17' (uid=1001 pid=8047 comm="/usr/libexec/gnome-session-check-accelerated " label="unconfined") mai 23 13:52:34 endless systemd[3453]: Starting Accessibility services bus... mai 23 13:52:34 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating service name='org.freedesktop.portal.IBus' requested by ':1.13' (uid=1001 pid=8035 comm="/usr/bin/ibus-daemon --daemonize --xim " label="unconfined") mai 23 13:52:34 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.a11y.Bus' mai 23 13:52:34 endless systemd[3453]: Started Accessibility services bus. mai 23 13:52:34 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.freedesktop.portal.IBus' mai 23 13:52:34 endless at-spi-bus-launcher[8061]: dbus-daemon[8061]: Activating service name='org.a11y.atspi.Registry' requested by ':1.2' (uid=1001 pid=8052 comm="/usr/lib/ibus/ibus-x11 --kill-daemon " label="unconfined") mai 23 13:52:34 endless at-spi-bus-launcher[8061]: dbus-daemon[8061]: Successfully activated service 'org.a11y.atspi.Registry' mai 23 13:52:34 endless at-spi-bus-launcher[8071]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry mai 23 13:52:36 endless systemd[3453]: Condition check resulted in GNOME Initial Setup Copy Worker being skipped. mai 23 13:52:36 endless gnome-session[7906]: gnome-session-binary[7906]: WARNING: Error creating FIFO: Arquivo existe mai 23 13:52:36 endless gnome-session-binary[7906]: WARNING: Error creating FIFO: Arquivo existe mai 23 13:52:36 endless systemd[3453]: Starting Monitor Session leader for GNOME Session... mai 23 13:52:36 endless systemd[3453]: Starting Sound Service... mai 23 13:52:36 endless systemd[3453]: Started OpenSSH Agent. mai 23 13:52:36 endless systemd[3453]: Reached target Session services which should run early before the graphical session is brought up. mai 23 13:52:36 endless systemd[3453]: Starting Tracker metadata extractor... mai 23 13:52:36 endless systemd[3453]: Started Monitor Session leader for GNOME Session. mai 23 13:52:36 endless systemd[3453]: Reached target Tasks to be run before GNOME Session starts. mai 23 13:52:36 endless gnome-session-c[8075]: Error creating FIFO: Arquivo existe mai 23 13:52:36 endless systemd[3453]: Starting GNOME Session Manager (session: gnome)... mai 23 13:52:36 endless systemd[3453]: ssh-agent.service: Succeeded. mai 23 13:52:36 endless rtkit-daemon[3835]: Successfully made thread 8076 of process 8076 (n/a) owned by '1001' high priority at nice level -11. mai 23 13:52:36 endless rtkit-daemon[3835]: Supervising 1 threads of 1 processes of 1 users. mai 23 13:52:37 endless tracker-extract[8078]: Set scheduler policy to SCHED_IDLE mai 23 13:52:37 endless tracker-extract[8078]: Setting priority nice level to 19 mai 23 13:52:37 endless gnome-keyring-ssh.desktop[8092]: SSH_AUTH_SOCK=/run/user/1001/keyring/ssh mai 23 13:52:37 endless systemd[3453]: Started GNOME Session Manager (session: gnome). mai 23 13:52:37 endless systemd[3453]: Reached target GNOME Session Manager is ready. mai 23 13:52:37 endless systemd[3453]: Starting GNOME Shell on X11... mai 23 13:52:39 endless gdm-Xorg-:0[7222]: (II) modeset(0): EDID vendor "CMN", prod id 5596 mai 23 13:52:39 endless gdm-Xorg-:0[7222]: (II) modeset(0): Printing DDC gathered Modelines: mai 23 13:52:39 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1366x768"x0.0 76.42 1366 1434 1479 1592 768 772 779 800 -hsync -vsync (48.0 kHz eP) mai 23 13:52:39 endless gnome-shell[8098]: Getting parental controls for user 1001 mai 23 13:52:40 endless systemd[1]: Stopping User Manager for UID 109... mai 23 13:52:40 endless systemd[7288]: Removed slice gnome\x2dsession\x2dmanager.slice. mai 23 13:52:40 endless systemd[7288]: Stopped target Main User Target. mai 23 13:52:40 endless systemd[7288]: Stopping D-Bus User Message Bus... mai 23 13:52:40 endless systemd[7288]: Stopping OpenSSH Agent... mai 23 13:52:40 endless systemd[7288]: ssh-agent.service: Main process exited, code=exited, status=2/INVALIDARGUMENT mai 23 13:52:40 endless systemd[7288]: dbus.service: Succeeded. mai 23 13:52:40 endless systemd[7288]: Stopped D-Bus User Message Bus. mai 23 13:52:40 endless agent-launch[8131]: dbus-update-activation-environment: error: unable to connect to D-Bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. mai 23 13:52:40 endless systemd[7288]: ssh-agent.service: Control process exited, code=exited, status=71/OSERR mai 23 13:52:40 endless systemd[7288]: ssh-agent.service: Failed with result 'exit-code'. mai 23 13:52:40 endless systemd[7288]: Stopped OpenSSH Agent. mai 23 13:52:40 endless systemd[7288]: Stopped target Basic System. mai 23 13:52:40 endless systemd[7288]: Stopped target Paths. mai 23 13:52:40 endless systemd[7288]: Stopped target Sockets. mai 23 13:52:40 endless systemd[7288]: Stopped target Timers. mai 23 13:52:40 endless systemd[7288]: dbus.socket: Succeeded. mai 23 13:52:40 endless systemd[7288]: Closed D-Bus User Message Bus Socket. mai 23 13:52:40 endless systemd[7288]: dirmngr.socket: Succeeded. mai 23 13:52:40 endless systemd[7288]: Closed GnuPG network certificate management daemon. mai 23 13:52:40 endless systemd[7288]: gpg-agent-browser.socket: Succeeded. mai 23 13:52:40 endless systemd[7288]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers). mai 23 13:52:40 endless systemd[7288]: gpg-agent-extra.socket: Succeeded. mai 23 13:52:40 endless systemd[7288]: Closed GnuPG cryptographic agent and passphrase cache (restricted). mai 23 13:52:40 endless systemd[7288]: gpg-agent-ssh.socket: Succeeded. mai 23 13:52:40 endless systemd[7288]: Closed GnuPG cryptographic agent (ssh-agent emulation). mai 23 13:52:40 endless systemd[7288]: gpg-agent.socket: Succeeded. mai 23 13:52:40 endless systemd[7288]: Closed GnuPG cryptographic agent and passphrase cache. mai 23 13:52:40 endless systemd[7288]: pulseaudio.socket: Succeeded. mai 23 13:52:40 endless systemd[7288]: Closed Sound System. mai 23 13:52:40 endless systemd[7288]: Reached target Shutdown. mai 23 13:52:40 endless systemd[7288]: systemd-exit.service: Succeeded. mai 23 13:52:40 endless systemd[7288]: Started Exit the Session. mai 23 13:52:40 endless systemd[7288]: Reached target Exit the Session. mai 23 13:52:40 endless systemd[1]: user@109.service: Succeeded. mai 23 13:52:40 endless systemd[1]: Stopped User Manager for UID 109. mai 23 13:52:40 endless systemd[1]: Stopping User Runtime Directory /run/user/109... mai 23 13:52:40 endless systemd[3453]: run-user-109.mount: Succeeded. mai 23 13:52:40 endless systemd[1]: run-user-109.mount: Succeeded. mai 23 13:52:40 endless systemd[1]: user-runtime-dir@109.service: Succeeded. mai 23 13:52:40 endless systemd[1]: Stopped User Runtime Directory /run/user/109. mai 23 13:52:40 endless systemd[1]: Removed slice User Slice of UID 109. mai 23 13:52:41 endless dbus-daemon[1538]: [system] Failed to activate service 'com.endlessm.RecordBootSuccess': timed out (service_start_timeout=25000ms) mai 23 13:52:44 endless rtkit-daemon[3835]: Supervising 1 threads of 1 processes of 1 users. mai 23 13:52:44 endless rtkit-daemon[3835]: Successfully made thread 8228 of process 8076 (n/a) owned by '1001' RT at priority 5. mai 23 13:52:44 endless rtkit-daemon[3835]: Supervising 2 threads of 1 processes of 1 users. mai 23 13:52:44 endless rtkit-daemon[3835]: Supervising 2 threads of 1 processes of 1 users. mai 23 13:52:44 endless rtkit-daemon[3835]: Successfully made thread 8229 of process 8076 (n/a) owned by '1001' RT at priority 5. mai 23 13:52:44 endless rtkit-daemon[3835]: Supervising 3 threads of 1 processes of 1 users. mai 23 13:52:46 endless systemd[1]: systemd-localed.service: Succeeded. mai 23 13:52:46 endless systemd[1]: systemd-hostnamed.service: Succeeded. mai 23 13:52:46 endless systemd[1]: fprintd.service: Succeeded. mai 23 13:52:56 endless systemd[3453]: Started Sound Service. mai 23 13:52:56 endless bluetoothd[3770]: Endpoint registered: sender=:1.524 path=/MediaEndpoint/A2DPSource/sbc mai 23 13:52:56 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.45' (uid=1001 pid=8078 comm="/usr/libexec/tracker-extract " label="unconfined") mai 23 13:52:56 endless systemd[3453]: Starting Virtual filesystem service - disk device monitor... mai 23 13:52:57 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor' mai 23 13:52:57 endless systemd[3453]: Started Virtual filesystem service - disk device monitor. mai 23 13:52:57 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.45' (uid=1001 pid=8078 comm="/usr/libexec/tracker-extract " label="unconfined") mai 23 13:52:57 endless systemd[3453]: Starting Virtual filesystem service - digital camera monitor... mai 23 13:52:57 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor' mai 23 13:52:57 endless systemd[3453]: Started Virtual filesystem service - digital camera monitor. mai 23 13:52:57 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.45' (uid=1001 pid=8078 comm="/usr/libexec/tracker-extract " label="unconfined") mai 23 13:52:57 endless systemd[3453]: Starting Virtual filesystem service - Apple File Conduit monitor... mai 23 13:52:57 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor' mai 23 13:52:57 endless systemd[3453]: Started Virtual filesystem service - Apple File Conduit monitor. mai 23 13:52:57 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.45' (uid=1001 pid=8078 comm="/usr/libexec/tracker-extract " label="unconfined") mai 23 13:52:57 endless systemd[3453]: Starting Virtual filesystem service - Media Transfer Protocol monitor... mai 23 13:52:57 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor' mai 23 13:52:57 endless systemd[3453]: Started Virtual filesystem service - Media Transfer Protocol monitor. mai 23 13:52:57 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.45' (uid=1001 pid=8078 comm="/usr/libexec/tracker-extract " label="unconfined") mai 23 13:52:57 endless systemd[3453]: Starting Virtual filesystem service - GNOME Online Accounts monitor... mai 23 13:52:57 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating service name='org.gnome.OnlineAccounts' requested by ':1.55' (uid=1001 pid=8364 comm="/usr/libexec/gvfs-goa-volume-monitor " label="unconfined") mai 23 13:52:58 endless goa-daemon[8368]: goa-daemon version 3.36.0 starting mai 23 13:52:58 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating service name='org.gnome.Identity' requested by ':1.56' (uid=1001 pid=8368 comm="/usr/libexec/goa-daemon " label="unconfined") mai 23 13:52:58 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.gnome.OnlineAccounts' mai 23 13:52:58 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor' mai 23 13:52:58 endless systemd[3453]: Started Virtual filesystem service - GNOME Online Accounts monitor. mai 23 13:52:58 endless systemd[3453]: Started Tracker metadata extractor. mai 23 13:52:58 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.gnome.Identity' mai 23 13:52:59 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.gtk.GLib.PACRunner' unit='glib-pacrunner.service' requested by ':1.56' (uid=1001 pid=8368 comm="/usr/libexec/goa-daemon " label="unconfined") mai 23 13:52:59 endless systemd[3453]: Starting GLib proxy auto-configuration service... mai 23 13:52:59 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.gtk.GLib.PACRunner' mai 23 13:52:59 endless systemd[3453]: Started GLib proxy auto-configuration service. mai 23 13:52:59 endless goa-daemon[8368]: /org/gnome/OnlineAccounts/Accounts/account_1568089395_0: Setting AttentionNeeded to TRUE because EnsureCredentials() failed with: Falha ao atualizar o token de acesso (rest-proxy-error-quark, 400): Bad Request (goa-error-quark, 4) mai 23 13:53:05 endless gnome-shell[8098]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. mai 23 13:53:05 endless gnome-shell[8098]: Will monitor session 5 mai 23 13:53:05 endless gnome-shell[8397]: current session already has an ibus-daemon. mai 23 13:53:06 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' requested by ':1.50' (uid=1001 pid=8098 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:53:06 endless systemd[3453]: Starting sandboxed app permission store... mai 23 13:53:06 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' mai 23 13:53:06 endless systemd[3453]: Started sandboxed app permission store. mai 23 13:53:09 endless systemd[3453]: tracker-extract.service: Succeeded. mai 23 13:53:09 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating service name='org.gnome.Shell.CalendarServer' requested by ':1.50' (uid=1001 pid=8098 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:53:09 endless gnome-shell[8098]: Attempting to add actor of type 'StBoxLayout' to a container of type 'StBoxLayout', but the actor has already a parent of type 'StBoxLayout'. mai 23 13:53:09 endless kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 mai 23 13:53:09 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating service name='ca.desrt.dconf' requested by ':1.50' (uid=1001 pid=8098 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:53:09 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'ca.desrt.dconf' mai 23 13:53:09 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service' requested by ':1.65' (uid=1001 pid=8407 comm="/usr/libexec/gnome-shell-calendar-server " label="unconfined") mai 23 13:53:09 endless polkitd[1720]: Registered Authentication Agent for unix-session:5 (system bus name :1.518 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 13:53:09 endless gnome-shell[8098]: Telepathy is not available, chat integration will be disabled. mai 23 13:53:10 endless systemd[3453]: Starting Evolution source registry... mai 23 13:53:10 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.67' (uid=1001 pid=8415 comm="/usr/libexec/evolution-source-registry " label="unconfined") mai 23 13:53:10 endless systemd[3453]: Starting Virtual filesystem metadata service... mai 23 13:53:10 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.gtk.vfs.Metadata' mai 23 13:53:10 endless systemd[3453]: Started Virtual filesystem metadata service. mai 23 13:53:10 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.gnome.evolution.dataserver.Sources5' mai 23 13:53:10 endless systemd[3453]: Started Evolution source registry. mai 23 13:53:10 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.gnome.Shell.CalendarServer' mai 23 13:53:12 endless gnome-shell[8098]: ../../../gobject/gsignal.c:1745: signal "clicked" already exists in the 'StButton' class ancestry mai 23 13:53:13 endless gnome-shell[8098]: Some code accessed the property 'AppIconButton' on the module 'appIconBar'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. mai 23 13:53:13 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating service name='org.gnome.Shell.Notifications' requested by ':1.50' (uid=1001 pid=8098 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:53:13 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.gnome.Shell.Notifications' mai 23 13:53:13 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.gnome.evolution.dataserver.Calendar8' unit='evolution-calendar-factory.service' requested by ':1.65' (uid=1001 pid=8407 comm="/usr/libexec/gnome-shell-calendar-server " label="unconfined") mai 23 13:53:13 endless systemd[3453]: Started GNOME Shell on X11. mai 23 13:53:13 endless systemd[3453]: Reached target GNOME Shell on X11. mai 23 13:53:13 endless systemd[3453]: Reached target GNOME Session is initialized. mai 23 13:53:13 endless systemd[3453]: Reached target GNOME session X11 services. mai 23 13:53:13 endless systemd[3453]: Reached target GNOME X11 Session. mai 23 13:53:13 endless systemd[3453]: Reached target GNOME Session (session: gnome). mai 23 13:53:13 endless systemd[3453]: Starting Evolution calendar service... mai 23 13:53:13 endless systemd[3453]: Starting Signal initialization done to GNOME Session Manager... mai 23 13:53:13 endless systemd[3453]: Starting GNOME Accessibility settings... mai 23 13:53:13 endless systemd[3453]: Starting GNOME Color management... mai 23 13:53:13 endless systemd[3453]: Starting GNOME Date & Time handling... mai 23 13:53:13 endless systemd[3453]: Starting GNOME Maintenance of expirable data... mai 23 13:53:13 endless systemd[3453]: Starting GNOME Keyboard handling... mai 23 13:53:13 endless systemd[3453]: Starting GNOME Media keys handling... mai 23 13:53:13 endless systemd[3453]: Starting GNOME Power management handling... mai 23 13:53:13 endless systemd[3453]: Starting GNOME Printer notifications... mai 23 13:53:13 endless systemd[3453]: Starting GNOME RFKill handling... mai 23 13:53:13 endless systemd[3453]: Starting GNOME Freedesktop screensaver handling... mai 23 13:53:13 endless systemd[3453]: Starting GNOME Sharing handling... mai 23 13:53:13 endless systemd[3453]: Starting GNOME Smartcard handling... mai 23 13:53:13 endless systemd[3453]: Starting GNOME Sound sample caching handling... mai 23 13:53:13 endless systemd[3453]: Starting GNOME USB protection handling... mai 23 13:53:13 endless systemd[3453]: Starting GNOME Wacom handling... mai 23 13:53:13 endless systemd[3453]: Starting GNOME WWan management... mai 23 13:53:13 endless systemd[3453]: Starting GNOME XSettings... mai 23 13:53:13 endless systemd[3453]: gnome-session-signal-init.service: Succeeded. mai 23 13:53:13 endless systemd[3453]: Started Signal initialization done to GNOME Session Manager. mai 23 13:53:13 endless dbus-daemon[1538]: [system] Activating via systemd: service name='com.endlessm.MogwaiSchedule1' unit='mogwai-scheduled.service' requested by ':1.518' (uid=1001 pid=8098 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:53:13 endless systemd[1]: Starting Download Scheduling Daemon... mai 23 13:53:13 endless NetworkManager[1540]: [1590252793.6431] agent-manager: req[0x55a71f00c6d0, :1.518/org.gnome.Shell.NetworkAgent/1001]: agent registered mai 23 13:53:13 endless gnome-session-binary[8080]: Entering running state mai 23 13:53:13 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.76' (uid=1001 pid=8528 comm="gdbus call -e -d org.freedesktop.DBus -o /org/free" label="unconfined") mai 23 13:53:13 endless vmware-user.desktop[8547]: vmware-user: could not open /proc/fs/vmblock/dev mai 23 13:53:13 endless dbus-daemon[1538]: [system] Activating via systemd: service name='com.endlessm.RecordBootSuccess' unit='record-boot-success.service' requested by ':1.587' (uid=1001 pid=8525 comm="dbus-send --system --type=method_call --dest=org.f" label="unconfined") mai 23 13:53:13 endless systemd[3453]: Starting Tracker metadata database store and lookup manager... mai 23 13:53:13 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.freedesktop.Tracker1' mai 23 13:53:13 endless tracker-store.desktop[8528]: (uint32 1,) mai 23 13:53:13 endless systemd[3453]: Started Tracker metadata database store and lookup manager. mai 23 13:53:14 endless gnome-shell[8098]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). mai 23 13:53:14 endless gnome-shell[8098]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). mai 23 13:53:14 endless gnome-shell[8098]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). mai 23 13:53:14 endless gnome-shell[8098]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). mai 23 13:53:14 endless gnome-shell[8098]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). mai 23 13:53:14 endless gnome-shell[8098]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). mai 23 13:53:14 endless gnome-shell[8098]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). mai 23 13:53:14 endless gnome-shell[8098]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). mai 23 13:53:14 endless gnome-shell[8098]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). mai 23 13:53:14 endless systemd[3453]: Started GNOME Freedesktop screensaver handling. mai 23 13:53:14 endless systemd[3453]: Reached target GNOME Freedesktop screensaver handling. mai 23 13:53:14 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.589' (uid=1001 pid=8454 comm="/usr/libexec/gsd-rfkill " label="unconfined") mai 23 13:53:14 endless cupsd[1536]: REQUEST localhost - - "POST / HTTP/1.1" 200 362 Create-Printer-Subscriptions successful-ok mai 23 13:53:14 endless systemd[1]: Starting Hostname Service... mai 23 13:53:14 endless systemd[3453]: Started GNOME Sharing handling. mai 23 13:53:14 endless systemd[3453]: Reached target GNOME Sharing handling. mai 23 13:53:14 endless systemd[3453]: Started GNOME Printer notifications. mai 23 13:53:14 endless systemd[3453]: Reached target GNOME Printer notifications. mai 23 13:53:14 endless systemd[3453]: Started GNOME Maintenance of expirable data. mai 23 13:53:14 endless systemd[3453]: Reached target GNOME Maintenance of expirable data. mai 23 13:53:14 endless systemd[3453]: Started GNOME Accessibility settings. mai 23 13:53:14 endless systemd[3453]: Reached target GNOME Accessibility settings. mai 23 13:53:14 endless systemd[3453]: Started GNOME Sound sample caching handling. mai 23 13:53:14 endless systemd[3453]: Reached target GNOME Sound sample caching handling. mai 23 13:53:14 endless systemd[3453]: Started GNOME WWan management. mai 23 13:53:14 endless systemd[3453]: Reached target GNOME WWan management. mai 23 13:53:14 endless systemd[3453]: Started GNOME USB protection handling. mai 23 13:53:14 endless systemd[3453]: Reached target GNOME USB protection handling. mai 23 13:53:14 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.597' (uid=1001 pid=8444 comm="/usr/libexec/gsd-datetime " label="unconfined") mai 23 13:53:14 endless systemd[1]: Starting Time & Date Service... mai 23 13:53:14 endless systemd[3453]: Started GNOME Media keys handling. mai 23 13:53:14 endless systemd[3453]: Reached target GNOME Media keys handling. mai 23 13:53:14 endless gsd-sharing[8456]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded. mai 23 13:53:14 endless gsd-sharing[8456]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded. mai 23 13:53:14 endless dbus-daemon[1538]: [system] Successfully activated service 'com.endlessm.MogwaiSchedule1' mai 23 13:53:14 endless systemd[1]: Started Download Scheduling Daemon. mai 23 13:53:14 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.hostname1' mai 23 13:53:14 endless systemd[1]: Started Hostname Service. mai 23 13:53:14 endless systemd[3453]: Started GNOME RFKill handling. mai 23 13:53:14 endless systemd[3453]: Reached target GNOME RFKill handling. mai 23 13:53:14 endless kernel: rfkill: input handler disabled mai 23 13:53:14 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.timedate1' mai 23 13:53:14 endless systemd[1]: Started Time & Date Service. mai 23 13:53:14 endless systemd[3453]: Started GNOME Smartcard handling. mai 23 13:53:14 endless systemd[3453]: Reached target GNOME Smartcard handling. mai 23 13:53:14 endless systemd[3453]: Started GNOME Wacom handling. mai 23 13:53:14 endless systemd[3453]: Reached target GNOME Wacom handling. mai 23 13:53:14 endless systemd[3453]: Started GNOME Keyboard handling. mai 23 13:53:14 endless systemd[3453]: Reached target GNOME Keyboard handling. mai 23 13:53:14 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.639' (uid=1001 pid=8450 comm="/usr/libexec/gsd-keyboard " label="unconfined") mai 23 13:53:14 endless systemd[1]: Starting Locale Service... mai 23 13:53:14 endless systemd[3453]: Started GNOME Power management handling. mai 23 13:53:14 endless systemd[3453]: Reached target GNOME Power management handling. mai 23 13:53:14 endless systemd[3453]: Started GNOME Color management. mai 23 13:53:14 endless systemd[3453]: Reached target GNOME Color management. mai 23 13:53:14 endless kernel: traps: vmtoolsd[8547] general protection fault ip:7f9b19ddf0dc sp:7ffc748fe438 error:0 in libvmtools.so.0.0.0[7f9b19dd3000+45000] mai 23 13:53:14 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.locale1' mai 23 13:53:14 endless systemd[1]: Started Locale Service. mai 23 13:53:14 endless systemd[3453]: Started GNOME Date & Time handling. mai 23 13:53:14 endless systemd[3453]: Reached target GNOME Date & Time handling. mai 23 13:53:15 endless gsd-media-keys[8451]: Failed to grab accelerator for keybinding settings:hibernate mai 23 13:53:15 endless gsd-media-keys[8451]: Failed to grab accelerator for keybinding settings:playback-random mai 23 13:53:15 endless gsd-media-keys[8451]: Failed to grab accelerator for keybinding settings:playback-repeat mai 23 13:53:15 endless gsd-media-keys[8451]: Failed to grab accelerator for keybinding settings:rfkill mai 23 13:53:15 endless colord[2288]: failed to get session [pid 8442]: Não há dados disponíveis mai 23 13:53:15 endless upowerd[1729]: up_kbd_backlight_brightness_read: assertion 'fd >= 0' failed mai 23 13:53:15 endless gsd-power[8452]: Failed to get brightness: GDBus.Error:org.freedesktop.UPower.GeneralError: error reading brightness mai 23 13:53:15 endless systemd[3453]: Started GNOME XSettings. mai 23 13:53:15 endless systemd[3453]: Reached target GNOME XSettings. mai 23 13:53:15 endless systemd[3453]: Reached target GNOME Session. mai 23 13:53:15 endless systemd[3453]: Reached target GNOME X11 Session (session: gnome). mai 23 13:53:15 endless systemd[3453]: Condition check resulted in GNOME Initial Setup being skipped. mai 23 13:53:15 endless systemd[3453]: Condition check resulted in GNOME Welcome Tour being skipped. mai 23 13:53:16 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.gnome.evolution.dataserver.Calendar8' mai 23 13:53:16 endless systemd[3453]: Started Evolution calendar service. mai 23 13:53:16 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.gnome.evolution.dataserver.AddressBook10' unit='evolution-addressbook-factory.service' requested by ':1.93' (uid=1001 pid=8438 comm="/usr/libexec/evolution-calendar-factory " label="unconfined") mai 23 13:53:16 endless systemd[3453]: Starting Evolution address book service... mai 23 13:53:16 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook10' mai 23 13:53:16 endless systemd[3453]: Started Evolution address book service. mai 23 13:53:19 endless gnome-shell[8098]: GNOME Shell started at Sat May 23 2020 13:53:11 GMT-0300 (-03) mai 23 13:53:19 endless gnome-shell[8098]: Registering session with GDM mai 23 13:53:19 endless systemd[3453]: tracker-miner-fs.service: State 'stop-sigterm' timed out. Killing. mai 23 13:53:19 endless systemd[3453]: tracker-miner-fs.service: Killing process 5855 (tracker-miner-f) with signal SIGKILL. mai 23 13:53:19 endless systemd[3453]: tracker-miner-fs.service: Killing process 6045 (pool-tracker-mi) with signal SIGKILL. mai 23 13:53:19 endless systemd[3453]: tracker-miner-fs.service: Main process exited, code=killed, status=9/KILL mai 23 13:53:19 endless systemd[3453]: tracker-miner-fs.service: Failed with result 'timeout'. mai 23 13:53:19 endless systemd[3453]: Starting Tracker file system data miner... mai 23 13:53:19 endless tracker-miner-f[8832]: Set scheduler policy to SCHED_IDLE mai 23 13:53:19 endless tracker-miner-f[8832]: Setting priority nice level to 19 mai 23 13:53:19 endless tracker-miner-f[8832]: Path '/sysroot/home/daniel/Downloads' being removed from recursive directories list, as it also exists in single directories list mai 23 13:53:19 endless systemd[3453]: Started Tracker file system data miner. mai 23 13:53:19 endless systemd[3453]: Reached target Current graphical user session. mai 23 13:53:20 endless gnome-software[8529]: plugin appstream took 3,7 seconds to do setup mai 23 13:53:20 endless gnome-software[8529]: enabled plugins: desktop-categories, dpkg, eos-updater, external-appstream, os-release, provenance, appstream, provenance-license, desktop-menu-path, flatpak, hardcoded-blacklist, rewrite-resource, eos, eos-blacklist, icons, malcontent, odrs, key-colors, key-colors-metadata mai 23 13:53:20 endless gnome-software[8529]: disabled plugins: dummy, repos, generic-updates mai 23 13:53:20 endless mogwai-schedule[8464]: Holding service for D-Bus peer ‘:1.644’ because: monitoring allow-downloads property mai 23 13:53:32 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating service name='com.endlessm.Speedwagon' requested by ':1.50' (uid=1001 pid=8098 comm="/usr/bin/gnome-shell " label="unconfined") mai 23 13:53:32 endless eos-link-user-endlessos.desktop[8850]: This tool has been deprecated, use 'gio open' instead. mai 23 13:53:32 endless eos-link-user-endlessos.desktop[8850]: See 'gio help open' for more info. mai 23 13:53:33 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'com.endlessm.Speedwagon' mai 23 13:53:33 endless gnome-shell[8098]: Could not create transient scope for PID 8850: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 8850 does not exist. mai 23 13:53:34 endless eos-link-user-endlessos.desktop[8865]: INFO:root:Found flatpak launcher for Google Chrome: '/var/lib/flatpak/app/com.google.Chrome/x86_64/eos3/b64e9ec5fb516c5d582cd828b5280e806be0814d89d80db7a2dedbc4a60ff4e5/files/bin/eos-google-chrome-app' mai 23 13:53:34 endless eos-link-user-endlessos.desktop[8865]: INFO:root:Flatpak launcher for Chrome found. Launching... mai 23 13:53:34 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[8865]: Found flatpak launcher for Google Chrome: '/var/lib/flatpak/app/com.google.Chrome/x86_64/eos3/b64e9ec5fb516c5d582cd828b5280e806be0814d89d80db7a2dedbc4a60ff4e5/files/bin/eos-google-chrome-app' mai 23 13:53:34 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[8865]: Flatpak launcher for Chrome found. Launching... mai 23 13:53:34 endless eos-link-user-endlessos.desktop[8865]: INFO:root:Running Google Chrome launcher with PID 8878 mai 23 13:53:34 endless /usr/share/eos-google-chrome-helper/eos-google-chrome.py[8865]: Running Google Chrome launcher with PID 8878 mai 23 13:53:34 endless eos-link-user-endlessos.desktop[8878]: WARNING:root:Could not find Flatpak ref com.google.Chrome in /sysroot/home/daniel/.local/share/flatpak: GLib.Error('App com.google.Chrome not installed', 'flatpak-error-quark', 1) mai 23 13:53:35 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.freedesktop.Flatpak' unit='flatpak-session-helper.service' requested by ':1.118' (uid=1001 pid=8881 comm="flatpak run --command=bash com.google.Chrome -c re" label="unconfined") mai 23 13:53:35 endless systemd[3453]: Starting flatpak session helper... mai 23 13:53:35 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.freedesktop.Flatpak' mai 23 13:53:35 endless systemd[3453]: Started flatpak session helper. mai 23 13:53:35 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.freedesktop.portal.Documents' unit='xdg-document-portal.service' requested by ':1.118' (uid=1001 pid=8881 comm="flatpak run --command=bash com.google.Chrome -c re" label="unconfined") mai 23 13:53:35 endless systemd[3453]: Starting flatpak document portal service... mai 23 13:53:35 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.freedesktop.portal.Documents' mai 23 13:53:35 endless systemd[3453]: Started flatpak document portal service. mai 23 13:53:35 endless systemd[3453]: Started flatpak-com.google.Chrome-8881.scope. mai 23 13:53:38 endless dbus-daemon[1538]: [system] Failed to activate service 'com.endlessm.RecordBootSuccess': timed out (service_start_timeout=25000ms) mai 23 13:53:42 endless eos-link-user-endlessos.desktop[8890]: [8953:8953:0523/135342.899715:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. mai 23 13:53:44 endless systemd[1]: systemd-hostnamed.service: Succeeded. mai 23 13:53:44 endless systemd[1]: systemd-timedated.service: Succeeded. mai 23 13:53:44 endless gnome-keyring-daemon[7859]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk mai 23 13:53:45 endless gnome-keyring-daemon[7859]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered mai 23 13:53:50 endless systemd[1]: systemd-localed.service: Succeeded. mai 23 13:53:54 endless eos-link-user-endlessos.desktop[8890]: [8973:8975:0523/135354.890748:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018 mai 23 13:53:57 endless gnome-keyring-daemon[7859]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered mai 23 13:54:31 endless kernel: geoclue[6233]: segfault at c8 ip 00007f2e4bb01c50 sp 00007ffd6dfbb4d0 error 4 in libgobject-2.0.so.0.6400.1[7f2e4bad5000+34000] mai 23 13:54:31 endless kernel: Code: 1f 84 00 00 00 00 00 0f 1f 00 41 54 55 53 48 89 fb 48 83 ec 20 48 85 ff 0f 84 a4 00 00 00 48 8b 07 48 85 c0 0f 84 a8 00 00 00 <48> 8b 28 48 89 ea 48 81 fd fc 03 00 00 0f 86 ed 00 00 00 48 83 e2 mai 23 13:54:31 endless systemd[1]: geoclue.service: Main process exited, code=dumped, status=11/SEGV mai 23 13:54:31 endless systemd[1]: geoclue.service: Failed with result 'core-dump'. mai 23 13:54:46 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.644' (uid=1001 pid=8529 comm="/usr/bin/gnome-software --gapplication-service " label="unconfined") mai 23 13:54:46 endless systemd[1]: Starting Locale Service... mai 23 13:54:46 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.locale1' mai 23 13:54:46 endless systemd[1]: Started Locale Service. mai 23 13:55:28 endless systemd[1]: systemd-localed.service: Succeeded. mai 23 13:56:47 endless systemd[3453]: Started Application launched by gnome-shell. mai 23 13:56:59 endless ntpd[4611]: 162.159.200.123 local addr 192.168.0.34 -> mai 23 13:57:19 endless systemd[3453]: gnome-launched-org.gnome.Nautilus.desktop-9761.scope: Succeeded. mai 23 13:57:40 endless kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 mai 23 13:57:42 endless systemd[3453]: Started Application launched by gnome-shell. mai 23 13:57:44 endless gdm-Xorg-:0[7222]: (II) modeset(0): EDID vendor "CMN", prod id 5596 mai 23 13:57:44 endless gdm-Xorg-:0[7222]: (II) modeset(0): Printing DDC gathered Modelines: mai 23 13:57:44 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1366x768"x0.0 76.42 1366 1434 1479 1592 768 772 779 800 -hsync -vsync (48.0 kHz eP) mai 23 13:57:48 endless dbus-daemon[1538]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.675' (uid=1001 pid=9811 comm="gnome-control-center " label="unconfined") mai 23 13:57:48 endless systemd[1]: Starting Hostname Service... mai 23 13:57:48 endless dbus-daemon[1538]: [system] Successfully activated service 'org.freedesktop.hostname1' mai 23 13:57:48 endless systemd[1]: Started Hostname Service. mai 23 13:58:18 endless systemd[1]: systemd-hostnamed.service: Succeeded. mai 23 13:59:14 endless ntpd[4611]: 209.58.185.100 local addr 192.168.0.34 -> mai 23 14:01:42 endless systemd[1]: Starting Cleanup of Temporary Directories... mai 23 14:01:43 endless systemd-tmpfiles[9998]: /usr/lib/tmpfiles.d/speech-dispatcher.conf:1: Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher → /run/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. mai 23 14:01:43 endless systemd-tmpfiles[9998]: /usr/lib/tmpfiles.d/speech-dispatcher.conf:2: Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → /run/speech-dispatcher/.cache; please update the tmpfiles.d/ drop-in file accordingly. mai 23 14:01:43 endless systemd-tmpfiles[9998]: /usr/lib/tmpfiles.d/speech-dispatcher.conf:3: Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher → /run/speech-dispatcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. mai 23 14:01:43 endless systemd-tmpfiles[9998]: /usr/lib/tmpfiles.d/speech-dispatcher.conf:4: Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache/speech-dispatcher → /run/speech-dispatcher/.cache/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. mai 23 14:01:43 endless systemd-tmpfiles[9998]: /usr/lib/tmpfiles.d/speech-dispatcher.conf:5: Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/log → /run/speech-dispatcher/log; please update the tmpfiles.d/ drop-in file accordingly. mai 23 14:01:46 endless systemd[1]: systemd-tmpfiles-clean.service: Succeeded. mai 23 14:01:46 endless systemd[1]: Started Cleanup of Temporary Directories. mai 23 14:02:09 endless tracker-store[8548]: Source ID 3 was not found when attempting to remove it mai 23 14:02:09 endless systemd[3453]: tracker-store.service: Succeeded. mai 23 14:02:09 endless tracker-store[8548]: OK mai 23 14:02:09 endless tracker-miner-f[8832]: (Sparql buffer) Error in array-update: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not execute sparql: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not remove files in volumes: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not remove files in volumes: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:09 endless tracker-miner-f[8832]: Could not initialize currently active mount points: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mai 23 14:02:10 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.107' (uid=1001 pid=8832 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 14:02:10 endless systemd[3453]: Starting Tracker metadata database store and lookup manager... mai 23 14:02:10 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.freedesktop.Tracker1' mai 23 14:02:10 endless systemd[3453]: Started Tracker metadata database store and lookup manager. mai 23 14:02:42 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.107' (uid=1001 pid=8832 comm="/usr/libexec/tracker-miner-fs " label="unconfined") mai 23 14:02:42 endless systemd[3453]: Starting Tracker metadata extractor... mai 23 14:02:42 endless tracker-extract[10108]: Set scheduler policy to SCHED_IDLE mai 23 14:02:42 endless tracker-extract[10108]: Setting priority nice level to 19 mai 23 14:02:42 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract' mai 23 14:02:42 endless systemd[3453]: Started Tracker metadata extractor. mai 23 14:03:12 endless systemd[3453]: tracker-extract.service: Succeeded. mai 23 14:03:12 endless ntpd[4611]: 85.91.1.180 local addr 192.168.0.34 -> mai 23 14:03:32 endless tracker-store[10073]: OK mai 23 14:03:32 endless systemd[3453]: tracker-store.service: Succeeded. mai 23 14:03:45 endless ntpd[4611]: 200.189.40.8 local addr 192.168.0.34 -> mai 23 14:04:52 endless ntpd[4611]: 143.107.229.210 local addr 192.168.0.34 -> mai 23 14:04:54 endless ntpd[4611]: 94.198.159.10 local addr 192.168.0.34 -> mai 23 14:09:32 endless wpa_supplicant[3673]: wlp2s0: WPA: Group rekeying completed with 80:d0:4a:90:f1:d9 [GTK=CCMP] mai 23 14:12:42 endless systemd[1]: Started Endless OS Automatic Updater. mai 23 14:12:43 endless systemd[1]: eos-autoupdater.service: Succeeded. mai 23 14:16:14 endless eos-metrics-eve[1542]: Uploaded 4 events from persistent cache, 17 events from buffer to https://production.metrics.endlessm.com/2/. mai 23 14:16:29 endless gnome-shell[8098]: (../clutter/clutter/clutter-actor-meta.c:109):clutter_actor_meta_real_set_enabled: runtime check failed: (!meta->priv->actor || !CLUTTER_ACTOR_IN_PAINT (meta->priv->actor)) mai 23 14:16:29 endless gnome-shell[8098]: (../clutter/clutter/clutter-actor-meta.c:109):clutter_actor_meta_real_set_enabled: runtime check failed: (!meta->priv->actor || !CLUTTER_ACTOR_IN_PAINT (meta->priv->actor)) mai 23 14:16:33 endless systemd[3453]: Started Application launched by gnome-shell. mai 23 14:16:33 endless org.gnome.Terminal.desktop[10731]: # _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ mai 23 14:16:33 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.140' (uid=1001 pid=10731 comm="gnome-terminal " label="unconfined") mai 23 14:16:33 endless systemd[3453]: Created slice apps.slice. mai 23 14:16:33 endless systemd[3453]: Created slice apps-org.gnome.Terminal.slice. mai 23 14:16:33 endless systemd[3453]: Starting GNOME Terminal Server... mai 23 14:16:33 endless dbus-daemon[7175]: [session uid=1001 pid=7175] Successfully activated service 'org.gnome.Terminal' mai 23 14:16:33 endless systemd[3453]: Started GNOME Terminal Server. mai 23 14:16:33 endless org.gnome.Terminal.desktop[10731]: # _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ mai 23 14:16:33 endless org.gnome.Terminal.desktop[10731]: # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) mai 23 14:16:33 endless org.gnome.Terminal.desktop[10731]: # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) mai 23 14:16:33 endless org.gnome.Terminal.desktop[10731]: # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) mai 23 14:16:33 endless systemd[3453]: Started VTE child process 10746 launched by gnome-terminal-server process 10736. mai 23 14:16:33 endless systemd[3453]: gnome-launched-org.gnome.Terminal.desktop-10731.scope: Succeeded. mai 23 14:17:04 endless gdm-Xorg-:0[7222]: (II) modeset(0): EDID vendor "CMN", prod id 5596 mai 23 14:17:04 endless gdm-Xorg-:0[7222]: (II) modeset(0): Printing DDC gathered Modelines: mai 23 14:17:04 endless gdm-Xorg-:0[7222]: (II) modeset(0): Modeline "1366x768"x0.0 76.42 1366 1434 1479 1592 768 772 779 800 -hsync -vsync (48.0 kHz eP) mai 23 14:17:04 endless polkitd[1720]: Registered Authentication Agent for unix-process:10829:187590 (system bus name :1.701 [flatpak remote-list --show-details], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 14:17:04 endless polkitd[1720]: Unregistered Authentication Agent for unix-process:10829:187590 (system bus name :1.701, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 14:17:04 endless polkitd[1720]: Registered Authentication Agent for unix-process:10834:187593 (system bus name :1.710 [flatpak list --runtime --show-details], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 14:17:05 endless polkitd[1720]: Unregistered Authentication Agent for unix-process:10834:187593 (system bus name :1.710, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 14:17:05 endless polkitd[1720]: Registered Authentication Agent for unix-process:10838:187611 (system bus name :1.719 [flatpak list --app --show-details], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 14:17:05 endless polkitd[1720]: Unregistered Authentication Agent for unix-process:10838:187611 (system bus name :1.719, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 14:17:05 endless polkitd[1720]: Registered Authentication Agent for unix-process:10842:187646 (system bus name :1.728 [flatpak history --columns=all], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) mai 23 14:17:06 endless polkitd[1720]: Unregistered Authentication Agent for unix-process:10842:187646 (system bus name :1.728, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_BR.UTF-8) ============ = Coredump = ============ systemd-coredump not enabled