This issue still persistens with the new ISOs.
Also the console got:
2025-05-03T08:38:48.042501Z ERROR readymade::disks::osprobe: os-prober failed to run! Are we root? Is it installed? Continuing without OS detection.
at src/disks/osprobe.rs:56
Please write a clearly visible warning into the readme of your repository.
Where does readymade stop, and titanoboa begin?
It looks like readymade gets the disk setup, copies files, then (before rebooting) invokes titanoboa to finish the install?
After the first reboot, is the initial welcome and install app still titanoboa?
Just trying to get a sense of where to report issues,
readymade
or
titanoboa
titanoboa = live-iso
readymade = installer
issues with the installer app itself should be reported to readymade, issues with anything else can go in titanoboa, if you’re not sure, we can always move your issue between the two places
I tried it:
Install dialog. There is only language selection. I want to install English/United_States locale with my e.g. German keyboard (so I can type in complicated password at disk encrypt dialog). In Anaconda there are two separate selections keyboard and locale.
As work around from top-right I selected Settings icon and from Setting application selected Keyboard and added my national keyboard..
I get three disks. First is HDD, second is SSD and third I don’t know what it is. For the third what ever it is, it is 1 GB and it will be just too small to install Blufin on ti. May I suggest installed to check if size of disk is large enough to save Blufin on it. Additionally, it is hard to see what option is selected. You see from my screen both HDD (top-left) and DVD-RAM (bottom-right) seems to be selected - both are in blue color. May I suggest to make currently selected disk way more visible. Like background color to get dark blue or something or maybe even better to have a border around disk selected.
What is the purpose of “Entire Disk” button, if this is the only option. Do we want somehow users to mentally accept there are going to install Blufin on whole disk? If this is purpose then it is fine, if not, this option is really redundant and could just be written with e.g. red color like “CAUTION: Entire disk will be used for Blufin”. I have been playing around and I can’t seem to select “Enable TPM” (I am not literate enough to even understand what is TPM for). But when does this button gets ungreyed and possible to check?
This is additional confirmation. It looks to me there are three dialogs related to disk selection that is probably too much. Can’t we reduce this to two or maybe one?
After installation finished there is dialog with “Reboot” button. I pressed this and I expected to see some “Please unplug your USB device” and press Enter (or something). But maybe this warning can be added to “Reboot” dialog.
After reboot I get field to decrypt disk. I type in my password, but it looks like my national keyboard is not recognized, so I can’t write my complicated password in this dialog. If I remember this is the same issue with Anaconda when I installed few mounts ago. I have started from beginning and set some simple password here (so I need to figure it out how to change disk encrypt password).
After reboot there is question about keyboard which is fine and I can select my national keyboard (just it would be nice to have this option when I set disk encrypt password).
After reboot I still see green dino background. I didn ujust update to get new updates and after reboot new background is displayed with today’s image. Nice.
EDIT:
Got it, pretty sure Mado is working on this.
That’s probably the USB stick
this was supposed to be a selector for entire disk, custom, etc, but Bluefin only supports entire disk, so this is what is shown.
This is a double confirmation, it’s your last chance to make sure the disk you selected is the correct one, this is once again partially because bluefin only offers full disk installations.
You don’t need to unplug your USB device like on Ubuntu, simply wait for the system to fully power off and remove it then, we could potentially add a note about this
Seems to be the same issue as 1…
This defeats the intention of a double confirmation, I do believe it will feel less odd when there’s more than one option on the install type page
Isn’t it what it says it is? A dvd drive with model name GH82N and a DVD-RAM inserted?
If so, it would really make sense to exclude such devices (all optical disc drives, I guess) from the installation target selection.
Also, filtering by volume size (e.g. minimum of 20GiB) as @red11 suggests sounds like a very useful suggestion 
.
Optical drives should be excluded yeah, red11 it would be helpful if you could file an issue.
I’d argue for a smaller minimum (maybe 15gb) to acomodate for devices with crappy drives, maybe this could be a distro configurable thing.
Hello, I tested this out inside a virtual machine on my framework 13 (I know the ublue crew loves framework references), but there is one thing I do have quite a smitten for that is not available as an option for the new bluefin installer, which I will say is quite a treat to use otherwise. For those of us who use LVM (such as for raid5ing our drives), there was no option to change the filesystem, that I could find, inside the installer, while if you use Silverblue and use the anaconda installer, you can use that just fine, unless I have made a grave error, that seems to be a regression in ability for this new installer. Is this intentional, or just something that is going to be worked on at a later date?
Thank you for your hardwork on this great project!
just tried the new install with secure boot enable
everything went smoothly
but a little worried about those error messages
should i be concerned ?
systemd-tmpfiles[419]: /usr/lib/tmpfiles.d/static-nodes-permissions.conf:12: Failed to resolve group ‘audio’: No such process
May 06 09:35:13 dracut-cmdline[439]: dracut-103-3.fc41
May 06 09:35:13 dracut-cmdline[439]: Using kernel command line parameters: rd.driver.pre=btrfs BOOT_IMAGE=(hd3,gpt2)/boot/ostree/default-efb46626086d1d86489941a67f7df89b4d207c11c95cb05461eea3>
May 06 09:35:13 systemd-tmpfiles[419]: /usr/lib/tmpfiles.d/static-nodes-permissions.conf:13: Failed to resolve group ‘audio’: No such process
May 06 09:35:13 systemd-tmpfiles[419]: /usr/lib/tmpfiles.d/static-nodes-permissions.conf:14: Failed to resolve group ‘disk’: No such process
May 06 09:35:13 systemd-tmpfiles[419]: /usr/lib/tmpfiles.d/static-nodes-permissions.conf:18: Failed to resolve group ‘kvm’: No such process
May 06 09:35:13 systemd-tmpfiles[419]: /usr/lib/tmpfiles.d/static-nodes-permissions.conf:19: Failed to resolve group ‘kvm’: No such process
May 06 09:35:13 systemd-tmpfiles[419]: /usr/lib/tmpfiles.d/static-nodes-permissions.conf:20: Failed to resolve group ‘kvm’: No such process
May 06 09:35:13 dracut-pre-trigger[560]: rd.md=0: removing MD RAID activation
May 06 09:35:13 systemd-tmpfiles[419]: Failed to parse ACL “d:group::r-x,d:group:adm:r-x,d:group:wheel:r-x,group::r-x,group:adm:r-x,group:wheel:r-x”, ignoring: Invalid argument
May 06 09:35:13 systemd-tmpfiles[419]: Failed to parse ACL “d:group:adm:r-x,d:group:wheel:r-x,group:adm:r-X,group:wheel:r-X”, ignoring: Invalid argument
May 06 09:35:13 systemd-tmpfiles[419]: Failed to parse ACL “d:group::r-x,d:group:adm:r-x,d:group:wheel:r-x,group::r-x,group:adm:r-x,group:wheel:r-x”, ignoring: Invalid argument
May 06 09:35:13 systemd-tmpfiles[419]: Failed to parse ACL “d:group:adm:r-x,d:group:wheel:r-x,group:adm:r-x,group:wheel:r-x”, ignoring: Invalid argument
May 06 09:35:13 systemd-tmpfiles[419]: Failed to parse ACL “group:adm:r–,group:wheel:r–”, ignoring: Invalid argument
May 06 09:35:13 systemd-modules-load[404]: Inserted module ‘v4l2loopback’
May 06 09:35:13 systemd-udevd[556]: Using default interface naming scheme ‘v255’.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:38 Unknown group ‘tty’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:39 Unknown group ‘tty’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:40 Unknown group ‘tty’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:41 Unknown group ‘tty’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:44 Unknown group ‘kmem’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:46 Unknown group ‘input’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:49 Unknown group ‘video’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:50 Unknown group ‘video’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:51 Unknown group ‘video’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:52 Unknown group ‘video’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:53 Unknown group ‘video’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:54 Unknown group ‘video’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:56 Unknown group ‘render’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:57 Unknown group ‘render’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:58 Unknown group ‘render’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:60 Unknown group ‘sgx’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:61 Unknown group ‘sgx’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:67 Unknown group ‘audio’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:77 Unknown group ‘audio’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:78 Unknown group ‘audio’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:79 Unknown group ‘video’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:81 Unknown group ‘lp’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:82 Unknown group ‘lp’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:83 Unknown group ‘lp’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:84 Unknown group ‘lp’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:85 Unknown group ‘lp’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:86 Unknown group ‘lp’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:88 Unknown group ‘disk’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:96 Unknown group ‘disk’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:97 Unknown group ‘disk’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:98 Unknown group ‘disk’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:99 Unknown group ‘disk’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:100 Unknown group ‘disk’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:101 Unknown group ‘disk’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:102 Unknown group ‘disk’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:111 Unknown group ‘kvm’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:116 Unknown group ‘kvm’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:118 Unknown group ‘kvm’, ignoring.
May 06 09:35:13 systemd-udevd[556]: /usr/lib/udev/rules.d/50-udev-default.rules:120 Unknown group ‘kvm’, ignoring.
May 06 09:35:13 systemd[1]: Starting systemd-tmpfiles-setup.service - Create System Files and Directories…
May 06 09:35:13 systemd[1]: Created slice system-modprobe.slice - Slice /system/modprobe.
May 06 09:35:13 systemd[1]: Starting modprobe@configfs.service - Load Kernel Module configfs…
May 06 09:35:13 systemd[1]: Finished systemd-udev-trigger.service - Coldplug All udev Devices.
May 06 09:35:13 systemd[1]: Condition check resulted in dev-tpmrm0.device - /dev/tpmrm0 being skipped.
May 06 09:35:13 systemd-tmpfiles[614]: /usr/lib/tmpfiles.d/systemd.conf:11: Failed to resolve group ‘utmp’: No such process
May 06 09:35:13 systemd-tmpfiles[614]: Failed to parse ACL “d:group::r-x,d:group:adm:r-x,d:group:wheel:r-x,group::r-x,group:adm:r-x,group:wheel:r-x”, ignoring: Invalid argument
May 06 09:35:13 systemd-tmpfiles[614]: Failed to parse ACL “d:group:adm:r-x,d:group:wheel:r-x,group:adm:r-X,group:wheel:r-X”, ignoring: Invalid argument
May 06 09:35:13 systemd-tmpfiles[614]: Failed to parse ACL “d:group::r-x,d:group:adm:r-x,d:group:wheel:r-x,group::r-x,group:adm:r-x,group:wheel:r-x”, ignoring: Invalid argument
May 06 09:35:13 systemd-tmpfiles[614]: Failed to parse ACL “d:group:adm:r-x,d:group:wheel:r-x,group:adm:r-x,group:wheel:r-x”, ignoring: Invalid argument
May 06 09:35:13 systemd-tmpfiles[614]: Failed to parse ACL “group:adm:r–,group:wheel:r–”, ignoring: Invalid argument
May 06 09:35:13 systemd-tmpfiles[614]: /usr/lib/tmpfiles.d/var.conf:14: Duplicate line for path “/var/log”, ignoring.
May 06 09:35:13 systemd-tmpfiles[614]: /usr/lib/tmpfiles.d/var.conf:15: Failed to resolve group ‘utmp’: No such process
May 06 09:35:13 systemd-tmpfiles[614]: /usr/lib/tmpfiles.d/var.conf:16: Failed to resolve group ‘utmp’: No such process
May 06 09:35:13 systemd-tmpfiles[614]: /usr/lib/tmpfiles.d/var.conf:17: Failed to resolve group ‘utmp’: No such process
❯ cat group
root:x:0:
wheel:x:10:stepomaticc
stepomaticc:x:1000:
docker:x:953:stepomaticc
incus-admin:x:956:stepomaticc
libvirt:x:958:stepomaticc
In my humble opinion what Ubuntu does it to nicely suggest to user to unplug USB key after installation finished and before rebooting, to not get into the issue like in Blufin, after clicking on “Reboot” button I just waited and machine restarted and booted from USB key again. Then I hard shout down computer and unplug USB key and turn on computer again. Ubuntu way is more user friendly to users.
Probably yes, don’t create too large requirement for disk free capacity. User can have small disk for system and mounts another disk for documents. If you don’t install a lot of programs, small disk may not be a problem. Sure until is too small… we must calculate that image may increase over time and user will install flatpaks and store documents.
Probably good idea to be some parameter for distro specific configuration. Some maintainers may decide that there should be bigger disk, because they want for e.g. save 5 images instead of 2 or what ever they decide.
Ok we’re going to conclude testing now! Alright so while we were doing this Noel and Jason were still investigating how to fix Anaconda for F42 and they were able to do so! Bazzite saves the day once again!
So what we’re going to do is just have two sets listed on this page, one set of ISOs using the Anaconda installer, and one using readymade. Note that some of these URLs are still busted.
We’re going to default to anaconda on the website so that we can finish this quest and get some rest. Both sets will end up being automated so we’ll still be able to follow readymade progress, etc.
We were also able to get LTS builds in there too so we finally have an LTS that can come with flatpaks on the ISO, which removes a major blocker for it going GA. Since brew and Firefox are now publishing aarch64 binaries it also means that our ARM build will be really close to feature parity with amd64!
@j0rge, nice Anaconda installer is working fine again. I am looking at Blufin documentation and I think this is going to be pretty confusing for the user that did not anticipate in this new Blufin ISO testing.
There are few things that in my humble opinion could be done simpler:
I don’t want to tell you what to do …but in my humble opinion there is absolutely no reason from end-users point of view that there should be this double installer complication. I think we should follow KISS design principle. I know we are all exited about everything related to Blufin including new installer. But… for many users this is just too much overhead, you know like: “WTF two installers???”
Honestly i think this is pretty self explanatory:
Status
There are currently two sets of installation media. One using the Anaconda installer, and one using the Readymade installer.
We are currently defaulting to Anaconda and are experimenting with moving to Readymade in the future.
The website is the intended method for users to download Bluefin.
The direct ISOs are linked below for convenience:
The webpage downloads sections image picker is even more “KISS”.
As the webpage is propably the page where people are going to be downloading the ISO, its pretty cut n dry selection, without any talking about installers or what they use.
@inffy, I agree download page is fine.
In my previous post I was referring to the @j0rge’s link to Download documentation like this:
In my humble opinion from docs it is not clear WHY are there two installers.
I know what you were referring to, and also referred to it.
I think that page is more advanced users, people who have read for example this testing thread and “know” what is going on.
Also “normal” users don’t by default land on that page.
Over explaining everything can get messy too…
Right, most users will get their download from the website and not a page on the docs.
Would it help you and the core team to add a sentence in the Readymade section in order to invite people to share their experience with the experimental images inside this discourse channel?
Like everything else around here it’s all OSS, anyone can feel free to click edit on any page in the docs and send in a PR (the formatting is markdown, just like it is on here):
I agree. If things are stable enough, lets put a bow on it and move on.
