Ubuntu 22.04.5 LTS old pc, and 24.04.1, Uefi pc

What are the errors?

Hi Andrew
I have some answers to your question, but I would like to send some .txt files
Can't find how to do it?
 // M@ts

This is a text based system... Just paste the contents

Hello

Ubuntu 22.04.5 LTS

Here is my little one AI routine to find errors. All problems are in the log file.
1. Search all variants for possible errors. Ex. The log file name is Log-2024-11-20_2024-11-22.txt

Then run cat Log-2024-11-20_2024-11-22.txt | grep link > Info-link.txt

2. If you find something extra interesting there
then you can go ahead and run on the date, the time, in seconds or minutes, Ex. below on 1 becomes 10-19 sec.
 cat Log-2024-11-20_2024-11-22.txt | grep "Nov 21 11:06:1" > "Info-link-Nov 21 11:06:1".txt
This is now very easy to find all ev. problem.

You can see that very many processes start before the Boot part is finished and must be put on the waiting list.
in some cases it is some process to be killed and sometimes it tears down the rest of the waiting ones,
and then it all starts again. Now it's going to be a huge mess.

To avoid this, no processes should start before the Boot part is finished.
The files are examples of things I've been looking for, Info-xxxx

More strange things,
why are some objects tested like MTP, if there are none, that test should be last, same thing with disks,
I have seen that sometimes the system searches for almost all file system types that exist before a hit. etc. etc. etc.

NOTE Today the above happened, on another PC: Ubuntu 24.04.1 LTS
This pc currently has no keyboard, thanks for the on-screen keyboard option
 (away with corded mouse, network cable, reboot KB. ok, the choice is KB: or Wifi)

See Log syslog-24.04.1_LTS

The disaster begins on 2024-11-25T09:08:14
Now the system thinks we have to restart, and shuts down everything,
when everything is stopped we will reboot 2024-11-25T09:09:06
You can see for yourself what it looks like after a fresh start with all possible options. consequential error.

// M@ts

/home/mats/0-Work/syslog-24.04.1_LTS
/home/mats/0-Work/Info-snap.txt
/home/mats/0-Work/Info-crash.txt
/home/mats/0-Work/Info-link-Nov 21 11:06:1.txt
/home/mats/0-Work/Info-link.txt
/home/mats/0-Work/Info-restor.txt
/home/mats/0-Work/Info-tracker.txt
/home/mats/0-Work/Info-power.txt
/home/mats/0-Work/Info-Sorry.txt
/home/mats/0-Work/Info-Kill.txt
/home/mats/0-Work/Info-warning.txt
/home/mats/0-Work/Info-Warning.txt
/home/mats/0-Work/Info-Tracker.txt
/home/mats/0-Work/Info-OOM.txt
/home/mats/0-Work/Log-2024-11-20_2024-11-22.txt

Shouldn't send the content without the files, ok an example.

Nov 21 11:17:24 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 11:17:25 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 11:17:25 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 11:17:25 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 11:17:25 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 11:17:26 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 11:17:26 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 11:17:26 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 11:17:26 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 11:17:26 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 11:17:26 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 11:17:28 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 11:17:28 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 11:17:28 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 11:17:28 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 11:17:28 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 11:17:34 OptiPlex gnome-shell[1456]: DING: (org.gnome.Nautilus:2038): Tracker-WARNING **: 11:17:34.523: Could not delete '.meta.isrunning': No such file or directory
Nov 21 16:33:25 OptiPlex nautilus[8933]: Connecting to org.freedesktop.Tracker3.Miner.Files
Nov 21 16:33:25 OptiPlex dbus-daemon[1313]: [session uid=1000 pid=1313] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Files' unit='tracker-miner-fs-3.service' requested by ':1.159' (uid=1000 pid=8933 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
Nov 21 16:33:25 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 16:33:26 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 16:33:26 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 16:33:26 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 16:33:26 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 16:33:26 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 16:33:26 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 16:33:27 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 16:33:27 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 16:33:27 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 16:33:27 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 16:33:28 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 16:33:28 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 16:33:28 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 16:33:28 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 16:33:28 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 16:33:55 OptiPlex nautilus[8933]: Unable to create connection for session-wide Tracker indexer: Tidsgränsen uppnåddes
Nov 21 16:33:55 OptiPlex nautilus[8933]: Could not establish a connection to Tracker: Tidsgränsen uppnåddes
Nov 21 16:33:55 OptiPlex nautilus[8933]: message repeated 3 times: [ Could not establish a connection to Tracker: Tidsgränsen uppnåddes]

Here comes info about the files

Info-Sorry

Nov 21 11:06:18 OptiPlex snapd-desktop-integration.snapd-desktop-integration[810]: Sorry, home directories outside of /home needs configuration.
Nov 22 12:18:17 OptiPlex snapd-desktop-integration.snapd-desktop-integration[809]: Sorry, home directories outside of /home needs configuration.

Info-OOM

Nov 21 11:06:14 OptiPlex systemd[1]: Starting Userspace Out-Of-Memory (OOM) Killer...
Nov 21 11:06:14 OptiPlex systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
Nov 22 12:18:13 OptiPlex systemd[1]: Starting Userspace Out-Of-Memory (OOM) Killer...
Nov 22 12:18:13 OptiPlex systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.

Info-Kill

Nov 21 00:10:45 OptiPlex systemd[1245]: Stopped target GNOME RFKill support target.
Nov 21 00:10:45 OptiPlex systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Nov 21 11:06:14 OptiPlex systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Nov 21 11:06:14 OptiPlex systemd[1]: Starting Userspace Out-Of-Memory (OOM) Killer...
Nov 21 11:06:14 OptiPlex systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
Nov 21 11:17:21 OptiPlex systemd[1287]: Starting GNOME RFKill support service...
Nov 21 11:17:22 OptiPlex systemd[1287]: Started GNOME RFKill support service.
Nov 21 11:17:22 OptiPlex systemd[1287]: Reached target GNOME RFKill support target.
Nov 21 17:50:59 OptiPlex systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 21 17:50:59 OptiPlex systemd[1]: Started Load/Save RF Kill Switch Status.
Nov 21 18:21:25 OptiPlex systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 21 18:21:25 OptiPlex systemd[1]: Started Load/Save RF Kill Switch Status.
Nov 21 18:21:33 OptiPlex systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 21 18:21:33 OptiPlex systemd[1]: Started Load/Save RF Kill Switch Status.
Nov 22 02:10:56 OptiPlex systemd[1287]: Stopped target GNOME RFKill support target.
Nov 22 02:10:58 OptiPlex systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Nov 22 12:18:13 OptiPlex systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Nov 22 12:18:13 OptiPlex systemd[1]: Starting Userspace Out-Of-Memory (OOM) Killer...
Nov 22 12:18:13 OptiPlex systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.

Info-warning

Sorry bad Swedish translation at system level,
can't understand Clutter, mutter

Nov 20 23:38:33 OptiPlex kernel: [ 764.507626] capability: warning: `gvfsd-admin' uses 32-bit capabilities (legacy support in use)
Nov 20 23:59:08 OptiPlex gnome-shell[1405]: Window manager warning: last_user_time (1999990) is greater than comparison timestamp (1999955). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Nov 20 23:59:08 OptiPlex gnome-shell[1405]: Window manager warning: W18 appears to be one of the offending windows with a timestamp of 1999990. Working around...
Nov 21 00:00:04 OptiPlex gnome-shell[1405]: Window manager warning: last_user_time (2055991) is greater than comparison timestamp (2055960). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Nov 21 00:00:04 OptiPlex gnome-shell[1405]: Window manager warning: W18 appears to be one of the offending windows with a timestamp of 2055991. Working around...
Nov 21 00:01:01 OptiPlex gnome-shell[1405]: Window manager warning: last_user_time (2112986) is greater than comparison timestamp (2112956). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Nov 21 00:01:01 OptiPlex gnome-shell[1405]: Window manager warning: W18 appears to be one of the offending windows with a timestamp of 2112986. Working around...
Nov 21 11:06:22 OptiPlex org.gnome.Shell.desktop[864]: Window manager warning: Failed to parse saved session file: Misslyckades med att öppna filen ”/var/lib/gdm3/.config/mutter/sessions/10e54e0b953e5d4092173218357757739500000008240000.ms”: Filen eller katalogen finns inte
Nov 21 11:17:23 OptiPlex gnome-shell[1456]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Nov 21 11:17:23 OptiPlex gnome-shell[1456]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Nov 21 11:17:23 OptiPlex gnome-shell[1456]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Nov 21 11:17:23 OptiPlex gnome-shell[1456]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Nov 21 11:17:23 OptiPlex gnome-shell[1456]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Nov 21 11:17:23 OptiPlex gnome-shell[1456]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Nov 21 11:17:23 OptiPlex gnome-shell[1456]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Nov 21 11:17:23 OptiPlex gnome-shell[1456]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Nov 21 11:17:23 OptiPlex gnome-shell[1456]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Nov 21 13:27:35 OptiPlex gnome-shell[1456]: Window manager warning: Ping serial 8494310 was reused for window W0, previous use was for window W3.
Nov 21 18:21:25 OptiPlex kernel: [26123.782872] warning: `iwconfig' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
Nov 22 12:18:21 OptiPlex org.gnome.Shell.desktop[864]: Window manager warning: Failed to parse saved session file: Misslyckades med att öppna filen ”/var/lib/gdm3/.config/mutter/sessions/109cd966dad4e2967e173227429651669000000008250000.ms”: Filen eller katalogen finns inte

Capital letter W
 Info-Warning

Nov 21 11:06:14 OptiPlex kernel: [ 0.330050] ACPI BIOS Warning (bug): Incorrect checksum in table [TCPA] - 0x00, should be 0xFFFFFF78 (20230628/utcksum-58)
Nov 21 11:06:14 OptiPlex kernel: [ 3.254803] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x000000000000082A-0x000000000000082A (\GIC3) (20230628/utaddress-204)
Nov 21 11:06:14 OptiPlex kernel: [ 3.254826] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x0000000000000828-0x000000000000082D (\GLBC) (20230628/utaddress-204)
Nov 21 11:06:14 OptiPlex kernel: [ 3.254838] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x000000000000082A-0x000000000000082A (\SACT) (20230628/utaddress-204)
Nov 21 11:06:14 OptiPlex kernel: [ 3.254849] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x0000000000000828-0x0000000000000828 (\SSTS) (20230628/utaddress-204)
Nov 21 11:06:14 OptiPlex kernel: [ 3.254866] ACPI Warning: SystemIO range 0x00000000000008B0-0x00000000000008BF conflicts with OpRegion 0x00000000000008B9-0x00000000000008B9 (\GHI5) (20230628/utaddress-204)
Nov 21 11:06:14 OptiPlex kernel: [ 3.254877] ACPI Warning: SystemIO range 0x00000000000008B0-0x00000000000008BF conflicts with OpRegion 0x00000000000008B8-0x00000000000008B8 (\GHI0) (20230628/utaddress-204)
Nov 21 11:06:14 OptiPlex kernel: [ 3.254891] ACPI Warning: SystemIO range 0x0000000000000880-0x00000000000008AF conflicts with OpRegion 0x000000000000088C-0x000000000000088C (\GIC2) (20230628/utaddress-204)
Nov 21 11:06:14 OptiPlex kernel: [ 3.254904] ACPI Warning: SystemIO range 0x0000000000000880-0x00000000000008AF conflicts with OpRegion 0x000000000000088F-0x000000000000088F (\GIU3) (20230628/utaddress-204)
Nov 21 11:06:14 OptiPlex kernel: [ 3.254914] ACPI Warning: SystemIO range 0x0000000000000880-0x00000000000008AF conflicts with OpRegion 0x000000000000088E-0x000000000000088E (\GIC1) (20230628/utaddress-204)
Nov 21 11:06:27 OptiPlex org.gnome.Shell.desktop[1180]: > Warning: Unsupported maximum keycode 708, clipping.
Nov 21 11:22:41 OptiPlex org.debian.apt[3072]: /usr/lib/python3/dist-packages/aptdaemon/worker/pkworker.py:35: PyGIWarning: PackageKitGlib was imported without specifying a version first. Use gi.require_version('PackageKitGlib', '1.0') before import to ensure that the right version gets loaded.
Nov 21 11:22:47 OptiPlex gnome-shell[3130]: > Warning: Unsupported maximum keycode 708, clipping.
Nov 21 11:22:56 OptiPlex org.debian.apt[3072]: /usr/lib/python3/dist-packages/aptdaemon/progress.py:490: Warning: Source ID 26 was not found when attempting to remove it
Nov 21 11:22:56 OptiPlex org.debian.apt[3072]: /usr/lib/python3/dist-packages/aptdaemon/progress.py:490: Warning: Source ID 27 was not found when attempting to remove it
Nov 22 12:18:13 OptiPlex kernel: [ 0.330220] ACPI BIOS Warning (bug): Incorrect checksum in table [TCPA] - 0x00, should be 0xFFFFFF78 (20230628/utcksum-58)
Nov 22 12:18:13 OptiPlex kernel: [ 3.245504] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x000000000000082A-0x000000000000082A (\GIC3) (20230628/utaddress-204)
Nov 22 12:18:13 OptiPlex kernel: [ 3.245528] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x0000000000000828-0x000000000000082D (\GLBC) (20230628/utaddress-204)
Nov 22 12:18:13 OptiPlex kernel: [ 3.245540] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x000000000000082A-0x000000000000082A (\SACT) (20230628/utaddress-204)
Nov 22 12:18:13 OptiPlex kernel: [ 3.245554] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082F conflicts with OpRegion 0x0000000000000828-0x0000000000000828 (\SSTS) (20230628/utaddress-204)
Nov 22 12:18:13 OptiPlex kernel: [ 3.247789] ACPI Warning: SystemIO range 0x00000000000008B0-0x00000000000008BF conflicts with OpRegion 0x00000000000008B9-0x00000000000008B9 (\GHI5) (20230628/utaddress-204)
Nov 22 12:18:13 OptiPlex kernel: [ 3.247807] ACPI Warning: SystemIO range 0x00000000000008B0-0x00000000000008BF conflicts with OpRegion 0x00000000000008B8-0x00000000000008B8 (\GHI0) (20230628/utaddress-204)
Nov 22 12:18:13 OptiPlex kernel: [ 3.247823] ACPI Warning: SystemIO range 0x0000000000000880-0x00000000000008AF conflicts with OpRegion 0x000000000000088C-0x000000000000088C (\GIC2) (20230628/utaddress-204)
Nov 22 12:18:13 OptiPlex kernel: [ 3.247834] ACPI Warning: SystemIO range 0x0000000000000880-0x00000000000008AF conflicts with OpRegion 0x000000000000088F-0x000000000000088F (\GIU3) (20230628/utaddress-204)
Nov 22 12:18:13 OptiPlex kernel: [ 3.247845] ACPI Warning: SystemIO range 0x0000000000000880-0x00000000000008AF conflicts with OpRegion 0x000000000000088E-0x000000000000088E (\GIC1) (20230628/utaddress-204)

Info-power

Nov 21 00:10:45 OptiPlex systemd[1245]: Stopped target GNOME power management target.
Nov 21 00:10:45 OptiPlex systemd[1245]: Stopping GNOME power management service...
Nov 21 11:06:14 OptiPlex kernel: [ 0.518754] thermal_sys: Registered thermal governor 'power_allocator'
Nov 21 11:06:14 OptiPlex dbus-daemon[619]: dbus[619]: Unknown group "power" in message bus configuration file
Nov 21 11:06:14 OptiPlex NetworkManager[620]: <info> [1732183574.0611] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (run: 10-globally-managed-devices.conf) (etc: default-wifi-powersave-on.conf)
Nov 21 11:06:14 OptiPlex kernel: [ 8.070029] intel_powerclamp: No package C-state available
Nov 21 11:06:21 OptiPlex dbus-daemon[619]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.37' (uid=128 pid=864 comm="/usr/bin/gnome-shell " label="unconfined")
Nov 21 11:06:21 OptiPlex systemd[1]: Starting Daemon for power management...
Nov 21 11:06:22 OptiPlex systemd[1]: Started Daemon for power management.
Nov 21 11:06:26 OptiPlex /usr/libexec/gdm-wayland-session[823]: dbus-daemon[823]: [session uid=128 pid=823] Activating service name='org.gnome.ScreenSaver' requested by ':1.23' (uid=128 pid=993 comm="/usr/libexec/gsd-power " label="unconfined")
Nov 21 11:17:21 OptiPlex systemd[1287]: Starting GNOME power management service...
Nov 21 11:17:24 OptiPlex systemd[1287]: Started GNOME power management service.
Nov 21 11:17:24 OptiPlex systemd[1287]: Reached target GNOME power management target.
Nov 21 11:17:26 OptiPlex dbus-daemon[1313]: [session uid=1000 pid=1313] Activating service name='org.gnome.ScreenSaver' requested by ':1.57' (uid=1000 pid=1664 comm="/usr/libexec/gsd-power " label="unconfined")

This has been visible for at least 5 years // M@ts
======================================

Nov 21 16:30:56 OptiPlex dbus-daemon[619]: Unknown group "power" in message bus configuration file
Nov 21 16:30:56 OptiPlex dbus-daemon[619]: Unknown group "power" in message bus configuration file
Nov 21 16:30:58 OptiPlex dbus-daemon[619]: Unknown group "power" in message bus configuration file
Nov 21 16:30:58 OptiPlex dbus-daemon[619]: Unknown group "power" in message bus configuration file
Nov 22 02:10:56 OptiPlex systemd[1287]: Stopped target GNOME power management target.
Nov 22 02:10:56 OptiPlex systemd[1287]: Stopping GNOME power management service...
Nov 22 02:10:58 OptiPlex systemd[1287]: Stopped GNOME power management service.
Nov 22 02:10:58 OptiPlex systemd[1]: Stopping Daemon for power management...
Nov 22 12:18:13 OptiPlex kernel: [ 0.518849] thermal_sys: Registered thermal governor 'power_allocator'
Nov 22 12:18:13 OptiPlex dbus-daemon[619]: dbus[619]: Unknown group "power" in message bus configuration file
Nov 22 12:18:13 OptiPlex NetworkManager[620]: <info> [1732274293.0619] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (run: 10-globally-managed-devices.conf) (etc: default-wifi-powersave-on.conf)
Nov 22 12:18:13 OptiPlex kernel: [ 8.164672] intel_powerclamp: No package C-state available
Nov 22 12:18:20 OptiPlex dbus-daemon[619]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.37' (uid=128 pid=864 comm="/usr/bin/gnome-shell " label="unconfined")
Nov 22 12:18:20 OptiPlex systemd[1]: Starting Daemon for power management...
Nov 22 12:18:21 OptiPlex systemd[1]: Started Daemon for power management.

Capital letter T

Info-Tracker

Nov 21 11:17:24 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 11:17:25 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 11:17:25 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 11:17:25 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 11:17:25 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 11:17:26 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 11:17:26 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 11:17:26 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 11:17:26 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 11:17:26 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 11:17:26 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 11:17:28 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 11:17:28 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 11:17:28 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 11:17:28 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 11:17:28 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 11:17:34 OptiPlex gnome-shell[1456]: DING: (org.gnome.Nautilus:2038): Tracker-WARNING **: 11:17:34.523: Could not delete '.meta.isrunning': No such file or directory
Nov 21 16:33:25 OptiPlex nautilus[8933]: Connecting to org.freedesktop.Tracker3.Miner.Files
Nov 21 16:33:25 OptiPlex dbus-daemon[1313]: [session uid=1000 pid=1313] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Files' unit='tracker-miner-fs-3.service' requested by ':1.159' (uid=1000 pid=8933 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
Nov 21 16:33:25 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 16:33:26 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 16:33:26 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 16:33:26 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 16:33:26 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 16:33:26 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 16:33:26 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 16:33:27 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 16:33:27 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 16:33:27 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 16:33:27 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 16:33:28 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 16:33:28 OptiPlex systemd[1287]: Starting Tracker file system data miner...
Nov 21 16:33:28 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 16:33:28 OptiPlex systemd[1287]: Stopped Tracker file system data miner.
Nov 21 16:33:28 OptiPlex systemd[1287]: Failed to start Tracker file system data miner.
Nov 21 16:33:55 OptiPlex nautilus[8933]: Unable to create connection for session-wide Tracker indexer: Tidsgränsen uppnåddes
Nov 21 16:33:55 OptiPlex nautilus[8933]: Could not establish a connection to Tracker: Tidsgränsen uppnåddes
Nov 21 16:33:55 OptiPlex nautilus[8933]: message repeated 3 times: [ Could not establish a connection to Tracker: Tidsgränsen uppnåddes]

Info-tracker

Nov 21 11:17:25 OptiPlex tracker-miner-f[1841]: Could not delete '.meta.isrunning': Filen eller katalogen finns inte
Nov 21 11:17:25 OptiPlex tracker-miner-f[1841]: Could not create store/endpoint: Database version is too new: got version 28, but 26 is needed
Nov 21 11:17:25 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 11:17:25 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Failed with result 'exit-code'.
Nov 21 11:17:25 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 1.
Nov 21 11:17:25 OptiPlex tracker-miner-f[1850]: Could not delete '.meta.isrunning': Filen eller katalogen finns inte
Nov 21 11:17:25 OptiPlex tracker-miner-f[1850]: Could not create store/endpoint: Database version is too new: got version 28, but 26 is needed
Nov 21 11:17:25 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 11:17:25 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Failed with result 'exit-code'.
Nov 21 11:17:26 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 2.
Nov 21 11:17:26 OptiPlex tracker-miner-f[1858]: Could not delete '.meta.isrunning': Filen eller katalogen finns inte
Nov 21 11:17:26 OptiPlex tracker-miner-f[1858]: Could not create store/endpoint: Database version is too new: got version 28, but 26 is needed
Nov 21 11:17:26 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 11:17:26 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Failed with result 'exit-code'.
Nov 21 11:17:26 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 3.
Nov 21 11:17:26 OptiPlex tracker-miner-f[1877]: Could not delete '.meta.isrunning': Filen eller katalogen finns inte
Nov 21 11:17:26 OptiPlex tracker-miner-f[1877]: Could not create store/endpoint: Database version is too new: got version 28, but 26 is needed
Nov 21 11:17:26 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 11:17:26 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Failed with result 'exit-code'.
Nov 21 11:17:26 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 4.
Nov 21 11:17:28 OptiPlex tracker-miner-f[1921]: Could not delete '.meta.isrunning': Filen eller katalogen finns inte
Nov 21 11:17:28 OptiPlex tracker-miner-f[1921]: Could not create store/endpoint: Database version is too new: got version 28, but 26 is needed
Nov 21 11:17:28 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 11:17:28 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Failed with result 'exit-code'.
Nov 21 11:17:28 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 5.
Nov 21 11:17:28 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Start request repeated too quickly.
Nov 21 11:17:28 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Failed with result 'exit-code'.
Nov 21 16:33:25 OptiPlex dbus-daemon[1313]: [session uid=1000 pid=1313] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Files' unit='tracker-miner-fs-3.service' requested by ':1.159' (uid=1000 pid=8933 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
Nov 21 16:33:25 OptiPlex tracker-miner-f[9029]: Could not delete '.meta.isrunning': Filen eller katalogen finns inte
Nov 21 16:33:25 OptiPlex tracker-miner-f[9029]: Could not create store/endpoint: Database version is too new: got version 28, but 26 is needed
Nov 21 16:33:25 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 16:33:25 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Failed with result 'exit-code'.
Nov 21 16:33:26 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 1.
Nov 21 16:33:26 OptiPlex tracker-miner-f[9041]: Could not delete '.meta.isrunning': Filen eller katalogen finns inte
Nov 21 16:33:26 OptiPlex tracker-miner-f[9041]: Could not create store/endpoint: Database version is too new: got version 28, but 26 is needed
Nov 21 16:33:26 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 16:33:26 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Failed with result 'exit-code'.
Nov 21 16:33:26 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 2.
Nov 21 16:33:27 OptiPlex tracker-miner-f[9050]: Could not delete '.meta.isrunning': Filen eller katalogen finns inte
Nov 21 16:33:27 OptiPlex tracker-miner-f[9050]: Could not create store/endpoint: Database version is too new: got version 28, but 26 is needed
Nov 21 16:33:27 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 16:33:27 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Failed with result 'exit-code'.
Nov 21 16:33:27 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 3.
Nov 21 16:33:27 OptiPlex tracker-miner-f[9062]: Could not delete '.meta.isrunning': Filen eller katalogen finns inte
Nov 21 16:33:27 OptiPlex tracker-miner-f[9062]: Could not create store/endpoint: Database version is too new: got version 28, but 26 is needed
Nov 21 16:33:27 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 16:33:27 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Failed with result 'exit-code'.
Nov 21 16:33:28 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 4.
Nov 21 16:33:28 OptiPlex tracker-miner-f[9079]: Could not delete '.meta.isrunning': Filen eller katalogen finns inte
Nov 21 16:33:28 OptiPlex tracker-miner-f[9079]: Could not create store/endpoint: Database version is too new: got version 28, but 26 is needed
Nov 21 16:33:28 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 16:33:28 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Failed with result 'exit-code'.
Nov 21 16:33:28 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 5.
Nov 21 16:33:28 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Start request repeated too quickly.
Nov 21 16:33:28 OptiPlex systemd[1287]: tracker-miner-fs-3.service: Failed with result 'exit-code'.

Info-crash

Sorry bad Swedish translation at system level,
can't understand Clutter, mutter

Nov 21 00:10:45 OptiPlex systemd[1245]: Stopped Path trigger for Apport crash notifications.
Nov 21 00:10:45 OptiPlex systemd[1]: Stopping LSB: automatic crash report generation...
Nov 21 00:10:45 OptiPlex systemd[1]: Stopping Tool to automatically collect and submit kernel crash signatures...
Nov 21 00:10:45 OptiPlex gnome-shell[1405]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 21 11:06:14 OptiPlex systemd[1]: Started Start whoopsie on modification of the /var/crash directory.
Nov 21 11:06:14 OptiPlex systemd[1]: Condition check resulted in Unix socket for apport crash forwarding being skipped.
Nov 21 11:06:14 OptiPlex systemd[1]: Starting LSB: automatic crash report generation...
Nov 21 11:06:14 OptiPlex apport[614]: * Starting automatic crash report generation: apport
Nov 21 11:06:14 OptiPlex systemd[1]: Started LSB: automatic crash report generation.
Nov 21 11:06:24 OptiPlex systemd[1]: Starting Tool to automatically collect and submit kernel crash signatures...
Nov 21 11:06:24 OptiPlex systemd[1]: Started crash report submission.
Nov 21 11:06:24 OptiPlex systemd[1]: Started Tool to automatically collect and submit kernel crash signatures.
Nov 21 11:17:14 OptiPlex systemd[1287]: Started Path trigger for Apport crash notifications.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Nov 22 02:10:55 OptiPlex gnome-shell[1456]: 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.
Nov 22 02:10:56 OptiPlex systemd[1287]: Stopped Path trigger for Apport crash notifications.
Nov 22 02:10:58 OptiPlex systemd[1]: Stopping LSB: automatic crash report generation...
Nov 22 02:10:58 OptiPlex systemd[1]: Stopping Tool to automatically collect and submit kernel crash signatures...
Nov 22 12:18:13 OptiPlex systemd[1]: Started Start whoopsie on modification of the /var/crash directory.
Nov 22 12:18:13 OptiPlex systemd[1]: Condition check resulted in Unix socket for apport crash forwarding being skipped.
Nov 22 12:18:13 OptiPlex systemd[1]: Starting LSB: automatic crash report generation...
Nov 22 12:18:13 OptiPlex apport[614]: * Starting automatic crash report generation: apport
Nov 22 12:18:13 OptiPlex systemd[1]: Started LSB: automatic crash report generation.

Info-snap

Nov 21 00:06:43 OptiPlex systemd[1245]: Started snap.snap-store.ubuntu-software-f533d2be-1cde-440f-ac73-fade36c4f78e.scope.
Nov 21 00:06:43 OptiPlex kernel: [ 2454.696279] audit: type=1400 audit(1732144003.550:70): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=3539 comm="snap-confine" capability=12 capname="net_admin"
Nov 21 00:06:43 OptiPlex kernel: [ 2454.696303] audit: type=1400 audit(1732144003.550:71): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=3539 comm="snap-confine" capability=38 capname="perfmon"
Nov 21 11:06:14 OptiPlex systemd[1]: Mounting Mount unit for snap-store, revision 1113...
Nov 21 11:06:14 OptiPlex systemd[1]: Mounting Mount unit for snap-store, revision 1216...
Nov 21 11:06:14 OptiPlex systemd[1]: Mounting Mount unit for snapd, revision 21759...
Nov 21 11:06:14 OptiPlex systemd[1]: Mounting Mount unit for snapd-desktop-integration, revision 178...
Nov 21 11:06:14 OptiPlex systemd[1]: Mounting Mount unit for snapd-desktop-integration, revision 253...
Nov 21 11:06:14 OptiPlex systemd[1]: Mounted Mount unit for snap-store, revision 1113.
Nov 21 11:06:14 OptiPlex systemd[1]: Mounted Mount unit for snap-store, revision 1216.
Nov 21 11:06:14 OptiPlex systemd[1]: Mounted Mount unit for snapd, revision 21759.
Nov 21 11:06:14 OptiPlex systemd[1]: Mounted Mount unit for snapd-desktop-integration, revision 178.
Nov 21 11:06:14 OptiPlex systemd[1]: Mounted Mount unit for snapd-desktop-integration, revision 253.
Nov 21 11:06:14 OptiPlex systemd[1]: Reached target Mounted snaps.
Nov 21 11:06:14 OptiPlex systemd-udevd[326]: sda: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda' failed with exit code 1.
Nov 21 11:06:14 OptiPlex systemd-udevd[323]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1.
Nov 21 11:06:14 OptiPlex systemd-udevd[334]: sda4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda4' failed with exit code 1.
Nov 21 11:06:14 OptiPlex systemd-udevd[318]: sda3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda3' failed with exit code 1.
Nov 21 11:06:14 OptiPlex systemd-udevd[330]: sda2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda2' failed with exit code 1.
Nov 21 11:06:14 OptiPlex systemd-udevd[326]: sda1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda1' failed with exit code 1.
Nov 21 11:06:14 OptiPlex systemd[1]: Starting Load AppArmor profiles managed internally by snapd...
Nov 21 11:06:14 OptiPlex snapd-apparmor[560]: main.go:132: Loading profiles [/var/lib/snapd/apparmor/profiles/snap-confine.snapd.21759 /var/lib/snapd/apparmor/profiles/snap-update-ns.firefox /var/lib/snapd/apparmor/profiles/snap-update-ns.snap-store /var/lib/snapd/apparmor/profiles/snap-update-ns.snapd-desktop-integration /var/lib/snapd/apparmor/profiles/snap-update-ns.vlc /var/lib/snapd/apparmor/profiles/snap.firefox.firefox /var/lib/snapd/apparmor/profiles/snap.firefox.geckodriver /var/lib/snapd/apparmor/profiles/snap.firefox.hook.configure /var/lib/snapd/apparmor/profiles/snap.firefox.hook.disconnect-plug-host-hunspell /var/lib/snapd/apparmor/profiles/snap.firefox.hook.post-refresh /var/lib/snapd/apparmor/profiles/snap.snap-store.hook.configure /var/lib/snapd/apparmor/profiles/snap.snap-store.snap-store /var/lib/snapd/apparmor/profiles/snap.snap-store.ubuntu-software /var/lib/snapd/apparmor/profiles/snap.snap-store.ubuntu-software-local-file /var/lib/snapd/apparmor/profiles/snap.snapd-desktop-integration.hook.configure /var/lib/snapd/apparmor/profiles/snap.snapd-desktop-integration.snapd-desktop-integration /var/lib/snapd/apparmor/profiles/snap.vlc.vlc]
Nov 21 11:06:14 OptiPlex systemd[1]: Finished Load AppArmor profiles managed internally by snapd.
Nov 21 11:06:14 OptiPlex systemd[1]: Starting Socket activation for snappy daemon...
Nov 21 11:06:14 OptiPlex systemd[1]: Listening on Socket activation for snappy daemon.
Nov 21 11:06:14 OptiPlex systemd[1]: Starting Wait until snapd is fully seeded...
Nov 21 11:06:14 OptiPlex kernel: [ 5.062514] systemd[1]: /lib/systemd/system/snapd.service:23: Unknown key name 'RestartMode' in section 'Service', ignoring.
Nov 21 11:06:14 OptiPlex kernel: [ 5.454831] systemd[1]: Reached target Mounting snaps.
Nov 21 11:06:15 OptiPlex snapd[649]: overlord.go:271: Acquiring state lock file
Nov 21 11:06:15 OptiPlex snapd[649]: overlord.go:276: Acquired state lock file
Nov 21 11:06:15 OptiPlex snapd[649]: daemon.go:250: started snapd/2.65.3+22.04 (series 16; classic) ubuntu/22.04 (amd64) linux/6.8.0-49-generic.
Nov 21 11:06:15 OptiPlex snapd[649]: daemon.go:353: adjusting startup timeout by 1m20s (pessimistic estimate of 30s plus 5s per snap)
Nov 21 11:06:15 OptiPlex snapd[649]: backends.go:58: AppArmor status: apparmor is enabled and all features are available
Nov 21 11:06:16 OptiPlex systemd[800]: Listening on REST API socket for snapd user session agent.
Nov 21 11:06:16 OptiPlex systemd[800]: Started Service for snap application snapd-desktop-integration.snapd-desktop-integration.
Nov 21 11:06:17 OptiPlex dbus-daemon[817]: [session uid=128 pid=817] Activating via systemd: service name='org.freedesktop.portal.Documents' unit='xdg-document-portal.service' requested by ':1.2' (uid=128 pid=810 comm="/usr/bin/snap run snapd-desktop-integration " label="unconfined")
Nov 21 11:06:17 OptiPlex kernel: [ 15.340249] audit: type=1400 audit(1732183577.257:61): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=810 comm="snap-confine" capability=12 capname="net_admin"
Nov 21 11:06:17 OptiPlex kernel: [ 15.340263] audit: type=1400 audit(1732183577.257:62): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=810 comm="snap-confine" capability=38 capname="perfmon"
Nov 21 11:06:17 OptiPlex dbus-daemon[619]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.31' (uid=0 pid=649 comm="/usr/lib/snapd/snapd " label="unconfined")
Nov 21 11:06:17 OptiPlex systemd[1]: tmp-snap.rootfs_qxccLg.mount: Deactivated successfully.
Nov 21 11:06:17 OptiPlex systemd[1]: Finished Wait until snapd is fully seeded.
Nov 21 11:06:18 OptiPlex snapd-desktop-integration.snapd-desktop-integration[810]: Sorry, home directories outside of /home needs configuration.
Nov 21 11:06:18 OptiPlex snapd-desktop-integration.snapd-desktop-integration[810]: See https://forum.snapcraft.io/t/11209 for details.
Nov 21 11:06:18 OptiPlex systemd[800]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 11:06:18 OptiPlex systemd[800]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'.
Nov 21 11:11:18 OptiPlex dbus-daemon[619]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.31' (uid=0 pid=649 comm="/usr/lib/snapd/snapd " label="unconfined")
Nov 21 11:11:19 OptiPlex snapd[649]: storehelpers.go:1019: cannot refresh: snap has no updates available: "bare", "core18", "core22", "firefox", "gnome-42-2204", "gtk-common-themes", "snap-store", "snapd", "snapd-desktop-integration", "vlc"
Nov 21 11:17:14 OptiPlex systemd[1287]: Listening on REST API socket for snapd user session agent.
Nov 21 11:17:14 OptiPlex systemd[1287]: Started Service for snap application snapd-desktop-integration.snapd-desktop-integration.
Nov 21 11:17:14 OptiPlex dbus-daemon[1313]: [session uid=1000 pid=1313] Activating via systemd: service name='org.freedesktop.portal.Documents' unit='xdg-document-portal.service' requested by ':1.0' (uid=1000 pid=1298 comm="/usr/bin/snap run snapd-desktop-integration " label="unconfined")
Nov 21 11:17:17 OptiPlex snapd-desktop-i[1467]: Failed to do gtk init. Waiting for a new session with desktop capabilities.
Nov 21 11:17:17 OptiPlex snapd-desktop-i[1467]: Checking session /org/freedesktop/login1/session/c1...
Nov 21 11:17:17 OptiPlex snapd-desktop-i[1467]: Checking session /org/freedesktop/login1/session/_33...
Nov 21 11:17:17 OptiPlex snapd-desktop-i[1467]: Is a desktop session! Forcing a reload.
Nov 21 11:17:17 OptiPlex snapd-desktop-i[1467]: Loop exited. Forcing reload.
Nov 21 11:17:17 OptiPlex systemd[1287]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Consumed 1.551s CPU time.
Nov 21 11:17:19 OptiPlex systemd[1287]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Scheduled restart job, restart counter is at 1.
Nov 21 11:17:19 OptiPlex systemd[1287]: Stopped Service for snap application snapd-desktop-integration.snapd-desktop-integration.
Nov 21 11:17:19 OptiPlex systemd[1287]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Consumed 1.551s CPU time.
Nov 21 11:17:19 OptiPlex systemd[1287]: Started Service for snap application snapd-desktop-integration.snapd-desktop-integration.
Nov 21 11:17:23 OptiPlex snapd-desktop-i[1599]: New theme: gtk=Yaru icon=Yaru cursor=Yaru, sound=Yaru
Nov 21 11:17:23 OptiPlex snapd-desktop-i[1599]: All available theme snaps installed
Nov 21 11:17:24 OptiPlex systemd[1287]: Started snap.snap-store.ubuntu-software-53acb3a6-72ff-4ae5-9547-4cb70fde01c0.scope.
Nov 21 11:17:24 OptiPlex kernel: [ 682.631312] audit: type=1400 audit(1732184244.132:63): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=1797 comm="snap-confine" capability=12 capname="net_admin"
Nov 21 11:17:24 OptiPlex kernel: [ 682.631332] audit: type=1400 audit(1732184244.132:64): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=1797 comm="snap-confine" capability=38 capname="perfmon"
Nov 21 11:17:24 OptiPlex systemd[1]: tmp-snap.rootfs_PPjs4p.mount: Deactivated successfully.
Nov 21 11:17:28 OptiPlex dbus-daemon[1313]: [session uid=1000 pid=1313] Activating via systemd: service name='org.freedesktop.portal.Desktop' unit='xdg-desktop-portal.service' requested by ':1.81' (uid=1000 pid=1797 comm="/snap/snap-store/1216/usr/bin/snap-store --gapplic" label="snap.snap-store.ubuntu-software (enforce)")
Nov 21 11:17:34 OptiPlex dbus-daemon[619]: [system] Activating via systemd: service name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.108' (uid=1000 pid=1797 comm="/snap/snap-store/1216/usr/bin/snap-store --gapplic" label="snap.snap-store.ubuntu-software (enforce)")
Nov 21 11:17:35 OptiPlex snap-store[1797]: plugin fwupd took 1.5 seconds to do setup
Nov 21 11:17:35 OptiPlex kernel: [ 694.111787] audit: type=1107 audit(1732184255.617:65): pid=619 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/PolicyKit1/Authority" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.4" pid=1797 label="snap.snap-store.ubuntu-software" peer_pid=632 peer_label="unconfined"
Nov 21 11:17:35 OptiPlex kernel: [ 694.113621] audit: type=1107 audit(1732184255.619:66): pid=619 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/PolicyKit1/Authority" interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" mask="send" name=":1.4" pid=1797 label="snap.snap-store.ubuntu-software" peer_pid=632 peer_label="unconfined"
Nov 21 11:17:35 OptiPlex kernel: [ 694.129410] audit: type=1107 audit(1732184255.635:67): pid=619 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/PolicyKit1/Authority" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.4" pid=1797 label="snap.snap-store.ubuntu-software" peer_pid=632 peer_label="unconfined"
Nov 21 11:17:35 OptiPlex kernel: [ 694.130517] audit: type=1107 audit(1732184255.636:68): pid=619 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/PolicyKit1/Authority" interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" mask="send" name=":1.4" pid=1797 label="snap.snap-store.ubuntu-software" peer_pid=632 peer_label="unconfined"
Nov 21 11:17:35 OptiPlex snap-store[1797]: enabled plugins: fwupd, os-release, packagekit-refine-repos, packagekit-refresh, appstream, hardcoded-blocklist, hardcoded-popular, modalias, packagekit, rewrite-resource, provenance, snap, systemd-updates, generic-updates, provenance-license, icons
Nov 21 11:17:35 OptiPlex snap-store[1797]: disabled plugins: dpkg, dummy, fedora-langpacks, fedora-pkgdb-collections, repos
Nov 21 11:17:36 OptiPlex kernel: [ 695.128797] audit: type=1400 audit(1732184256.634:69): apparmor="DENIED" operation="open" class="file" profile="snap.snap-store.ubuntu-software" name="/etc/appstream.conf" pid=1797 comm="snap-store" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Nov 21 11:17:41 OptiPlex systemd[800]: Closed REST API socket for snapd user session agent.
Nov 21 11:18:06 OptiPlex kernel: [ 725.064509] audit: type=1326 audit(1732184286.569:70): auid=1000 uid=1000 gid=1000 ses=4 subj=snap.snap-store.ubuntu-software pid=1797 comm="pool-org.gnome." exe="/snap/snap-store/1216/usr/bin/snap-store" sig=0 arch=c000003e syscall=93 compat=0 ip=0x7f463ffbea9b code=0x50000
Nov 21 11:18:07 OptiPlex snap-store[1797]: adding wildcard app */*/*/org.gnome.Builder.desktop/* to plugin cache
Nov 21 11:18:07 OptiPlex snap-store[1797]: adding wildcard app */*/*/org.gnome.Calculator.desktop/* to plugin cache
Nov 21 11:18:07 OptiPlex snap-store[1797]: adding wildcard app */*/*/org.gnome.clocks.desktop/* to plugin cache
Nov 21 11:18:07 OptiPlex snap-store[1797]: adding wildcard app */*/*/org.gnome.Dictionary.desktop/* to plugin cache
Nov 21 11:18:07 OptiPlex snap-store[1797]: adding wildcard app */*/*/org.gnome.Documents.desktop/* to plugin cache
Nov 21 11:18:07 OptiPlex snap-store[1797]: adding wildcard app */*/*/org.gnome.Evince/* to plugin cache
Nov 21 11:18:07 OptiPlex snap-store[1797]: adding wildcard app */*/*/org.gnome.gedit.desktop/* to plugin cache
Nov 21 11:18:07 OptiPlex snap-store[1797]: adding wildcard app */*/*/org.gnome.Maps.desktop/* to plugin cache
Nov 21 11:18:07 OptiPlex snap-store[1797]: adding wildcard app */*/*/org.gnome.Weather/* to plugin cache
Nov 21 11:18:07 OptiPlex snap-store[1797]: Only 0 apps for recent list, hiding
Nov 21 11:18:08 OptiPlex snapd[649]: storehelpers.go:1019: cannot refresh: snap has no updates available: "bare", "core18", "core22", "firefox", "gnome-42-2204", "gtk-common-themes", "snap-store", "snapd", "snapd-desktop-integration", "vlc"
Nov 21 11:18:10 OptiPlex snap-store[1797]: not handling error failed for action refresh: E: Misslyckades med att hämta http://se.archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease #012E: Misslyckades med att hämta http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease #012E: Vissa indexfiler kunde inte hämtas. De har ignorerats eller så har de gamla använts istället.
Nov 21 11:18:10 OptiPlex snapd[649]: storehelpers.go:1019: cannot refresh: snap has no updates available: "bare", "core18", "core22", "firefox", "gnome-42-2204", "gtk-common-themes", "snap-store", "snapd", "snapd-desktop-integration", "vlc"
Nov 21 11:18:11 OptiPlex snapd[649]: storehelpers.go:1019: cannot refresh: snap has no updates available: "bare", "core18", "core22", "firefox", "gnome-42-2204", "gtk-common-themes", "snap-store", "snapd", "snapd-desktop-integration", "vlc"
Nov 21 11:18:17 OptiPlex snap-store[1797]: not handling error failed for action refresh: E: Misslyckades med att hämta http://se.archive.ubuntu.com/ubuntu/dists/jammy/InRelease #012E: Misslyckades med att hämta http://se.archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease #012E: Misslyckades med att hämta http://se.archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease #012E: Misslyckades med att hämta http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease #012E: Vissa indexfiler kunde inte hämtas. De har ignorerats eller så har de gamla använts istället.
Nov 21 11:18:18 OptiPlex snapd[649]: storehelpers.go:1019: cannot refresh: snap has no updates available: "bare", "core18", "core22", "firefox", "gnome-42-2204", "gtk-common-themes", "snap-store", "snapd", "snapd-desktop-integration", "vlc"
Nov 21 12:51:17 OptiPlex snapd[649]: storehelpers.go:1019: cannot refresh: snap has no updates available: "bare", "core18", "core22", "firefox", "gnome-42-2204", "gtk-common-themes", "snap-store", "snapd", "snapd-desktop-integration", "vlc"
Nov 21 13:27:42 OptiPlex systemd[1287]: Started snap.firefox.firefox-8e84df4f-5339-40aa-ae69-bca1c5a1ac2a.scope.
Nov 21 13:27:42 OptiPlex systemd[1]: tmp-snap.rootfs_6HPI6H.mount: Deactivated successfully.
Nov 21 13:27:42 OptiPlex kernel: [ 8501.130713] audit: type=1400 audit(1732192062.828:71): apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.firefox" name="/usr/local/share/" pid=3774 comm="5" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Nov 21 13:27:42 OptiPlex firefox_firefox.desktop[3774]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/doc /usr/local/share/doc none bind,ro 0 0): cannot open directory "/usr/local/share": permission denied
Nov 21 13:27:42 OptiPlex firefox_firefox.desktop[3774]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot write to "/var/lib/snapd/hostfs/usr/share/gimp/2.0/help" because it would affect the host in "/var/lib/snapd"
Nov 21 13:27:42 OptiPlex firefox_firefox.desktop[3774]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/javascript/jquery /usr/share/javascript/jquery none bind,ro 0 0): cannot write to "/var/lib/snapd/hostfs/usr/share/javascript/jquery" because it would affect the host in "/var/lib/snapd"
Nov 21 13:27:42 OptiPlex firefox_firefox.desktop[3774]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/javascript/sphinxdoc /usr/share/javascript/sphinxdoc none bind,ro 0 0): cannot write to "/var/lib/snapd/hostfs/usr/share/javascript/sphinxdoc" because it would affect the host in "/var/lib/snapd"
Nov 21 13:27:42 OptiPlex firefox_firefox.desktop[3774]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/sphinx_rtd_theme /usr/share/sphinx_rtd_theme none bind,ro 0 0): cannot write to "/var/lib/snapd/hostfs/usr/share/sphinx_rtd_theme" because it would affect the host in "/var/lib/snapd"
Nov 21 13:27:42 OptiPlex firefox_firefox.desktop[3774]: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot write to "/var/lib/snapd/hostfs/usr/share/xubuntu-docs" because it would affect the host in "/var/lib/snapd"
Nov 21 13:27:47 OptiPlex dbus-daemon[619]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.130' (uid=1000 pid=3759 comm="/snap/firefox/5273/usr/lib/firefox/firefox " label="snap.firefox.firefox (enforce)")
Nov 21 13:27:48 OptiPlex kernel: [ 8506.463959] audit: type=1107 audit(1732192068.162:72): pid=619 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/timedate1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.131" pid=3759 label="snap.firefox.firefox" peer_pid=3890 peer_label="unconfined"
Nov 21 13:27:48 OptiPlex kernel: [ 8506.539119] audit: type=1107 audit(1732192068.237:73): pid=619 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/timedate1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.131" pid=3759 label="snap.firefox.firefox" peer_pid=3890 peer_label="unconfined"
Nov 21 13:27:50 OptiPlex dbus-daemon[1313]: [session uid=1000 pid=1313] Activating service name='io.snapcraft.Settings' requested by ':1.131' (uid=1000 pid=3938 comm="dbus-send --print-reply=literal --session --dest=i" label="snap.firefox.firefox (enforce)")
Nov 21 13:27:50 OptiPlex dbus-daemon[1313]: [session uid=1000 pid=1313] Successfully activated service 'io.snapcraft.Settings'
Nov 21 13:27:50 OptiPlex io.snapcraft.Settings[3941]: userd.go:93: Starting snap userd
Nov 21 16:33:27 OptiPlex kernel: [19645.520899] audit: type=1107 audit(1732203207.495:74): pid=619 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/timedate1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.227" pid=3759 label="snap.firefox.firefox" peer_pid=9055 peer_label="unconfined"
Nov 21 17:18:51 OptiPlex systemd[1287]: snap.firefox.firefox-8e84df4f-5339-40aa-ae69-bca1c5a1ac2a.scope: Consumed 59min 34.166s CPU time.
Nov 21 17:33:47 OptiPlex systemd[1287]: Started snap.firefox.firefox-3e99031e-acba-4443-8a03-446bd5bdd7b5.scope.
Nov 21 17:33:51 OptiPlex dbus-daemon[619]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.269' (uid=1000 pid=11084 comm="/snap/firefox/5273/usr/lib/firefox/firefox " label="snap.firefox.firefox (enforce)")
Nov 21 17:33:52 OptiPlex kernel: [23270.090890] audit: type=1107 audit(1732206832.155:75): pid=619 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/timedate1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.270" pid=11084 label="snap.firefox.firefox" peer_pid=11206 peer_label="unconfined"
Nov 21 17:33:52 OptiPlex kernel: [23270.159387] audit: type=1107 audit(1732206832.223:76): pid=619 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/timedate1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.270" pid=11084 label="snap.firefox.firefox" peer_pid=11206 peer_label="unconfined"
Nov 21 19:18:42 OptiPlex kernel: [29560.353845] audit: type=1326 audit(1732213122.573:77): auid=1000 uid=1000 gid=1000 ses=4 subj=snap.snap-store.ubuntu-software pid=1797 comm="pool-org.gnome." exe="/snap/snap-store/1216/usr/bin/snap-store" sig=0 arch=c000003e syscall=93 compat=0 ip=0x7f463ffbea9b code=0x50000
Nov 21 20:28:41 OptiPlex systemd[1287]: Started snap.firefox.firefox-dfc55658-7d45-48a9-bb3f-ea79b7b4b0b0.scope.
Nov 21 20:32:47 OptiPlex systemd[1287]: Started snap.firefox.firefox-70c33fe5-c3a5-4dee-a793-04d18842fa97.scope.
Nov 21 21:02:16 OptiPlex systemd[1287]: Started snap.firefox.firefox-c0c7234e-bfd2-43e1-87c6-2565e44c3ded.scope.
Nov 21 22:21:17 OptiPlex snapd[649]: storehelpers.go:1019: cannot refresh: snap has no updates available: "bare", "core18", "core22", "firefox", "gnome-42-2204", "gtk-common-themes", "snap-store", "snapd", "snapd-desktop-integration", "vlc"
Nov 22 00:51:17 OptiPlex snapd[649]: storehelpers.go:1019: cannot refresh: snap has no updates available: "bare", "core18", "core22", "firefox", "gnome-42-2204", "gtk-common-themes", "snap-store", "snapd", "snapd-desktop-integration", "vlc"
Nov 22 02:10:54 OptiPlex kernel: [54291.788236] audit: type=1107 audit(1732237854.617:79): pid=619 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/login1" interface="org.freedesktop.login1.Manager" member="PrepareForShutdown" name=":1.15" mask="receive" pid=11084 label="snap.firefox.firefox" peer_pid=654 peer_label="unconfined"
Nov 22 02:10:57 OptiPlex firefox_firefox.desktop[11084]: /home/mats/snap/firefox/common/.mozilla/firefox/wwjnwgsp.default-release-1/minidumps/614ad95f-3e65-f358-f08f-117cac5f1722.dmp
Nov 22 02:10:57 OptiPlex systemd[1287]: snap.snap-store.ubuntu-software-53acb3a6-72ff-4ae5-9547-4cb70fde01c0.scope: Consumed 23.207s CPU time.
Nov 22 02:10:58 OptiPlex snapd[649]: main.go:168: Exiting on terminated signal.
Nov 22 02:10:58 OptiPlex systemd[1287]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Consumed 1.200s CPU time.
Nov 22 02:10:58 OptiPlex systemd[1]: snapd.seeded.service: Deactivated successfully.
Nov 22 02:10:58 OptiPlex systemd[1]: Stopped Wait until snapd is fully seeded.
Nov 22 02:10:58 OptiPlex systemd[1]: Condition check resulted in Ubuntu core (all-snaps) system shutdown helper setup service being skipped.
Nov 22 12:18:13 OptiPlex systemd[1]: Mounted Mount unit for snap-store, revision 1113.
Nov 22 12:18:13 OptiPlex systemd[1]: Mounted Mount unit for snap-store, revision 1216.
Nov 22 12:18:13 OptiPlex systemd[1]: Mounted Mount unit for snapd, revision 21759.
Nov 22 12:18:13 OptiPlex systemd[1]: Mounted Mount unit for snapd-desktop-integration, revision 178.
Nov 22 12:18:13 OptiPlex systemd[1]: Mounted Mount unit for snapd-desktop-integration, revision 253.
Nov 22 12:18:13 OptiPlex systemd[1]: Reached target Mounted snaps.
Nov 22 12:18:13 OptiPlex systemd-udevd[326]: sda: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda' failed with exit code 1.
Nov 22 12:18:13 OptiPlex systemd-udevd[321]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1.
Nov 22 12:18:13 OptiPlex systemd-udevd[318]: sda2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda2' failed with exit code 1.
Nov 22 12:18:13 OptiPlex systemd-udevd[313]: sda3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda3' failed with exit code 1.
Nov 22 12:18:13 OptiPlex systemd-udevd[326]: sda1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda1' failed with exit code 1.
Nov 22 12:18:13 OptiPlex systemd-udevd[314]: sda4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda4' failed with exit code 1.
Nov 22 12:18:13 OptiPlex systemd[1]: Starting Load AppArmor profiles managed internally by snapd...
Nov 22 12:18:13 OptiPlex snapd-apparmor[544]: main.go:132: Loading profiles [/var/lib/snapd/apparmor/profiles/snap-confine.snapd.21759 /var/lib/snapd/apparmor/profiles/snap-update-ns.firefox /var/lib/snapd/apparmor/profiles/snap-update-ns.snap-store /var/lib/snapd/apparmor/profiles/snap-update-ns.snapd-desktop-integration /var/lib/snapd/apparmor/profiles/snap-update-ns.vlc /var/lib/snapd/apparmor/profiles/snap.firefox.firefox /var/lib/snapd/apparmor/profiles/snap.firefox.geckodriver /var/lib/snapd/apparmor/profiles/snap.firefox.hook.configure /var/lib/snapd/apparmor/profiles/snap.firefox.hook.disconnect-plug-host-hunspell /var/lib/snapd/apparmor/profiles/snap.firefox.hook.post-refresh /var/lib/snapd/apparmor/profiles/snap.snap-store.hook.configure /var/lib/snapd/apparmor/profiles/snap.snap-store.snap-store /var/lib/snapd/apparmor/profiles/snap.snap-store.ubuntu-software /var/lib/snapd/apparmor/profiles/snap.snap-store.ubuntu-software-local-file /var/lib/snapd/apparmor/profiles/snap.snapd-desktop-integration.hook.configure /var/lib/snapd/apparmor/profiles/snap.snapd-desktop-integration.snapd-desktop-integration /var/lib/snapd/apparmor/profiles/snap.vlc.vlc]
Nov 22 12:18:13 OptiPlex systemd[1]: Finished Load AppArmor profiles managed internally by snapd.
Nov 22 12:18:13 OptiPlex systemd[1]: Starting Socket activation for snappy daemon...
Nov 22 12:18:13 OptiPlex systemd[1]: Listening on Socket activation for snappy daemon.
Nov 22 12:18:13 OptiPlex systemd[1]: Starting Wait until snapd is fully seeded...
Nov 22 12:18:13 OptiPlex kernel: [ 5.074302] systemd[1]: /lib/systemd/system/snapd.service:23: Unknown key name 'RestartMode' in section 'Service', ignoring.
Nov 22 12:18:13 OptiPlex kernel: [ 5.468913] systemd[1]: Reached target Mounting snaps.
Nov 22 12:18:13 OptiPlex kernel: [ 6.182271] systemd[1]: Mounting Mount unit for snap-store, revision 1113...
Nov 22 12:18:13 OptiPlex kernel: [ 6.199378] systemd[1]: Mounting Mount unit for snap-store, revision 1216...
Nov 22 12:18:13 OptiPlex kernel: [ 6.212135] systemd[1]: Mounting Mount unit for snapd, revision 21759...
Nov 22 12:18:13 OptiPlex kernel: [ 6.229634] systemd[1]: Mounting Mount unit for snapd-desktop-integration, revision 178...
Nov 22 12:18:13 OptiPlex kernel: [ 6.245504] systemd[1]: Mounting Mount unit for snapd-desktop-integration, revision 253...
Nov 22 12:18:14 OptiPlex snapd[646]: overlord.go:271: Acquiring state lock file
Nov 22 12:18:14 OptiPlex snapd[646]: overlord.go:276: Acquired state lock file
Nov 22 12:18:14 OptiPlex snapd[646]: daemon.go:250: started snapd/2.65.3+22.04 (series 16; classic) ubuntu/22.04 (amd64) linux/6.8.0-49-generic.
Nov 22 12:18:15 OptiPlex snapd[646]: daemon.go:353: adjusting startup timeout by 1m20s (pessimistic estimate of 30s plus 5s per snap)
Nov 22 12:18:15 OptiPlex snapd[646]: backends.go:58: AppArmor status: apparmor is enabled and all features are available
Nov 22 12:18:15 OptiPlex systemd[792]: Listening on REST API socket for snapd user session agent.
Nov 22 12:18:15 OptiPlex systemd[792]: Started Service for snap application snapd-desktop-integration.snapd-desktop-integration.
Nov 22 12:18:16 OptiPlex dbus-daemon[817]: [session uid=128 pid=817] Activating via systemd: service name='org.freedesktop.portal.Documents' unit='xdg-document-portal.service' requested by ':1.2' (uid=128 pid=809 comm="/usr/bin/snap run snapd-desktop-integration " label="unconfined")
Nov 22 12:18:16 OptiPlex kernel: [ 15.383247] audit: type=1400 audit(1732274296.276:61): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=809 comm="snap-confine" capability=12 capname="net_admin"
Nov 22 12:18:16 OptiPlex kernel: [ 15.383261] audit: type=1400 audit(1732274296.276:62): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=809 comm="snap-confine" capability=38 capname="perfmon"
Nov 22 12:18:16 OptiPlex systemd[1]: tmp-snap.rootfs_DoYM3K.mount: Deactivated successfully.
Nov 22 12:18:16 OptiPlex dbus-daemon[619]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.34' (uid=0 pid=646 comm="/usr/lib/snapd/snapd " label="unconfined")
Nov 22 12:18:16 OptiPlex systemd[1]: Finished Wait until snapd is fully seeded.
Nov 22 12:18:17 OptiPlex snapd-desktop-integration.snapd-desktop-integration[809]: Sorry, home directories outside of /home needs configuration.
Nov 22 12:18:17 OptiPlex snapd-desktop-integration.snapd-desktop-integration[809]: See https://forum.snapcraft.io/t/11209 for details.
Nov 22 12:18:17 OptiPlex systemd[792]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Main process exited, code=exited, status=1/FAILURE
Nov 22 12:18:17 OptiPlex systemd[792]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'.

Does anyone want the entire log file on
Ubuntu 24.04.1
which crashes in Boot and then restarts automatically
(5896 lines)
Don't know if you have already received it via Crash report

Crash report is in connection with the crash and perhaps does not include that it restarts again?

Sometimes the log file gets too big, over several days, (500 MB)
it can be due to several things. I have noticed that the Boot starts with disk check, this may mean that the previous shutdown is not error-free and therefore does not change to a new log.

It is now 01:35
and I have looked for my claim and found evidence.
In the log over 3 days 20-22/11 there is no "Stopping rsyslog.service" and fsck is run at each Boot.

Since there are no matches on 20/11 there must have been updates on 20/11 and therefore the matches came 21-22/11

NOTE NOTE
Good morning 27/11 09.45
at 01.54 I switched off 24.04.5.
09.00 I started again and checked this morning's Boot log for fsck, and found something funny, 01.54
notes that both my 2 partitions are sucessfully dead, hence fsck 09.00

This is what happens at 01.54

/ root system sucessfully dead < l ove the explanation

The unit systemd-fsck@dev-disk-by\x2duuid-7807\x2d5BA2.service has successfully entered the 'dead' state.

/home system
The unit systemd-fsck@dev-disk-by\x2duuid-31a7e080\x2dbd51\x2d45e6\x2dbab8\x2d0107adff04ba.service has successfully entered the 'dead' state.

More problems
Why are these in a non Uefi pc.

mats@OptiPlex:~$ [ -d /sys/firmware/efi ] && echo "UEFI" || echo "Legacy"
Legacy
mats@OptiPlex:~$

Nov 27 09:00:29 OptiPlex kernel: [ 2.607504] registered taskstats version 1
Nov 27 09:00:29 OptiPlex kernel: [ 2.608013] Loading compiled-in X.509 certificates
Nov 27 09:00:29 OptiPlex kernel: [ 2.610238] Loaded X.509 cert 'Build time autogenerated kernel key: 980a6e2497136d3c3006f05ac599b4e6d94c4fe6'
Nov 27 09:00:29 OptiPlex kernel: [ 2.611935] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969'
Nov 27 09:00:29 OptiPlex kernel: [ 2.613629] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19'
Nov 27 09:00:29 OptiPlex kernel: [ 2.613636] blacklist: Loading compiled-in revocation X.509 certificates
Nov 27 09:00:29 OptiPlex kernel: [ 2.613683] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0'
Nov 27 09:00:29 OptiPlex kernel: [ 2.613732] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2017): 242ade75ac4a15e50d50c84b0d45ff3eae707a03'
Nov 27 09:00:29 OptiPlex kernel: [ 2.613785] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (ESM 2018): 365188c1d374d6b07c3c8f240f8ef722433d6a8b'
Nov 27 09:00:29 OptiPlex kernel: [ 2.613837] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2019): c0746fd6c5da3ae827864651ad66ae47fe24b3e8'
Nov 27 09:00:29 OptiPlex kernel: [ 2.613882] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v1): a8d54bbb3825cfb94fa13c9f8a594a195c107b8d'
Nov 27 09:00:29 OptiPlex kernel: [ 2.613926] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v2): 4cf046892d6fd3c9a5b03f98d845f90851dc6a8c'
Nov 27 09:00:29 OptiPlex kernel: [ 2.613974] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v3): 100437bb6de6e469b581e61cd66bce3ef4ed53af'
Nov 27 09:00:29 OptiPlex kernel: [ 2.614017] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (Ubuntu Core 2019): c1d57b8f6b743f23ee41f4f7ee292f06eecadfb9'
Nov 27 09:00:29 OptiPlex kernel: [ 2.628834] Key type .fscrypt registered
Nov 27 09:00:29 OptiPlex kernel: [ 2.628845] Key type fscrypt-provisioning registered

// M@ts

This question was expired because it remained in the 'Open' state without activity for the last 15 days.