Blufin unbootable with Jan-26 and Jan-29, but boots fine with Jan-19

When I start Blufin at boot process screen becomes black and on top left of screen “-” like cursor appears. I have waited for 15 minutes and it looks system hangs.

This issue started to appear previous week with Jan-26 image. I reverted back image at boot loader to previous image from Jan-19 and Blufin started up successfully.

Today still on Jan-19 image I did “ujust update” and Jan-29 downloaded without an issue after reboot I still get black screen with white “-” cursor at top left.

I rebooted and from boot loader selected Jan-19 and it boots up successfully.

It looks some issue at my system. Does someone else have the same issue?

rpm-ostree status returns:

State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:stable
                   Digest: sha256:7321f3dcb4d70e0c572701b006f0668479a8dc9b6832ae15377c40bfd214dbed
                  Version: 41.20250129.4 (2025-01-29T20:42:33Z)
                     Diff: 140 upgraded, 66 removed

● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:stable
                   Digest: sha256:59119e20585df337400bf3621167a242007c48654bb5bc2070189f6952306381
                  Version: 41.20250119.1 (2025-01-19T06:00:40Z)

Since Jan-19 works fine, it could be a kernel or graphics driver problem. Check journalctl -b -1 for errors. You can try nomodeset at boot or roll back with rpm-ostree cleanup -r alternativally you can also sudo rpm-ostree rollback to stay on the January 19th image until the issue is resolved.

edit: Share your system details and logs with the Bluefin team for further investigation GitHub · Where software is built

I have executed journal command and uploaded it. Click on “Download all” button and txt file will download.

I dont’see a “Download all” button - I would also advise to file a bug report - accessible through the above github link, this so the developers can also support you.

It looks button disappeared. I uploaded to different upload service. Download button should work now.

Hey,

I have somewhat similar issue, but with bluefin:latest and only happening in VM.

hidden after the update

My bluefin:stable all AMD PC:

State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: last run 5h 7min ago
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:stable
                   Digest: sha256:7321f3dcb4d70e0c572701b006f0668479a8dc9b6832ae15377c40bfd214dbed
                  Version: 41.20250129.4 (2025-01-29T20:42:33Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:stable
                   Digest: sha256:894f38c3eb977ac1d286e48b8aa7f002d3efcda7038ba67ca1406bef1c656c74
                  Version: 41.20250126.1 (2025-01-26T06:01:24Z)
PC Specs

e.g., bluefin:latest NOK VM

State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:latest
                   Digest: sha256:6bab0d22d7469c0010eb9eb20aa69bfb237436c6d040bf9b8ff547433766f28b
                  Version: latest-41.20250131 (2025-01-31T04:59:37Z)
                     Diff: 242 upgraded, 1 removed, 11 added
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:latest
                   Digest: sha256:16297e2e4ac806c7bc9fd80b2f286864dbc2118d0c00442fc6c8ec709d385ff1
                  Version: latest-41.20250201 (2025-02-01T04:59:37Z)
                     Diff: 245 upgraded, 1 removed, 11 added

All my other physical devices are OK with the same bluefin:latest.

State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:latest
                   Digest: sha256:785299a240d635bc1fbb37f2d28b44e5837f14e6bcedccdfd68f880ef95f52b4
                  Version: latest-41.20250130.1 (2025-01-30T04:59:56Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:latest
                   Digest: sha256:3831410a18f80c9be5a350fc860d8500c46e740f9d16d9551ca22e64df347ff8
                  Version: latest-41.20250129.2 (2025-01-29T05:00:19Z)

Update: fixed the VM issue by switching the video driver.

1 Like

I am also using Blufin inside virtual machine Virtualbox 7.1.6).

Where did you change video driver and how?

Hey,

Select the VM > Settings > Display > Graphics Controller - select VBoxSVGA and make sure Enable 3D Acceleration is not enabled

1 Like

@CyberOto, I have booted up Blufin with Jan-19 image and it boots fine. Updated Blufin to Feb-2 image. Powered off machine and changed to VBoxSVGA in VirtualBox virtual machine. Now it is little bit better Blufin boots to login screen. I have only one user on this Linux. I usually press Enter end then type in password and Enter to login. Now keyboard does not respont to any action also with mouse I can’t click on login user. It looks like Blufin is now frozzen at this stage.

I have reverted to Jan-19 image and Blufin boots up without an issue.

I will probably try:

  • few times over weeks to update Blufin image if issue is fixed
  • update VirtualBox when new update is available (probably in time frame of 3 months)
  • just move back to my old friend “Ubuntu 24.04 desktop” another virtual machine I have and works just fine

I am wondering if this issue is also present on GTS version?

I have not tested GTS in VM yet.

Here is a screenshot of my VM settings, if you want to experiment.

1 Like

Problem solved! Thanks for sharing print-screen.

TL;DR:

  • Change Graphic Controller to VBoxSVGA
  • Change Video Memory to the max of GUI it allows (in my case 128 MB)

Details:

  1. Booted up Blufin Jan-19 image and “ujust update”.
  2. After reboot freezes.
  3. I saw I have terrible low “Video Memory” set only to 16 MB. I set it to 128 MB (max that can be set using GUI).
  4. Rebooted and the same issue with VirtualBox VMSVGA Graphic Controller in Display settings.
  5. Changed VirtualBox VMSVGA to VBoxSVGA and rebooted and it booted up just fine and I can login.

I don’t know why this virtual machine have had only 16 MB, probably default when machine is created and I always (maybe I forgot for this one) to increase it to the maximum setting.

Still something is not the way it used to be on Jan-19, because recommended setting for Linux is VMSVGA and VBoxSVGA is recommended for Windows. It even warns for “Invalid settings detected” warning in GUI itself when changing to VBoxSVGA.

I have been playing around in Blufin and now it looks like working fine.

Thanks

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.