[SOLVED] Mint 21.3 Cinnamon PC goes to sleep after several hours and does not wake

[RefreshMint]

tldr;
This issue was not power event related, but was the desktop crashing. Which was caused by installing the OpenRGB app from an external repo rather than the flatpak from Software Manager

Double update: The issue still occured after removal of the external repo and package, and was semi-power event related. Turns out the solution was disabling CPU C-States in the bios, as the system would freeze after an indeterminate period of time while idle (typically 3-4 hours). With CPU C-States disbaled the freezing has stopped and I've been stable for ~60 hours with several 3+ and 8+ hour idle sessions.


I'm having an issue where my PC, when left idle for several hours (~3 or more), will go into what seems to be a sleep/hibernate state and will not wake up without having to power cycle. When this happens, my screens power off, the keyboard is unresponsive (num lock/caps lock will not toggle and switching usb ports has no effect) and the mouse is unresponsive. Short-pressing the power button does nothing and the only way to get the machine working again is with a power cycle.

Interestingly enough, if I only leave my PC alone for an hour or two the screens are off, as I expect from my settings, yet wiggling the mouse or typing on the keyboard will wake it up. And this issue does not occur when I boot Windows.

I've tried disabling the

Code: Select all

/usr/bin/nvidia-sleep.sh

by chucking

Code: Select all

exit 0

at the top as suggested by this thread: viewtopic.php?t=346628 which made no difference.

My power management settings are set to

Turn off the screen when inactive for: 15 minutes
Suspend when inactive for: Never

and the Screensaver settings are

Delay before starting the screensaver: 5 minutes
Lock the computer when put to sleep: off (I toggled that to see if it had any effect - it did not)
Lock the computer after the screensaver starts: on
Delay before locking: Lock immediately

inxi -Fxxxrz output:

Code: Select all

System:
  Kernel: 6.5.0-17-generic x86_64 bits: 64 compiler: N/A
    Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
    Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: TUF GAMING B550-PLUS (WI-FI) v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 2423
    date: 08/10/2021
CPU:
  Info: 12-core model: AMD Ryzen 9 5900X bits: 64 type: MT MCP smt: enabled
    arch: Zen 3 rev: 0 cache: L1: 768 KiB L2: 6 MiB L3: 64 MiB
  Speed (MHz): avg: 2503 high: 3700 min/max: 2200/4950 boost: enabled
    cores: 1: 2200 2: 2975 3: 2200 4: 2200 5: 2200 6: 2200 7: 2200 8: 2200
    9: 2200 10: 2200 11: 2200 12: 2200 13: 2800 14: 2200 15: 2200 16: 2200
    17: 2200 18: 3700 19: 2200 20: 3599 21: 3700 22: 3700 23: 2200 24: 2200
    bogomips: 177597
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: eVga.com.
    driver: nvidia v: 545.29.06 pcie: speed: 2.5 GT/s lanes: 16 ports:
    active: none off: DP-2,DP-3 empty: DP-1,HDMI-A-1,Unknown-1
    bus-ID: 07:00.0 chip-ID: 10de:1e84 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 5120x1440 s-dpi: 96 s-size: 1355x381mm (53.3x15.0")
    s-diag: 1408mm (55.4")
  Monitor-1: DP-2 pos: primary,left res: 2560x1440 dpi: 109
    size: 597x336mm (23.5x13.2") diag: 685mm (27")
  Monitor-2: DP-4 pos: right res: 2560x1440 dpi: 109
    size: 597x336mm (23.5x13.2") diag: 685mm (27")
  OpenGL: renderer: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2
    v: 4.6.0 NVIDIA 545.29.06 direct render: Yes
Audio:
  Device-1: NVIDIA TU104 HD Audio vendor: eVga.com. driver: snd_hda_intel
    v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 07:00.1 chip-ID: 10de:10f8
    class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 09:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: SteelSeries ApS Arctis Pro Wireless type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-4.3:5 chip-ID: 1038:1294
    class-ID: 0300
  Sound Server-1: ALSA v: k6.5.0-17-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s
    lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp5s0 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    pcie: speed: 5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0 chip-ID: 10ec:8125
    class-ID: 0200
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-5:3 chip-ID: 8087:0029 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: <filter>
Drives:
  Local Storage: total: 8.19 TiB used: 286.07 GiB (3.4%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 2TB
    size: 1.82 TiB speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 2B2QEXM7 temp: 40.9 C scheme: GPT
  ID-2: /dev/sda vendor: Western Digital model: WD20EARX-00PASB0
    size: 1.82 TiB speed: 6.0 Gb/s type: N/A serial: <filter> rev: AB51
    scheme: MBR
  ID-3: /dev/sdb vendor: Crucial model: CT2000MX500SSD1 size: 1.82 TiB
    speed: 6.0 Gb/s type: SSD serial: <filter> rev: 033 scheme: GPT
  ID-4: /dev/sdc vendor: Western Digital model: WD30EZRX-00SPEB0
    size: 2.73 TiB speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 0A80 scheme: GPT
Partition:
  ID-1: / size: 691.01 GiB used: 286.04 GiB (41.4%) fs: ext4
    dev: /dev/nvme0n1p5
  ID-2: /boot/efi size: 96 MiB used: 31.1 MiB (32.4%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: nvidia temp: 48 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos:
  Packages: 2417 apt: 2393 flatpak: 24
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http://packages.linuxmint.com virginia main upstream import backport
    2: deb http://archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http://archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http://archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/thopiekar-openrgb-jammy.list
    1: deb [signed-by=/etc/apt/keyrings/thopiekar-openrgb-jammy.gpg] https://ppa.launchpadcontent.net/thopiekar/openrgb/ubuntu jammy main
Info:
  Processes: 484 Uptime: 29m wakeups: 1 Memory: 31.24 GiB
  used: 3.81 GiB (12.2%) Init: systemd v: 249 runlevel: 5 Compilers:
  gcc: 11.4.0 alt: 11/12 Shell: Bash v: 5.1.16 running-in: gnome-terminal
  inxi: 3.3.13

Hostname and uname info (in case its helpful):

Code: Select all

 Static hostname: Dodecacore
       Icon name: computer-desktop
         Chassis: desktop
      Machine ID: 0d1ce2a36a2743a796257183b53a05bd
         Boot ID: 768e3e686b9b43c2991d28861cfefab9
Operating System: Linux Mint 21.3                 
          Kernel: Linux 6.5.0-17-generic
    Architecture: x86-64
 Hardware Vendor: ASUS
  Hardware Model: System Product Name
  Linux Dodecacore 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

and the results of

Code: Select all

journalctl -b -1 | tee >(gzip --stdout > journalctl_new_$USER.gz)

is here:
https://termbin.com/ezle

It looks like a kernel update was just released which I have not rebooted to try, and I may check Asus's website to see if there's a bios update. I will try switching to the 535 nvidia driver tonight before I go to sleep in hopes I wake up happy to a PC that also wakes up =)

Toggling things one at a time over the course of the week has driven me a bit batty, so I'm hoping someone may have more insight than I do in tracking the problem down.

Is there some setting I missed to tell Mint to not go into sleep/hibernate after 3 or 4 hours? Or is there something else anyone can think of to try?

Thanks for the help!

[RefreshMint]

Got frisky and changed three setttings last night:
- Updated to the latest motherboard BIOS
- Disabled Fast boot
- Changed to the recommended 5.35 NVidia driver

PC still did not wake up this morning.

Latest 500 lines from journalctl are here: https://termbin.com/re5b

It looks like the last entry is ~4 hours after I was using the PC, ~22:00 last use and ~02:00 last entry.

Any suggestions on what to try next?

[SMG]

Got frisky and changed three setttings last night:
- Updated to the latest motherboard BIOS
- Disabled Fast boot
- Changed to the recommended 5.35 NVidia driver

Welcome to the forum, RefreshMint.

Good to hear you updated the BIOS/UEFI because there were a number of updates to improve system performance and stability.

When the system goes to sleep, there are lines posted in dmesg/journalctl which indicate the computer is going to sleep. Usually, network connections register the first messages saying they are preparing for sleep before the lines saying the computer is going to suspend. There are no such lines in what you posted.

Are you sure the computer is going to sleep? Maybe check your drive lights to see if they are live or sleeping.

Is there any setting in BIOS/UEFI which might put the computer to sleep? (Sort of like a reverse Wake on LAN?)

[RefreshMint]

Welcome to the forum, RefreshMint.

Thank you for the welcome and the assistance!

Are you sure the computer is going to sleep?

That's an excellent question, and the answer is that I can't be certain. The system acts as though it's gone into a hibernate/sleep mode however, like you, I couldn't find anything in the logs that looked like a power event. The only clues I have are that:
- The monitors have powered down (likely due to the 15 minute inactivity timeout in the settings)
- Mouse and keyboard are unresponsive
- The RGB lights in the case have changed state
- The only way to get the system to respond again is to long-press the power button to shut down then press again to power back up

I took a look through the BIOS settings today and didn't see anything that referenced a sleep timer (The motherboard is an Asus B550 Plus Wifi, in case there are known defects with it?). While perusing the BIOS I did notice a setting on how to handle the RGB settings on a sleep/hibernate/power event and instructed it to turn them off. Since my case doesn't have HDD or network indicator LEDs that's the next best thing I can think of to check if it's a sleep/hibernate issue or something locking the system up.

Decided this afternoon to disconnect all peripherals except for network, mouse, keyboard, displayports to the GPU, and audio line-out as well on the off-chance a usb or other external device is related.

I'll report back tomorrow after I wake up to see if anything has changed. Hopefully with some good news (or more clues)!

Thanks!

[RefreshMint]

Good news!

When I walked by my desk this morning, the RGB LEDs were still doing what they were doing last night and I was able to "wake" it by wiggling the mouse and hitting keys on the keyboard.

Going to give it another 24 hours as-is, and if it survives I'll add peripherals one at a time until the issue comes back. Or doesn't, which would do my mental health a great disservice =)

Though it could still have been related to the old BIOS, since I realized last night when going through all the pages of BIOS settings that DOCP was disabled after updating it the other day so my RAM was running slower than it should have been. That's what I get for changing multiple variables at a time!

Thanks again, and hopefully I can track down what device causes it or find that I'm just crazy.

[SMG]

Good news!

When I walked by my desk this morning, the RGB LEDs were still doing what they were doing last night and I was able to "wake" it by wiggling the mouse and hitting keys on the keyboard.

Good to hear you are making progress on the investigation. It's good to have a working system even if we may not understand why it is working.

[RefreshMint]

Unfortunately the PC did not survive the night, however this time there was another clue. The screens were still on, the screensaver was showing but was not moving or able to be interacted with showing at time of 22:34, and the keyboard and mouse were also unresponsive. Even after swapping their USB ports.

It looks like the last journal entry that wasn't cron was referencing the screensaver at (22:25) and the screensaver clock was stuck displaying a time about ten minutes later (22:34). Is there a chance that the screensaver service is locking up and causing this issues?

Or maybe, as the average time for the cron jobs to run after invoking CRON was 2-4 minutes in the log, that anacron could be behind it? As the invocation for cron was called yet the logs indicating jobs were run were not printed. Looking at the other journal logs this is not the first time that the CRON log shows up a few minutes before the journal entries stop. Though calling

Code: Select all

crontab -l

for both my user and root says there are no jobs:

jebus@Dodecacore:~$ crontab -l
no crontab for jebus
jebus@Dodecacore:~$ sudo crontab -l
[sudo] password for jebus:
no crontab for root

Here's the latest journalctl for reference:
https://termbin.com/uqx6

My only other guess at this point is that my PC may be haunted =)

[SMG]

Unfortunately the PC did not survive the night, however this time there was another clue. The screens were still on, the screensaver was showing but was not moving or able to be interacted with showing at time of 22:34, and the keyboard and mouse were also unresponsive. Even after swapping their USB ports.

If you do not have a 6.2 kernel installed, install the last one available and boot into it and see if this problem still happens.

The 6.2 is available in Update Manager.

• Open Update Manager.
• Select View > Linux Kernels and click Continue.
• Make sure 6.2 is selected on the left panel and then click the top-most option on the right panel. An "Install" button will appear.
• Install the kernel.
• The next time you boot (I am presuming you see the grub menu because you are dual booting--let us know if this is not the case and you need instructions to see the grub menu), select Advanced Options and then select the 6.2 kernel without (recovery mode) after it and continue booting.

It is likely the cron job is Update Manager checking for updates. Some people with flatpaks installed have run into issues in the past with flatpak updates, but I haven't seen any of those lately so I'm not sure if that is still a possible issue for some people.

[RefreshMint]

Done, just booted in to 6.2.0-39 (formerly 6.5.0-18) and will give this kernel a go. Hadn't considered swapping to 6.2, thanks for the suggestion!

Hopefully 6.2 has good news or, failing that, more clues!

[RefreshMint]

Overnight test on 6.2 kernel was successful - the PC woke up after wiggling the mouse/pressing keyboard keys. Going to give it another 24 hours before adding peripherals back... for science!

[RefreshMint]

Success! The 48 hours test on the 6.2 kernel has been stable!

Thank you for the suggestion on try a previous kernel version, if 6.2 recognizes all the peripherals I'll be reattaching I'm thinking this one may be solved. Though hopefully a future 6.5 (or beyond) kernel will also be as stable as this one.

[SMG]

Success! The 48 hours test on the 6.2 kernel has been stable!

Thank you for the suggestion on try a previous kernel version, if 6.2 recognizes all the peripherals I'll be reattaching I'm thinking this one may be solved.

Unfortunately, 6.2 is end of life this month (unless something changed).

[RefreshMint]

Unfortunately, 6.2 is end of life this month

In the immortal words of Tinny Tim from Futurama

You raised my hopes and dashed them quite expertly, Bravo!

Seems like the only options are to stop getting updates on this PC, try to narrow down what exactly in 6.5 is doing this with a fresh install and adding things one-by-one, or hope a future 6.5 (or beyond) kernel revision fixes whatever weirdness is happening?

I'll submit an issue via the linux mint reporting page, though who knows if they'll be able to reproduce the problem.

Is there anything else you can think of to try?

And, in case I haven't already said as much, thank you for all the help and suggestions!

[SMG]

Seems like the only options are to stop getting updates on this PC, try to narrow down what exactly in 6.5 is doing this with a fresh install and adding things one-by-one, or hope a future 6.5 (or beyond) kernel revision fixes whatever weirdness is happening?

I'll submit an issue via the linux mint reporting page, though who knows if they'll be able to reproduce the problem.

Kernels come from Ubuntu. You can get to bug reports for specific kernels in Update Manager. Go to the 6.5 kernel having the problem and click it and you should have several links appear including one which is "Bug Reports".

Is there anything else you can think of to try?

There is a 6.5-oem kernel and Ubuntu 24.04 will be coming out probably with 6.8 so my hopes are one of those would fix this issue.

You can install the latest 6.5-oem kernel with

Code: Select all

sudo apt-get install linux-oem-22.04d

and reboot. However, I don't recall if the OEM or the HWE is the higher version so you may have to select the OEM in grub menu's Advanced Options.

There are others still using the 6.2 because they are waiting for bug fixes to be back-ported to the 6.5.

[RefreshMint]

Even better news, the issue seems to be resolved in the latest 6.5.0-12 kernel! I installed it Thursday when I noticed this in the changelog:

* The display becomes frozen after some time when a HDMI device is connected.
(LP: #2049027)
- drm/i915/dmc: Don't enable any pipe DMC events

As one of my screens does have an HDMI connection to a second PC the summary seemed like it could be related to the issue I was experiencing. With this kernel version installed I've been stable for at least two 8+ hour idle times.

I'll start re-introducing additional peripherals today with my fingers crossed that this is the answer. And if I'm still stable for the next few days I'll edit the subject to say solved!

Thank you for all the help!

[SMG]

Even better news, the issue seems to be resolved in the latest 6.5.0-12 kernel! I installed it Thursday when I noticed this in the changelog:

* The display becomes frozen after some time when a HDMI device is connected.
(LP: #2049027)
- drm/i915/dmc: Don't enable any pipe DMC events

As one of my screens does have an HDMI connection to a second PC the summary seemed like it could be related to the issue I was experiencing. With this kernel version installed I've been stable for at least two 8+ hour idle times.

Good to hear.
(I think you meant kernel 6.5.0-21.)

[RefreshMint]

You are absolutely correct, I typoed the kernel and meant version 6.5.0-21.

Had one mystery lock up yesterday, and woke up to another one this morning. Pulling the plugs, one-by-one, on the USB peripherals again to see if it is indeed one of those causing the trouble or if I just got really lucky for a the first few days after switching to 6.5.0-21.

Latest journalctl is here:
https://termbin.com/p4ur

Though, like the others, there's nothing suspicious in it I could find. =(

If I can't rule out the last remaining USB device (wireless headset) I'll try the oem kernels to see if anything changes.

Thanks for the help, and I'll keep trying to find the solution!

[SMG]

Latest journalctl is here:
https://termbin.com/p4ur

Though, like the others, there's nothing suspicious in it I could find. =(

Nothing jumps out at me either in the log.

[RefreshMint]

Nothing jumps out at me either in the log.

Agreed. The only remotely suspicious thing is some errors with the Cinnamon screensaver:

Code: Select all

Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]: Traceback (most recent call last):
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]:   File "/usr/share/cinnamon-screensaver/widgets/marqueeLabel.py", line 109, in _marquee_idle
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]:     if (self.hadjust.get_upper() == self.hadjust.get_page_size()) == self.get_allocated_width():
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]: AttributeError: 'NoneType' object has no attribute 'get_upper'
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]: Error in sys.excepthook:
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]: Traceback (most recent call last):
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]:   File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 153, in apport_excepthook
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]:     with os.fdopen(os.open(pr_filename,
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]: FileNotFoundError: [Errno 2] No such file or directory: '/var/crash/_usr_share_cinnamon-screensaver_cinnamon-screensaver-main.py.1000.crash'
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]: Original exception was:
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]: Traceback (most recent call last):
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]:   File "/usr/share/cinnamon-screensaver/widgets/marqueeLabel.py", line 109, in _marquee_idle
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]:     if (self.hadjust.get_upper() == self.hadjust.get_page_size()) == self.get_allocated_width():
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]: AttributeError: 'NoneType' object has no attribute 'get_upper'
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]: Traceback (most recent call last):
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]:   File "/usr/share/cinnamon-screensaver/widgets/marqueeLabel.py", line 109, in _marquee_idle
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]:     if (self.hadjust.get_upper() == self.hadjust.get_page_size()) == self.get_allocated_width():
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]: AttributeError: 'NoneType' object has no attribute 'get_upper'
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]: Error in sys.excepthook:
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]: Traceback (most recent call last):
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]:   File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 153, in apport_excepthook
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]:     with os.fdopen(os.open(pr_filename,
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]: FileNotFoundError: [Errno 2] No such file or directory: '/var/crash/_usr_share_cinnamon-screensaver_cinnamon-screensaver-main.py.1000.crash'
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]: Original exception was:
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]: Traceback (most recent call last):
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]:   File "/usr/share/cinnamon-screensaver/widgets/marqueeLabel.py", line 109, in _marquee_idle
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]:     if (self.hadjust.get_upper() == self.hadjust.get_page_size()) == self.get_allocated_width():
Feb 26 22:12:07 Dodecacore org.cinnamon.ScreenSaver[20680]: AttributeError: 'NoneType' object has no attribute 'get_upper'
...
Feb 26 22:12:14 Dodecacore org.cinnamon.ScreenSaver[20680]: Screen rect (0,0-5120x1440) and 2 monitor rects (0,0-5120x1440) add up, sending change notification
Feb 26 22:12:14 Dodecacore org.cinnamon.ScreenSaver[20680]: Screen rect (0,0-5120x1440) and 2 monitor rects (0,0-5120x1440) add up, sending change notification
Feb 26 22:12:14 Dodecacore cinnamon-screensaver-pam-helper[20825]: pam_unix(cinnamon-screensaver:auth): conversation failed
Feb 26 22:12:14 Dodecacore cinnamon-screensaver-pam-helper[20825]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [jebus]
Feb 26 22:12:14 Dodecacore org.cinnamon.ScreenSaver[20680]: Fractional scaling active: False
Feb 26 22:12:14 Dodecacore org.cinnamon.ScreenSaver[20680]: Fractional scaling active: False
Feb 26 22:12:14 Dodecacore org.cinnamon.ScreenSaver[20680]: Fractional scaling active: False
Feb 26 22:12:17 Dodecacore cinnamon-screensaver-pam-helper[20866]: pam_ecryptfs: seteuid error
Feb 26 22:12:17 Dodecacore cinnamon-screensaver-pam-helper[20866]: gkr-pam: unlocked login keyring
Feb 26 22:12:47 Dodecacore cinnamon-session[1509]: WARNING: t+40983.80812s: Detected that screensaver has left the bus
Feb 26 22:12:47 Dodecacore org.cinnamon.ScreenSaver[20680]: Error in sys.excepthook:
Feb 26 22:12:47 Dodecacore org.cinnamon.ScreenSaver[20680]: Original exception was:
Feb 26 22:12:47 Dodecacore org.cinnamon.ScreenSaver[20680]: Error in sys.excepthook:
Feb 26 22:12:47 Dodecacore org.cinnamon.ScreenSaver[20680]: Original exception was:
Feb 26 22:12:47 Dodecacore org.cinnamon.ScreenSaver[20680]: Error in sys.excepthook:
Feb 26 22:12:47 Dodecacore org.cinnamon.ScreenSaver[20680]: Original exception was:
Feb 26 22:12:47 Dodecacore org.cinnamon.ScreenSaver[20680]: Error in sys.excepthook:
Feb 26 22:12:47 Dodecacore org.cinnamon.ScreenSaver[20680]: Original exception was:
Feb 26 22:12:47 Dodecacore org.cinnamon.ScreenSaver[20680]: Error in sys.excepthook:
Feb 26 22:12:47 Dodecacore org.cinnamon.ScreenSaver[20680]: Original exception was:
Feb 26 22:12:47 Dodecacore org.cinnamon.ScreenSaver[20680]: Error in sys.excepthook:
Feb 26 22:12:47 Dodecacore org.cinnamon.ScreenSaver[20680]: Original exception was:

However those were posted ~5 hours before the final entry in the log. So there's no certainty it's related with such a large time delta, even with no activity on the machine.

Just had another lock-up/monitors-off/no-wake episode. Logs, as is usual, don't seem to indicate the cause. Only other crumb is that the screensaver is one of the final things to post an entry. But that was 10 minutes prior to the last entry, and there doesn't seem to be any correlation between this log's final entries and the previous.
https://termbin.com/r5k5

Removed the final USB device and will also remove the HDMI cables from one of my screens too and see what happens.

This is a head-scratching adventure!

[SMG]

Nothing jumps out at me either in the log.

Agreed. The only remotely suspicious thing is some errors with the Cinnamon screensaver:

I saw those also, but they were all through the log. There were multiple episodes of that. However, the fact everything seems to work with the 6.2 kernel would seem to indicate Cinnamon screensaver is not an issue.

There were also multiple episodes of network IP issues, but it didn't happen in the same place in the several logs you posted so it would not seem related to the freeze.

Just had another lock-up/monitors-off/no-wake episode. Logs, as is usual, don't seem to indicate the cause. Only other crumb is that the screensaver is one of the final things to post an entry. But that was 10 minutes prior to the last entry, and there doesn't seem to be any correlation between this log's final entries and the previous.
https://termbin.com/r5k5

This one like at least one of the others (but not all the others) just completed doing flatpak update checks.