Feb 23 19:46:07 jak-t480s gnome-shell[7170]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x55709e7a4320] is on because it needs an allocation.
Feb 23 19:46:07 jak-t480s gnome-shell[7170]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x55709e824f10] is on because it needs an allocation.
Feb 23 19:46:07 jak-t480s gnome-shell[7170]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x55709eadbf20] is on because it needs an allocation.
Feb 23 19:46:12 jak-t480s sudo[3056709]:      jak : TTY=pts/10 ; PWD=/home/jak/Projects/Ubuntu/Merges/packagekit/packagekit-1.2.5-2ubuntu1 ; USER=root ; COMMAND=/usr/bin/apt dist-upgrade
Feb 23 19:46:12 jak-t480s sudo[3056709]: pam_unix(sudo:session): session opened for user root(uid=0) by jak(uid=1000)
Feb 23 19:46:16 jak-t480s systemd[1]: tmp-apt\x2dbtrfs\x2dsnapshot\x2dmp\x2dmyxwf8n2.mount: Deactivated successfully.
Feb 23 19:46:22 jak-t480s systemd[1]: Reloading.
Feb 23 19:46:22 jak-t480s systemd[1]: fstrim.timer: Deactivated successfully.
Feb 23 19:46:22 jak-t480s systemd[1]: Stopped Discard unused blocks once a week.
Feb 23 19:46:22 jak-t480s systemd[1]: Stopping Discard unused blocks once a week...
Feb 23 19:46:22 jak-t480s systemd[1]: Started Discard unused blocks once a week.
Feb 23 19:46:22 jak-t480s systemd[1]: Reloading.
Feb 23 19:46:25 jak-t480s systemd[1]: Reloading.
Feb 23 19:46:25 jak-t480s systemd[1]: apt-daily-upgrade.timer: Deactivated successfully.
Feb 23 19:46:25 jak-t480s systemd[1]: Stopped Daily apt upgrade and clean activities.
Feb 23 19:46:25 jak-t480s systemd[1]: Stopping Daily apt upgrade and clean activities...
Feb 23 19:46:25 jak-t480s systemd[1]: Started Daily apt upgrade and clean activities.
Feb 23 19:46:25 jak-t480s systemd[1]: apt-daily.timer: Deactivated successfully.
Feb 23 19:46:25 jak-t480s systemd[1]: Stopped Daily apt download activities.
Feb 23 19:46:25 jak-t480s systemd[1]: Stopping Daily apt download activities...
Feb 23 19:46:25 jak-t480s systemd[1]: Started Daily apt download activities.
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus...
Feb 23 19:46:27 jak-t480s bluetoothd[2312]: Disconnected from D-Bus. Exiting.
Feb 23 19:46:27 jak-t480s kernel: traps: bluetoothd[2312] general protection fault ip:7f2ce0e42f3d sp:7ffdf3a53868 error:0 in libc.so.6 (deleted)[7f2ce0ccf000+194000]
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping Modem Manager...
Feb 23 19:46:27 jak-t480s cups-browsed[1877936]: Wed Feb 23 19:46:27 2022 Avahi server disappeared, shutting down service browsers, removing DNS-SD-discovered print queues.
Feb 23 19:46:27 jak-t480s cups-browsed[1877936]: Wed Feb 23 19:46:27 2022 checking queues in 0s
Feb 23 19:46:27 jak-t480s ModemManager[391369]: <info>  caught signal, shutting down...
Feb 23 19:46:27 jak-t480s systemd[1]: NetworkManager-wait-online.service: Deactivated successfully.
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (II) event2  - Power Button: device removed
Feb 23 19:46:27 jak-t480s wpa_supplicant[2359]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Feb 23 19:46:27 jak-t480s systemd[1]: Stopped Network Manager Wait Online.
Feb 23 19:46:27 jak-t480s wpa_supplicant[2359]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping Network Manager...
Feb 23 19:46:27 jak-t480s wpa_supplicant[2359]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
Feb 23 19:46:27 jak-t480s NetworkManager[1392176]: <info>  [1645641987.9683] caught SIGTERM, shutting down normally.
Feb 23 19:46:27 jak-t480s thermald[3166]: Terminating ...
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping Accounts Service...
Feb 23 19:46:27 jak-t480s avahi-daemon[2310]: Disconnected from D-Bus, exiting.
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Feb 23 19:46:27 jak-t480s avahi-daemon[2310]: Got SIGTERM, quitting.
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping Manage, Install and Generate Color Profiles...
Feb 23 19:46:27 jak-t480s avahi-daemon[2310]: Leaving mDNS multicast group on interface lxdbr0.IPv6 with address fd42:cf9e:1f28:f331::1.
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping GNOME Display Manager...
Feb 23 19:46:27 jak-t480s bluetoothd[2312]: Endpoint unregistered: sender=:1.88 path=/MediaEndpoint/A2DPSink/sbc
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping Location Lookup Service...
Feb 23 19:46:27 jak-t480s bluetoothd[2312]: Endpoint unregistered: sender=:1.88 path=/MediaEndpoint/A2DPSource/sbc
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping PackageKit Daemon...
Feb 23 19:46:27 jak-t480s bluetoothd[2312]: Endpoint unregistered: sender=:1.88 path=/MediaEndpoint/A2DPSink/sbc_xq
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping Power Profiles daemon...
Feb 23 19:46:27 jak-t480s bluetoothd[2312]: Endpoint unregistered: sender=:1.88 path=/MediaEndpoint/A2DPSource/sbc_xq
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping RealtimeKit Scheduling Policy Service...
Feb 23 19:46:27 jak-t480s bluetoothd[2312]: Endpoint unregistered: sender=:1.88 path=/MediaEndpoint/A2DPSource/faststream
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping Switcheroo Control Proxy service...
Feb 23 19:46:27 jak-t480s bluetoothd[2312]: Endpoint unregistered: sender=:1.88 path=/MediaEndpoint/A2DPSource/faststream_duplex
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (EE)
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: Fatal server error:
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (EE) systemd-logind disappeared (stopped/restarted?)
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (EE)
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (EE)
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: Please consult the The X.Org Foundation support
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]:          at http://wiki.x.org
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]:  for help.
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (EE) Please also check the log file at "/home/jak/.local/share/xorg/Xorg.0.log" for additional information.
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (EE)
Feb 23 19:46:28 jak-t480s kernel: seahorse[1205191]: segfault at 55d50bdfc61e ip 00007f2f630a573e sp 00007ffddbde57e0 error 6 in libavahi-glib.so.1.0.2[7f2f630a5000+2000]
Feb 23 19:46:28 jak-t480s kernel: Code: 19 00 00 e8 04 fb ff ff 0f 1f 40 00 f3 0f 1e fa 48 83 ec 08 48 85 ff 74 20 8b 47 08 85 c0 75 38 48 8b 07 c7 47 08 01 00 00 00 <c7> 80 a8 00 00 00 01 00 00 00 48 83 c4 08 c3 48 8d 0d 74 1a 00 00
Feb 23 19:46:28 jak-t480s kernel: wlan0: deauthenticating from 7a:45:58:16:13:da by local choice (Reason: 3=DEAUTH_LEAVING)
Feb 23 19:46:28 jak-t480s kernel: cups-browsed[1877936]: segfault at 56429a744024 ip 00007f4a3f7fb73e sp 00007ffdf2067a40 error 6 in libavahi-glib.so.1.0.2[7f4a3f7fb000+2000]
Feb 23 19:46:28 jak-t480s kernel: Code: 19 00 00 e8 04 fb ff ff 0f 1f 40 00 f3 0f 1e fa 48 83 ec 08 48 85 ff 74 20 8b 47 08 85 c0 75 38 48 8b 07 c7 47 08 01 00 00 00 <c7> 80 a8 00 00 00 01 00 00 00 48 83 c4 08 c3 48 8d 0d 74 1a 00 00
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping User Login Management...
Feb 23 19:46:27 jak-t480s bluetoothd[2312]: Endpoint unregistered: sender=:1.88 path=/MediaEndpoint/A2DPSource/ldac
Feb 23 19:46:28 jak-t480s fwupd[3041804]: 18:46:28:0006 FuPluginUpower       failed to query lid state
Feb 23 19:46:28 jak-t480s fwupd[3041804]: 18:46:28:0007 FuPluginUpower       failed to query lid state
Feb 23 19:46:28 jak-t480s fwupd[3041804]: 18:46:28:0007 FuPluginUpower       failed to query power type
Feb 23 19:46:28 jak-t480s fwupd[3041804]: 18:46:28:0048 FuMain               another service has claimed the dbus name org.freedesktop.fwupd
Feb 23 19:46:28 jak-t480s google-chrome.desktop[2517568]: [2517562:2517597:0223/194628.032151:FATAL:bus.cc(1224)] D-Bus connection was disconnected. Aborting.
Feb 23 19:46:28 jak-t480s google-chrome.desktop[2517568]: [2517562:2517704:0223/194628.034020:FATAL:bus.cc(1224)] D-Bus connection was disconnected. Aborting.
Feb 23 19:46:28 jak-t480s udisksd[2357]: malloc_consolidate(): unaligned fastbin chunk detected
Feb 23 19:46:28 jak-t480s cups-browsed[1877936]: Wed Feb 23 19:46:28 2022 ERROR: Failed to create client: An unexpected D-Bus error occurred
Feb 23 19:46:28 jak-t480s cups-browsed[1877936]: Wed Feb 23 19:46:28 2022 checking queues in 0s
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (II) event10 - Logitech USB Optical Mouse: device removed
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (II) event17 - Elan Touchpad: device removed
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (II) event8  - USB PnP Audio Device(EEPROM): device removed
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (II) event7  - Yubico Yubikey 4 OTP+U2F+CCID: device removed
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (II) event6  - Video Bus: device removed
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (II) event0  - Sleep Button: device removed
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (II) event18 - Elan TrackPoint: device removed
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (II) event4  - ThinkPad Extra Buttons: device removed
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (II) event19 - Integrated Camera: Integrated C: device removed
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (II) event3  - AT Translated Set 2 keyboard: device removed
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (II) event9  - Unicomp Inc Ruffian6_x Kbrd v3_xx: device removed
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (II) AIGLX: Suspending AIGLX clients for VT switch
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping Thermal Daemon Service...
Feb 23 19:46:28 jak-t480s avahi-daemon[2310]: Leaving mDNS multicast group on interface lxdbr0.IPv4 with address 10.79.93.1.
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping Desktop service for Ubuntu Advantage...
Feb 23 19:46:28 jak-t480s avahi-daemon[2310]: Leaving mDNS multicast group on interface wlan0.IPv6 with address 2a02:908:2816:fb20:1e96:a7b6:4b94:519a.
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping Disk Manager...
Feb 23 19:46:28 jak-t480s avahi-daemon[2310]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.101.
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping Daemon for power management...
Feb 23 19:46:28 jak-t480s avahi-daemon[2310]: Leaving mDNS multicast group on interface lo.IPv6 with address ::1.
Feb 23 19:46:27 jak-t480s systemd[1]: Stopping WPA supplicant...
Feb 23 19:46:28 jak-t480s avahi-daemon[2310]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Feb 23 19:46:27 jak-t480s systemd[1]: rtkit-daemon.service: Deactivated successfully.
Feb 23 19:46:28 jak-t480s wpa_supplicant[2359]: p2p-dev-wlan0: CTRL-EVENT-TERMINATING
Feb 23 19:46:27 jak-t480s systemd[1]: Stopped RealtimeKit Scheduling Policy Service.
Feb 23 19:46:28 jak-t480s avahi-daemon[2310]: avahi-daemon 0.8 exiting.
Feb 23 19:46:27 jak-t480s systemd[1]: rtkit-daemon.service: Consumed 17.278s CPU time.
Feb 23 19:46:27 jak-t480s systemd[1]: accounts-daemon.service: Deactivated successfully.
Feb 23 19:46:27 jak-t480s systemd[1]: Stopped Accounts Service.
Feb 23 19:46:27 jak-t480s systemd[1]: accounts-daemon.service: Consumed 35.283s CPU time.
Feb 23 19:46:27 jak-t480s systemd[1]: networkd-dispatcher.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 19:46:27 jak-t480s systemd[1]: networkd-dispatcher.service: Failed with result 'exit-code'.
Feb 23 19:46:27 jak-t480s systemd[1]: unattended-upgrades.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 19:46:27 jak-t480s systemd[1]: unattended-upgrades.service: Failed with result 'exit-code'.
Feb 23 19:46:27 jak-t480s systemd[1]: kerneloops.service: Deactivated successfully.
Feb 23 19:46:27 jak-t480s systemd[1]: kerneloops.service: Consumed 2.914s CPU time.
Feb 23 19:46:27 jak-t480s systemd[1]: power-profiles-daemon.service: Deactivated successfully.
Feb 23 19:46:27 jak-t480s systemd[1]: Stopped Power Profiles daemon.
Feb 23 19:46:27 jak-t480s systemd[1]: switcheroo-control.service: Deactivated successfully.
Feb 23 19:46:27 jak-t480s systemd[1]: Stopped Switcheroo Control Proxy service.
Feb 23 19:46:27 jak-t480s systemd[1]: colord.service: Deactivated successfully.
Feb 23 19:46:27 jak-t480s systemd[1]: Stopped Manage, Install and Generate Color Profiles.
Feb 23 19:46:27 jak-t480s systemd[1]: colord.service: Consumed 1min 20.834s CPU time.
Feb 23 19:46:28 jak-t480s systemd[1]: ubuntu-advantage-desktop-daemon.service: Deactivated successfully.
Feb 23 19:46:28 jak-t480s systemd[1]: Stopped Desktop service for Ubuntu Advantage.
Feb 23 19:46:28 jak-t480s systemd[1]: packagekit.service: Deactivated successfully.
Feb 23 19:46:28 jak-t480s systemd[1]: Stopped PackageKit Daemon.
Feb 23 19:46:28 jak-t480s systemd[1]: packagekit.service: Consumed 2.032s CPU time.
Feb 23 19:46:28 jak-t480s systemd[1]: whoopsie.service: Deactivated successfully.
Feb 23 19:46:28 jak-t480s udisksd[2357]: udisks daemon version 2.9.4 exiting
Feb 23 19:46:28 jak-t480s wireplumber[5943]: 0x55f7bf4045c8: error 16
Feb 23 19:46:28 jak-t480s seahorse[1205191]: failure communicating with to avahi: Daemon connection failed
Feb 23 19:46:28 jak-t480s systemd[1]: geoclue.service: Deactivated successfully.
Feb 23 19:46:28 jak-t480s systemd[1]: Stopped Location Lookup Service.
Feb 23 19:46:28 jak-t480s systemd[1]: geoclue.service: Consumed 4min 5.781s CPU time.
Feb 23 19:46:28 jak-t480s systemd[1]: upower.service: Deactivated successfully.
Feb 23 19:46:28 jak-t480s systemd[1]: Stopped Daemon for power management.
Feb 23 19:46:28 jak-t480s systemd[1]: upower.service: Consumed 43.066s CPU time.
Feb 23 19:46:28 jak-t480s systemd[1]: polkit.service: Deactivated successfully.
Feb 23 19:46:28 jak-t480s systemd[1]: Stopped Authorization Manager.
Feb 23 19:46:28 jak-t480s systemd[1]: polkit.service: Consumed 26.682s CPU time.
Feb 23 19:46:28 jak-t480s systemd[5652]: obex.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 19:46:28 jak-t480s systemd[5652]: obex.service: Failed with result 'exit-code'.
Feb 23 19:46:28 jak-t480s systemd[1]: dbus.service: Deactivated successfully.
Feb 23 19:46:28 jak-t480s systemd[1]: Stopped D-Bus System Message Bus.
Feb 23 19:46:28 jak-t480s systemd[1]: dbus.service: Consumed 6min 614ms CPU time.
Feb 23 19:46:28 jak-t480s gvfsd-dnssd[3168827]: Error initializing Avahi: An unexpected D-Bus error occurred
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.0517] device (lxdbr0): bridge port veth80f8d64c was detached
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.0518] device (veth80f8d64c): released from master device lxdbr0
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.0519] device (lxdbr0): bridge port vetha17216b2 was detached
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.0520] device (vetha17216b2): released from master device lxdbr0
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.0521] device (lxdbr0): bridge port vetha47c8f2b was detached
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.0521] device (vetha47c8f2b): released from master device lxdbr0
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.0523] device (lxdbr0): bridge port vethf8f181a1 was detached
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.0523] device (vethf8f181a1): released from master device lxdbr0
Feb 23 19:46:28 jak-t480s systemd[1]: avahi-daemon.service: Deactivated successfully.
Feb 23 19:46:28 jak-t480s systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
Feb 23 19:46:28 jak-t480s systemd[1]: avahi-daemon.service: Consumed 5min 42.452s CPU time.
Feb 23 19:46:28 jak-t480s kernel: rfkill: input handler enabled
Feb 23 19:46:28 jak-t480s systemd[1]: whoopsie.service: Scheduled restart job, restart counter is at 1.
Feb 23 19:46:28 jak-t480s systemd[1]: Stopped crash report submission daemon.
Feb 23 19:46:28 jak-t480s wpa_supplicant[2359]: wlan0: CTRL-EVENT-DISCONNECTED bssid=7a:45:58:16:13:da reason=3 locally_generated=1
Feb 23 19:46:28 jak-t480s systemd[1]: Started crash report submission daemon.
Feb 23 19:46:28 jak-t480s ModemManager[391369]: <info>  ModemManager is shut down
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.1109] device (wlan0): state change: activated -> deactivating (reason 'unmanaged', sys-iface-state: 'managed')
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <warn>  [1645641988.1116] dispatcher: (161) failed: The connection is closed
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.1117] manager: NetworkManager state is now CONNECTED_LOCAL
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.1118] device (wlan0): state change: deactivating -> unmanaged (reason 'removed', sys-iface-state: 'managed')
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.1121] dhcp4 (wlan0): canceled DHCP transaction
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.1121] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.1121] dhcp4 (wlan0): state changed no lease
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.1123] dhcp6 (wlan0): canceled DHCP transaction
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.1123] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.1123] dhcp6 (wlan0): state changed no lease
Feb 23 19:46:28 jak-t480s systemd[1]: gdm.service: Deactivated successfully.
Feb 23 19:46:28 jak-t480s Keybase[1726295]: [1726295:0223/194628.126099:FATAL:bus.cc(1220)] D-Bus connection was disconnected. Aborting.
Feb 23 19:46:28 jak-t480s kernel: traps: Bluez D-Bus thr[1726329] trap int3 ip:557fefa36649 sp:7f8b9a5dfc50 error:0 in Keybase[557fed3d3000+6068000]
Feb 23 19:46:28 jak-t480s systemd[1]: Stopped GNOME Display Manager.
Feb 23 19:46:28 jak-t480s systemd[1]: Stopping Firmware update daemon...
Feb 23 19:46:28 jak-t480s systemd[5652]: evolution-source-registry.service: Consumed 18.638s CPU time.
Feb 23 19:46:28 jak-t480s systemd[1]: fwupd.service: Deactivated successfully.
Feb 23 19:46:28 jak-t480s systemd[1]: Stopped Firmware update daemon.
Feb 23 19:46:28 jak-t480s systemd[1]: fwupd.service: Consumed 1.335s CPU time.
Feb 23 19:46:28 jak-t480s systemd[5652]: evolution-addressbook-factory.service: Consumed 8.021s CPU time.
Feb 23 19:46:28 jak-t480s systemd[5652]: xdg-desktop-portal-gtk.service: Consumed 1h 29min 1.644s CPU time.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s wpa_supplicant[2359]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s systemd[1]: ModemManager.service: Deactivated successfully.
Feb 23 19:46:28 jak-t480s systemd[1]: Stopped Modem Manager.
Feb 23 19:46:28 jak-t480s systemd[5652]: gvfs-udisks2-volume-monitor.service: Consumed 34.744s CPU time.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s wpa_supplicant[2359]: wlan0: PMKSA-CACHE-REMOVED 7a:45:58:16:13:da 0
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s google-chrome.desktop[2517568]: [0223/194628.199566:ERROR:elf_dynamic_array_reader.h(64)] tag not found
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s kernel: traps: Core Thread[2516351] general protection fault ip:1f71143 sp:7f39dbdf4328 error:0 in spotify[1f1d000+1f32000]
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
Feb 23 19:46:28 jak-t480s wpa_supplicant[2359]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Feb 23 19:46:28 jak-t480s systemd[5652]: xdg-desktop-portal.service: Consumed 2min 35.357s CPU time.
Feb 23 19:46:28 jak-t480s wpa_supplicant[2359]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.1749] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Feb 23 19:46:28 jak-t480s wpa_supplicant[2359]: wlan0: CTRL-EVENT-TERMINATING
Feb 23 19:46:28 jak-t480s systemd[1]: wpa_supplicant.service: Deactivated successfully.
Feb 23 19:46:28 jak-t480s systemd[1]: Stopped WPA supplicant.
Feb 23 19:46:28 jak-t480s systemd[1]: wpa_supplicant.service: Consumed 47.187s CPU time.
Feb 23 19:46:28 jak-t480s systemd[5652]: evolution-calendar-factory.service: Consumed 4min 14.526s CPU time.
Feb 23 19:46:28 jak-t480s google-chrome.desktop[2517568]: [0223/194628.301521:ERROR:directory_reader_posix.cc(42)] opendir /home/jak/.config/google-chrome/Crash Reports/attachments/c03849f8-514d-4985-860d-d0828b9c61d9: No such file or directory (2)
Feb 23 19:46:28 jak-t480s google-chrome.desktop[2517568]: [0223/194628.303455:WARNING:minidump_to_upload_parameters.cc(32)] duplicate key guid, discarding value d2ea2e4bba05454db482ef29b8e8a8d8
Feb 23 19:46:28 jak-t480s gnome-shell-cal[7493]: The calendar backend for 'Contacts' has crashed.
Feb 23 19:46:28 jak-t480s gnome-shell-cal[7493]: The calendar backend for 'Contacts' has crashed.
Feb 23 19:46:28 jak-t480s gnome-shell-cal[7493]: The calendar backend for 'DebConf' has crashed.
Feb 23 19:46:28 jak-t480s gnome-shell-cal[7493]: The calendar backend for 'DebConf16' has crashed.
Feb 23 19:46:28 jak-t480s gnome-shell-cal[7493]: The calendar backend for 'Familie' has crashed.
Feb 23 19:46:28 jak-t480s gnome-shell-cal[7493]: The calendar backend for 'Feiertage in Deutschland' has crashed.
Feb 23 19:46:28 jak-t480s gnome-shell-cal[7493]: The calendar backend for 'julian.klode@canonical.com' has crashed.
Feb 23 19:46:28 jak-t480s gnome-shell-cal[7493]: The calendar backend for 'Holidays in United States' has crashed.
Feb 23 19:46:28 jak-t480s gnome-shell-cal[7493]: The calendar backend for 'Holidays in Germany' has crashed.
Feb 23 19:46:28 jak-t480s gnome-shell-cal[7493]: The calendar backend for 'julian.klode@gmail.com' has crashed.
Feb 23 19:46:28 jak-t480s tracker-miner-f[1756753]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Feb 23 19:46:28 jak-t480s whoopsie[3059253]: [19:46:28] Using lock path: /var/lock/whoopsie/lock
Feb 23 19:46:28 jak-t480s whoopsie[3059253]: [19:46:28] Could not connect to the system bus: Error sending credentials: Error sending message: Broken pipe
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was notify on NMDeviceEthernet 0x55709e6a4850.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was notify on NMDeviceWifi 0x55709e3a2840.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was notify on NMActiveConnection 0x55709dfc76c0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was notify on NMAccessPoint 0x7fa460009bd0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was state-changed on NMDeviceEthernet 0x55709e6a4850.
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was state-changed on NMDeviceWifi 0x55709e3a2840.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x5570a4fa3260.
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x5570a4fa3260.
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a4fdb800.
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s org.gnome.Shell.desktop[7170]: == Stack trace for context 0x55709e2af190 ==
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a4fdb800.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a4fdb800.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55709fdf4350.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5570a4fa3260.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a4fd7450.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a4fd7450.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a4fd7450.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5570a47443f0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5570a4fa3260.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a51698c0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a51698c0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a51698c0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55709f975c50.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5570a4fa3260.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55709ecbabe0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55709ecbabe0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55709ecbabe0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55709faf14c0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5570a4fa3260.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a50506d0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a50506d0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a50506d0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55709fafdc30.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5570a4fa3260.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a050f630.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a050f630.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a050f630.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5570a00832e0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5570a4fa3260.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a051d340.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a051d340.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a051d340.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55709f994170.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5570a4fa3260.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a051c0a0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a051c0a0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a051c0a0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5570a0496cc0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5570a4fa3260.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a0560530.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a0560530.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a0560530.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5570a02ccb20.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5570a4fa3260.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a05272f0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a05272f0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a05272f0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5570a04ae360.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5570a4fa3260.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a0526050.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a0526050.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a0526050.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5570a04dd010.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5570a4fa3260.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: 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.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending callback was set_container(), a vfunc.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x5570a0510640.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x5570a0510640.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a02a9660.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a02a9660.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5570a02a9660.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5570a04c3ab0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5570a0510640.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55709efc8e80.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55709efc8e80.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55709efc8e80.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5570a47551a0.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5570a0510640.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: 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.
Feb 23 19:46:28 jak-t480s gnome-shell[7170]: The offending callback was set_container(), a vfunc.
Feb 23 19:46:28 jak-t480s NetworkManager[1392176]: <info>  [1645641988.4557] exiting (success)
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (EE) systemd-logind: ReleaseControl failed: Connection was disconnected before a reply was received
Feb 23 19:46:28 jak-t480s /usr/libexec/gdm-x-session[6205]: (EE) Server terminated with error (1). Closing log file.
Feb 23 19:46:28 jak-t480s systemd[1]: cups-browsed.service: Main process exited, code=dumped, status=11/SEGV
Feb 23 19:46:28 jak-t480s systemd[1]: cups-browsed.service: Failed with result 'core-dump'.
Feb 23 19:46:28 jak-t480s systemd[1]: NetworkManager.service: Deactivated successfully.
Feb 23 19:46:28 jak-t480s systemd[1]: Stopped Network Manager.
Feb 23 19:46:28 jak-t480s systemd[1]: NetworkManager.service: Consumed 17min 43.438s CPU time.
Feb 23 19:46:28 jak-t480s systemd[1]: systemd-logind.service: Deactivated successfully.
Feb 23 19:46:28 jak-t480s systemd[5652]: snap.spotify.spotify.e84bc77a-bb05-4c03-88aa-202f8cfea6b5.scope: Consumed 2h 11min 10.856s CPU time.
Feb 23 19:46:28 jak-t480s systemd[1]: Stopped User Login Management.
Feb 23 19:46:28 jak-t480s systemd[1]: systemd-logind.service: Consumed 58.715s CPU time.
Feb 23 19:46:28 jak-t480s systemd[1]: bluetooth.service: Main process exited, code=dumped, status=11/SEGV
Feb 23 19:46:28 jak-t480s systemd[1]: bluetooth.service: Failed with result 'core-dump'.
Feb 23 19:46:28 jak-t480s systemd[1]: Stopped Bluetooth service.
Feb 23 19:46:28 jak-t480s systemd[1]: bluetooth.service: Consumed 7.354s CPU time.
Feb 23 19:46:28 jak-t480s tracker-miner-fs-3[1756753]: OK
Feb 23 19:46:28 jak-t480s systemd[5652]: tracker-miner-fs-3.service: Consumed 35.727s CPU time.
Feb 23 19:46:28 jak-t480s google-chrome.desktop[2517568]: X connection to :0 broken (explicit kill or server shutdown).
Feb 23 19:46:28 jak-t480s gnome-session[6649]: gnome-session-binary[6649]: WARNING: App 'org.gnome.SettingsDaemon.Power.desktop' exited with code 1
Feb 23 19:46:28 jak-t480s gnome-session-binary[6649]: WARNING: App 'org.gnome.SettingsDaemon.Power.desktop' exited with code 1
Feb 23 19:46:28 jak-t480s gnome-session[6649]: gnome-session-binary[6649]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 1
Feb 23 19:46:28 jak-t480s gnome-session-binary[6649]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 1
Feb 23 19:46:28 jak-t480s gnome-session[6649]: gnome-session-binary[6649]: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
Feb 23 19:46:28 jak-t480s gnome-session-binary[6649]: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
Feb 23 19:46:28 jak-t480s gnome-session[6649]: gnome-session-binary[6649]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
Feb 23 19:46:28 jak-t480s gnome-session-binary[6649]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
Feb 23 19:46:28 jak-t480s gnome-session[6649]: gnome-session-binary[6649]: WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1
Feb 23 19:46:28 jak-t480s gnome-session-binary[6649]: WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1
Feb 23 19:46:28 jak-t480s gnome-session[6649]: gnome-session-binary[6649]: WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' exited with code 1
Feb 23 19:46:28 jak-t480s gnome-session-binary[6649]: WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' exited with code 1
Feb 23 19:46:28 jak-t480s systemd[5652]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 19:46:28 jak-t480s systemd[5652]: gnome-terminal-server.service: Failed with result 'exit-code'.
Feb 23 19:46:28 jak-t480s systemd[5652]: gnome-terminal-server.service: Consumed 9min 42.737s CPU time.
Feb 23 19:46:28 jak-t480s systemd[5652]: xdg-desktop-portal-gnome.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 19:46:28 jak-t480s systemd[5652]: xdg-desktop-portal-gnome.service: Failed with result 'exit-code'.
Feb 23 19:46:28 jak-t480s systemd[5652]: xdg-desktop-portal-gnome.service: Consumed 1min 25.408s CPU time.
Feb 23 19:46:28 jak-t480s ibus-daemon[7478]: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). See the documentation of g_child_watch_source_new() for possible causes.
Feb 23 19:46:28 jak-t480s thermald[3166]: terminating on user request ..
Feb 23 19:46:29 jak-t480s systemd[1]: udisks2.service: Main process exited, code=dumped, status=6/ABRT
Feb 23 19:46:29 jak-t480s systemd[1]: udisks2.service: Failed with result 'core-dump'.
Feb 23 19:46:29 jak-t480s systemd[1]: Stopped Disk Manager.
Feb 23 19:46:29 jak-t480s systemd[1]: udisks2.service: Consumed 8.386s CPU time.
Feb 23 19:46:29 jak-t480s systemd[5652]: keybase.gui.service: Main process exited, code=killed, status=5/TRAP
Feb 23 19:46:29 jak-t480s systemd[5652]: keybase.gui.service: Failed with result 'signal'.
Feb 23 19:46:29 jak-t480s systemd[5652]: keybase.gui.service: Unit process 1726309 (Keybase) remains running after unit stopped.
Feb 23 19:46:29 jak-t480s systemd[5652]: keybase.gui.service: Unit process 1726344 (Keybase) remains running after unit stopped.
Feb 23 19:46:29 jak-t480s systemd[5652]: keybase.gui.service: Consumed 7min 2.615s CPU time.
Feb 23 19:46:29 jak-t480s gsd-smartcard[7689]: Error releasing name org.gnome.SettingsDaemon.Smartcard: The connection is closed
Feb 23 19:46:29 jak-t480s gsd-sound[7700]: Error releasing name org.gnome.SettingsDaemon.Sound: The connection is closed
Feb 23 19:46:29 jak-t480s gsd-datetime[7685]: Error releasing name org.gnome.SettingsDaemon.Datetime: The connection is closed
Feb 23 19:46:29 jak-t480s gsd-screensaver[7673]: Error releasing name org.gnome.SettingsDaemon.ScreensaverProxy: The connection is closed
Feb 23 19:46:29 jak-t480s gsd-housekeepin[7698]: Error releasing name org.gnome.SettingsDaemon.Housekeeping: The connection is closed
Feb 23 19:46:29 jak-t480s gvfsd[1745321]: A connection to the bus can't be made
Feb 23 19:46:29 jak-t480s gvfsd[1745298]: A connection to the bus can't be made
Feb 23 19:46:29 jak-t480s gvfsd[1757042]: A connection to the bus can't be made
Feb 23 19:46:29 jak-t480s gvfsd[3168588]: A connection to the bus can't be made
Feb 23 19:46:29 jak-t480s gvfsd[1971845]: A connection to the bus can't be made
Feb 23 19:46:29 jak-t480s gvfsd[3168827]: A connection to the bus can't be made
Feb 23 19:46:29 jak-t480s wireplumber[5943]: [string "policy-bluetooth.lua"]:121: bad argument #1 to 'find' (string expected, got nil)
Feb 23 19:46:29 jak-t480s systemd[5652]: Stopping D-Bus User Message Bus...
Feb 23 19:46:29 jak-t480s systemd[1]: run-user-1000-doc.mount: Deactivated successfully.
Feb 23 19:46:29 jak-t480s google-chrome.desktop[2517568]: [0223/194629.505347:ERROR:scoped_ptrace_attach.cc(37)] process not stopped
Feb 23 19:46:29 jak-t480s systemd[1]: run-user-1000-gvfs.mount: Deactivated successfully.
Feb 23 19:46:29 jak-t480s io.snapcraft.Settings[1205942]: Exiting on terminated.
Feb 23 19:46:29 jak-t480s systemd[5652]: dbus.service: Killing process 7591 (JS Helper) with signal SIGKILL.
Feb 23 19:46:29 jak-t480s systemd[5652]: xdg-document-portal.service: Main process exited, code=exited, status=20/n/a
Feb 23 19:46:29 jak-t480s systemd[5652]: xdg-document-portal.service: Failed with result 'exit-code'.
Feb 23 19:46:29 jak-t480s systemd[5652]: xdg-document-portal.service: Consumed 4.176s CPU time.
Feb 23 19:46:29 jak-t480s systemd[5652]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 19:46:29 jak-t480s systemd[5652]: xdg-permission-store.service: Failed with result 'exit-code'.
Feb 23 19:46:29 jak-t480s systemd[5652]: at-spi-dbus-bus.service: Consumed 1min 38.437s CPU time.
Feb 23 19:46:29 jak-t480s systemd[5652]: gvfs-afc-volume-monitor.service: Consumed 45.951s CPU time.
Feb 23 19:46:29 jak-t480s systemd[5652]: dconf.service: Consumed 4.195s CPU time.
Feb 23 19:46:29 jak-t480s systemd[5652]: gvfs-metadata.service: Consumed 1.179s CPU time.
Feb 23 19:46:29 jak-t480s systemd[5652]: gvfs-daemon.service: Consumed 5.874s CPU time.
Feb 23 19:46:29 jak-t480s systemd[5652]: flatpak-session-helper.service: Main process exited, code=exited, status=1/FAILURE
Feb 23 19:46:29 jak-t480s systemd[5652]: flatpak-session-helper.service: Failed with result 'exit-code'.
Feb 23 19:46:29 jak-t480s systemd[5652]: Stopped D-Bus User Message Bus.
Feb 23 19:46:29 jak-t480s systemd[5652]: dbus.service: Consumed 36min 49.057s CPU time.
Feb 23 19:46:29 jak-t480s systemd[5652]: Started D-Bus User Message Bus.
Feb 23 19:46:29 jak-t480s dbus-daemon[3059334]: [session uid=1000 pid=3059334] AppArmor D-Bus mediation is enabled
Feb 23 19:46:29 jak-t480s systemd[1]: thermald.service: Deactivated successfully.
Feb 23 19:46:29 jak-t480s systemd[1]: Stopped Thermal Daemon Service.
Feb 23 19:46:29 jak-t480s systemd[1]: thermald.service: Consumed 41min 47.204s CPU time.
Feb 23 19:46:29 jak-t480s systemd[1]: dbus.socket: Deactivated successfully.
Feb 23 19:46:29 jak-t480s systemd[1]: Closed D-Bus System Message Bus Socket.
Feb 23 19:46:44 jak-t480s dbus-daemon[3059334]: [session uid=1000 pid=3059334] Reloaded configuration
Feb 23 19:46:44 jak-t480s dbus-daemon[3059334]: [session uid=1000 pid=3059334] Reloaded configuration
Feb 23 19:46:44 jak-t480s dbus-daemon[3059334]: [session uid=1000 pid=3059334] Reloaded configuration
Feb 23 19:46:44 jak-t480s dbus-daemon[3059334]: [session uid=1000 pid=3059334] Reloaded configuration
Feb 23 19:46:44 jak-t480s dbus-daemon[3059334]: [session uid=1000 pid=3059334] Reloaded configuration
Feb 23 19:46:44 jak-t480s dbus-daemon[3059334]: [session uid=1000 pid=3059334] Reloaded configuration
Feb 23 19:46:44 jak-t480s dbus-daemon[3059334]: [session uid=1000 pid=3059334] Reloaded configuration
Feb 23 19:46:48 jak-t480s systemd[1]: session-2.scope: Deactivated successfully.
Feb 23 19:46:48 jak-t480s systemd[1]: session-2.scope: Consumed 3d 1h 7min 59.713s CPU time.
Feb 23 19:46:53 jak-t480s dbus-daemon[3059334]: [session uid=1000 pid=3059334] Reloaded configuration
Feb 23 19:46:53 jak-t480s dbus-daemon[3059334]: [session uid=1000 pid=3059334] Reloaded configuration
Feb 23 19:46:53 jak-t480s dbus-daemon[3059334]: [session uid=1000 pid=3059334] Reloaded configuration