五 20 16:04:59 ubuntu-Precision-5570 kernel: #9 #10 #11 #12 #13 #14 #15 五 20 16:04:59 ubuntu-Precision-5570 kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance' 五 20 16:04:59 ubuntu-Precision-5570 kernel: pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid 五 20 16:04:59 ubuntu-Precision-5570 kernel: pci 0000:00:07.1: DPC: RP PIO log size 0 is invalid 五 20 16:04:59 ubuntu-Precision-5570 kernel: pnp 00:05: disabling [mem 0xc0000000-0xcfffffff] because it overlaps 0000:00:02.0 BAR 9 [mem 0x00000000-0xdfffffff 64bit pref] 五 20 16:04:59 ubuntu-Precision-5570 kernel: perf uncore: Cannot find matched IMC device. 五 20 16:04:59 ubuntu-Precision-5570 kernel: perf uncore: Cannot find matched IMC device. 五 20 16:04:59 ubuntu-Precision-5570 kernel: hpet_acpi_add: no address or irqs in _CRS 五 20 16:04:59 ubuntu-Precision-5570 kernel: i8042: Warning: Keylock active 五 20 16:04:59 ubuntu-Precision-5570 kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log. 五 20 16:04:59 ubuntu-Precision-5570 kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard 五 20 16:04:59 ubuntu-Precision-5570 kernel: platform eisa.0: Cannot allocate resource for EISA slot 1 五 20 16:04:59 ubuntu-Precision-5570 kernel: platform eisa.0: Cannot allocate resource for EISA slot 2 五 20 16:04:59 ubuntu-Precision-5570 kernel: platform eisa.0: Cannot allocate resource for EISA slot 3 五 20 16:04:59 ubuntu-Precision-5570 kernel: platform eisa.0: Cannot allocate resource for EISA slot 4 五 20 16:04:59 ubuntu-Precision-5570 kernel: platform eisa.0: Cannot allocate resource for EISA slot 5 五 20 16:04:59 ubuntu-Precision-5570 kernel: platform eisa.0: Cannot allocate resource for EISA slot 6 五 20 16:04:59 ubuntu-Precision-5570 kernel: platform eisa.0: Cannot allocate resource for EISA slot 7 五 20 16:04:59 ubuntu-Precision-5570 kernel: platform eisa.0: Cannot allocate resource for EISA slot 8 五 20 16:04:59 ubuntu-Precision-5570 kernel: acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00) 五 20 16:04:59 ubuntu-Precision-5570 kernel: wmi_bus wmi_bus-PNP0C14:02: WQBC data block query control method not found 五 20 16:04:59 ubuntu-Precision-5570 kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00) 五 20 16:04:59 ubuntu-Precision-5570 kernel: pci 10000:e0:06.0: Primary bus is hard wired to 0 五 20 16:04:59 ubuntu-Precision-5570 kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00) 五 20 16:04:59 ubuntu-Precision-5570 kernel: usb: port power management may be unreliable 五 20 16:04:59 ubuntu-Precision-5570 kernel: pci 10000:e0:06.2: Primary bus is hard wired to 0 五 20 16:04:59 ubuntu-Precision-5570 kernel: acpi PNP0C14:04: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00) 五 20 16:04:59 ubuntu-Precision-5570 kernel: acpi PNP0C14:05: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00) 五 20 16:04:59 ubuntu-Precision-5570 kernel: acpi PNP0C14:06: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00) 五 20 16:04:59 ubuntu-Precision-5570 kernel: acpi PNP0C14:07: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00) 五 20 16:04:59 ubuntu-Precision-5570 kernel: acpi PNP0C14:08: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00) 五 20 16:04:59 ubuntu-Precision-5570 kernel: pci 10000:e0:06.0: Primary bus is hard wired to 0 五 20 16:04:59 ubuntu-Precision-5570 kernel: pci 10000:e0:06.2: Primary bus is hard wired to 0 五 20 16:04:59 ubuntu-Precision-5570 kernel: pcieport 10000:e0:06.0: can't derive routing for PCI INT D 五 20 16:04:59 ubuntu-Precision-5570 kernel: pcieport 10000:e0:06.0: PCI INT D: no GSI 五 20 16:04:59 ubuntu-Precision-5570 kernel: pcieport 10000:e0:06.2: can't derive routing for PCI INT B 五 20 16:04:59 ubuntu-Precision-5570 kernel: pcieport 10000:e0:06.2: PCI INT B: no GSI 五 20 16:04:59 ubuntu-Precision-5570 kernel: pcieport 10000:e0:06.0: can't derive routing for PCI INT A 五 20 16:04:59 ubuntu-Precision-5570 kernel: nvme 10000:e1:00.0: PCI INT A: not connected 五 20 16:04:59 ubuntu-Precision-5570 kernel: pcieport 10000:e0:06.2: can't derive routing for PCI INT A 五 20 16:04:59 ubuntu-Precision-5570 kernel: nvme 10000:e2:00.0: PCI INT A: not connected 五 20 16:04:59 ubuntu-Precision-5570 systemd-udevd[434]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. 五 20 16:04:59 ubuntu-Precision-5570 systemd-udevd[487]: nvme1n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme1n1' failed with exit code 1. 五 20 16:04:59 ubuntu-Precision-5570 systemd-udevd[477]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. 五 20 16:04:59 ubuntu-Precision-5570 systemd-udevd[434]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. 五 20 16:04:59 ubuntu-Precision-5570 kernel: resource sanity check: requesting [mem 0xfedc0000-0xfedcffff], which spans more than pnp 00:05 [mem 0xfedc0000-0xfedc7fff] 五 20 16:04:59 ubuntu-Precision-5570 kernel: caller igen6_probe+0x16e/0x550 [igen6_edac] mapping multiple BARs 五 20 16:04:59 ubuntu-Precision-5570 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-66.ucode failed with error -2 五 20 16:04:59 ubuntu-Precision-5570 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-65.ucode failed with error -2 五 20 16:04:59 ubuntu-Precision-5570 kernel: iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver 五 20 16:04:59 ubuntu-Precision-5570 systemd-udevd[476]: video4linux: Process '/usr/lib/snapd/snap-device-helper add snap_firefox_firefox /class/video4linux 0:0' failed with exit code 1. 五 20 16:04:59 ubuntu-Precision-5570 kernel: dell_smm_hwmon: unable to get SMM Dell signature 五 20 16:04:59 ubuntu-Precision-5570 kernel: thermal thermal_zone11: failed to read out thermal zone (-61) 五 20 16:04:59 ubuntu-Precision-5570 avahi-daemon[760]: chroot.c: open() failed: No such file or directory 五 20 16:04:59 ubuntu-Precision-5570 avahi-daemon[721]: Failed to open /etc/resolv.conf: Invalid argument 五 20 16:04:59 ubuntu-Precision-5570 udisksd[748]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory 五 20 16:04:59 ubuntu-Precision-5570 udisksd[748]: Failed to load the 'mdraid' libblockdev plugin 五 20 16:04:59 ubuntu-Precision-5570 boltd[778]: [47ef8780-a036-domain0 ] udev: failed to determine if uid is stable: unknown NHI PCI id '0x463e' 五 20 16:05:00 ubuntu-Precision-5570 thermald[747]: Unsupported condition 4 (Motion) 五 20 16:05:00 ubuntu-Precision-5570 thermald[747]: Unsupported condition 9 (Aggregate_power_percentage) 五 20 16:05:00 ubuntu-Precision-5570 thermald[747]: Unsupported condition 9 (Aggregate_power_percentage) 五 20 16:05:00 ubuntu-Precision-5570 thermald[747]: Unsupported condition 9 (Aggregate_power_percentage) 五 20 16:05:00 ubuntu-Precision-5570 thermald[747]: Unsupported condition 9 (Aggregate_power_percentage) 五 20 16:05:00 ubuntu-Precision-5570 thermald[747]: Unsupported conditions are present 五 20 16:05:00 ubuntu-Precision-5570 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.ETMD], AE_NOT_FOUND (20210730/psargs-330) 五 20 16:05:00 ubuntu-Precision-5570 kernel: 五 20 16:05:00 ubuntu-Precision-5570 kernel: No Local Variables are initialized for Method [_OSC] 五 20 16:05:00 ubuntu-Precision-5570 kernel: 五 20 16:05:00 ubuntu-Precision-5570 kernel: Initialized Arguments for Method [_OSC]: (4 arguments defined for method invocation) 五 20 16:05:00 ubuntu-Precision-5570 kernel: Arg0: 000000005f65267f Buffer(16) 5D A8 3B B2 B7 C8 42 35 五 20 16:05:00 ubuntu-Precision-5570 kernel: Arg1: 0000000053dc616d Integer 0000000000000001 五 20 16:05:00 ubuntu-Precision-5570 kernel: Arg2: 000000005890af0d Integer 0000000000000002 五 20 16:05:00 ubuntu-Precision-5570 kernel: Arg3: 000000007d0aa799 Buffer(8) 00 00 00 00 05 00 00 00 五 20 16:05:00 ubuntu-Precision-5570 kernel: 五 20 16:05:00 ubuntu-Precision-5570 kernel: ACPI Error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) 五 20 16:05:00 ubuntu-Precision-5570 upowerd[984]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:001 五 20 16:05:01 ubuntu-Precision-5570 gnome-session-binary[1184]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed 五 20 16:05:01 ubuntu-Precision-5570 gnome-session-binary[1184]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed 五 20 16:05:01 ubuntu-Precision-5570 systemd[1081]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:05:01 ubuntu-Precision-5570 tracker-miner-f[1242]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location. 五 20 16:05:01 ubuntu-Precision-5570 tracker-miner-f[1242]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location. 五 20 16:05:01 ubuntu-Precision-5570 tracker-miner-f[1242]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location. 五 20 16:05:01 ubuntu-Precision-5570 tracker-miner-f[1242]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location. 五 20 16:05:01 ubuntu-Precision-5570 tracker-miner-f[1242]: Unable to get XDG user directory path for special directory &DOWNLOAD. Ignoring this location. 五 20 16:05:01 ubuntu-Precision-5570 tracker-miner-f[1242]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location. 五 20 16:05:01 ubuntu-Precision-5570 tracker-miner-f[1242]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location. 五 20 16:05:01 ubuntu-Precision-5570 tracker-miner-f[1242]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location. 五 20 16:05:01 ubuntu-Precision-5570 tracker-miner-f[1242]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location. 五 20 16:05:01 ubuntu-Precision-5570 kernel: kauditd_printk_skb: 64 callbacks suppressed 五 20 16:05:01 ubuntu-Precision-5570 systemd[1081]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:05:01 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[1181]: dbus-daemon[1181]: [session uid=127 pid=1181] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=127 pid=1228 comm="/usr/bin/gnome-shell " label="unconfined") 五 20 16:05:01 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[1181]: dbus-daemon[1181]: [session uid=127 pid=1181] Successfully activated service 'org.a11y.Bus' 五 20 16:05:01 ubuntu-Precision-5570 org.gnome.Shell.desktop[1350]: (WW) Option "-listen" for file descriptors is deprecated 五 20 16:05:01 ubuntu-Precision-5570 org.gnome.Shell.desktop[1350]: Please use "-listenfd" instead. 五 20 16:05:01 ubuntu-Precision-5570 org.gnome.Shell.desktop[1350]: (WW) Option "-listen" for file descriptors is deprecated 五 20 16:05:01 ubuntu-Precision-5570 org.gnome.Shell.desktop[1350]: Please use "-listenfd" instead. 五 20 16:05:01 ubuntu-Precision-5570 systemd[1081]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:05:01 ubuntu-Precision-5570 upowerd[984]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:002 五 20 16:05:02 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[1181]: dbus-daemon[1181]: [session uid=127 pid=1181] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=127 pid=1228 comm="/usr/bin/gnome-shell " label="unconfined") 五 20 16:05:02 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[1181]: dbus-daemon[1181]: [session uid=127 pid=1181] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' 五 20 16:05:02 ubuntu-Precision-5570 systemd[1081]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:05:02 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[1181]: dbus-daemon[1181]: [session uid=127 pid=1181] Activating service name='org.gnome.Shell.Notifications' requested by ':1.3' (uid=127 pid=1228 comm="/usr/bin/gnome-shell " label="unconfined") 五 20 16:05:02 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[1337]: dbus-daemon[1337]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=127 pid=1228 comm="/usr/bin/gnome-shell " label="unconfined") 五 20 16:05:02 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[1337]: dbus-daemon[1337]: Successfully activated service 'org.a11y.atspi.Registry' 五 20 16:05:02 ubuntu-Precision-5570 org.gnome.Shell.desktop[1228]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/102b5640c982bb0ef6165303390148717800000011840000.ms”: No such file or directory 五 20 16:05:02 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[1181]: dbus-daemon[1181]: [session uid=127 pid=1181] Successfully activated service 'org.gnome.Shell.Notifications' 五 20 16:05:02 ubuntu-Precision-5570 systemd[1081]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:05:02 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[1181]: dbus-daemon[1181]: [session uid=127 pid=1181] Activating service name='org.freedesktop.systemd1' requested by ':1.9' (uid=127 pid=1490 comm="/usr/libexec/gsd-sharing " label="unconfined") 五 20 16:05:02 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[1181]: dbus-daemon[1181]: [session uid=127 pid=1181] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 五 20 16:05:02 ubuntu-Precision-5570 gsd-sharing[1490]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 五 20 16:05:02 ubuntu-Precision-5570 gsd-sharing[1490]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 五 20 16:05:02 ubuntu-Precision-5570 gnome-shell[1228]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed 五 20 16:05:02 ubuntu-Precision-5570 gnome-shell[1228]: cr_declaration_parse_list_from_buf: assertion 'parser' failed 五 20 16:05:02 ubuntu-Precision-5570 gnome-shell[1228]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed 五 20 16:05:02 ubuntu-Precision-5570 gnome-shell[1228]: cr_declaration_parse_list_from_buf: assertion 'parser' failed 五 20 16:05:02 ubuntu-Precision-5570 xbrlapi.desktop[1633]: openConnection: connect: No such file or directory 五 20 16:05:02 ubuntu-Precision-5570 xbrlapi.desktop[1633]: cannot connect to braille devices daemon brltty at :0 五 20 16:05:02 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[1181]: dbus-daemon[1181]: [session uid=127 pid=1181] Activating service name='org.gnome.ScreenSaver' requested by ':1.23' (uid=127 pid=1545 comm="/usr/libexec/gsd-power " label="unconfined") 五 20 16:05:02 ubuntu-Precision-5570 gsd-media-keys[1519]: Failed to grab accelerator for keybinding settings:hibernate 五 20 16:05:02 ubuntu-Precision-5570 gsd-media-keys[1519]: Failed to grab accelerator for keybinding settings:playback-repeat 五 20 16:05:02 ubuntu-Precision-5570 gnome-shell[1228]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed 五 20 16:05:02 ubuntu-Precision-5570 gnome-shell[1228]: cr_declaration_parse_list_from_buf: assertion 'parser' failed 五 20 16:05:02 ubuntu-Precision-5570 gnome-shell[1228]: ATK Bridge is disabled but a11y has already been enabled. 五 20 16:05:02 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[1181]: dbus-daemon[1181]: [session uid=127 pid=1181] Successfully activated service 'org.gnome.ScreenSaver' 五 20 16:05:02 ubuntu-Precision-5570 org.gnome.Shell.desktop[1663]: The XKEYBOARD keymap compiler (xkbcomp) reports: 五 20 16:05:02 ubuntu-Precision-5570 org.gnome.Shell.desktop[1663]: > Warning: Unsupported maximum keycode 708, clipping. 五 20 16:05:02 ubuntu-Precision-5570 org.gnome.Shell.desktop[1663]: > X11 cannot support keycodes above 255. 五 20 16:05:02 ubuntu-Precision-5570 org.gnome.Shell.desktop[1663]: Errors from xkbcomp are not fatal to the X server 五 20 16:05:02 ubuntu-Precision-5570 gnome-shell[1228]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found 五 20 16:05:02 ubuntu-Precision-5570 gnome-shell[1228]: Page flip discarded: CRTC property (GAMMA_LUT) not found 五 20 16:05:02 ubuntu-Precision-5570 systemd[1081]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Start request repeated too quickly. 五 20 16:05:02 ubuntu-Precision-5570 systemd[1081]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:05:02 ubuntu-Precision-5570 systemd[1081]: Failed to start Service for snap application snapd-desktop-integration.snapd-desktop-integration. 五 20 16:05:03 ubuntu-Precision-5570 upowerd[984]: treated changed event as add on /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-USBC000:003 五 20 16:05:04 ubuntu-Precision-5570 gdm-fingerprint][1716]: gkr-pam: no password is available for user 五 20 16:05:04 ubuntu-Precision-5570 thermald[747]: Manufacturer didn't provide adequate support to run in 五 20 16:05:04 ubuntu-Precision-5570 thermald[747]: optimized configuration on Linux with open source 五 20 16:05:04 ubuntu-Precision-5570 thermald[747]: You may want to disable thermald on this system if you see issue 五 20 16:05:04 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[1181]: dbus-daemon[1181]: [session uid=127 pid=1181] Activating service name='org.freedesktop.systemd1' requested by ':1.9' (uid=127 pid=1490 comm="/usr/libexec/gsd-sharing " label="unconfined") 五 20 16:05:04 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[1181]: dbus-daemon[1181]: [session uid=127 pid=1181] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 五 20 16:05:04 ubuntu-Precision-5570 gsd-sharing[1490]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 五 20 16:05:04 ubuntu-Precision-5570 gsd-sharing[1490]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 五 20 16:05:04 ubuntu-Precision-5570 systemd[1]: kerneloops.service: Found left-over process 1792 (kerneloops) in control group while starting unit. Ignoring. 五 20 16:05:04 ubuntu-Precision-5570 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. 五 20 16:05:04 ubuntu-Precision-5570 gdm-password][1715]: gkr-pam: unable to locate daemon control file 五 20 16:05:05 ubuntu-Precision-5570 systemd[1823]: app-gnome-gnome\x2dkeyring\x2dpkcs11-2071.scope: Failed to add PIDs to scope's control group: No such process 五 20 16:05:05 ubuntu-Precision-5570 systemd[1823]: app-gnome-gnome\x2dkeyring\x2dpkcs11-2071.scope: Failed with result 'resources'. 五 20 16:05:05 ubuntu-Precision-5570 systemd[1823]: Failed to start Application launched by gnome-session-binary. 五 20 16:05:05 ubuntu-Precision-5570 systemd[1823]: app-gnome-gnome\x2dkeyring\x2dsecrets-2069.scope: Failed to add PIDs to scope's control group: No such process 五 20 16:05:05 ubuntu-Precision-5570 systemd[1823]: app-gnome-gnome\x2dkeyring\x2dsecrets-2069.scope: Failed with result 'resources'. 五 20 16:05:05 ubuntu-Precision-5570 systemd[1823]: Failed to start Application launched by gnome-session-binary. 五 20 16:05:05 ubuntu-Precision-5570 systemd[1823]: app-gnome-gnome\x2dkeyring\x2dssh-2072.scope: Failed to add PIDs to scope's control group: No such process 五 20 16:05:05 ubuntu-Precision-5570 systemd[1823]: app-gnome-gnome\x2dkeyring\x2dssh-2072.scope: Failed with result 'resources'. 五 20 16:05:05 ubuntu-Precision-5570 systemd[1823]: Failed to start Application launched by gnome-session-binary. 五 20 16:05:05 ubuntu-Precision-5570 gnome-session-binary[2041]: GnomeDesktop-WARNING: Could not create transient scope for PID 2077: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 2077 does not exist. 五 20 16:05:05 ubuntu-Precision-5570 systemd[1823]: org.gnome.Shell@x11.service: Start request repeated too quickly. 五 20 16:05:05 ubuntu-Precision-5570 snapd-desktop-i[1833]: cannot open display: 五 20 16:05:05 ubuntu-Precision-5570 systemd[1823]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:05:06 ubuntu-Precision-5570 at-spi-dbus-bus.desktop[2085]: dbus-daemon[2085]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=2086 comm="/usr/bin/gnome-shell " label="unconfined") 五 20 16:05:06 ubuntu-Precision-5570 at-spi-dbus-bus.desktop[2085]: dbus-daemon[2085]: Successfully activated service 'org.a11y.atspi.Registry' 五 20 16:05:06 ubuntu-Precision-5570 systemd[1823]: Dependency failed for GNOME XSettings service. 五 20 16:05:06 ubuntu-Precision-5570 at-spi2-registr[2247]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client 五 20 16:05:06 ubuntu-Precision-5570 at-spi2-registr[2247]: Unable to register client with session manager 五 20 16:05:06 ubuntu-Precision-5570 gnome-session-binary[2041]: GnomeDesktop-WARNING: Could not create transient scope for PID 2356: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 2356 does not exist. 五 20 16:05:06 ubuntu-Precision-5570 systemd[1823]: app-gnome-snap\x2duserd\x2dautostart-2330.scope: Failed to add PIDs to scope's control group: No such process 五 20 16:05:06 ubuntu-Precision-5570 systemd[1823]: app-gnome-snap\x2duserd\x2dautostart-2330.scope: Failed with result 'resources'. 五 20 16:05:06 ubuntu-Precision-5570 systemd[1823]: Failed to start Application launched by gnome-session-binary. 五 20 16:05:06 ubuntu-Precision-5570 gsd-media-keys[2284]: Failed to grab accelerator for keybinding settings:hibernate 五 20 16:05:06 ubuntu-Precision-5570 gsd-media-keys[2284]: Failed to grab accelerator for keybinding settings:playback-repeat 五 20 16:05:06 ubuntu-Precision-5570 gnome-shell[2086]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found 五 20 16:05:06 ubuntu-Precision-5570 gnome-shell[2086]: Page flip discarded: CRTC property (GAMMA_LUT) not found 五 20 16:05:06 ubuntu-Precision-5570 gnome-shell[2086]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found 五 20 16:05:06 ubuntu-Precision-5570 gnome-shell[2086]: Page flip discarded: CRTC property (GAMMA_LUT) not found 五 20 16:05:06 ubuntu-Precision-5570 gnome-shell[2086]: ATK Bridge is disabled but a11y has already been enabled. 五 20 16:05:07 ubuntu-Precision-5570 gdm-launch-environment][1052]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed 五 20 16:05:07 ubuntu-Precision-5570 gsd-color[2275]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Sharp_Corporation_gdm_127 五 20 16:05:07 ubuntu-Precision-5570 gnome-shell[2086]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found 五 20 16:05:07 ubuntu-Precision-5570 gnome-shell[2086]: Page flip discarded: CRTC property (GAMMA_LUT) not found 五 20 16:05:07 ubuntu-Precision-5570 pulseaudio[1151]: After module unload, module 'module-null-sink' was still loaded! 五 20 16:05:16 ubuntu-Precision-5570 nautilus[2234]: Could not delete '.meta.isrunning': No such file or directory 五 20 16:05:20 ubuntu-Precision-5570 systemd[1081]: xdg-permission-store.service: Failed with result 'exit-code'. 五 20 16:05:20 ubuntu-Precision-5570 systemd[1081]: xdg-document-portal.service: Failed with result 'exit-code'. 五 20 16:06:08 ubuntu-Precision-5570 ubuntu-appindicators@ubuntu.com[2086]: unable to update icon for software-update-available 五 20 16:06:08 ubuntu-Precision-5570 ubuntu-appindicators@ubuntu.com[2086]: unable to update icon for livepatch 五 20 16:06:35 ubuntu-Precision-5570 pulseaudio[1832]: X11 I/O error handler called 五 20 16:06:35 ubuntu-Precision-5570 pulseaudio[1832]: X11 I/O error exit handler called, preparing to tear down X11 modules 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Connection to xwayland lost 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Could not release device '/dev/input/event12' (13,76): GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: Unknown object '/org/freedesktop/login1/session/_33'. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Could not release device '/dev/input/event1' (13,65): GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: Unknown object '/org/freedesktop/login1/session/_33'. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was notify on NMDeviceWifi 0x558a232842b0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was notify on NMActiveConnection 0x558a2328a180. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was state-changed on NMDeviceWifi 0x558a232842b0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x558a25e900c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x558a25e900c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x558a25e900c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a23293f30. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a23293f30. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a23293f30. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a23293f30. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x558a21954250. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x558a25e900c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a23292c30. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a23292c30. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a23292c30. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a23292c30. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x558a25ee49f0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x558a25e900c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a22262960. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a22262960. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a22262960. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a22262960. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x558a2226bcb0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x558a25e900c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a2223d9c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a2223d9c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a2223d9c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a2223d9c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x558a25e68430. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x558a25e900c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a21878f80. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a21878f80. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a21878f80. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a21878f80. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x558a224fa4f0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x558a25e900c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a218651a0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a218651a0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a218651a0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a218651a0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x558a225bf5a0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x558a25e900c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a218caa10. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a218caa10. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a218caa10. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a218caa10. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x558a2329f380. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x558a25e900c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a22625120. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a22625120. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a22625120. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a22625120. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x558a23298c10. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x558a25e900c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a23be8b40. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a23be8b40. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a23be8b40. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a23be8b40. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x558a222873b0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x558a25e900c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a25eaeb20. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a25eaeb20. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a25eaeb20. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a25eaeb20. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x558a2227bea0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x558a25e900c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a2223def0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a2223def0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a2223def0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a2223def0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x558a22273e20. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x558a25e900c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a222532e0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a222532e0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a222532e0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x558a222532e0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x558a2226a010. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x558a25e900c0. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. 五 20 16:06:35 ubuntu-Precision-5570 gnome-shell[2086]: The offending callback was set_container(), a vfunc. 五 20 16:06:35 ubuntu-Precision-5570 systemd[2897]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:06:35 ubuntu-Precision-5570 gnome-session-binary[2940]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed 五 20 16:06:35 ubuntu-Precision-5570 gnome-session-binary[2940]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed 五 20 16:06:35 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[2935]: dbus-daemon[2935]: [session uid=127 pid=2935] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=127 pid=2981 comm="/usr/bin/gnome-shell " label="unconfined") 五 20 16:06:35 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[2935]: dbus-daemon[2935]: [session uid=127 pid=2935] Successfully activated service 'org.a11y.Bus' 五 20 16:06:35 ubuntu-Precision-5570 systemd[2897]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:06:35 ubuntu-Precision-5570 tracker-miner-f[3043]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location. 五 20 16:06:35 ubuntu-Precision-5570 tracker-miner-f[3043]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location. 五 20 16:06:35 ubuntu-Precision-5570 tracker-miner-f[3043]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location. 五 20 16:06:35 ubuntu-Precision-5570 tracker-miner-f[3043]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location. 五 20 16:06:35 ubuntu-Precision-5570 tracker-miner-f[3043]: Unable to get XDG user directory path for special directory &DOWNLOAD. Ignoring this location. 五 20 16:06:35 ubuntu-Precision-5570 tracker-miner-f[3043]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location. 五 20 16:06:35 ubuntu-Precision-5570 tracker-miner-f[3043]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location. 五 20 16:06:35 ubuntu-Precision-5570 tracker-miner-f[3043]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location. 五 20 16:06:35 ubuntu-Precision-5570 tracker-miner-f[3043]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location. 五 20 16:06:35 ubuntu-Precision-5570 systemd[2897]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:06:36 ubuntu-Precision-5570 org.gnome.Shell.desktop[3130]: (WW) Option "-listen" for file descriptors is deprecated 五 20 16:06:36 ubuntu-Precision-5570 org.gnome.Shell.desktop[3130]: Please use "-listenfd" instead. 五 20 16:06:36 ubuntu-Precision-5570 org.gnome.Shell.desktop[3130]: (WW) Option "-listen" for file descriptors is deprecated 五 20 16:06:36 ubuntu-Precision-5570 org.gnome.Shell.desktop[3130]: Please use "-listenfd" instead. 五 20 16:06:36 ubuntu-Precision-5570 systemd[2897]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:06:36 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[2935]: dbus-daemon[2935]: [session uid=127 pid=2935] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=127 pid=2981 comm="/usr/bin/gnome-shell " label="unconfined") 五 20 16:06:36 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[2935]: dbus-daemon[2935]: [session uid=127 pid=2935] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' 五 20 16:06:36 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[2935]: dbus-daemon[2935]: [session uid=127 pid=2935] Activating service name='org.gnome.Shell.Notifications' requested by ':1.3' (uid=127 pid=2981 comm="/usr/bin/gnome-shell " label="unconfined") 五 20 16:06:36 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[3042]: dbus-daemon[3042]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=127 pid=2981 comm="/usr/bin/gnome-shell " label="unconfined") 五 20 16:06:36 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[3042]: dbus-daemon[3042]: Successfully activated service 'org.a11y.atspi.Registry' 五 20 16:06:36 ubuntu-Precision-5570 org.gnome.Shell.desktop[2981]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10922a4df68f8e80ba165303399560096200000029400000.ms”: No such file or directory 五 20 16:06:36 ubuntu-Precision-5570 gnome-shell[2981]: JS ERROR: TypeError: this._managerProxy is undefined _onGeoclueVanished@resource:///org/gnome/shell/ui/status/location.js:169:9 五 20 16:06:36 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[2935]: dbus-daemon[2935]: [session uid=127 pid=2935] Activating service name='org.freedesktop.systemd1' requested by ':1.9' (uid=127 pid=3181 comm="/usr/libexec/gsd-sharing " label="unconfined") 五 20 16:06:36 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[2935]: dbus-daemon[2935]: [session uid=127 pid=2935] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 五 20 16:06:36 ubuntu-Precision-5570 gsd-sharing[3181]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 五 20 16:06:36 ubuntu-Precision-5570 gsd-sharing[3181]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 五 20 16:06:36 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[2935]: dbus-daemon[2935]: [session uid=127 pid=2935] Successfully activated service 'org.gnome.Shell.Notifications' 五 20 16:06:36 ubuntu-Precision-5570 systemd[2897]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:06:36 ubuntu-Precision-5570 gnome-shell[2981]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed 五 20 16:06:36 ubuntu-Precision-5570 gnome-shell[2981]: cr_declaration_parse_list_from_buf: assertion 'parser' failed 五 20 16:06:36 ubuntu-Precision-5570 gnome-shell[2981]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed 五 20 16:06:36 ubuntu-Precision-5570 gnome-shell[2981]: cr_declaration_parse_list_from_buf: assertion 'parser' failed 五 20 16:06:36 ubuntu-Precision-5570 xbrlapi.desktop[3333]: openConnection: connect: No such file or directory 五 20 16:06:36 ubuntu-Precision-5570 xbrlapi.desktop[3333]: cannot connect to braille devices daemon brltty at :0 五 20 16:06:36 ubuntu-Precision-5570 gsd-media-keys[3202]: Failed to grab accelerator for keybinding settings:hibernate 五 20 16:06:36 ubuntu-Precision-5570 gsd-media-keys[3202]: Failed to grab accelerator for keybinding settings:playback-repeat 五 20 16:06:36 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[2935]: dbus-daemon[2935]: [session uid=127 pid=2935] Activating service name='org.gnome.ScreenSaver' requested by ':1.23' (uid=127 pid=3221 comm="/usr/libexec/gsd-power " label="unconfined") 五 20 16:06:36 ubuntu-Precision-5570 gnome-shell[2981]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed 五 20 16:06:36 ubuntu-Precision-5570 gnome-shell[2981]: cr_declaration_parse_list_from_buf: assertion 'parser' failed 五 20 16:06:36 ubuntu-Precision-5570 gnome-shell[2981]: ATK Bridge is disabled but a11y has already been enabled. 五 20 16:06:36 ubuntu-Precision-5570 /usr/libexec/gdm-wayland-session[2935]: dbus-daemon[2935]: [session uid=127 pid=2935] Successfully activated service 'org.gnome.ScreenSaver' 五 20 16:06:36 ubuntu-Precision-5570 org.gnome.Shell.desktop[3360]: The XKEYBOARD keymap compiler (xkbcomp) reports: 五 20 16:06:36 ubuntu-Precision-5570 org.gnome.Shell.desktop[3360]: > Warning: Unsupported maximum keycode 708, clipping. 五 20 16:06:36 ubuntu-Precision-5570 org.gnome.Shell.desktop[3360]: > X11 cannot support keycodes above 255. 五 20 16:06:36 ubuntu-Precision-5570 org.gnome.Shell.desktop[3360]: Errors from xkbcomp are not fatal to the X server 五 20 16:06:36 ubuntu-Precision-5570 gnome-shell[2981]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found 五 20 16:06:36 ubuntu-Precision-5570 gnome-shell[2981]: Page flip discarded: CRTC property (GAMMA_LUT) not found 五 20 16:06:36 ubuntu-Precision-5570 systemd[2897]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Start request repeated too quickly. 五 20 16:06:36 ubuntu-Precision-5570 systemd[2897]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:06:36 ubuntu-Precision-5570 systemd[2897]: Failed to start Service for snap application snapd-desktop-integration.snapd-desktop-integration. 五 20 16:06:37 ubuntu-Precision-5570 gdm-fingerprint][3400]: gkr-pam: no password is available for user 五 20 16:06:38 ubuntu-Precision-5570 gdm-password][3399]: gkr-pam: unable to locate daemon control file 五 20 16:06:38 ubuntu-Precision-5570 gnome-session-binary[3421]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.systemd1.TransactionIsDestructive: Transaction for gnome-session-wayland@ubuntu.target/start is destructive (gnome-session-manager@ubuntu.service has 'stop' job queued, but 'start' is included in transaction). 五 20 16:06:39 ubuntu-Precision-5570 gnome-shell[2981]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found 五 20 16:06:39 ubuntu-Precision-5570 gnome-shell[2981]: Page flip discarded: CRTC property (GAMMA_LUT) not found 五 20 16:06:39 ubuntu-Precision-5570 gnome-shell[2981]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found 五 20 16:06:39 ubuntu-Precision-5570 gnome-shell[2981]: Page flip discarded: CRTC property (GAMMA_LUT) not found 五 20 16:06:39 ubuntu-Precision-5570 gnome-shell[2981]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found 五 20 16:06:39 ubuntu-Precision-5570 gnome-shell[2981]: Page flip discarded: CRTC property (GAMMA_LUT) not found 五 20 16:06:39 ubuntu-Precision-5570 org.gnome.Shell.desktop[3451]: The XKEYBOARD keymap compiler (xkbcomp) reports: 五 20 16:06:39 ubuntu-Precision-5570 org.gnome.Shell.desktop[3451]: > Warning: Unsupported maximum keycode 708, clipping. 五 20 16:06:39 ubuntu-Precision-5570 org.gnome.Shell.desktop[3451]: > X11 cannot support keycodes above 255. 五 20 16:06:39 ubuntu-Precision-5570 org.gnome.Shell.desktop[3451]: Errors from xkbcomp are not fatal to the X server 五 20 16:06:39 ubuntu-Precision-5570 systemd[1823]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:06:39 ubuntu-Precision-5570 systemd[1823]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'. 五 20 16:06:40 ubuntu-Precision-5570 pulseaudio[1832]: After module unload, module 'module-null-sink' was still loaded! 五 20 16:06:40 ubuntu-Precision-5570 gdm-fingerprint][3456]: gkr-pam: no password is available for user 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: org.gnome.Shell@wayland.service: State 'stop-sigterm' timed out. Killing. 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: org.gnome.Shell@wayland.service: Main process exited, code=dumped, status=11/SEGV 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: org.gnome.Shell@wayland.service: Failed with result 'timeout'. 五 20 16:06:40 ubuntu-Precision-5570 gnome-session-binary[2041]: WARNING: Could not get session class: No such device or address 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: xdg-desktop-portal-gnome.service: Failed with result 'exit-code'. 五 20 16:06:40 ubuntu-Precision-5570 xdg-desktop-por[2264]: Failed to get application states: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying 五 20 16:06:40 ubuntu-Precision-5570 snapd-desktop-i[3461]: cannot open display: 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:06:40 ubuntu-Precision-5570 evolution-calen[2139]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: The connection is closed (g-io-error-quark, 18) 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: xdg-document-portal.service: Failed with result 'exit-code'. 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: xdg-permission-store.service: Failed with result 'exit-code'. 五 20 16:06:40 ubuntu-Precision-5570 gdm-password][3455]: gkr-pam: unable to locate daemon control file 五 20 16:06:40 ubuntu-Precision-5570 kernel: kauditd_printk_skb: 2 callbacks suppressed 五 20 16:06:40 ubuntu-Precision-5570 snapd-desktop-i[3545]: cannot open display: 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:06:40 ubuntu-Precision-5570 snapd-desktop-i[3639]: cannot open display: 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: app-gnome-gnome\x2dkeyring\x2dpkcs11-3781.scope: Failed to add PIDs to scope's control group: No such process 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: app-gnome-gnome\x2dkeyring\x2dpkcs11-3781.scope: Failed with result 'resources'. 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: Failed to start Application launched by gnome-session-binary. 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: app-gnome-gnome\x2dkeyring\x2dsecrets-3779.scope: Failed to add PIDs to scope's control group: No such process 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: app-gnome-gnome\x2dkeyring\x2dsecrets-3779.scope: Failed with result 'resources'. 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: Failed to start Application launched by gnome-session-binary. 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: app-gnome-gnome\x2dkeyring\x2dssh-3782.scope: Failed to add PIDs to scope's control group: No such process 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: app-gnome-gnome\x2dkeyring\x2dssh-3782.scope: Failed with result 'resources'. 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: Failed to start Application launched by gnome-session-binary. 五 20 16:06:40 ubuntu-Precision-5570 gnome-session-binary[3755]: GnomeDesktop-WARNING: Could not create transient scope for PID 3787: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 3787 does not exist. 五 20 16:06:40 ubuntu-Precision-5570 systemd[1823]: org.gnome.Shell@x11.service: Start request repeated too quickly. 五 20 16:06:41 ubuntu-Precision-5570 snapd-desktop-i[3823]: cannot open display: 五 20 16:06:41 ubuntu-Precision-5570 systemd[1823]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:06:41 ubuntu-Precision-5570 snapd-desktop-i[3885]: cannot open display: 五 20 16:06:41 ubuntu-Precision-5570 systemd[1823]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. 五 20 16:06:41 ubuntu-Precision-5570 at-spi-dbus-bus.desktop[3796]: dbus-daemon[3796]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=3794 comm="/usr/bin/gnome-shell " label="unconfined") 五 20 16:06:41 ubuntu-Precision-5570 at-spi-dbus-bus.desktop[3796]: dbus-daemon[3796]: Successfully activated service 'org.a11y.atspi.Registry' 五 20 16:06:41 ubuntu-Precision-5570 systemd[1823]: Dependency failed for GNOME XSettings service. 五 20 16:06:41 ubuntu-Precision-5570 at-spi2-registr[4124]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client 五 20 16:06:41 ubuntu-Precision-5570 at-spi2-registr[4124]: Unable to register client with session manager 五 20 16:06:41 ubuntu-Precision-5570 gnome-session-binary[3755]: GnomeDesktop-WARNING: Could not create transient scope for PID 4220: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 4220 does not exist. 五 20 16:06:41 ubuntu-Precision-5570 systemd[1823]: app-gnome-snap\x2duserd\x2dautostart-4193.scope: Failed to add PIDs to scope's control group: No such process 五 20 16:06:41 ubuntu-Precision-5570 systemd[1823]: app-gnome-snap\x2duserd\x2dautostart-4193.scope: Failed with result 'resources'. 五 20 16:06:41 ubuntu-Precision-5570 systemd[1823]: Failed to start Application launched by gnome-session-binary. 五 20 16:06:41 ubuntu-Precision-5570 systemd[1823]: app-gnome-user\x2ddirs\x2dupdate\x2dgtk-4201.scope: Failed to add PIDs to scope's control group: No such process 五 20 16:06:41 ubuntu-Precision-5570 systemd[1823]: app-gnome-user\x2ddirs\x2dupdate\x2dgtk-4201.scope: Failed with result 'resources'. 五 20 16:06:41 ubuntu-Precision-5570 systemd[1823]: Failed to start Application launched by gnome-session-binary. 五 20 16:06:42 ubuntu-Precision-5570 gsd-media-keys[4157]: Failed to grab accelerator for keybinding settings:playback-repeat 五 20 16:06:42 ubuntu-Precision-5570 gsd-media-keys[4157]: Failed to grab accelerator for keybinding settings:hibernate 五 20 16:06:42 ubuntu-Precision-5570 gnome-shell[3794]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found 五 20 16:06:42 ubuntu-Precision-5570 gnome-shell[3794]: Page flip discarded: CRTC property (GAMMA_LUT) not found 五 20 16:06:42 ubuntu-Precision-5570 gnome-shell[3794]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found 五 20 16:06:42 ubuntu-Precision-5570 gnome-shell[3794]: Page flip discarded: CRTC property (GAMMA_LUT) not found 五 20 16:06:42 ubuntu-Precision-5570 gnome-shell[3794]: ATK Bridge is disabled but a11y has already been enabled. 五 20 16:06:42 ubuntu-Precision-5570 gnome-shell[2981]: Connection to xwayland lost 五 20 16:06:42 ubuntu-Precision-5570 gdm-launch-environment][2890]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed 五 20 16:06:42 ubuntu-Precision-5570 gsd-color[4147]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Sharp_Corporation_gdm_127 五 20 16:06:42 ubuntu-Precision-5570 gnome-shell[3794]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found 五 20 16:06:42 ubuntu-Precision-5570 gnome-shell[3794]: Page flip discarded: CRTC property (GAMMA_LUT) not found 五 20 16:06:52 ubuntu-Precision-5570 nautilus[4111]: Could not delete '.meta.isrunning': No such file or directory 五 20 16:06:55 ubuntu-Precision-5570 systemd[2897]: xdg-document-portal.service: Failed with result 'exit-code'. 五 20 16:06:55 ubuntu-Precision-5570 systemd[2897]: xdg-permission-store.service: Failed with result 'exit-code'. 五 20 16:07:17 ubuntu-Precision-5570 gnome-keyring-daemon[3586]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 五 20 16:07:19 ubuntu-Precision-5570 gnome-shell[3794]: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed 五 20 16:07:20 ubuntu-Precision-5570 gnome-shell[3794]: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed