Call for Testing: Bluefin LTS (Alpha)

Bluefin
,
21

i cant boot the .iso inside gnome boxes or virt manager

ive tryed:

  • redownloading the iso
  • building the iso from source
  • both uefi & Legacy boot
  • and with & without secure boot enabled
2 Likes
22

Ok fresh ISO is up. Booted in virt-manager fine for me, the wallpaper is broken but we know why. All the other stuff seems to be working now, including pkexec and the flatpak installation.

1 Like
23

Grabbed new ISO to try install.

I didn’t try to install over a working bluefin - I figure the partition’s boot issue is still the same. So I cleared the partitions before installing achillobator.

After install

rpm-ostree reports Version: stream10.1 (2025-01-02T20:00:53Z)

ujust install-system-flatpaks now works and prompts me for authentication.

It lists like 69 flatpaks to install and I cant see the top of the list just the 30-69th position. Maybe it can handle paging better.

It appears flatpaks come down sequentially. It might be worth trying to run some in parallel (not a big deal it’s a one off thing)

I tried to run ujust --choose which doesn’t have fzf so I installed brew install fzf

Then run ujust --choose to run bluefin-cli.

NOTE: is there a way to see a list of just targets without --choose as fzf wouldn’t be as important.
I realise this behavior may not be relevant as the ISO progresses.

Tried ujust device-info it fails with fpaste command not found
(may not be of interest at the moment)

Noticed atuin ctrl-r or up arrow don’t behave the same - they dont list history with a filter behavior as in bluefin. (may not be of interest at the moment)

I ran rpm-ostree status a bit later and I noticed a pending deployment with info

Version: stream10.1 (2025-01-03T00:45:28Z)

I did a reboot but the system never booted.

I forced off power and back on to see what would happen.

I then was on the previously pending version.

Tried ujust update to see what happened.

It reported update pending and had 3 layers to fetch.

It was doing something no progress indicators waited a while

It finished an staged image was waiting Version: stream10.1 (2025-01-03T00:57:22Z)

So rebooted again sudo reboot now

Booted fine

After reboot the User control in the center of the login screen is not focussed and I had to hit tab to focus it.

Logged in fine all seems fine.

As i like remote desktop login i tried to enable that but it doesn’t allow me to enable it every time i go back to settings it’s disabled again. Does not appear to work.(may not be of interest at the moment)

1 Like
24

ujust by itself will print the list and the descriptions.

25

:sheep: :slight_smile: I thought I’d tried that, obviously not…
Thank you…

EDIT.
I just realised that I tried just not ujust my goof.

26

I just realised atuin for shell history is different because it seems to be staying empty.

27

Atuin wasnt working because we forgot to add bash-preexec to the bluefin-cli hahahha. Add it with brew install bash-preexec and itll work again

1 Like
28

Thank you very much for all this testing! I’ve been using this on my main system for a bit so that I can test it and I didnt run into those issues. That fpaste catch was great, I completely forgot we didnt have that on the image yet. The newest images should be working much better, we cleared up a ton of stuff and fixed the pkexec issue that you were running into with flatpak remote-add. The Multiple candidate justfile in ‘/var/home/user’ issue was also fixed

29

Just a reminder for the people that are testing this image out: nothing is guaranteed yet! We broke automatic updates a few times, some stuff isnt working yet (…), so please make sure to manually update your system so you get the latest fixes. Also, if you run into any issue, make sure to report it to our github repo! It would help out a lot to know what is going on GitHub - centos-workstation/achillobator: Bluefin LTS, built on CentOS Stream with bootc . The more reported issues we get the faster we can get this to a better alpha/beta state! Thank you all very much!

We also have been restructuring a TON of stuff using this as an experiementation ground for new stuff, so maybe we will run into regressions, and do not hesitate to write your issues or gripes with this image. We are aiming to use this to make sure we can get rid of a ton of tech debt from the other repos on the Universal Blue org on Github.

2 Likes
30

Installing bash-preexec fixed atuin.

1 Like
31

Will fpaste be fixed in an image update like sudo bootc upgrade or ujust update or some other method?

1 Like
32

Its still an open PR, it just needs to be merged and youll get it soon!

1 Like
33

I have a general comment why are some apps use kexec and others sudo
seems to me having everything do things the same way would be good.
Even in ujust stuff alone some are sudo others are kexec.

In addition I don’t enjoy getting prompted multiple times by kexec for my password when multiple things are done.

Just running through other ujust commands that aren’t hardware coupled.

Updated to latest via ujust update reboot
fpaste is now in image ujust device-info worked fine. :white_check_mark:

  • ujust check-idle-power-draw
    • Error sudo: powerstat command not found
  • just distrobox-assemble
    • This works for wolfi at least but I found some of the messages could be improved.
    • I don’t quite understand why there is an ALL option here but this is not an issue.
    • I selected wolfi and got a warning
      • WARNING: This will assemble and replace the current wolfi with the one defined in /etc/distrobox/distrobox.ini
      • I was surprised to see this as I currently have no distroboxes installed.
      • I let it proceed and it reported
        • Yes the error no such container appeared twice.
        • - Deleting wolfi...
        • Error: no such container wolfi
        • Error: no such container wolfi
        • Cannot find container wolfi
          Then it showed and successfully created the container
        • - Creating wolfi...
  • ujust logs-last-boot ujust logs-this-boot
    • both work both produce an error when i hit q to exit the pager. example of error
    • error: Recipe logs-last-boot wast terminated on line 17 by signal 13
    • maybe can make it so it doesnt report an error for quitting.
  • ujust regenerate-grub
    • Error /usr/sbin/grub2/probe: error: failed to get cannonical path of composefs’
    • something missing perhaps.
    • also the missmatched quotes on composefs bit is a bit messy but maybe a pain upstream to address.
  • ujust toggle-updates
    • Error Failed to enable unit: Unit ublue-update.timer does not exist
  • ujust toggle-user-motd
    • No error’s but no indication of what it did or if its now on or off.
34

These were just copied over from Bluefin you may be the first person actually trying them. :smile: For sure we’re going to get rid of a bunch of them.

1 Like
35

Ok we’ve gotten enough interest to make this happen so we moved it into the ublue org last night. Note that we’re not pushing to ghcr.io/ublue-os/bluefin:lts yet but we’ll be doing that shortly. That will be the final URL (the packages we’re publishing now were just a test and need to be renamed). Here’s the repo:

And here is the inprogress documentation - which reads a lot like the readme but I’ll be working on it over the next few days.

6 Likes
36

Fresh ISO is up - I’ve only tested it once in a VM:

https://download.projectbluefin.io/bluefin-lts.iso

1 Like
37

Works great for me in a VM! In Gnome Boxes there’s a random slowdown once every 30-ish seconds (that the system recovers from), but that may very well be the VM :slight_smile:

I installed it from scratch, installed the Flatpaks, and poked around a bit. Looks great!

Thanks for building this! Exciting to see all the new technology being tested here :slight_smile:

38

Really glad to see this get greenlit, hopefully this can replace my janky Ubuntu setup on the work lappy once the software I need supports RHEL 10.

edit: or maybe I can distrobox? that might just work, I’d have to try

1 Like
40

Just updated a machine that hadn’t touched the internet in awhile.

In case anyone runs into a similar error to the one mentioned here, you will need to bootc switch to the new repo tag.

$ sudo bootc switch ghcr.io/ublue-os/bluefin:lts

$ sudo bootc status
● Booted image: ghcr.io/ublue-os/bluefin:lts
        Digest: sha256:2fbe31859d5c1b94599e4f040a236b2ae748bbc919992bcb166d4e2cd5ed0a50
       Version: stream10.1 (2025-03-05 18:12:38 UTC)

  Rollback image: ghcr.io/ublue-os/bluefin-lts:latest
          Digest: sha256:47dce50424e1a0b20b51f79825f4afa87946a2d417941ba9b29230f7e88a1133
         Version: stream10 (2025-01-29 05:26:19 UTC)
41

Is there a way one can check what the difference between two images without switching?

For example, I would like to compare the packages in the ghcr.io/ublue-os/bluefin:lts to ghcr.io/ublue-os/bluefin:stable (or any two bluefin channels for that matter).

To describe it: assume you run rpm -qa > bluefin-lts and rpm-qa > bluefin-stable and do a diff to see what versions differ, what is extra/missing on each side – but without having to install them in order to run the command.