Ah, I didn't see the link he'd posted to the log.
What I'm seeing is sr0 acting up, which is a CD-ROM... it might be an actual CD-ROM or a loop-mount with bad sectors being treated as a CD-ROM.
And I'm seeing that the kernel is having problems allocating memory to a PCIe device:
pci 0000:1d:06.0: BAR 14: failed to assign [mem size 0x00200000]
And I see ALSA misconfiguration:
desktop alsactl[850]: alsa-lib main.c:1021:(snd_use_case_mgr_open) error: failed to import hw:0 (empty configuration)
And I see that gnome is having trouble communicating with systemd:
desktop gnome-session-binary[1149]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
desktop gsd-sharing[1258]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
desktop gnome-software[2272]: internal error: failed, but no error code: cancelled
And PulseAudio problems:
desktop pulseaudio[1484]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
It's accessing unexpected files:
Apr 4 10:19:37 desktop gnome-shell[1637]: DING: Gjs-Message: 09:47:17.293: JS LOG: Error connecting to Nautilus#012GNOME nautilus 3.36.3#012Gtk-Message: 09:55:37.312: Failed to load module "canberra-gtk-module"#012Gtk-Message: 09:55:37.316: Failed to load module "canberra-gtk-module"#012Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size#012Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index3/size#012Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present#012Sandbox: attempt to open unexpected file /sys/devices/system/cpu#012Sandbox: unexpected multiple open of file /proc/cpuinfo#012Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size#012Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index3/size#012Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present#012Sandbox: attempt to open unexpected file /sys/devices/system/cpu#012Sandbox: unexpected multiple open of file /proc/cpuinfo#012Gtk-Message: 10:09:44.223: Failed to load module "canberra-gtk-module"#012Gtk-Message: 10:09:44.224: Failed to load module "canberra-gtk-module"#012Gtk-Message: 10:13:26.821: Failed to load module "canberra-gtk-module"#012Gtk-Message: 10:13:26.823: Failed to load module "canberra-gtk-module"
I'm seeing CPU errors:
mce: [Hardware Error]: CPU 9: Machine Check: 0 Bank 5: bea0000000000108
... but that could be attributable to the GPU:
Then there's this:
desktop gnome-software-service.desktop[43700]: [2:0404/093748.072865:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
That file (/run/dbus/system_bus_socket
) exists on my system... something must have removed it (or irreparably corrupted it) on the OP's system. That might be the root cause of the problem currently being addressed:
desktop gnome-shell[1637]: Unable to mount volume Hp: Gio.IOErrorEnum: Error mounting /dev/sdc1 at /media/desktop/Hp: Unknow error when mounting /dev/sdc1
With 210 matches for the word 'fail', 616 matches for the word 'error', and 188 matches for the word 'warn' in the logs provided, I'd recommend doing a BIOS update (if one is available, given the following errors:
ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20210730/tbfadt-615)
), resetting the BIOS to defaults (to be sure the CPU isn't overclocked or undervolted), disabling SecureBoot and TPM in BIOS, doing a drive check and a full reinstall.
That still doesn't address, however, the root cause of the current failure. I'd recommend checking what I listed in my prior post. There's something very wrong with this system.