OS randomly freezes

[mysticrooster]

Describe the bug

I want to say maybe once a week, the operating system will just freeze. No input has any response. I have to force shutoff the computer in order to get it to work.

What did you expect to happen?

I expected the OS to function as normal

Output of bootc status

● Booted image: ghcr.io/ublue-os/bluefin-dx:stable
        Digest: sha256:5c9df4df4139dc55cb5a9c3fc74d88ea02c3d54833f087dbe41e96a17dddcf5e (amd64)
       Version: 43.20251209.1 (2025-12-09T03:29:24Z)

  Rollback image: ghcr.io/ublue-os/bluefin-dx:stable
          Digest: sha256:fd0283aa5f5f4f27babf0b2c7c5e1971632f477f5eda78215016f5602267e63d (amd64)
         Version: 43.20251202 (2025-12-02T01:44:29Z)

Output of groups

julian wheel docker incus-admin libvirt

Extra information or context

Here are the logs from after I booted the computer. I think it usually happens when I am using LibreWolf (a Firefox fork). I am not 100% if that's a sure pattern but maybe it'll help?

 3:46:39 PM systemd-logind: Failed to open '/boot/loader/entries': Remote address changed
 3:46:38 PM pkexec: pam_systemd(polkit-1:session): Failed to check if /run/user/0/bus exists, ignoring: Permission denied
 3:46:38 PM systemd-logind: Failed to open '/boot/loader/entries': Remote address changed
 3:46:37 PM gdm-session-wor: gkr-pam: unable to locate daemon control file
 3:46:17 PM pkexec: gdm-greeter: The value for the SHELL variable was not found in the /etc/shells file [USER=root] [TTY=unknown] [CWD=/run/gdm/home/gdm-greeter] [COMMAND=/usr/libexec/ublue-privileged-setup]
 3:46:14 PM systemd-logind: Failed to open '/boot/loader/entries': Remote address changed
 3:46:06 PM systemd-tmpfile: "/root" already exists and is not a directory.
 3:46:05 PM systemd: Failed to start systemd-remount-fs.service - Remount Root and Kernel File Systems.
 3:46:05 PM systemd-remount: /usr/bin/mount for / exited with exit status 32.
 3:46:05 PM kernel: leds framework_laptop::kbd_backlight: Setting an LED's brightness failed (-5)
 3:46:05 PM systemd: Failed to start systemd-remount-fs.service - Remount Root and Kernel File Systems.
 3:46:05 PM systemd-remount: /usr/bin/mount for / exited with exit status 32.
 3:46:05 PM kernel: cros-usbpd-charger cros-usbpd-charger.6.auto: probe with driver cros-usbpd-charger failed with error -71
 3:46:04 PM systemd: Failed to start systemd-remount-fs.service - Remount Root and Kernel File Systems.
 3:46:04 PM systemd-remount: /usr/bin/mount for / exited with exit status 32.
 3:46:03 PM systemd-udevd: /usr/lib/udev/rules.d/10-switch.rules:1 Unknown group 'nintendo_switch', ignoring.
 3:46:03 PM kernel: /usr/bin/mount for / exited with exit status 32.
 3:46:03 PM kernel: Failed to start systemd-remount-fs.service - Remount Root and Kernel File Systems.
 3:45:48 PM kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
 3:45:45 PM systemd-udevd: /usr/lib/udev/rules.d/60-block.rules:16 Unknown group 'disk', ignoring.
 3:45:44 PM systemd-tmpfile: /usr/lib/tmpfiles.d/var.conf:17: Failed to resolve group 'utmp': No such process
 3:45:44 PM kernel: /usr/lib/tmpfiles.d/static-nodes-permissions.conf:20: Failed to resolve group 'kvm': No such process
 3:45:44 PM kernel: /usr/lib/tmpfiles.d/static-nodes-permissions.conf:19: Failed to resolve group 'kvm': No such process
 3:45:44 PM kernel: /usr/lib/tmpfiles.d/static-nodes-permissions.conf:18: Failed to resolve group 'kvm': No such process
 3:45:44 PM kernel: /usr/lib/tmpfiles.d/static-nodes-permissions.conf:14: Failed to resolve group 'disk': No such process
 3:45:44 PM kernel: /usr/lib/tmpfiles.d/static-nodes-permissions.conf:13: Failed to resolve group 'audio': No such process
 3:45:44 PM kernel: /usr/lib/tmpfiles.d/static-nodes-permissions.conf:12: Failed to resolve group 'audio': No such process
 3:45:44 PM kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q39 due to previous error (AE_AML_PACKAGE_LIMIT) (20250404/psparse-529)

[afernandezortuzar]

Hi!

Maybe this has nothing to do with your case, but i had a similar problem few months ago and after hours of research i got to the conclusion that it was an AMD problem, and it happens in gnome distros other that bluefin. To solve it i had to stop using the night light option and always have performance mode on. I read people say that with only one of these two they could get around the issue, not my case.

I hope this works for you, while we wait for a real solution.

[repires]

try debugging using ask.projectbluefin.io

probably problem upstream nvidia and/or selinux

[ahme-dev]

@shusterrooster do you have your disk encrypted? Personally had similar issues due to that

[repires]

Possible issues to be reverted by 6.19.+

https://www.phoronix.com/news/AMDGPU-Linux-6.19-Regressions

[afernandezortuzar]

We'll see. It doesn't mention GUI freezes and this problem is way older than version 6.19.

[repires]

We'll see. It doesn't mention GUI freezes and this problem is way older than version 6.19.

I have same the same regressions since 6.17.11.

6.18.5+ seems to be fixed. Let's wait to release cycle and see. Thank you for you feedback.

[dosubot]

Hi, @shusterrooster. I'm Dosu, and I'm helping the bluefin team manage their backlog and am marking this issue as stale.

Recap

• You reported an intermittent full system freeze about once a week that requires a hard power-off.
• No clear error has been identified yet, and the issue remains unresolved.
• Possible angles discussed so far include LibreWolf, AMDGPU/kernel regressions, Night Light/performance mode, disk encryption, and upstream NVIDIA/SELinux causes.
• You shared bootc status and a few post-boot logs, but there hasn’t been enough signal yet to confirm the root cause.

Next Steps

• Please let us know if this is still happening on the latest version of bluefin.
• If it is still relevant, you can keep the discussion open by commenting here; otherwise, this issue will be automatically closed in 14 days.

Thanks for your understanding and contribution.