Version 20250803 causes frequent crashes on ThinkPad T14 Gen 1

[Jarartur]

Describe the bug

Recently I upgraded from some June build to 20250803. Now the GNOME desktop launches weirdly. I see a gray screen with 3 squares loading slowly. After that the laptop frequently crashes when trying to sleep or launching some apps (like Thunderbird flatpak).

I don't really know what to report more. I can do some testing if anyone asks me to.

What did you expect to happen?

Same behavior as before: booting straight to lock screen and no crashes.

Output of bootc status

● Booted image: ghcr.io/ublue-os/bluefin-dx:stable
        Digest: sha256:a79a473c3eb9066b4dfa1a09803d4fe5db830d8d8b13eb32bdd7abbf4f708f3d (amd64)
       Version: 42.20250803.2 (2025-08-03T06:07:48Z)

  Rollback image: ghcr.io/ublue-os/bluefin-dx:stable
          Digest: sha256:efac2b865385550e54a08d571b70ad32d55928ded67e2a7ecb64f70a2aeec825 (amd64)
         Version: 42.20250629.1 (2025-06-29T16:37:42Z)

Output of groups

jarartur wheel i2c

Extra information or context

No response

[hanthor]

Try disabling all gnome extensions and see if it improves. Then you can experiment turning them back on

[Jarartur]

It is not extensions. I disabled all of them with the global switch and it is the same.
BTW the squares in question:

[hanthor]

If you hit the escape key, you'll be able to see the messages behind this python splash screen. It's getting stuck somewhere in the boot

[Jarartur]

Wierdly enought it is only displayed sometimes. I once logged in without this screen, next time it was there. The only error I could find is this:

× systemd-remount-fs.service - Remount Root and Kernel File Systems
     Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; enabled-runtime; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Wed 2025-08-06 15:12:25 CEST; 4min 3s ago
 Invocation: 336891e1e50b4f799074af7c184eb886
       Docs: man:systemd-remount-fs.service(8)
             https://systemd.io/API_FILE_SYSTEMS
    Process: 1515 ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE)
   Main PID: 1515 (code=exited, status=1/FAILURE)
   Mem peak: 2M
        CPU: 19ms

sie 06 15:12:25 bluefin systemd-remount-fs[1516]: mount: /: fsconfig system call failed: overlay: No changes allowed in reconfigure.
sie 06 15:12:25 bluefin systemd-remount-fs[1516]:        dmesg(1) may have more information after failed mount system call.
sie 06 15:12:25 bluefin systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems...
sie 06 15:12:25 bluefin systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE
sie 06 15:12:25 bluefin systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'.
sie 06 15:12:25 bluefin systemd[1]: Failed to start systemd-remount-fs.service - Remount Root and Kernel File Systems.

[hanthor]

ujust logs-last-boot

Should give you the logs from the failed boot. If it won't boot, then on that three dot screen you can hit the ESC key and see what the boot logs are showing on the screen.

[Jarartur]

It never fails, just takes a long time which never happened on the previous versions. The only fail I've seen during the boot is the systemd-remount-fs.service one.

[hanthor]

Can you paste the logs from ujust logs-this-boot

You can also check the output of systemd-analyze blame

To see what taking time in the boot

[Jarartur]

boot_bad_logs.log
boot_good_logs.log
systemd_bad.txt
systemd_good.txt

Here are attached logs from the "good" boot where everything went as usual, and the "bad" where there was the loading screen present.

BTW, thank you for helping me with this; I am learning a lot. I will go through them on my own too.

[dosubot]

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

Issue Summary:

• After upgrading to version 20250803 on your ThinkPad T14 Gen 1, GNOME shows a gray screen with slow-loading squares and frequent crashes.
• Disabling GNOME extensions did not fix the problem.
• Logs indicate a failure in systemd-remount-fs.service related to overlay filesystem reconfiguration.
• Maintainer hanthor suggested checking boot logs and systemd-analyze blame; you provided detailed logs from both good and bad boots.
• The investigation and troubleshooting discussion is ongoing.

Next Steps:

• Please confirm if this issue persists with the latest bluefin updates; if so, you can keep the discussion open by commenting here.
• Otherwise, I will automatically close this issue in 14 days.

Thank you for your understanding and contribution.

For more details, see the official documentation at https://docs.projectbluefin.io